Everything you need to run EIDGuard.

Task-oriented guides for setting up EIDGuard, restoring from a recovery point, and keeping an eye on your tenants day to day.

Getting started with EIDGuard: deployment and your first backup

Microsoft Entra External ID has no first-party backup. EIDGuard fills that gap: it continuously exports your tenant's configuration, users, groups, apps, Conditional Access, user flows, identity providers, branding, and more, into versioned recovery points you can compare against and restore from, all from a web dashboard.

Read article

Restoring from a recovery point

Every EIDGuard backup is a full recovery point. From the dashboard you can restore a single deleted object, one resource type, or the whole tenant, and every restore starts as a preview, so you always see exactly what would change before anything does.

Read article

Restoring a deleted user flow

A deleted user flow is one of the sharper failures in a customer identity tenant: sign-up and sign-in stop working for every application that referenced it, and Microsoft Entra has no recycle bin for user flows: they are hard deleted the moment they are removed. This article covers what breaks, how to restore the flow from a recovery point, and what to check before you call it fixed.

Read article

Backing up Conditional Access policies in Entra External ID

Conditional Access policies are one of the few things in Entra with a genuine safety net: delete one and you have 30 days to restore it from the portal. That safety net is narrower than it looks: it covers deletion but not modification, it expires, and a restored policy does not always come back the way it left. This article covers what Microsoft protects, where the gaps are, and how EIDGuard fills them.

Read article

Drift detection and daily operations

A backup you never look at is a hope, not a plan. EIDGuard's daily operations loop is designed so you'd notice, within a day, if your tenant changed unexpectedly or your backups stopped matching reality: scheduled backups, nightly verification against the live tenant, and a dashboard that surfaces anything off.

Read article

Does Microsoft back up Microsoft Entra External ID?

No. Microsoft keeps the identity platform running, replicated, and highly available, but it does not keep a restorable copy of your tenant's configuration. There is a limited 30-day recycle bin for a specific list of object types, and for everything outside that list, deletion is immediate and permanent. This article explains exactly where the line falls, so you can decide what you need to protect yourself.

Read article

What happens if an Entra External ID tenant is deleted?

Tenant deletion is the one failure with no safety net at all. Individual objects inside a tenant get a 30-day recycle bin; the tenant itself does not. Once deletion completes it is permanent, and neither your administrators nor Microsoft Support can bring it back. This article covers what deletion actually involves, why it is harder to do by accident than people fear, and what recovery looks like if it happens anyway.

Read article

Building a disaster recovery plan for Microsoft Entra External ID

Most disaster recovery plans cover databases, application servers, and storage, and stop at the identity layer, on the assumption that the cloud provider has it handled. For customer identity that assumption is only half true: Microsoft keeps the platform running, but your tenant's configuration is yours to protect. This article walks through building a recovery plan for an External ID tenant: what to protect, how fast you need to recover, and how to know the plan works.

Read article