Microsoft 365 Group Expiration Policy: Staged Rollout, Renewal and Restore
How to enable Microsoft 365 group expiration without a deletion wave: capture the policy, close ownership gaps, pilot on selected groups, widen to all, verify dates, and switch off and restore safely.

In this guide
Table of Contents
Table of contents
To switch on the Microsoft 365The KBY LexiconMicrosoft 365Microsoft 365 is Microsoft's subscription suite of Office apps and cloud services such as Exchange Online, SharePoint, OneDrive and Teams, run on an Entra ID tenant.
group expiration policy safely, treat it as a staged change rather than a single toggle. Capture the current policy with Get-MgGroupLifecyclePolicy, find every Microsoft 365 group without an owner and set an alternate notification address, pilot the policy on Selected groups (up to 500), then widen ManagedGroupTypes to All. The key constraint is what happens on the first run: Microsoft documents that when expiration is first set up, any group older than the lifetime is set to 35 days until expiration unless it is renewed automatically or by its owner. A group that expires is deleted one day after its expiration date and can be restored for 30 days, a period that cannot be changed. The way back is to set ManagedGroupTypes to None and restore any group that has already been deleted.
#Context: why expiration needs a rollout plan
Expiration is turned off by default in every tenant. Microsoft positions it as a clean-up tool for unused groups and teams: an administrator sets a lifetime, groups that are in use renew themselves, owners of quiet groups are asked to renew, and groups nobody renews are deleted. When a group expires, almost all of its associated services go with it, including the group mailbox, the Planner plan, the SharePoint site and the team. Archived teams are included.
That makes expiration a governance control with a deletion at the end of it, and the first enablement is the riskiest moment. A tenant that has run for years without expiration usually holds many groups older than any sensible lifetime, so enabling the policy for all groups at once puts a large set of groups on a 35-day clock on the same day. Most will renew through activity. The ones that do not are the ones nobody is watching: groups with no owner, groups whose owner has left, and groups that hold content but see little day-to-day use. If you already restrict who can create groups, as described in restricting Microsoft 365 Group creation to an approved security group, expiration is the matching control at the other end of the lifecycle.
Licensing is a precondition. Microsoft states that configuring and using the policy requires you to possess, but not necessarily assign, Microsoft Entra IDThe KBY LexiconMicrosoft Entra IDA concise technical definition of Microsoft Entra ID: what it is, how it fits identity architecture, and where engineers must validate before change. P1 or P2 licences for the members of all groups the policy applies to.
#Architecture: one policy, three scopes and an activity signal
In Microsoft Graph the policy is a single groupLifecyclePolicy object. Only one exists per tenant, so you cannot give different groups different lifetimes. It has four properties:
groupLifetimeInDays: the number of days before a group expires and needs renewal. The admin centre offers 180 and 365 or a custom value, which must be at least 30 days.managedGroupTypes:All,SelectedorNone.alternateNotificationEmails: where notices go for groups without owners; separate several addresses with a semicolon.id: the read-only policy identifier that the update cmdlets need.
Each Microsoft 365 group carries two read-only timestamps that the policy drives: expirationDateTime, when the group is set to expire, and renewedDateTime, when it was last renewed. Both are returned by default and both are in UTC.
Renewal is activity-based. Documented actions that renew a group include viewing, editing, downloading, moving, sharing or uploading files in SharePoint (viewing a SharePoint page does not count), reading or writing a group message in Outlook, visiting a Teams channel, viewing a post in a Viva Engage community, and viewing, creating, editing or responding to a form. Renewal is not immediate: activity flags the group, and a group near expiry is renewed within 24 hours, around 35 days before it would expire. Owners of a renewed group receive no notice.
| Scope | What it covers | Documented limit or effect | Use it for |
|---|---|---|---|
| Selected | Only the groups you add to the policy | Up to 500 groups | A pilot with known, owned groups |
| All | Every Microsoft 365 group in the tenant | The 500-group limit does not apply | Tenant-wide rollout after the pilot |
| None | No group | Active groups lose their expiration date; groups already expired are not affected | Rollback |
The lifecycle a group follows once it is in scope:
Rendering diagram...
Two timing rules shape the rollout. First, on first setup, groups older than the lifetime get 35 days until expiration. Second, whenever you change the policy, the service recalculates every group’s expiration date from the date the group was created and then applies the new policy. The second rule means a later reduction in the lifetime can bring many expiration dates forward at once; that is an inference from the documented recalculation, so check dates after any change.

