Forum Discussion
Office 365 Group Naming policies and Azure Active Directory
Looks like the naming policy is doing a pretty good job in my tenant...
Office 365 Naming Policy in action
I started digging into Groups management today, and I stumbled across this thread, as well as this article: https://support.office.com/en-us/article/Office-365-Groups-Naming-Policy-6ceca4d3-cad1-4532-9f0f-d469dfbbb552
The article has no date, but judging from the above replies, I'm guessing it's recent. Has anybody tried this yet? It provides instructions on setting naming policy and custom blocked words, as well as includes all of the applications in which the naming policy will work. There are some limitations that puzzle me though:
"Power BI workspaces aren't compliant with naming policy yet. Power BI workspaces created in your organization with naming policies will fail."
My company utilizes PowerBI. The clause above indicates that I will, therefore, not be able to implement any group naming policies on our Azure tenant, because if I do, PowerBI workspaces will fail. Am I interpreting this correctly? Is there a way I could instead isolate PowerBI from the naming convention policy?
Just confirmed that the solution outlined by Tony Redmond does work as expected. There are a number of other similar support articles on the exact subject that are not correct in minute details. Reference: https://www.petri.com/office-365-groups-naming-policy
Could you cite an authority for the statement that the Azure AD Naming Policy has been deprecated? I wrote about it in January https://www.petri.com/office-365-groups-naming-policy and it seems in rude good health still.
I fear that you are mistaking the distribution group naming policy that is in EAC. This only applies to distribution groups whereas the discussion here is about Office 365 Groups.
- Thanks Tony for the clarification. You may be correct. I think my testing may have not been sufficient after all. I reviewed your article and am testing. I have played with numerous similar recommendations without success. However, this may be related to impatience. I will report on results...
Looks like the naming policy is doing a pretty good job in my tenant...
Office 365 Naming Policy in action