azuread/eeid-toolkit
Microsoft Entra External ID implementation and migration guidance for AI coding assistants.
Implement Microsoft Entra External ID Microsoft-hosted authentication, redirect-based sign-in, and optional branding in an application. Invoke directly or from eeid-onboarding after Microsoft-hosted is selected.
Implement new Microsoft Entra External ID Native V2 authentication with in-app forms and the server-driven API in a public-client application. Invoke directly or from eeid-onboarding; not a V1-to-V2 migration skill.
Migrate an app's Microsoft Entra External ID native authentication from V1 to V2. Apps that call the native auth API V1 directly (raw HTTP such as /oauth2/v2.0/initiate) move to API V2 (authorize-challenge, HAL flows). Apps on the MSAL native auth SDK V1 methods (signIn, signUp, resetPassword) move to its V2 methods (signInV2, signUpV2, resetPasswordV2), in JavaScript single-page apps (CustomAuthPublicClientApplication, @azure/msal-browser) iOS or macOS apps (MSALNativeAuthPublicClientApplication), and Android apps (INativeAuthPublicClientApplication). Use when the user asks to migrate, upgrade, or move native auth to V2 or "the new native auth API", to assess or plan it, to change or approve the plan, to apply a reviewed plan, or to continue one in progress. Supports sign-in, sign-up, and self-service password reset, in full or per flow. Do not use for server-side MSAL for JavaScript, upgrading an MSAL package alone, Azure AD B2C migration, adding native auth to a new app, or browser-redirect MSAL flows.
Help choose between Web (Microsoft-hosted) and Native (Embedded native authentication V2) for Microsoft Entra External ID and delegate to the selected implementation skill.