SPO: URL namespace for intranet related sites

%3CLINGO-SUB%20id%3D%22lingo-sub-1240619%22%20slang%3D%22en-US%22%3ESPO%3A%20URL%20namespace%20for%20intranet%20related%20sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1240619%22%20slang%3D%22en-US%22%3E%3CP%3EHi.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20got%20vast%20amounts%20of%20SPO%20sites%20that%20were%20created%20long%20before%20we%20got%20around%20to%20event%20think%20about%20URL%20naming%20conventions.%20So%20for%20our%20upcoming%20Intranet%20sites%2C%20we're%20in%20the%20risk%20of%20getting%20hit%20by%20site%20URL%20name%20collisions.%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20have%20other%20SPO%20admins%20handled%20this%20-%20have%20you%20for%20example%20prefix'ed%20intranet%20related%20sites%20with%20something%20(f.eks.%20example%20%22i-%22%2C%20such%20that%20a%20site's%20URL%20will%20be%20%22i-%3CSITENAME%3E%22)%20in%20the%20URL%2C%20so%20that%20intranet%20related%20sites%20gets%20their%20own%20name%20space%3F%3C%2FSITENAME%3E%3C%2FP%3E%3CP%3EIs%20is%20possible%20to%20gather%20sites%20under%20some%20other%20base%20than%20%22%2Fsites%22%2C%20for%20example%20%22%2Fhome%22%20or%20%22%2Fsites%2Fintranet%22%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1240619%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1240813%22%20slang%3D%22en-US%22%3ERe%3A%20SPO%3A%20URL%20namespace%20for%20intranet%20related%20sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1240813%22%20slang%3D%22en-US%22%3EI%20think%20I%20have%20already%20answered%20this%20in%20the%20question%20about%20naming%20conventions%20for%20Hubs.%20To%20add%20some%20more%20things%20here%2C%20remember%20that%20you%20can%20rename%20a%20SPO%20Site%20Today%20using%20the%20SPO%20Admin%20Center%20or%20PowerShell%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1241657%22%20slang%3D%22en-US%22%3ERe%3A%20SPO%3A%20URL%20namespace%20for%20intranet%20related%20sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1241657%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F423531%22%20target%3D%22_blank%22%3E%40kenneho%3C%2FA%3E%26nbsp%3BThis%20is%2C%20of%20course%2C%20one%20of%20the%20reasons%20that%20governance%20should%20come%20first%20when%20you%20implement%20SharePoint%20Online!%20Naming%20collisions%20are%20inevitable%20if%20you%20don't%20plan!%20If%20you%20are%20not%20ready%20to%20build%20your%20intranet%20when%20you%20deploy%2C%20make%20a%20land%20grab%20for%20critical%20function%20names%20by%20creating%20communication%20sites%20for%20things%20like%20HR%2C%20Payroll%2C%20Benefits%2C%20IT%2C%20Finance%2C%20Legal%2C%20etc.%20This%20is%20what%20I%20do%20most%20often%20when%20I%20work%20with%20clients.%20Microsoft%20IT%20did%20it%20too.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBut%2C%20when%20the%20ship%20has%20already%20sailed%2C%20you%20need%20to%20come%20up%20with%20another%20strategy.%20In%20some%20cases%2C%20we%20have%20worked%20with%20the%20site%20owner%20to%20%22take%20back%20the%20name%22%20by%20migrating%20their%20team%20content%20to%20a%20new%20URL%20(usually%2C%20the%20culprit%20is%20a%20team%20site%20created%20for%20a%20very%20small%20number%20of%20people%20so%20the%20impact%20is%20small)%2C%20fully%20deleting%20the%20original%20site%2C%20and%20then%20re-using%20the%20URL%20for%20the%20intranet%20communication%20site.%20In%20other%20cases%2C%20we%20have%20had%20to%20come%20up%20with%20other%20URLs%20-%20different%20abbreviations%2C%20such%20as%20InformationTechnology%20or%20InfoTech%20or%20ITDept%20instead%20of%20IT.%20You%20could%20also%20use%20a%20prefix%20for%20the%20URL%20as%20you%20suggest%2C%20which%20could%20help%20users%20quickly%20identify%20whether%20a%20site%20is%20%22official.%22%20This%20approach%20will%20be%20hard%20to%20enforce%20if%20you%20allow%20self-service%20site%20creation.%20If%20you%20don't%20allow%20users%20to%20create%20intranet%20sites%20on%20their%20own%2C%20you%20may%20not%20need%20this%20type%20of%20naming%20convention%20because%20you%20will%20have%20more%20control%20over%20the%20site%20names.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

Hi.

 

We've got vast amounts of SPO sites that were created long before we got around to event think about URL naming conventions. So for our upcoming Intranet sites, we're in the risk of getting hit by site URL name collisions. 

How have other SPO admins handled this - have you for example prefix'ed intranet related sites with something (f.eks. example "i-", such that a site's URL will be "i-<sitename>") in the URL, so that intranet related sites gets their own name space?

Is is possible to gather sites under some other base than "/sites", for example "/home" or "/sites/intranet"?

2 Replies
I think I have already answered this in the question about naming conventions for Hubs. To add some more things here, remember that you can rename a SPO Site Today using the SPO Admin Center or PowerShell

@kenneho This is, of course, one of the reasons that governance should come first when you implement SharePoint Online! Naming collisions are inevitable if you don't plan! If you are not ready to build your intranet when you deploy, make a land grab for critical function names by creating communication sites for things like HR, Payroll, Benefits, IT, Finance, Legal, etc. This is what I do most often when I work with clients. Microsoft IT did it too.

 

But, when the ship has already sailed, you need to come up with another strategy. In some cases, we have worked with the site owner to "take back the name" by migrating their team content to a new URL (usually, the culprit is a team site created for a very small number of people so the impact is small), fully deleting the original site, and then re-using the URL for the intranet communication site. In other cases, we have had to come up with other URLs - different abbreviations, such as InformationTechnology or InfoTech or ITDept instead of IT. You could also use a prefix for the URL as you suggest, which could help users quickly identify whether a site is "official." This approach will be hard to enforce if you allow self-service site creation. If you don't allow users to create intranet sites on their own, you may not need this type of naming convention because you will have more control over the site names.