SharePoint/ Teams Private channels - can no longer manage or create groups

[JC1231530]

Hello!

We have created many SharePoint/security in order to manage granular permissions to view or view/edit confidential information within SharePoint/ Teams Private channels. Over the last week, we've noticed that the ability to manage or create these groups has been taken away. This does not appear to impact standard channels, only security groups contained within private Teams channels.

Whenever we try to modify the membership of the groups that we have been managing in the past, the only option we have is "Actions" and the usual "New" option has disappeared.

How it used to be:

We have also lost the ability to create new SharePoint/security groups within private channels too.

I suspect this is a bug? We still have complete ownership of this SharePoint private channel so it doesn't make sense that we can't change existing groups that we have ownership permissions for.

Any guidance would be very much appreciated 🙂

Many thanks,

J

[#2]

Bumping for a response.

[#3]

Hi, I'm facing the same issue and have opened a Ticket in Microsoft, waiting for their response.

Hope it's clear what happened.

[#4]

I'm glad it's not only us.

If this function has been depreciated it will be enormously impactful for us and we will have to spend weeks transferring data to standard channels (as you can't convert private to standard). This also means having to create entirely new SharePoint groups and populating their memberships as groups do not transfer from private to standard channels, and visa versa.

[#5]

Bumping once more.

[#6 · Accepted solution]

This was a change implemented by Microsoft:

"(Updated) SharePoint channel sites - Temporary permissions editing
MC282480 · Published Sep 1, 2021 · Last updated Sep 23, 2021
Service
SharePoint Online

Message Summary
Updated September 23, 2021: In two weeks, the window for editing channel site permissions from SharePoint will close. Once this window closes on October 7th 2021, all channel site level permissions will need to be managed from within Microsoft Teams.

We recently provided guidance (June - MC261534) “SharePoint: Updates for Microsoft Teams connected team sites” about how to edit permissions for SharePoint team sites that are connected to a channel in Microsoft Teams.

In the post, we specified that the addition, removal, or the editing of permissions for a channel site would need to be done in Settings for the team in Teams.

To allow team owners more time to adjust to this change, we have temporarily enabled (for the first three weeks of September) users to continue to edit site permissions in the SharePoint team site. This will allow you to audit and remove permissions that have been added directly to the SharePoint site.
Key points:

This temporary update is available to all customers until mid-to-late September 2021.

We will alert you via a follow-up Message center post to announce when this window is closing.
How this will affect your organization:

Starting this week, team owners can edit site level permissions for the channel site for the next three weeks. After three weeks, team owners will need to manage channel site permissions in Settings for the team in Microsoft Teams.

What you need to do to prepare:

You do not need to do anything to prepare. This is a temporary change to the way site permissions will be managed for Teams connected experiences. In a few weeks, all channel site permissions will be managed in Microsoft Teams Settings."

Learn more:

Manage Teams connected sites: https://docs.microsoft.com/SharePoint/teams-connected-sites
Private channels in Microsoft Teams: https://docs.microsoft.com/en-us/MicrosoftTeams/private-channels
"A private channel site syncs data classification and inherits guest access permissions from the site of the parent team. Membership to the site owner and member groups are kept in sync with the membership of the private channel within Teams. Site permissions for a private channel site can't be managed independently through SharePoint."