Would like the ability to force ownership of a private channel
We had an issue where a private channel, before members were added the owner was removed from the team creating an ownerless channel. We are expecting these types of accidents to happen in the future, would like to add a way for an admin to force ownership of the channel.
Waiting eagerly on the "about two months from now" update from Apr 29 as we close in on 3 months.
Update - looks like you can now edit channel members from the admin console! Great news.
We have just discovered this problem while testing as we found some users have been using private channels.
This lack of ability to access a private channel as a system administrator is shocking. MS want people to trust in this platform but this current problem with private channels puts data at risk.
It needs resolving asap
Same issue here with attempting to make changes to a planner and inadvertently causing issues with a private channel.
I'm baffled that this was not something caught in testing. This seems pretty imperative to be able to recover a private collaboration channel when human error happens. How has Microsoft not planned for this issue?
German Garbuglia commented
Same issue today. We start playing with Planner. Trying to reduce the people with access to the Plan, we delete accidentally all members of the Team, a.k.a. all members on public or private channels. We don't care about the public ones but the private ones are ownerless and memberless. So, I tried powershell Teams beta module, Graph API, SharePoint permissions, etc. Always the same PrivateChannelOwnerNotFound... So right now there is no way to force ownership. Even if you are a Tenant admin.
Any update on getting this fixed. Im running into the same situation.
Frode Wika commented
We have made a service request with Microsoft for this issue and the latest information we got is that they are working on it and hope to have a fix for this in about two months from now.