Forum Discussion
Solved
Best way to delete orphaned private channel sites?
I was testing private channels in my business tenant, where I am the only member - along with 2 guest accounts. When I tried creating a private channel, it seemed to work - but when I tried to go to...
Use PowerShell, yes. And Teams leaving SPO sites behind when deleted is a well known "issue", or "feature", depending on who you ask 🙂
Perfect, thanks. In this case I'd say issue, since private channel sites are currently invisible in the admin center 🙂 Now off to test again to see why private channels aren't working in my tenant.
And in case anyone else is having issues with private channels, this is what I am seeing Dec 2, 2019..
It's only specific to my personal tenant, a Business Essentials. My work E3 works fine.
Happens in app, browsers, mobile.
Create PC, site is created. Sometimes with a storage quota of 26214400, sometimes with a quota of 1048576. That's a bit strange.
Go to files tab in Teams, get scenario errors (663, 439, 430) different each time.
Each time I go to files tab it creates a new SPO site. /sites/TEAM-CHANNEL for first, then -CHANNEL2, then -CHANNEL29, then -CHANNEL5, always a unique site name.
If I go directly to the site, I can see the document library, that looks fine, but the Members/Owners/Visitors permission groups aren't created.
Off to figure out how I can log a support call without a phone# - admin center only allows calls it seems. Maybe it's not fully deployed in my tenant....
It's only specific to my personal tenant, a Business Essentials. My work E3 works fine.
Happens in app, browsers, mobile.
Create PC, site is created. Sometimes with a storage quota of 26214400, sometimes with a quota of 1048576. That's a bit strange.
Go to files tab in Teams, get scenario errors (663, 439, 430) different each time.
Each time I go to files tab it creates a new SPO site. /sites/TEAM-CHANNEL for first, then -CHANNEL2, then -CHANNEL29, then -CHANNEL5, always a unique site name.
If I go directly to the site, I can see the document library, that looks fine, but the Members/Owners/Visitors permission groups aren't created.
Off to figure out how I can log a support call without a phone# - admin center only allows calls it seems. Maybe it's not fully deployed in my tenant....