Adopting to Microsoft Teams - Naming Conventions / Metadata

%3CLINGO-SUB%20id%3D%22lingo-sub-331740%22%20slang%3D%22en-US%22%3EAdopting%20to%20Microsoft%20Teams%20-%20Naming%20Conventions%20%2F%20Metadata%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331740%22%20slang%3D%22en-US%22%3E%3CP%3EHello!!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20will%20be%20rolling%20out%20(already%20out%20for%20some%20parts)%20Teams%20to%20thousands%20of%20users.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20struggling%20with%20the%20pros%20and%20cons%20of%20having%20a%20naming%20convention%3A%3C%2FP%3E%3CP%3EE.g.%20Country_Department_Team%20name%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20created%20a%20sharepoint%20list%20%2Fform%20for%20users%20to%20request%20a%20new%20team%20to%20be%20made..and%20the%20IT%20Team%20would%20automatically%20create%20the%20team%20using%20a%20powershell%20script.%20Users%20would%20answer%20questions%20like%20their%20department%2C%20country%2C%20if%20its%20a%20private%20or%20public%20team%20and%20the%20team%20description%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20also%20thought%20about%20attaching%20a%20teams%20best%20practices%201-2min%20guide%20when%20users%20request%20a%20new%20team%20on%20our%20form%20which%20could%20be%20nice%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20we%20are%20not%20sure%20what%20the%20point%20of%20having%20this%20provisioning%20tool%20in%20place%20if%20users%20can%20just%20go%20into%20their%20teams%20settings%20and%20rename%20their%20team%3F%3F%3F%3F%3C%2FP%3E%3CP%3EThen%20isnt%20any%20form%20of%20tracking%20teams%20creation%20and%20who%20owns%20them%20gone%3F%20as%20the%20link%20to%20the%20teams%20name%20is%20gone.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20any%20best%20practices%20or%20tools%20to%20track%20whos%20created%20teams%2C%20the%20owners%2C%20last%20activity%2C%20and%20even%20duplicating%20teams%20names%20could%20be%20a%20major%20issue%3F%20Is%20this%20a%20big%20enough%20reason%20to%20have%20a%20provisioning%20process%20and%20stop%20thousands%20of%20teams%20being%20created%20in%20one%20day...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you!%20I%20welcome%20any%20other%20suggestions%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-331740%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdoption%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETeams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-331775%22%20slang%3D%22en-US%22%3ERe%3A%20Adopting%20to%20Microsoft%20Teams%20-%20Naming%20Conventions%20%2F%20Metadata%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331775%22%20slang%3D%22en-US%22%3EYou%20can%20track%20changes%20to%20Teams%20through%20the%20Audit%20log%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Faudit-log-events%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Faudit-log-events%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20mentioned%2C%20you%20can%20use%20the%20Security%20and%20Compliance%20Centre%20to%20track%20audited%20changes%20to%20Teams%20and%20email%20them%20to%20a%20mailbox%20or%20back%20into%20a%20Team%2Fthe%20Team.%20I%20don't%20know%20whether%20the%20audit%20log%20would%20track%20a%20renaming%20of%20an%20actual%20team.%20However%2C%20this%20can%20be%20easily%20tested.%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-331774%22%20slang%3D%22en-US%22%3ERe%3A%20Adopting%20to%20Microsoft%20Teams%20-%20Naming%20Conventions%20%2F%20Metadata%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331774%22%20slang%3D%22en-US%22%3E%3CP%3EDo%20you%20recommend%20we%20have%20a%20naming%20convention%20but%20is%20there%20anything%20to%20track%20teams%20and%20be%20more%20organised%20like%20I%20wrote%20in%20my%20original%20post%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20big%20con%20is%20simply%20to%20understand%20what%20is%20the%20actual%20point%20of%20having%20a%20naming%20convention%20if%20we%20wont%20be%20able%20to%20keep%20track%20of%20a%20team%20thats%20changed%20its%20name%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-331766%22%20slang%3D%22en-US%22%3ERe%3A%20Adopting%20to%20Microsoft%20Teams%20-%20Naming%20Conventions%20%2F%20Metadata%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331766%22%20slang%3D%22en-US%22%3EYes%2C%20and%20this%20too%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fadmin%2Fcreate-groups%2Fmanage-creation-of-groups%3Fview%3Do365-worldwide%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fadmin%2Fcreate-groups%2Fmanage-creation-of-groups%3Fview%3Do365-worldwide%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20said%2C%20you%20can't%20stop%20a%20Team%20owner%20renaming%20a%20Team%20but%20there%20are%20things%20like%20this%20you%20can%20do.%20If%20you%20restricted%20the%20Office%20365%20Group%20creation%2C%20applied%20the%20Office%20365%20group%20naming%20policy%20and%20when%20creating%20groups%20make%20users%20only%20Team%20members%20you%20could%20effectively%20stop%20them%20either%20creating%20or%20renaming%20Teams.%20This%2C%20however%2C%20may%20be%20a%20bit%20of%20an%20admin%20overhead.%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-331760%22%20slang%3D%22en-US%22%3ERe%3A%20Adopting%20to%20Microsoft%20Teams%20-%20Naming%20Conventions%20%2F%20Metadata%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331760%22%20slang%3D%22en-US%22%3E%3CP%3EDo%20you%20mean%20this%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fadmin%2Fcreate-groups%2Fgroups-naming-policy%3Fview%3Do365-worldwide%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fadmin%2Fcreate-groups%2Fgroups-naming-policy%3Fview%3Do365-worldwide%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20did%20read%20through%20this%20but%20not%20sure%20if%20the%20organisation%20would%20be%20completely%20aligned..%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-331754%22%20slang%3D%22en-US%22%3ERe%3A%20Adopting%20to%20Microsoft%20Teams%20-%20Naming%20Conventions%20%2F%20Metadata%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331754%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F252982%22%20target%3D%22_blank%22%3E%40testio2%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20are%20some%20recommendations%3C%2FP%3E%3CP%3E%26gt%3B%20Restrict%20Office%20365%20Group%20creation%2C%20which%20restricts%20users%20from%20creating%20new%20Teams.%26nbsp%3B%3C%2FP%3E%3CP%3E%26gt%3B%20Use%20the%20Security%20and%20Compliance%20Centre%20to%20track%20audited%20changes%20to%20Teams%20and%20email%20them%20to%20a%20mailbox%20or%20back%20into%20a%20Team%2Fthe%20Team%3C%2FP%3E%3CP%3E%26gt%3B%20Use%20Teams%20Analytics%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAt%20present%2C%20AFAIK%2C%20there%20is%20no%20way%20to%20prevent%20the%20re-naming%20of%20the%20Team%20as%20Team%20Owners%20have%20the%20ability%20to%20do%20this.%20You%20could%2C%20however%2C%20make%20it%20so%20that%20only%20IT%20are%20the%20Team%20Owners%20and%20the%20users%20in%20the%20Teams%20are%20members%20only.%20It%20may%20be%20more%20admin%2C%20but%20you%20would%20retain%20control.%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1110270%22%20slang%3D%22en-US%22%3ERe%3A%20Adopting%20to%20Microsoft%20Teams%20-%20Naming%20Conventions%20%2F%20Metadata%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1110270%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20researching%20this%20same%20topic%20as%20we%20are%20rolling%20out%20Teams%20to%20some%203000%20employees%20globally.%26nbsp%3B%20Unfortunately%2C%20I'm%20not%20finding%20much%20guidance%20either.%26nbsp%3B%20I%20did%20find%20this%20%3CA%20title%3D%22https%3A%2F%2Fharvard.service-now.com%2Fithelp%3Fid%3Dkb_article%26amp%3Bsys_id%3D4e738c1ddbcfb708dffdbc32ba96190e%22%20href%3D%22https%3A%2F%2Fharvard.service-now.com%2Fithelp%3Fid%3Dkb_article%26amp%3Bsys_id%3D4e738c1ddbcfb708dffdbc32ba96190e%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Epage%20by%20which%20Harvard%3C%2FA%3E%20published%20to%20its%20employees%20on%20their%20naming%20convention%20policies.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F252982%22%20target%3D%22_blank%22%3E%40testio2%3C%2FA%3E%2C%20It%20looks%20like%20you%20posted%20this%20in%20February%20of%20last%20year.%26nbsp%3B%20I'm%20assuming%20you've%20rolled%20out%20Teams%20since%20then.%26nbsp%3B%20Do%20you%20have%20any%20advice%20to%20share%20per%20naming%20Teams%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1262492%22%20slang%3D%22en-US%22%3ERe%3A%20Adopting%20to%20Microsoft%20Teams%20-%20Naming%20Conventions%20%2F%20Metadata%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1262492%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F431018%22%20target%3D%22_blank%22%3E%40AdamL842%3C%2FA%3E%2C%20if%20you%20have%20a%20strict%20Teams%20governance%20policy%2C%20you%20can%20include%20that%20in%20it.%20Just%20add%20this%3A%20%22Renaming%20Teams%20after%20it%20has%20been%20created%20through%20a%20self-service%20process%2C%20is%20prohibited%22.%20And%20then%20implement%20this%20solution%20to%20take%20control%20over%20duplicate%20display%20names%20that%20the%20Teams%20client%20does%20not%20currently%20have.%20You%20can%20tweak%20this%20a%20little%20to%20give%20you%20more%20control%20over%20your%20naming%20convention.%20Using%20the%20Teams%20client%20for%20creating%20Teams%20can%20be%20turned%20off%20for%20all%20users%20once%20you%20have%20this%20rolled%20out.%20%3CA%20href%3D%22https%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%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%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%3CLINGO-SUB%20id%3D%22lingo-sub-1262496%22%20slang%3D%22en-US%22%3ERe%3A%20Adopting%20to%20Microsoft%20Teams%20-%20Naming%20Conventions%20%2F%20Metadata%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1262496%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F252982%22%20target%3D%22_blank%22%3E%40testio2%3C%2FA%3E%2C%26nbsp%3Bif%20you%20have%20a%20strict%20Teams%20governance%20policy%2C%20you%20can%20include%20that%20in%20it.%20You%20could%20add%20something%20like%20this%3A%20%22Renaming%20Teams%20after%20it%20has%20been%20created%20through%20a%20self-service%20process%2C%20is%20prohibited%22.%20And%20then%20implement%20this%20solution%20to%20take%20control%20over%20duplicate%20display%20names%20that%20the%20Teams%20client%20does%20not%20currently%20have.%20You%20can%20tweak%20this%20a%20little%20to%20give%20you%20more%20control%20over%20your%20naming%20convention.%20Using%20the%20Teams%20client%20for%20creating%20Teams%20can%20be%20turned%20off%20for%20all%20users%20once%20you%20have%20this%20rolled%20out.%20%3CA%20href%3D%22https%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%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
Contributor

