entra1-1  Exercise 2: Translate the Old Runbook
===============================================

Source: Microsoft Learn, "New name for Azure Active Directory" (naming changes and
exceptions, and the glossary of updated terminology). Check that page again if you
need the latest wording.

THE ANSWERS
-----------
 1. "Azure AD tenant"
    Renamed -> Microsoft Entra tenant.

 2. "Azure Active Directory Premium P1"
    Renamed -> Microsoft Entra ID P1. (Same for P2. The licensing, pricing and
    capabilities did not change.)

 3. "AAD Connect"
    Renamed -> Microsoft Entra Connect (formerly Azure AD Connect). It syncs
    identities from on-premises Active Directory to Entra ID.

 4. "Azure AD Conditional Access"
    Renamed -> Microsoft Entra Conditional Access; on second use just
    "Conditional Access".

 5. "Azure AD B2C"
    NOT renamed. Azure AD B2C keeps its name. Microsoft's successor for external
    identities is Microsoft Entra External ID. (The page says Azure AD B2C was no
    longer available to buy for new customers from 1 May 2025.)

 6. "ADAL" (Azure AD Authentication Library)
    NOT renamed. It is deprecated; existing apps keep working but no security
    fixes are released. Microsoft's replacement is MSAL (Microsoft Authentication
    Library); apps should migrate.

 7. "Azure AD PowerShell"
    NOT renamed. Its cmdlets keep their "AzureAD" names. The module was planned for
    deprecation on 30 March 2024; the recommended module is Microsoft Graph
    PowerShell.

 8. "AD FS" (Active Directory Federation Services)
    NOT renamed. It is part of Windows Server Active Directory, which is not
    branded Entra.

 9. "Azure AD Graph"
    NOT renamed. It is deprecated, with no investment beyond security fixes. The
    replacement is Microsoft Graph.

10. "DirSync"
    NOT renamed, and no longer supported: it no longer works. The replacement is
    Microsoft Entra Connect.

HOW TO REMEMBER IT
------------------
Three rules cover most cases:
  - Anything that was "Azure AD <feature>" became "Microsoft Entra <feature>".
  - Active Directory (on-premises) and AD FS were never "Azure" anything, so they
    kept their names.
  - Developer-facing names (APIs, URLs, cmdlets, libraries) mostly did not change,
    which is why old names survive in code, scripts and some messages.

WHY THIS WORKS AS AN ANSWER
---------------------------
It separates "renamed" from "left alone", which is the question you'll actually
face when an old document, script or error message uses a name you don't
recognise. It also notes the deprecated items, so you don't send a client toward
something that is on its way out.