MSDN Documentation

Azure AD Deprecation Notice and Migration Guide

This document outlines the deprecation schedule and provides essential guidance for migrating from Azure Active Directory (Azure AD) to Microsoft Entra ID.

What is Happening?

Microsoft is consolidating its identity and access management offerings under the Microsoft Entra brand. As part of this initiative, Azure Active Directory (Azure AD) is being renamed and integrated into Microsoft Entra ID. This is primarily a branding and naming change, and the core functionality of Azure AD remains available within Microsoft Entra ID.

Key Dates and Milestones

• Current Status: Azure AD is now Microsoft Entra ID.
• Feature Parity: All existing Azure AD features are available in Microsoft Entra ID.
• New Features: Future innovations and new capabilities will be released under the Microsoft Entra brand.
• Deprecation Timeline: While Azure AD is now Microsoft Entra ID, specific legacy endpoints or older versions might have separate deprecation schedules. Always refer to the official Microsoft Entra documentation for the most up-to-date information on specific feature deprecations.

Why is this Change Happening?

This transition aims to:

• Simplify the Microsoft security and identity portfolio under a unified brand.
• Enhance the integration of identity and access management with other Microsoft security solutions.
• Provide a clearer path for customers to adopt advanced identity capabilities.

Impact on Your Services

For most users and applications, the transition to Microsoft Entra ID will be seamless. The underlying services and APIs remain the same. However, it is crucial to be aware of:

• API and SDK Updates: Ensure that any tooling, scripts, or applications that directly reference "Azure AD" in their code or configuration are updated to reflect "Microsoft Entra ID" where appropriate. This might involve updating client libraries or endpoint references if older, specific versions are being used.
• Documentation References: When referring to documentation, prioritize resources that mention Microsoft Entra ID to ensure you are using the most current information.
• Renaming in Portals: You will notice the name change reflected across the Azure portal and other Microsoft management interfaces.

Migration Steps and Best Practices

While a direct "migration" in terms of data transfer is generally not required for the naming change, here are recommended steps:

1. Review Your Current Usage: Identify all instances where Azure AD is referenced in your infrastructure, code, and documentation.
2. Update Applications and Scripts: If your applications or scripts directly use Azure AD SDKs or endpoints, check for any necessary updates or reconfigurations related to the name change. Most modern SDKs will handle this transition automatically.
3. Consult Official Documentation: Refer to the Microsoft Entra ID documentation for detailed guidance on specific services, APIs, and any potential impact on older configurations.
4. Educate Your Teams: Inform your development, operations, and security teams about the name change and where to find updated information.

Code Example: Authenticating with Microsoft Entra ID (Conceptual)

The following is a conceptual example of how an authentication flow might look. The actual implementation details will depend on the chosen SDK and language.

// Example using Microsoft Authentication Library (MSAL) for JavaScript
import { PublicClientApplication } from "@azure/msal-browser";

const msalConfig = {
    auth: {
        clientId: "YOUR_CLIENT_ID",
        authority: "https://login.microsoftonline.com/YOUR_TENANT_ID", // Use Microsoft Entra ID endpoint
        redirectUri: "http://localhost:3000",
    }
};

const msalInstance = new PublicClientApplication(msalConfig);

async function signIn() {
    try {
        const response = await msalInstance.acquireTokenPopup({
            scopes: ["user.read"]
        });
        console.log("Authentication successful:", response);
        // Proceed with using the access token
    } catch (error) {
        console.error("Authentication failed:", error);
    }
}