Forum Discussion
Hello from the Office 365 Groups Engineering Team
Hi Jim - We have been unable to turn on Office 365 groups (BTW is this the authoritative name? I have heard other names) in our environment. One of the blockers was that we couldn't specify a group prefix (which would invite lots of name collisions in our environment) that's gone, but apparently Planner ignores it. My understanding (not sure how I aquired it) is that Planner uses Office 365 groups but it is provisioned in a manner that will ignore the group prefix that we have selected for Office groups. Is my understanding correct? That planner has a dependency on groups, but that it ignores the group prefix we fought hard and waited for? Thanks - Greg
Hi Gregory Frick. You are correct that Planner bypasses the naming policy because they currently use the msgraph api's that talk directly to AAD. AAD team is currently working on implementing the naming policy.
We implemented from our side (Exchange Online) as a way to give customers DL naming policy parity in a more expedient fashion. AAD must now implement this feature from their side so all workloads will create groups using the same naming policy.
- Thanks Jim Van Eaton. Do you know if the AAD Team has an ETA. @Brian Arkills