SOLVED

Naming Policy

%3CLINGO-SUB%20id%3D%22lingo-sub-52797%22%20slang%3D%22en-US%22%3ENaming%20Policy%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52797%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20list%20of%20group%20names%20used%20to%20be%20so%20neat%2C%20all%20starting%20with%20my%20set%20prefix%20to%20ensure%20everyone%20knew%20what%20they%20were.%20Now%20it's%20down%20right%20ruined%20by%20the%20combined%20efforts%20of%20Yammer%20and%20Teams%20users.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20release%20the%20AzureAD%20naming%20scheme%20components%20ASAP%2C%20and%20restore%20my%20sanity.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-52797%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%20Groups%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-56558%22%20slang%3D%22en-US%22%3ERe%3A%20Naming%20Policy%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-56558%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20there%20somewhere%20we%20can%20track%20the%20release%20of%20this%20or%20be%20notified%20when%20it's%20available%3F%20%26nbsp%3BI%20looked%20through%20the%20roadmap%20but%20didn't%20see%20anything%2C%20however%2C%20it's%20completely%20possible%20I%20missed%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52909%22%20slang%3D%22en-US%22%3ERe%3A%20Naming%20Policy%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52909%22%20slang%3D%22en-US%22%3E%3CP%3EHave%20been%20waiting%20this%20'forever'%2C%20we%20only%20can%20allow%20certain%20users%20to%20create%20groups%20until%20this%20gets%20put%20in%20place%20for%20the%20reasons%20above.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52902%22%20slang%3D%22en-US%22%3ERe%3A%20Naming%20Policy%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52902%22%20slang%3D%22en-US%22%3E%3Ca%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F353518%22%3E%40christophe%3C%2Fa%3E%20can%20you%20share%20with%20us%20why%20is%20taking%20so%20long%20to%20get%20this...at%20least%20a%20high%20level%20summary%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52895%22%20slang%3D%22en-US%22%3ERe%3A%20Naming%20Policy%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52895%22%20slang%3D%22en-US%22%3E%3CP%3EAnd%20I%20thought%20we're%20only%20going%20to%20get%20good%20news%20today%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52847%22%20slang%3D%22en-US%22%3ERe%3A%20Naming%20Policy%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52847%22%20slang%3D%22en-US%22%3E%3CP%3ESteven%20we%20hear%20you%20but%20unfortunately%20there%20is%20a%20bit%20more%20work%20to%20be%20done%20before%20we%20release%20this%20and%20latest%20ETA%20(subject%20to%20change!)%20is%20June.%3C%2FP%3E%3C%2FLINGO-BODY%3E
MVP

My list of group names used to be so neat, all starting with my set prefix to ensure everyone knew what they were. Now it's down right ruined by the combined efforts of Yammer and Teams users.

 

Please release the AzureAD naming scheme components ASAP, and restore my sanity.

 

 

5 Replies
best response confirmed by Steven Collier (MVP)
Solution

Steven we hear you but unfortunately there is a bit more work to be done before we release this and latest ETA (subject to change!) is June.

And I thought we're only going to get good news today :(

@Christophe can you share with us why is taking so long to get this...at least a high level summary

Have been waiting this 'forever', we only can allow certain users to create groups until this gets put in place for the reasons above.

Is there somewhere we can track the release of this or be notified when it's available?  I looked through the roadmap but didn't see anything, however, it's completely possible I missed it.

 

Thanks!