365 Group Deletion Policy
Currently an Owner of a group can delete that group - I'm aware soft-deletion is coming, but ideally we want to be able to stop users from deleting groups entirely. An Azure policy to specify who can delete groups would put power back with the IT Dept. This will allow us to empower users, but without the risk of them deleting groups and the content getting past the retention period and being permanently lost.
Thank you for your feedback. Please tell us more about how you would expect to use this.
Prevent accidental deletion on groups should be an option
I agree there is a gap here. It's great to be able to control who can create groups. It's also great that we can set an expiration policy. What's probably more critical than either of those is who can manually delete a group. Due to the potential consequences of deleting a group and the ease in which a group owner can do it...is pretty freighting! Let's say there is a group that has existed for a couple years and it is linked to Teams. One of the owners decides the team is no longer needed and just deletes it. Then a month later they decide to go to the SharePoint site to retrieve files...no mas. I don't think your average user understands all the relationships there so there should be the most control around deletion even more so than creation.
Since switching to Microsoft Teams our SP Teamsite owners are able to create teams based on their Sharepoint TeamSite. They decided they don't need the Team and delete it which allows them to delete the group which kills their access to their SharePoint teamsite. This needs to be fixed somehow.
Deletion of the group should be with the administrator not the with the site owner
Mergim Esati commented
I can't believe we're seriously discussing about whether or not this should be a feature in Office 365...
Come on, Microsoft, we're in 2019. We've seen plenty of incredible stories: Moon landing, we can cure many diseases and all that stuff, but we can't prohibit users from deleting their groups. Say what?
We just had an issue where one of our users deleted 3 of our groups after switching to a different department, thinking they were leaving the team. Either this, or separate locations for the delete option to prevent these accidents would've been greatly beneficial.
To complement this we would also like to be able to choose whether teachers (owners) are allowed or not allowed to manually add students (members) to Teams for Education when using Microsoft School Data Sync.
Obviously this should be a feature from the get go. If you allow any user to create groups - so that they have freedom to collaborate and create organic and innovative ways to do so - you cannot let them just create a group, work in it, and then destroy it's existance.
This is a MUST for any business implementation and not only should be able to be blocked at the tenant level, it should be configurable at the user level.
So that you can specify by group whether it can or cannot be deleted AND by user, who can or cannot delete his own groups.
We have been limiting our users to Exchange Online, Skype for Business, SharePoint, and OneDrive for almost 2 years while we wait for this important governance feature to be implemented. Even with the Retention policy capabilities for Groups and Teams, there is still important data that becomes unrecoverable when an Office 365 Group is deleted.
We can consider adopting Groups and Teams within our enterprise when either (A) Office 365 Groups can be fully recovered for up to 7 years or (B) deletion of Office 365 Groups can be restricted to administrators.
This is preventing our full adoption - from a business perspective, we need to manage the information life-cycle by controlling the 'archiving' and retention and final deletion. Without this control - we are unable to give users the Owner permissions which means the whole thing has to be mediated by IT and that defeats the purpose.
Surprised this isn't at the top of the list!
Daniel B commented
We may want to delegate managing the members of a department group without giving rights to delete the group. As a first step a tenant wide setting to control whether owners can delete groups, or just admins, would be a good start. In a second step this should be something that can be set per group. It makes sense in a agile environment where users can create groups for their initiatives or projects, but for some groups it needs to be managed more strictly.
Dominik Dünnebacke commented
Highly support this feature. It terrifies me that a user is able to delete an Office 365 group. This might make sense for user created groups for a specific use case (like projects) where the user has the authority to make the decision.
When using static groups for departments or subdivisions, this can highly affect productivity. Thus the right to delete groups should be manageable by IT dept.
There are some amazing things I can do, but it's both too easy to accidentally delete a group, and also terrifying there is no easy to way to undo/restore the action.
I'm also taking advantage of Dynamic Membership rules for some of my O365 Groups (integrating Teams/SharePoint in a holy triumvirate), and I would love to empower department/team owners with Owner rights to do interesting things, but deleting their groups is NOT one of them ! Some kind of toggle for that one permission would be enormously handy.
Absolutely this is necessary. It appears that even someone that is a Team Owner can actually delete the Office 365 Group and Team via Sharepoint. Even though is asks for confirmation, this potentially lends itself for someone intentionally or unintentionally deleting an entire Sharepoint site and documents, the O365 Group Mailbox, and the entire Team. Just as we are able to restrict Group Creation, it is even more so necessary to restrict the ability to delete a Group.
Paul Bullock commented
Provide a Powershell much like the Azure Templates for setting who can create groups but for deletion restriction or admin UI to choose who can delete Office 365 groups. Very surprised that this delete group feature does not respect retention rules.
Brian Zhang Larsen commented
We need this - especially as it is even possible to delete groups with retention policies applied!
Before we can allow our users access to Microsoft Teams, we need to be able to ensure recoverability of Group/Team content which complies with our organization's data retention requirements (7 years). If it's possible for an end-user (i.e. Group owner) to delete a Group and consequently the Group's content such that it's unrecoverable, that will not comply. Preventing Group deletion might enable us to roll out Groups/Teams/Planner.
I'm an O365 admin for a school district and just recently ran into this. A teacher was trying to delete some extra groups that she no longer needed and accidentally deleted a group created via SDS for Teams for EDU. I tried to restore the group and it would not let me, it was giving me an error. After a couple of days the group was recreated by SDS. It would be nice if teachers/group owners didn't have the ability to delete the group. We already limit who can create a group, we'd like only those that can create a group to be able to delete a group.
James Reed commented
Also add integration points to prevent deletion via Teams. We've had users delete Teams, not realizing the O365 Group was deleted. Expecting the reverse workflow as well.
yes agree, greatly needed!!