What problem does it solve?
Setting up Microsoft Entra ID (formerly Azure AD) single sign-on for a Webiny project requires coordinating Entra app registrations, Cognito federation settings, attribute mappings, and multi-step deployments, which is error-prone without a clear guide.
Core Features & Use Cases
- Cognito Federation Setup: Add Entra ID as an OIDC identity provider through the
<Cognito /> extension in webiny.config.tsx with client ID, client secret, and issuer URL.
- Attribute and Role Mapping: Override default OIDC claim mappings and map Entra ID groups to Webiny roles and teams via a
CognitoIdpConfig implementation.
- Login Variants: Configure Entra-only login (hiding password forms), MFA, and multi-environment callback URLs for production deployments.
- Use Case: An enterprise team wants employees to sign into the Webiny admin panel with their Microsoft 365 accounts, with Entra ID groups determining each user's Webiny role.
Quick Start
Ask the AI to configure Microsoft Entra ID login for your Webiny project using Cognito Federation with your Entra app registration credentials.