Hi everyone,
I'm looking for advice from people who have experience with SharePoint Domain Renames and Microsoft 365 Copilot.
I recently renamed my SharePoint domain from:
oldcompany.sharepoint.com
to
newcompany.sharepoint.com
The rename completed successfully.
The strange thing is that SharePoint itself appears to be working, and Copilot can still access content in some situations.
What still works
- SharePoint sites exist and can be opened.
- Documents still exist.
- Search can find documents.
- Copilot can find SharePoint content if I explicitly ask for it in a chat.
For example, if I ask Copilot:
"Find the folder X"
or
"Show me the document Y"
Copilot is often able to locate the content and even read the document.
This makes me think the underlying data, permissions, and search index are still working.
What no longer works
The problem is the workflow around references.
Before the rename I could:
- Attach SharePoint files via "Cloud Files"
- Browse through SharePoint document libraries
- Navigate folders in the file picker
- Reference documents in notebooks
- Reference folders directly
- Use SharePoint content as context for Copilot conversations
Now I cannot.
When I choose:
Attach → Cloud Files
or try to create notebook references, I can no longer browse through the document libraries like I used to.
The websites themselves are visible.
The document libraries and folder navigation are not.
This completely breaks my workflow because I can no longer select documents and folders as context for Copilot.
Interesting clue
One of the broken file picker links contains something similar to:
Plain Text
https://newcompany-my.sharepoint.com/...
listurl=https://oldcompany.sharepoint.com/sites/ProjectSite/...
The old SharePoint domain still appears inside the URL.
That makes me wonder whether:
- the File Picker
- notebook references
- folder references
- Copilot's SharePoint integration
are still using old cached URLs from before the rename.
Additional observation
This is what confuses me:
Copilot can still find and read documents when I ask directly in chat.
So the content appears to exist and be searchable.
However, the UI components used to browse libraries and attach files no longer work correctly.
Because of that, this does not feel like a typical permission issue or a broken search index.
It feels more like a broken reference/navigation layer.
My questions
Has anyone experienced this after a SharePoint Domain Rename?
Specifically:
- Did it eventually fix itself?
- Was Microsoft Support required?
- Is there a way to rebuild File Picker references?
- Is there a way to refresh notebook and SharePoint library references?
- Are these old URLs cached somewhere?
- Is this a known side effect of a Domain Rename?
- Or am I better off abandoning troubleshooting and rebuilding the tenant?
At this point I'm trying to figure out whether this is:
"wait a few days and Microsoft catches up"
or
"you'll waste days of your life chasing this and should rebuild instead"
Any experiences would be greatly appreciated.
Thanks!