Event details
- Forrest_HApr 05, 2024Iron Contributor
Luke-PlannerPM How does your #4 answer work if Admins have restricted who can create Groups? We have purposely limited who can create Groups to prevent users from creating Redundant / Duplicate Teams when originally rolled out Teams. As described in the MS Article here
Does the backend service workflow do this as a privileged task or does it assume the user Sharing the Personal Plan has the permission to create M365 groups? or does it simply ignore the restriction?There has been a longstanding confusion on my part around the Personal Plans based on Rosters and users only being able to create them via Graph. It seems that earlier guidance was wrong. We have people creating Project Plans that are not mapped to groups and they no longer work here. Management of orphaned plans is becoming overwhelming. This getting complicated for me to follow. I believe that the terms "Project Plans" versus "Planner Plans" is part of the issue, especially when many articles talk about merging features between them.