Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 6/9 advisories · checked 14:23 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Entra: Soft deletion and restoration for cloud security groups

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

What the notice says

Microsoft’s text, safely structured

To help organizations recover from accidental or malicious deletions, Microsoft Entra is introducing soft deletion and restoration for cloud security groups. This feature allows deleted groups to be restored within 30 days, preserving their settings, ownership, and membership—reducing the need to rebuild access models from scratch.

When this will happen

  • Public preview: Rollout began in late in October 2025 and is expected to complete by early November 2025.
  • General availability (Worldwide): Rollout begins in late February 2026 and is expected to complete by early March 2026.

How this affects your organization

Who is affected:

  • Admins managing Microsoft Entra cloud security groups.
  • Users whose access is governed by security groups.

What will happen:

  • Deleted cloud security groups will enter a soft deleted state and appear in the Deleted groups blade.
  • During soft deletion:
    • Access granted via the group is removed.
    • The group is restorable for up to 30 days.
  • After 30 days, the group is permanently deleted.
  • Restoration recovers:
    • Group properties (name, description, type)
    • Settings (roles, policies)
    • Ownership and membership (assigned and dynamic)
  • Admin tools supported:
    • Microsoft Entra admin center
    • Microsoft Graph
    • PowerShell
  • Audit logs will capture deletion, restoration, and hard delete actions.
  • Users lose access via the group during soft deletion; restoring the group reapplies access based on the group’s previous configuration.
  • If a resource (for example, a SharePoint site, app, or policy scope) is protected by a soft deleted group, affected users immediately lose access via that group. If users had direct or alternate access paths, those remain unchanged.

What you can do to prepare

  • Identify critical groups:
    • Inventory and tag critical security groups that gate access to sensitive resources.
  • Update admin runbooks:
    • Add steps to restore a deleted group before attempting to rebuild it.
  • Test in a pilot (after preview reaches your tenant):
    • Create a test security group, grant it access to a nonproduction resource, soft delete, validate access removal, then restore and confirm access returns as expected
    • If you automate group management, validate your automation handles soft deleted objects and does not immediately hard delete them.
  • Communicate to helpdesk and resource owners:
    • Create guidelines on how to check deleted groups, how to restore, and when to escalate before recreating a group.

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Learn more

Links from the notice and their documentation checks

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 7 linked pages have not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 14:23 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current