Forum Discussion
Group Naming Policy
MicrosoftThe 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.
The reason why the naming policy was working before is that Groups used the Exchange Online distribution group naming policy, which is free.
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...
Hi,
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.
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: https://www.petri.com/aad-licensing-groups-teams
If you don't like this, tell your local Microsoft representative and ask them to pass the message to the AAD licensing team.
