Forum Discussion
Planner access issues.
We faced a problem with access to Planner.
We disabled Groups and Plan creation in our tenant and during pilot fase we made groups using PowerShall with one owner. In some of this Groups owner can't access their Plan in Planner with error message:
"Oops, something went wrong ...
This plan is not available. The plan may have been deleted, or you no longer have access to it."
with correlation number, time and Planner version
Owner can add members and owners to Group and they don't have any problem with Planner.
First owner is listed in the Group but isn't a member in the Plan. When new owner add him in Plan access get back on track.
Did anyone face something similar? How to prevent from this bug?
I have a similar issue. I'm creating a group via Flow and despite being added as the group owner, when I go to the related Planner I get the same error with a (very useful^) correlation ID for my troubles.
If I go to the Group setting and then add myself as a member, I can then access the Planner board no problem but obviously this seems a bit backward i.e. Owner can't see the board but Member can.
My suspicion is that adding myself manually as a member gives everything a kick, and the mechanics behind the access to Planner is re-triggered (or something similar). This is just a guess of course!
Be interesting to see if anyone else has the same problem and if so, how they resolve it.
- I should add that I am using the Microsoft Graph to assign owners and members to Groups via Flow. Also, one thing I have also noticed is that when I try to add a 'New Plan', I cannot select the group that was created via Flow. Whether this is because I'm not recognised as an Owner or not (when I look at Group settings in Admin I am listed as an Owner), I've yet to determine.
Definitely some bugs in the Office 365 apps though which, given the rate of change, is expected I suppose. As long as Microsoft react quick enough, and the bugs aren't severe enough, it's ok. Joe Ayre Workthis really helped me, thank you!
- Did you open a ticket? I assume you have used the Azure AD policicy to prevent groups creation, don't you?
Not yet. Yes you are right we used Azure AD policy to prevent groups creation.
Same issue!
