Forum Discussion
Naming policy for O365 groups
Adam,
- If you purchased Enterprise Mobility + Security E3 then it does include Azure AD P1 https://www.microsoft.com/en-us/cloud-platform/enterprise-mobility-security-pricing
- You can still define a list of blocked words using this paraemeter CustomBlockedWordsList, we are deprecating this particular one: EnableMSStandardBlockedWords see this https://docs.microsoft.com/en-us/azure/active-directory/active-directory-accessmanagement-groups-settings-cmdlets
- As Drew mentioned to test this feature, you'll need to be logged in as a non-admin, from the documentation: "Selective administrators are exempted from these policies, across all group workloads and endpoints, so that they can create groups with these blocked words and with their desired naming conventions. " 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
- DeletedApr 26, 2018
cfiessinger I think we need some clarification here. We have read in multiple places that blocked words and naming policies are only available with AAD P1 licensing, except for this one link which also happens to be the most current.
"Using the Office 365 Groups Naming Policy preview requires Azure Active Directory Premium P1 licenses or Azure AD Basic EDU licenses for each unique user that is a member of one or more Office 365 groups."
AAD Basic comes with any version of an EDU tenant. I know other EDUs have been discussing this as well, and I believe have this stuff in place. Since this now appears to be an option we want to make sure this isn't too good to be true since there is only one piece of documentation that proves it.
https://docs.microsoft.com/en-us/azure/active-directory/groups-naming-policy
Can you confirm this is correct information in this doc?