Skip to main content

Delete Microsoft 365 Group

This article provides the finding of deleting a Microsoft 365 Group
in four different ways, as an owner of the Group or as a SharePoint Admin.

I did this investigation because I was not really sure how, if or when a Group and the associated SPO site is deleted.

If you're a SharePoint Admin you can also delete the Group from Microsoft 365 Admin Center or the SharePoint Admin Center.

You can also use the PnP or the Exchange Online PowerShell modules to delete (remove) a Group but that's a different discussion, how to get access.


Removed Group through Azure Portal Microsoft 365 Admin Center SharePoint Admin Center Role
  All Groups Deleted Groups Active Groups Deleted Groups Active Sites Deleted Sites SharePoint Admin Group Owner
Azure Portal             X X
AzureAD PowerShell             X X
Microsoft Admin Center             X N/A
SharePoint Admin Center             X N/A
Result 30 minutes after removal            
                 
Removed Group through Azure Portal Microsoft 365 Admin Center SharePoint Admin Center Role
  All Groups Deleted Groups Active Groups Deleted Groups Active Sites Deleted Sites SharePoint Admin Group Owner
Azure Portal             X X
AzureAD PowerShell             X X
Microsoft Admin Center             X N/A
SharePoint Admin Center             X N/A
Result the next day after removal            
                 
Not visible                
Visible                

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Error when running Register-SPAppPrincipal

Problem You get the error, "Cannot find an SPWeb object with Id or Url" , when trying to get the RootWeb of the SPSite object when you register a new app with the Register-SPAppPrincipal PowerShell cmdl. Register-SPAppPrincipal -NameIdentifier $appPrincipalIdentifier -Site $site.RootWeb -DisplayName 'ProviderHostedApp' The cause could be The user who is running the script is NOT a farm administrator. Fix the problem Add the user to the farm administrator group
Post a Comment
Read more

Enable PowerShell commandlets for SharePoint 2013 in PowerShell ISE

Open the PowerShell ISE and create a profile by running the following code: if (!(test-path $profile.AllUsersAllHosts)) { new-item -type file -path $profile.AllUsersAllHosts-force } Open the newly created profile with the following command: psEdit $profile.AllUsersAllHosts The profile will be open in the PowerShell ISE. Add the following code to the profile: (If the profile for some reason doesn't open then you can get it here: C:\Windows\System32\WindowsPowerShell\v1.0\profile.ps1) if ((Get-PSSnapIn -Name Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue) -eq $null ) { Add-PSSnapIn -Name Microsoft.SharePoint.PowerShell } Save the profile. Next time you open the PowerShell ISE you will have all the Microsoft.SharePoint.PowerShell commandlets.
1 comment
Read more

Can't read from source file or disk

When you are using Windows Explorer View in SharePoint you can't MOVE a file from one site to another if it's not directly below the root site, but you can copy the file. See the different scenarios below. Working Scenario Moving files between libraries within the same site. For example: "http://sharepointsite/sites/site1/site2/library1" (source) "http://sharepointsite/sites/site1/site2/library2" (destination) Moving files between libraries across different sites as long as they are directly below the root site. For example: "http://sharepointsite/site1/library1 (source) "http://sharepointsite/site2/library2 (destination) Non-working Scenario Moving files between libraries in sub-sites that are more than 1 level below the root site. For example: "http://sharepointsite/sites/site1/site1/library1" (source) "http://sharepointsite/sites/site1/site2/library2" (destination)
3 comments
Read more