Hello!!

 

We will be rolling out (already out for some parts) Teams to thousands of users.

 

We are struggling with the pros and cons of having a naming convention:

E.g. Country_Department_Team name

 

We created a sharepoint list /form for users to request a new team to be made..and the IT Team would automatically create the team using a powershell script. Users would answer questions like their department, country, if its a private or public team and the team description

 

We also thought about attaching a teams best practices 1-2min guide when users request a new team on our form which could be nice

 

But we are not sure what the point of having this provisioning tool in place if users can just go into their teams settings and rename their team????

Then isnt any form of tracking teams creation and who owns them gone? as the link to the teams name is gone. 

 

Is there any best practices or tools to track whos created teams, the owners, last activity, and even duplicating teams names could be a major issue? Is this a big enough reason to have a provisioning process and stop thousands of teams being created in one day...

 

Thank you! I welcome any other suggestions :)

8 Replies
Highlighted

Hi @testio2

 

Here are some recommendations

> Restrict Office 365 Group creation, which restricts users from creating new Teams. 

> Use the Security and Compliance Centre to track audited changes to Teams and email them to a mailbox or back into a Team/the Team

> Use Teams Analytics

 

At present, AFAIK, there is no way to prevent the re-naming of the Team as Team Owners have the ability to do this. You could, however, make it so that only IT are the Team Owners and the users in the Teams are members only. It may be more admin, but you would retain control.

