Forum Discussion
O365 Groups Prefix Policy
The fix for this issue is deploying, and based on what customers have told us, the fix works when it's avaiable in thier region. If you PM your tenant details, we can look into whether the fix has reached your tenant.
@Eric, It was me who posted that feedback on uservoice (https://office365.uservoice.com/forums/286611-office-365-groups/suggestions/15008712-separate-naming-policy-for-o365-groups-and-dls).
We are having a problem with naming conventions which apply to DLs coming from on-prem AD. They sometimes get applied and sometimes don't. Moreover, the policy does not get applied to the email address (understandably so, because it will then invalidate the on-prem AD without a writeback). However, for O35 groups the it does get applied to email address but is inconsistent and many times it misses doing so. (I asked that on the erstwhile community also, but the responder gor confused between O365 groups and on-prem DLs: https://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365admin-mso_manage/o365-groups-naming-policy-ignores-email-address/897a8555-8dea-4096-b0b2-761fdd5372c2)
Moreover, The DLs / Security Groups created in on-prem AD are only done by an administrator but O365 groups when created by administrators does not get the policy applied. I don't see how that could be made consistent as Tony mentioned above. For on-prem DLs, administrators can manually follow a policy while creation, but for general users creating O365 groups we need to enforce a policy via automation (so as to avoid post-facto policy violations after documents and team sites etc are provisioned and populated).
Hence we need to differentiate the policies between on-prem DLs (or mail-enabled security groups) versus O365 groups only.
Any update on this ? We want to apply prefix for just the O365 groups
Hi.
I have the same issue....
You state that a fix is deployed, how do I know if I got this and what is the fix.
