SOLVED

Duplicate Team Names

%3CLINGO-SUB%20id%3D%22lingo-sub-325063%22%20slang%3D%22en-US%22%3EDuplicate%20Team%20Names%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325063%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20we%20are%20currently%20testing%20teams%20at%20my%20company%20and%20we%20discovered%20that%20there%20is%20nothing%20to%20stop%20Teams%20multiple%20teams%20being%20made%20of%20the%20same%20name.%20My%20question%20is%20what%20are%20the%20repercussions%20of%20this%20happening.%20Any%20information%20would%20be%20helpful.%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-325063%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325868%22%20slang%3D%22en-US%22%3ERe%3A%20Duplicate%20Team%20Names%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325868%22%20slang%3D%22en-US%22%3EYep!%20This%20is%20the%20case%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325857%22%20slang%3D%22en-US%22%3ERe%3A%20Duplicate%20Team%20Names%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325857%22%20slang%3D%22en-US%22%3E%3CP%3EBesides%20being%20a%20bit%20of%20pain%20when%20Teams%20have%20duplicate%20names%20there%20isn't%20anything%20bad%20that%20should%20happen.%20We%20as%20an%20organization%20in%20multiple%20regions%20did%20have%20to%20turn%20off%20the%20ability%20for%20any%20user%20to%20create%20a%20team%20and%20institute%20a%20naming%20convention%20to%20help%20mitigate%20this%20issue%20though.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20note%20that%20if%20two%20(or%20more)%20Teams%20have%20the%20same%20name%20the%20associated%20O365%20Group%20email%20and%20associated%20SharePoint%20Team%20site%20will%20be%20created%20with%20random%20numbers%20at%20the%20end.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20for%20example%20if%20you%20have%20a%20Team%20called%20Accounting%20and%20a%20second%20group%20in%20a%20different%20region%20creates%20a%20Team%20called%20Accounting%20that%20second%20O365%20group%20email%20will%20be%20called%20something%20like%20Accounting852%40sitename.onmicrosoft.com%20and%20the%20SharePoint%20site%20will%20be%26nbsp%3B%3CEM%3E%3CA%20href%3D%22https%3A%2F%2Fsitename.sharepoint.com%2Fsites%2Faccounting852%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsitename.sharepoint.com%2Fsites%2Faccounting852%3C%2FA%3E%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325115%22%20slang%3D%22en-US%22%3ERe%3A%20Duplicate%20Team%20Names%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325115%22%20slang%3D%22en-US%22%3E%3CP%3EThat's%20one%20of%20the%20reasons%20why%20some%20organizations%20opt%20to%20centrally%20manage%20team%2Fgroup%20creation%20-%20giving%20the%20end%20users%20the%20freedom%20to%20self-provision%20teams%2Fgroups%20is%20great%20in%20theory%2C%20but%20can%20easily%20get%20out%20of%20hand.%20Sadly%2C%20naming%20policies%20do%20not%20help%20with%20this%20particular%20scenario%2C%20although%20I%20see%20no%20reason%20why%20an%20option%20for%20this%20cannot%20be%20added%20as%20part%20of%20the%20policy%20configuration.%20Put%20it%20on%20UserVoice%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325072%22%20slang%3D%22en-US%22%3ERe%3A%20Duplicate%20Team%20Names%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325072%22%20slang%3D%22en-US%22%3EYou%20can%20manually%20or%20programmatically%20do%20checks%20on%20existing%20groupnames%20though%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325069%22%20slang%3D%22en-US%22%3ERe%3A%20Duplicate%20Team%20Names%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325069%22%20slang%3D%22en-US%22%3EThere%20is%20currently%20no%20control%20of%20having%20duplicate%20team%2Fgroup%20names.%20these%20are%20just%20the%20display%20names%20but%20the%20URL%20and%20groupmail%20etc%20gets%20another%20name%20behind%20the%20scenes..often%20The%20name%20with%20a%20number%20after%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1261614%22%20slang%3D%22en-US%22%3ERe%3A%20Duplicate%20Team%20Names%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1261614%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F271407%22%20target%3D%22_blank%22%3E%40Nick_Boyd%3C%2FA%3E%26nbsp%3Bif%20you%20interested%20in%20using%20a%20self-service%20process%20for%20your%20Teams%20provisioning%2C%20we%20developed%20a%20solution%20using%20a%20combination%20of%20PowerApps%2C%20PowerShell%20script%2C%20PowerAutomate%20and%20SharePoint.%20It%20solves%20the%20duplicate%20display%20name%20issue%20and%20retains%20the%20possibility%20of%20applying%20a%20naming%20convention%20and%20blocked%20words.%20Here%20is%20the%20link%20to%20the%20article%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Finsterswap.wordpress.com%2F2020%2F03%2F25%2Fhow-to-develop-microsoft-teams-self-service-app-to-replace-the-duplicate-display-name-limitation-in-the-teams-client%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Finsterswap.wordpress.com%2F2020%2F03%2F25%2Fhow-to-develop-microsoft-teams-self-service-app-to-fix-the-duplicate-display-name-limitation-in-the-teams-client%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

So we are currently testing teams at my company and we discovered that there is nothing to stop Teams multiple teams being made of the same name. My question is what are the repercussions of this happening. Any information would be helpful. Thanks!

6 Replies
Highlighted
Solution
There is currently no control of having duplicate team/group names. these are just the display names but the URL and groupmail etc gets another name behind the scenes..often The name with a number after
Highlighted
You can manually or programmatically do checks on existing groupnames though

Adam
Highlighted

That's one of the reasons why some organizations opt to centrally manage team/group creation - giving the end users the freedom to self-provision teams/groups is great in theory, but can easily get out of hand. Sadly, naming policies do not help with this particular scenario, although I see no reason why an option for this cannot be added as part of the policy configuration. Put it on UserVoice :)

Highlighted

Besides being a bit of pain when Teams have duplicate names there isn't anything bad that should happen. We as an organization in multiple regions did have to turn off the ability for any user to create a team and institute a naming convention to help mitigate this issue though. 

 

Also note that if two (or more) Teams have the same name the associated O365 Group email and associated SharePoint Team site will be created with random numbers at the end.

 

So for example if you have a Team called Accounting and a second group in a different region creates a Team called Accounting that second O365 group email will be called something like Accounting852@sitename.onmicrosoft.com and the SharePoint site will be https://sitename.sharepoint.com/sites/accounting852

Highlighted
Yep! This is the case
Highlighted

@Nick_Boyd if you interested in using a self-service process for your Teams provisioning, we developed a solution using a combination of PowerApps, PowerShell script, PowerAutomate and SharePoint. It solves the duplicate display name issue and retains the possibility of applying a naming convention and blocked words. Here is the link to the article: https://insterswap.wordpress.com/2020/03/25/how-to-develop-microsoft-teams-self-service-app-to-fix-t...