Forum Discussion
Solved
SharePoint Farm Shutdown & DNS Redirect
I am working on a migration project which involves migration of SP On-Prem farm to SPO. We are planning to shutdown the source On-Prem farm. If user has any URl's stored in favorite then the requirem...
- I suggest you de-scope that requirement.
If your old site is http://foo and you want it to now be https://foo.sharepoint.com, even if you get single sign on, migrate to Azure Active Directory or have some other federation in place, there can't be a way to get all links that pointed to and old location to a new location. I don't see this happening.
Sure with group policy you can change the default home page. But if an old URL was http://foo/sites/hr/sitepages/home.aspx and now its https://foo.sharepoint.com/sites/hr/pages/home.aspx, you'd have to map every single page. what happens if they're using a new communications site online, but have a team site on prem? What about a publishing site becoming a wiki site? You can't possibly map every URL.
People can post links under MyLinks web part. Their can be links in a links library. They can be hard coded on a page. They can be saved in someone's favorites, including edge, IE, chrome, firefox, or safari.
I would love to hear how anyone successfully did this. I don't see it happening.
But I am willing to learn how to solve this problem!
That is exactly the approach to take. As you can't do a simple DNS CNAME from a vanity URL to a SharePoint Online URL, you have to do a web redirect which unfortunately does introduce a new point of failure - but it's the only way to keep your vanity URL.