Forum Discussion

MVP

Sep 20, 2017

Group Naming Policy

Now in preview https://support.office.com/en-us/article/Office-365-Groups-Naming-Policy-6ceca4d3-cad1-4532-9f0f-d469dfbbb552?ui=en-US&rs=en-US&ad=US The only surprising thing I see is "Group nami...

groups

cfiessinger

Microsoft

Sep 20, 2017

The Azure AD Premium requirement was communicated last April in this blog post: https://blogs.office.com/en-us/2017/04/06/whats-new-in-office-365-groups-for-april-2017/ & good feedback for our licensing specialists

Abhimanyu Singh

Iron Contributor

Sep 21, 2017

See this: https://office365.uservoice.com/forums/286611-office-365-groups/suggestions/15008712-separate-naming-policy-for-o365-groups-and-dls

And this: https://office365.uservoice.com/forums/286611-office-365-groups/suggestions/14479938-allow-creation-of-naming-policy-for-o365-groups

The naming policy was working before without AAD Premium. But it had niggling problems and were not separated between DLs synced from on-premise AD and cloud-only groups. Why this requirement of AAD Premium now? Is there something special with O365 Groups that this warrants a premium subscription? Doesn't matter if it was announced in April. The logic still stands.

TonyRedmond
MVP
Sep 22, 2017
The reason why the naming policy was working before is that Groups used the Exchange Online distribution group naming policy, which is free.
VasilMichev
MVP
Sep 21, 2017
That $20bn target puts some presure I guess :)

But joking aside, I would definitely love to see at least some of the features that are "locked" to AAD Premium licenses now become available at least for the E3/E5 SKUs, without requiring additional licensing...