Forum Discussion

Brent Ellis's avatar
Brent Ellis
Silver Contributor
Nov 18, 2016

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...
Office 365 Groups
Julio Lima's avatar
Julio Lima
Copper Contributor
Apr 29, 2019

jprimmer Guys, I had the same problem, the issue is that the error message leads you t another path. try to go to the Azure AD -> Groups-> and Delete the group from there, if it was deleted, delete from the Deleted Groups as well (purge them).

 

Also, delete from the Portal Office->Admin-> Groups (if it's there - should not).  Give 48 hours, the site will be automatically deleted. I was getting precisely the same policy message, and I had no more policy enabled . I  actually deleted all policies and gave it 7 days as requested by Microsoft and still nothing, same error... then I spoke with a Premier Support guy, he told me about this Office Groups issue, which I thought it had nothing to do and I would be wasting my time, but it did the work. After I removed the Office Groups for my SP and Teams sites, Voila!!! sites deleted automatically.

Jason Gould's avatar
Jason Gould
Brass Contributor
Apr 29, 2019

Julio Lima 

 

Here is an example. This sharepoint site won't delete. At one time it was associated with a O365 Group (if I remember correctly). The Group was deleted and is GONE, but the sharepoint site remains and CAN'T BE DELETED!

 

Here is the sharepoint site. Details of site even state it is no longer associated with a Group;

 

Here are the errors trying to delete;


 

Here you can see Admin Portal Groups;

 

Here you can see there is no longer a Group for it in Azure AD;

 

 

  • Julio Lima's avatar
    Julio Lima
    Copper Contributor
    Apr 29, 2019

    Jason Gould  I know is frustrating, trying to help here. I was also going crazy as well. These admin centers are now a maze to go thru, and they keep evolving.  hope you find the answer soon. 

     

    I am sure will be a non-sense PowerShell that will solve the issue.

     

    Regards,

     

    Julio