Security loophole in Private Channels?
We came across an interesting use case in our organization today. We have a Team and a private channel within that Teams team. Within the private channel a subsite was created. I am not an owner or member of the Team nor am I a member or owner of the private channel. However during creation of the subsite I was able to be invited with unique permissions to the subsite and I was successfully able to access it. After the initial creation of the subsite, our admin was not able to add or remove or effect any additional permissions on that subsite. Is this a loophole? I expected that without being a member of the private channel I would have absolutely zero access to any items associated with the private channel and site. Which has remained true (when I go to the private channel URL I get denied access) except that I do have access to this specific subsite. My instinct is that the reason permissions cannot be changed after the fact is that this is a genuine loophole and permissions weren't intended by Microsoft to be able to be granted at all on the subsite. This is due to the fact it is under the private channel and permissions should only be able to be changed via the admin UI or from the Teams application. Has anyone come across this in their work? Any guesses or explanations for why the subsite access would be initially available? Is this just genuinely a loophole in the permissions architecture?
Create a calendar for a private channel
Good evening everyone, I need to create a calendar for a private channel. I was hoping someone could provide me with some advice on the best way to accomplish this with OOB Microsoft technology. I was thinking of creating a group calendar and having a PowerApp / Flow add items to it from the team's channel. Would love to hear some other thoughts on this. Any information is appreciated, HydeSecond Generation of Private Channels Scales Up to New Heights
Boasting a 20-fold increase in scalability and a cloud mailbox to hold a channel calendar, Microsoft is giving Teams private channels a significant revamp in an update that will roll out in late September 2025. The new mailbox is the new home for compliance records for private channels, which means that Microsoft 365 retention policies need a review to make sure that conversations are retained as desired. https://practical365.com/teams-private-channels-2025/Private Channels Just Don’t Get Any Respect
Microsoft launched private channels in November 2019. A lot has happened since and private channels don’t really get much attention these days. That’s a pity because private channels can be very useful in the right situation. I rediscovered this fact recently when working through an issue with a university where private channels were the right answer. Like all technologies, happiness comes from choosing the right tool. https://office365itpros.com/2024/11/08/private-channels-no-respect/Message regarding Teams private channel being out of space
We have a Team site that is set up with the default 1 TB of storage. This site has at least one private channel. Today, the owners of that private channel received notification that their Team site was out of space. From the Admin console, I could see that it was only using 5% of the storage capacity, but when we look at the user's computer, we see a banner that notifies us that we need to free up space. We emptied the recycle bin (there were a few files in it, but no more than 15). Additionally, from the Teams client, the user (who again, is the owner of the private channel) saw a prompt to add space to the SharePoint site. After walking through both of those steps (emptying recycle bin and adding space to the site) the users were able to once again start modifying and saving the files in that channel. I know the private channels run under their own SharePoint sites. As an Admin, do we have a way to look at the storage for these channels? Is there any documentation on what this size quota is set to when a new private channel is created? I assume that your general channels will pull from the main Team site quota since the content all resides in the same SharePoint site. I was just surprised by this behavior and haven't been able to find documentation specifically on the private channel SharePoint site.
Possible bug with wikis in private channels
When adding a wiki to a private channel members of the channel can't see the wiki. Instead they get the following error message: "It looks like your sharepoint doesn't allow adding Wiki tabs. ...." If the link is opened in share point by the creator and shared then when other members go to that link they are told they don't have permission and can request it. Once requested and granted the wiki is viewable in teams. Anyone else had this?