#Implementation: capture, pilot, widen
Use an account with the Groups Administrator role, which Microsoft lists as able to create, read, update and delete the expiration policy and renew any group; prefer it to Global Administrator. The Microsoft Graph PowerShell cmdlets below are in the Microsoft.Graph.Groups module, and the policy cmdlets document Directory.ReadWrite.All as their delegated permission.
-
Connect and capture the current state. Confirm the tenant and save whatever policy exists before any change.
1Connect-MgGraph -Scopes "Directory.ReadWrite.All" 2Get-MgContext 3Get-MgGroupLifecyclePolicy | Tee-Object -Variable Before | 4 ConvertTo-Json | Out-File .\lifecycle-policy-before.jsonWith a policy in place the output shows its
Id,AlternateNotificationEmails,GroupLifetimeInDaysandManagedGroupTypes. No output means no expiration policy exists in the tenant. Stop if the context shows the wrong tenant. -
Find groups without owners. The policy sends their notices to the alternate address, and Microsoft advises against enabling expiration on a group whose owner has no valid email address.
1$m365 = Get-MgGroup -Filter "groupTypes/any(c:c eq 'Unified')" -All 2$m365 | Where-Object { -not (Get-MgGroupOwner -GroupId $_.Id) } | 3 Select-Object Id, DisplayName | Export-Csv .\ownerless-groups.csvAssign an owner to each group in the file through your normal process, or accept that its notices go to the alternate address. Before any group comes into scope, also check whether it carries duties beyond collaboration, such as group-based licensing; give such a group a named owner who watches renewal notices before you widen the policy to all groups.
-
Pilot on selected groups. If no policy exists, create one scoped to
Selected, then add each pilot group by object ID. The alternate address should be a monitored shared mailbox, not a person.1$policy = New-MgGroupLifecyclePolicy -GroupLifetimeInDays 365 ` 2 -ManagedGroupTypes Selected -AlternateNotificationEmails "groups-expiry@contoso.com" 3Add-MgGroupToLifecyclePolicy -GroupLifecyclePolicyId $policy.Id ` 4 -GroupId "<pilot-group-object-id>"If a policy already exists, do not create a second one: run
$policy = $Before, change its scope withUpdate-MgGroupLifecyclePolicy -GroupLifecyclePolicyId $policy.Id -ManagedGroupTypes Selected, then add the pilot groups with the sameAdd-MgGroupToLifecyclePolicycommand. Choose pilot groups that are owned and in active use, and include one quiet test group you own so you can watch the notification path end to end. -
Read the pilot’s expiration dates.
1Get-MgGroup -GroupId "<pilot-group-object-id>" | 2 Select-Object DisplayName, ExpirationDateTime, RenewedDateTimeEach pilot group should show a non-empty
ExpirationDateTimein UTC. A group older than the lifetime shows a date about 35 days out. -
Widen to all groups. After the pilot has run through at least one notification cycle without surprises, change the scope.
1Update-MgGroupLifecyclePolicy -GroupLifecyclePolicyId $policy.Id ` 2 -ManagedGroupTypes All -GroupLifetimeInDays 365 ` 3 -AlternateNotificationEmails "groups-expiry@contoso.com"Record the time of the change, the policy ID and the before file in your change record. Every Microsoft 365 group in the tenant now has an expiration date.
#Validation: prove the policy is doing what you intended
Read the policy back with Get-MgGroupLifecyclePolicy and compare it with the change record: one policy, the intended GroupLifetimeInDays, ManagedGroupTypes and alternate address. Then sample groups with Get-MgGroup and check that ExpirationDateTime is populated for groups in scope.
To see renewal working, watch the activity audit logs in Microsoft Entra ID, where Microsoft says administrators can list automatically renewed groups. For the quiet test group, expect owner emails 30, 15 and 1 days before expiry; for a team, the notice also appears in the Teams activity feed for owners. The email links to the group details page, where the owner can see when the group was last renewed and when it expires, and renew it. A successful manual renewal moves RenewedDateTime forward and extends ExpirationDateTime by the lifetime. An administrator can also renew a group from PowerShell with Invoke-MgRenewGroup -GroupId <id>, which documents Group.ReadWrite.All as its least privileged delegated permission.
#Failure modes
- An unexpected wave of expiry notices after enablement. Cause: groups older than the lifetime were set to 35 days until expiration. Response: identify the quiet groups that matter, renew them with
Invoke-MgRenewGroupand assign owners; if the volume is unmanageable, set the scope back toSelectedorNone. - Notices go unread. Cause: ownerless groups notify only the alternate address, and owners without a valid mailbox cannot act on the email. Response: monitor the alternate mailbox and fix ownership before widening scope.
- Delayed or missing emails. Microsoft states it never deletes a group before the last email is sent, so a notification delay does not shorten the clock; check ownership and the alternate address.
- Expiration dates moved after a policy edit. Cause: a policy change recalculates every expiration date from the group’s creation date. Response: compare a sample of dates with the before state after any edit.
- A restored dynamic group is empty at first. Cause: a restored dynamic group is treated as a new group and repopulated from its rule, which can take up to 24 hours. Response: wait, then check membership.
- You cannot add another pilot group. Cause:
Selectedholds up to 500 groups. Response: widen toAllrather than working around the limit.