Best, Chris

Highlighted

Do you mean this? 

https://docs.microsoft.com/en-us/office365/admin/create-groups/groups-naming-policy?view=o365-worldw...

 

I did read through this but not sure if the organisation would be completely aligned.. 

Highlighted
Yes, and this too

https://docs.microsoft.com/en-us/office365/admin/create-groups/manage-creation-of-groups?view=o365-w...

As said, you can't stop a Team owner renaming a Team but there are things like this you can do. If you restricted the Office 365 Group creation, applied the Office 365 group naming policy and when creating groups make users only Team members you could effectively stop them either creating or renaming Teams. This, however, may be a bit of an admin overhead.

Best, Chris
Highlighted

Do you recommend we have a naming convention but is there anything to track teams and be more organised like I wrote in my original post?

 

A big con is simply to understand what is the actual point of having a naming convention if we wont be able to keep track of a team thats changed its name

Highlighted
You can track changes to Teams through the Audit log

https://docs.microsoft.com/en-us/microsoftteams/audit-log-events

As mentioned, you can use the Security and Compliance Centre to track audited changes to Teams and email them to a mailbox or back into a Team/the Team. I don't know whether the audit log would track a renaming of an actual team. However, this can be easily tested.

Best, Chris
Highlighted

I'm researching this same topic as we are rolling out Teams to some 3000 employees globally.  Unfortunately, I'm not finding much guidance either.  I did find this page by which Harvard published to its employees on their naming convention policies. 

@testio2, It looks like you posted this in February of last year.  I'm assuming you've rolled out Teams since then.  Do you have any advice to share per naming Teams?

Highlighted

@AdamL842, if you have a strict Teams governance policy, you can include that in it. Just add this: "Renaming Teams after it has been created through a self-service process, is prohibited". And then implement this solution to take control over duplicate display names that the Teams client does not currently have. You can tweak this a little to give you more control over your naming convention. Using the Teams client for creating Teams can be turned off for all users once you have this rolled out. https://insterswap.wordpress.com/2020/03/25/how-to-develop-microsoft-teams-self-service-app-to-fix-t...

Highlighted

@testio2, if you have a strict Teams governance policy, you can include that in it. You could add something like this: "Renaming Teams after it has been created through a self-service process, is prohibited". And then implement this solution to take control over duplicate display names that the Teams client does not currently have. You can tweak this a little to give you more control over your naming convention. Using the Teams client for creating Teams can be turned off for all users once you have this rolled out. https://insterswap.wordpress.com/2020/03/25/how-to-develop-microsoft-teams-self-service-app-to-fix-t...