Quantcast
Channel: Azure Active Directory forum
Viewing all articles
Browse latest Browse all 16000

Office 365 group naming policy: Compliance across workloads

$
0
0

We have enabled group naming policy for testing purpose, used prefix as string 'Grp' and user attribute [department] as suffix. However when we compared it with article (//docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/groups-naming-policy) on compliance across workloads found below things). I had provided feedback on this article but I was asked to post here on MSDN.

1.

Exchange Admin Center: Getting below error
"A prefix or suffix required by your organization is missing from one or more of the following group name, alias, email address. The suggested group name is 'Grp_Test_IT'. Please add the missing information and try again."
Do we need to add prefix and suffix details manually in the group name, they are not populating automatically?
2.
Microsoft 365 Admin Center:
Users don't have access to Microsoft 365 Admin Center. I could not create group having 'SharePoint, Exchange, Application, Privileged role administrator permissions'. Global admin can create group from Admin center but he is exempted from policy.
Which other roles can be used to create O365 group from Microsoft 365 Admin Center.
3.
Azure active directory portal:
User are not allowed to create Groups from Azure active directory portal. Needs permissions like SharePoint Admin.
4.
Planner:
□ Before O365 group naming policy enabled
® when owner edit the Group name, change in group name is not allowed for Group created before naming policy enabled
□ After O365 group naming policy enabled
® New Plan/O365 Group:
◊ Policy is reflecting for new Plan/Group created
◊ However when owner tries to edit the group name again, change in group name is not reflecting
® Existing Plan/O365 Group:
◊ Neither Policy is reflecting for existing plan/group name on editing nor change in group name is allowed and reflecting
5.
Yammer and Teams:
In Yammer and Teams, while editing group name, it accepts the same name for group as previous name(No change in name is required). But in other workloads like(OWA, Stream, SharePoint), group name needs to be changed at least by letter(remove or add).



Viewing all articles
Browse latest Browse all 16000

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>