Apr 06 2017 06:09 AM
Apr 06 2017 06:09 AM
Today, we are pleased to announce the release of the following features to help you manage Office 365 Groups: deletion recovery, retention policies and label management. We've also summarized recent enhancements to help admins manage group as well as key upcoming features in this blog post: https://aka.ms/groupsupdate
Have a question about Office 365 Groups administration? Ask Microsoft during our AMA at 9am PT on April 13, 2017. Join here: https://aka.ms/groupsama
Apr 06 2017 10:33 AM
Congrats on reaching yet another important goal. And congrats to the entire security and compliance team for delivering the unified CLP vision.
Apr 18 2017 06:10 AM
We really appreciate the efforts for enhancing group-governance!
Features for adding pre/suffix to OWA-groups requires AAD premium. We do have several services, apps and even domain controllers in Azure, but the AAD linked to our tenant is licensed with "basic" license. We use ADFS and AAD-sync to our directories so I believe we did like most, and simply created a tenant with AAD included :)
Our problem is that our users (employees and students) label OWA-groups with department names etc. These names have a high probability of being used by exchange in the future, since all addresses created on our federated domain, also gets an onmicrosoft-address (naturally). Example: If a student creates a group called “Sales”, we have a problem… :smiling_face_with_smiling_eyes:
Two ways to solve this: we could add a new non-federated domain (won't work with federated domains) and add groups to that domain, but we rather avoid this. Or we can add a pre/suffix to the group, but that requires AAD premium.
Are there any other options? We could create a list of banned names, but there are some creative people at our university ;)
This is the one small issue we face now with groups (and therefore Teams, Planner, Modern Sites etc). Not a huge problem today, but it might be in the future. For us it looks like an AAD Premium subscription is the way to go, but that is one hefty price when including all our students. If anyone could point us in the right direction on this, it would be much appreciated!
Apr 18 2017 08:19 AM
Apr 23 2017 11:01 PM
I've enabled, and then disabled+deleted a retention policy.
Ever since I'm having issues with affected SharePoint Sites.
I can no longer delete folders with content in them, Error: You have to delete all the items in this folder before you delete the folder.
Cannot delete subsites of affected sites, error: Sorry, something went wrong. This site cannot be deleted because it is on hold for eDiscovery.
We don't have any other retention policies active, or any eDiscovery cases that should affected the sites.
Any ideas what is happening here?
Apr 24 2017 01:18 AM
Great group-governance feature. Like what you guys are doing on these topics!
Apr 24 2017 09:25 AM
Not sure what the issue is, my recommendation is to contact support to get this adressed.