Group Naming Policy


Now in preview


The only surprising thing I see is "Group naming policy requires Azure active directory Premium P1 license for unique users that are members of Office 365 groups." I interpret this to mean that the naming policy is only active when those creating groups have an Azure AD Premium P1 license or equivalent (like EMS 1). I think this is a bad decision, but we shall see what the market says.

9 Replies
The Azure AD Premium requirement was communicated last April in this blog post: & good feedback for our licensing specialists



I see:

*Azure Active Directory Premium is required.


at the bottom of the page. I am not sure that this effectively communicates the need for a premium license for a feature that is a) free in its Exchange distribution group naming policy equivalent and b) relatively easy to impose through PowerShell scripting. I know that the answer is that you're not licensing a single feature but a group of features, but still, this one sticks a tad.

See this:


And this:


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.

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...

The reason why the naming policy was working before is that Groups used the Exchange Online distribution group naming policy, which is free.

Why is a P1 license required to be able to apply a naming policy to the Office 365 groups?  That should be made available as part of the free Azure AD license.

Also discussed here:


If you don't like this, tell your local Microsoft representative and ask them to pass the message to the AAD licensing team.

I know this is realy sad...
I have a customer that was holding Groups creation before having proper governance "controls" for naming. I know that requirement for AAD P1 will be a blocker for them.
I guess they will just ditch th Groups feature and stick with the old-school aproach.
Bye bye modern workplace for them :'(

It sucks, to be sure. If complaints get you nowhere (and I fully expect MS to not change their mind about this) then consider whether other features of AAD P1 will be worth adopting for your organization, making the investment more worthwhile.