Expire Groups based on inactivity
Currently group expiration is based on an renewal date, example: require the owner to renew every 6 months.
However, the risk is if the owner doesn't see the email(s) (they get three) then the group could be removed even if there is legitimate group activity going on.
We would like the group expiration to be influenced by actual group activity, so if you see the email alias associated with a group actively being used then do not delete the group, but instead send the owner an email saying "are you still using this? We won't delete it, but we just want to make sure it is still needed."
So essentially the code would say: "if the group is actively being used, send the notification but do not delete the group unless the owner actively says it is okay to delete."
As we talked about at Ignite 2018, we’re working on adding activity-based group renewal.
Stay tuned as we get closer to be ready to release this.
Brian Coyne commented
Also confused on if this is rolled out in GA or not?
So what's the status on this? I had a meeting yesterday with Microsoft and one of the Teams engineers, he said it was available and I've come across several articles that it was now availble and on by default. But when I go to the Azure portal I see "Coming up: Office 365 groups will be auto-renewed if user activities are detected before expiration. Learn more about groups auto-renewal"
Which takes me to a 3 month old article with no mention of the general release date
Meanwhile this technet article tells implies it's already in place:
So do we have this feature or not?
Django Lohn commented
Combine this with multiple policies and then include (or do not add) specific groups to the applying policy and we are much more flexible: vote https://office365.uservoice.com/forums/286611-office-365-groups/suggestions/37979776-o365-group-expiration-date
Please consider this enhancement. Actively used groups should not be at risk of expiring due to missed emails.
Mark Simone commented
This is currently a big miss. It should really be based on a combination of the last activity of the underlying features (last chat activity, last sharepoint activity, last mailbox activity). Ideally, these should be options as well because something like a mailbox that may be receiving automated incoming email from the company should be optional as the last activity check.
Additionally, it would be nice to see the ability to have more than just a tenant policy for expiration. Admins should be able to create multiple policies that possibly leverage the classification labels for example.
This is particularly confusing for Planner which creates a group in the background.