#Security and compliance boundaries
The policy cmdlets document Directory.ReadWrite.All, which is broad, so run the change from a dedicated admin session and disconnect afterwards. Ordinary users can renew and restore groups they own, and can read the policy settings. User Administrators can restore any deleted Microsoft 365 group except groups assigned to the Global Administrator role.
Expiration does not override compliance holds. If a group’s mailbox is on legal hold, the mailbox is retained after the group’s data from apps such as Planner, SharePoint sites and Teams is permanently deleted 30 days after deletion, and an administrator can restore that mailbox with Exchange cmdlets. If a Microsoft Purview retention policy covers groups, conversations and files are kept in the retention container for the retention period and are recoverable through eDiscovery, although users no longer see the group. Expiration is not an archive: for a group you will no longer use but whose content you need, export it first using Microsoft’s guidance on archiving groups, teams and Viva Engage.
#Recovery: switching expiration off and restoring groups
To stop further expirations, set the scope to None. Microsoft documents that active groups then have no expiration date, but groups that have already expired are not affected, so restoration is a separate step.
1Update-MgGroupLifecyclePolicy -GroupLifecyclePolicyId $policy.Id -ManagedGroupTypes None
2Get-MgGroupLifecyclePolicyTo return to the exact earlier configuration, apply the values saved in lifecycle-policy-before.json with the same cmdlet; if that file is empty because no policy existed before, None is the earlier behaviour. Prefer this to Remove-MgGroupLifecyclePolicy, which deletes the policy object and its settings along with disabling expiration.
Restoring an expired group uses the Microsoft Graph PowerShell beta module, and the documented scope is Group.ReadWrite.All. First confirm the group is still in the deleted items, then restore it:
1Connect-MgGraph -Scopes "Group.ReadWrite.All"
2Get-MgBetaDirectoryDeletedGroup
3Restore-MgBetaDirectoryDeletedItem -DirectoryObjectId <objectId>
4Get-MgBetaGroup -GroupId <objectId>A group with documents, SharePoint sites or other persistent objects can take up to 24 hours to restore fully. Success looks like the group appearing in Exchange, its plan in Planner and its SharePoint content available again. Do not use Remove-MgBetaDirectoryDeletedItem or Delete permanently on the Deleted groups pane in the Microsoft Entra admin center during an incident: both remove the group permanently, and there is no way back.
#Operating group expiration after rollout
- Each week, review the alternate notification mailbox and the list of ownerless groups, and assign owners as people leave.
- After any policy edit, read the policy back and sample
ExpirationDateTimevalues against the change record. - Check the Microsoft Entra audit logs for automatic renewals so you know the activity signal is reaching the directory.
- Keep the restore runbook ready, including the 30-day window and the 24-hour completion time, and test it once on a deleted test group.
- Before shortening the lifetime, compare group creation dates with the new lifetime to see which expiration dates would come forward, because the recalculation applies to every group in scope.
The next safe decision after a clean pilot is whether to widen to All. Make it once ownership gaps are closed, the alternate mailbox is monitored, and an owner has seen and acted on a real renewal email.
About this page
Credited to
Dates
Published
Sources
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
Read-only scripts
- Windows devices with no BitLocker recovery key in Entra IDMicrosoft Entra ID, Windows
- Intune devices that haven't synced in N daysMicrosoft Intune
- Mailboxes forwarding to external addressesExchange Online
- BitLocker status of every volume on this PCWindows
Upcoming deadlines
- Intune moves to macOS 15 and laterQ4 2026
- SAP SuccessFactors provisioning: move from basic auth to workload identityNovember 2026
- Intune November release: JIT registration reminder at APNs renewal and automatic JIT for eligible tenantsNovember 2026
Explore KBY
The KBY Brief
A short email about twice a week with new runbooks, configuration traps and fixes from KBY Technologies.
SubscribeRelated Engineering Labs
Simulator
Intune Assignments
Check whether a user and device receive an Intune app or policy: group include and exclude rules, assignment filters in include or exclude mode, and app intent conflicts.
Calculator
Apple Update Dates
Work out when an iOS or macOS update becomes visible under a Declarative Device Management or legacy deferral, and when a DDM enforcement deadline forces the install.
Related articles
Enterprise IT Management
Restricting Microsoft 365 Group Creation to an Approved Security Group
How to limit Microsoft 365 Group creation to one approved security group with the Group.Unified directory setting, including state capture, validation from both sides, failure modes and a tested rollback.
Enterprise IT Management
Microsoft 365 Group Licensing: Fixing MutuallyExclusiveViolation
How to find the conflicting service plans behind a MutuallyExclusiveViolation, remove the overlap safely, and reprocess users in Microsoft 365 group-based licensing.
Enterprise IT Management
Bounded Enterprise IT Management Operations in Microsoft 365
A method for one bounded Microsoft 365 change: scope, baseline, pilot, observation and rollback, with evidence defined before action.
Enterprise IT Management
Microsoft 365 Conditional Access Blocking Legacy Auth: AADSTS53003
How to trace AADSTS53003 and legacy authentication blocks in Entra sign-in logs and remediate clients without weakening Conditional Access.
Discover more
Graduate Learning
Lexicon Definitions
Was this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Engineering insights, direct to you.
Receive the latest Systems Engineering tutorials, production guides, Engineering Labs and operational best practices.
Comments
Add a thoughtful note on Microsoft 365 Group Expiration Policy: Staged Rollout, Renewal and Restore. Comments are checked for spam and held for moderation before appearing.