Identity resilience glossary
Microsoft Entra ID
Microsoft Entra ID is Microsoft's cloud identity and access management service, formerly called Azure Active Directory. Organizations use it to authenticate identities and manage access to applications and resources. Its identity objects and settings include users, groups, application configurations, and access policies; it is a different service from Windows Server Active Directory.
Why it matters
Microsoft Entra ID helps determine who can use connected business applications and under what conditions. That makes tenant configuration part of everyday business operations. A group assignment or application setting can affect access even when the identity service itself is available. Teams need to understand which settings support important workflows and who is responsible for changing them.
Illustrative identity example
An application requires assignment, and a support group's members have no other assignment to it. An administrator removes that group by mistake. The affected employees can still authenticate to Entra ID, but new sign-ins to the application fail. The investigation identifies the changed assignment and its intended state. After correcting it, the team checks an affected employee's normal workflow.
How it differs from Active Directory
The former Azure Active Directory name can cause confusion. Microsoft Entra ID is not a hosted copy of an Active Directory domain controller. The services have different administration models and application integrations. Organizations can connect them through a hybrid identity design, but that does not make their objects, policies, or recovery procedures interchangeable.
Recovery considerations
Recovery planning should distinguish an unavailable service from an incorrect tenant configuration. Microsoft provides native recovery capabilities for supported objects and properties, with defined limits. Teams still need a documented known-good state, a record of important dependencies, and tested procedures for the scenarios they expect to handle. A successful configuration change should be followed by an access check.