Forum Discussion
Brent Ellis
Nov 18, 2016Silver Contributor
Force delete Group Site Collection after Group Deleted?
I don't suppose there is a way to force delete a site collection after the group is deleted? I created a test group that happened to use the name that I now need to use. I deleted that group day...
jprimmer
Apr 05, 2019Copper Contributor
Jason Gould Did you get any resolution from Microsoft on this? Currently dealing with the exact same problem and they seem mystified by it :-/
Julio Lima
Apr 26, 2019Copper Contributor
Just went to the same issue. You need to delete the Office 365 groups in two places. If you delete online in the Admin Center->Groups, you still need to go inside Portal Azure and permanent delete the Groups there. Portal Azure ->Azure Active Directory -> Groups -> Deleted Groups -> Send them to SPACE :)
You give a day or two and the sites will be deleted. :)
This whole issue has nothing to do with ediscovery policies.. crazy!
- Jason GouldApr 26, 2019Brass Contributor
FYI, our tenant still has issues. I get an email every day telling me that they are waiting on the escalation team to offer some form of input. Every site says there is a compliance policy in place and can't be deleted. Doesn't matter what I do. All retention and label policies were deleted.
I'm pretty sure that somehow when I deleted an old retention policy (without disabling it first) that it somehow wasn't fully removed. It was a 7yr retention policy on email and sharepoint. Of course the policy doesn't appear in any powershell commands, but it's the only policy that I had previously and is the only logical explanation.
I've tried EVERYTHING. Nothing works and Microsoft still can't fix it.
- Julio LimaApr 26, 2019Copper Contributor
- Jason GouldApr 26, 2019Brass Contributor
My issue is different I suspect. I can delete the group out of Office365 Admin section. That also causes it to delete in Azure Active Directory. The issue I've been experiencing is that the Sharepoint site never gets deleted and can't be via the portal or powershell. It complains about compliance policy (when none exist).
And this "policy" gets applied to even newly created sites. I've disabled and deleted all retention policies. Tried to exclude sites from retention policies. Made sure there were no eDiscovery cases. And a bunch of other things. Nothing works. Microsoft can delete them for me, but that's not a solution.