You are backing up Entra ID….right?

In a similar style to my previous M365 backup post (yet-another-m365-backup-blog/) this isn’t just a re-write of other posts BUT..........

What would happen if you didn’t have your Users or Groups, your Enterprise App registrations, MFA configurations etc etc…?

It got me casting my mind back to when we only really had the option of on-premise infrastructure, and probably used Active Directory for Identity and access management, and I can’t remember a time where I saw an environment that didn’t at least have a read only domain controller, probably powered down and kept safely (i.e. Air gapped) as a recovery mechanism. Much like a two tier or three tier AD PKI hierarchy where you would have Root CA’s and Intermediate CA’s offline protecting private keys against compromise. Most likely though the DC’s in their infrastructure were backed up on a routine basis, onto separate storage and were kept for a business determined retention period. If a restore was required, it was relatively simple, restore the DC, or restore the object from the backup platform and continue business as usual.

Whilst they are two very different services, IMO the same requirements apply to Entra ID. You need to be able to respond to outages, compromises and misconfigurations and ease and speed of recoverability is absolutely key. Of course you need coverage to recover users, groups, Role Assignments etc, but you almost certainly need to be able to recover Audit logs, your enterprise applications and app registrations, Intune configurations, MFA settings and BitLocker key protectors as well!

Alongside all of that, you want these recovery points stored immutably, securely and true backup requires a separate logical infrastructure, so stored in a separate infrastructure than the one its protecting!

Dataplanet have the solutions needed to protect your Identity services - reach out for a free demo, or visit our microsite - https://entraid-backup.co.uk/