SMSMC Blog

Microsoft's Seven-Day Safety Net for Deleted Identities

Microsoft Entra's new Hard Deletion Protection gives seven days to recover a deleted account, group or app identity. What it does, what it doesn't, and the recovery plan you still need.

By Jim Venuto

Key takeaways

  • A new safety net arrived. Microsoft Entra’s Hard Deletion Protection, now in preview, blocks the permanent removal of a deleted identity for seven days, giving you time to recover from an accidental or malicious deletion.
  • It does not stop the deletion itself. The account, group or app still goes inactive the moment it is soft deleted, and anything that depends on it can break right away. The protection only buys you recovery time.
  • It is a one-way switch, and it is cloud-only. Once you turn protection on for an object you cannot turn it off, and it does not cover users synchronized from your on-premises Active Directory.
  • A feature is not a plan. Break-glass accounts, offboarding discipline, restricted deletion rights and tested recovery still do the heavy lifting. This is one more layer, not the whole wall.

A few years ago I watched a 40-person firm lose access to its main line-of-business application on a Friday afternoon. Not to ransomware. Not to a breach. An IT contractor was cleaning up “unused” accounts in Microsoft 365 and deleted a service identity that an integration quietly depended on. The app stopped authenticating. Nobody could say exactly what the deleted object had been connected to, because no one had written it down. They spent the weekend rebuilding the connections by trial and error.

That story is ordinary. The most expensive identity incidents I see at small businesses and local government offices are not dramatic attacks. They are a wrong click, a rushed offboarding, or a departing administrator with too much access and a grudge. Your Microsoft 365 directory is the keys to the entire building: every login, every mailbox, every app connection. Until recently, if the wrong key got thrown away and then purged, you were rebuilding from memory.

Microsoft has now closed part of that gap, and it is worth understanding both what changed and what did not.

What Microsoft actually shipped

Entra already kept a deleted object in a “soft deleted” state for 30 days, during which an administrator could restore it. The catch was that someone could permanently delete the object inside that window and end the recovery chance early.

The new capability, Hard Deletion Protection, blocks that permanent removal for the first seven days after an object is soft deleted. If someone deletes a protected account and then tries to purge it, the purge is refused until the week is up. Restore the object and the protection comes right back with it; delete it again and a fresh seven-day clock starts.

A few specifics that matter for how you would actually use it:

  • What it covers: cloud-only users, cloud-only groups, applications and service principals. Users synchronized from on-premises Active Directory are not supported.
  • It protects, it does not prevent. The object still goes inactive on the first (soft) deletion, which can disrupt dependent services immediately. Hard Deletion Protection is about recovery, not prevention.
  • It is one-way. Protection cannot be disabled once enabled. If you protect something by mistake, the only way to remove it is to soft delete it and wait out the seven days.
  • The housekeeping. You need the Microsoft Entra Backup Administrator role, you can protect up to 20 objects of a single type per operation, enabling it is written to the audit log, and there is no extra license required for the currently supported object types.

It is in preview, so treat it as something to pilot deliberately rather than switch on across your whole tenant this afternoon.

Why this is the right risk to worry about

Owners tend to picture the external hacker. But identity directories fail far more often from the inside, and the consequences are just as serious:

  • The offboarding that goes wrong. Staff turnover means accounts get deleted every month. Delete the wrong one, or one that an automated process depends on, and you have created an outage you may not immediately understand.
  • The forgotten machine identities. Applications and service principals are the identities nobody remembers until they break. They hold permissions, they run integrations, and they rarely appear on anyone’s mental map of “important accounts.”
  • The departing administrator. The person with the keys on their way out the door is a scenario every small business should plan for and most never do.

A deleted-and-purged cloud identity is not a quick restore. Microsoft is explicit that its Backup and Recovery tooling cannot bring back a hard-deleted object; it has to be recreated and reconfigured, with new identifiers and access relationships rebuilt from scratch. That is the Friday-afternoon weekend I described, and a seven-day pause on permanent deletion is a genuinely useful guardrail against it.

What a feature like this cannot do for you

Here is where experience makes me cautious about any single toggle. Hard Deletion Protection narrows one failure mode. It does nothing about the broader discipline that actually keeps an identity system recoverable. If you want this to be more than a checkbox, pair it with the basics:

  • Break-glass accounts. Two cloud-only emergency administrator accounts, excluded from your normal conditional access, stored offline, and tested. When identity goes wrong, this is how you get back in.
  • Restrict who can permanently delete. Use Entra’s protected actions to put an extra authentication requirement in front of sensitive operations, including permanent deletion of directory objects. Fewer people should be able to purge an identity than can create one.
  • Watch the deletions. Track deletion events in the audit logs and export them to a monitoring platform so a mass deletion sets off an alarm instead of a mystery.
  • Write down the dependencies. The reason that 40-person firm lost a weekend is that no one had documented what the service identity connected to. Knowing which apps and integrations depend on which identities turns a crisis into a lookup.
  • Offboard on a checklist, not from memory. Disable first, confirm nothing breaks, then remove. A disciplined removal process prevents most of the accidents this feature is designed to recover from.

Microsoft publishes solid recoverability guidance for the rest of the picture, and it is worth a read before you decide this one feature has you covered.

The honest summary

Hard Deletion Protection is a good, overdue addition, and if you run Microsoft 365 you should plan to pilot it on your most critical cloud-only accounts and app identities. But it covers a slice of the risk: cloud-only objects, a seven-day window, recovery rather than prevention. The accounts synced from your on-premises directory, the outage the moment something is deleted, and the question of who should be able to delete at all are still yours to manage.

The businesses that recover gracefully from an identity mistake are not the ones with the newest feature switched on. They are the ones who decided, before anything went wrong, how they would get back in, who is allowed to pull the trigger, and what breaks when an identity disappears.

If you are not sure how your Microsoft 365 or Entra environment would survive a wrong deletion, that is exactly the kind of gap a short assessment surfaces. Book a free 30-minute call and we will walk through your break-glass and offboarding plan together. Finding the gap on a quiet Tuesday is a great deal cheaper than finding it on a Friday afternoon.

Sources