| Service limits and restrictions |
limits-quotas |
0.95 |
The page is a reference for Azure AD B2C service limits and restrictions and is expected to list concrete numerical limits, quotas, and constraints specific to the service, which qualify as expert knowledge not reliably known from training. |
| Error codes |
troubleshooting |
0.92 |
Provides a list of specific Azure AD B2C error codes and their meanings, enabling targeted diagnosis and resolution—classic troubleshooting reference. |
| ClaimsSchema |
configuration |
0.90 |
Reference for ClaimsSchema element, claim type definitions, and usage; includes specific attribute names and constraints not generally known. |
| ClaimsTransformations |
configuration |
0.90 |
Defines ClaimsTransformations element and supported transformation types, parameters, and usage patterns unique to B2C. |
| OAuth2 identity provider |
configuration |
0.90 |
Detailed reference for OAuth2 technical profiles including metadata, endpoints, and claim mappings—precise configuration schema. |
| Predicates |
configuration |
0.90 |
Details the Predicates and PredicateValidations elements, including validation rules and schema specifics that are highly product-specific configuration knowledge. |
| REST |
configuration |
0.90 |
Explains how to call REST APIs from policies with specific metadata (timeouts, headers, claims mapping)—detailed configuration reference. |
| Technical Profiles |
configuration |
0.90 |
Core reference for TechnicalProfiles element with many profile types and their specific parameters/metadata—central configuration schema for the product. |
| BuildingBlocks |
configuration |
0.88 |
Documents the BuildingBlocks XML element and its child elements, including names and semantics unique to Azure AD B2C. |
| OpenID Connect identity provider |
configuration |
0.88 |
Reference for OIDC technical profiles with parameters like response_type, scopes, and metadata unique to Azure AD B2C integration. |
| Phone number |
configuration |
0.88 |
Reference for phone number-specific transformations, including function names, expected formats, and parameters that are highly product-specific. |
| SAML identity provider |
configuration |
0.88 |
Reference for SAML 2.0 IdP technical profiles with entity IDs, endpoints, and claim mappings—product-specific configuration schema. |
| Self-asserted |
configuration |
0.88 |
Reference for self-asserted profiles (UI pages) with specific metadata (input fields, validation, display controls)—core configuration details. |
| TrustFrameworkPolicy |
configuration |
0.88 |
Reference for TrustFrameworkPolicy XML with element/attribute names and allowed values; highly product-specific configuration schema. |
| Boolean |
configuration |
0.86 |
Provides concrete examples of boolean transformation functions, including function names and parameter usage specific to the IEF schema. |
| Date |
configuration |
0.86 |
Shows specific date transformation functions and parameters in the IEF schema, which are product-specific configuration details. |
| DisplayControls |
configuration |
0.86 |
Reference for display controls with control types, metadata names, and configuration parameters unique to Azure AD B2C custom policies. |
| External accounts |
configuration |
0.86 |
Explains handling of alternativeSecurityIds and related transformations, with schema details unique to B2C social identities. |
| General |
configuration |
0.86 |
Contains concrete examples of general transformation functions with their names and parameter structures unique to Azure AD B2C. |
| Integer |
configuration |
0.86 |
Documents integer transformation functions and usage patterns specific to the IEF schema. |
| JSON |
configuration |
0.86 |
Provides examples of JSON transformation functions, including function identifiers and parameters unique to Azure AD B2C. |
| RelyingParty |
configuration |
0.86 |
Reference for RelyingParty element including DefaultUserJourney, token claims, and policy linkage—product-specific configuration schema. |
| SAML token issuer |
configuration |
0.86 |
Describes how Azure AD B2C issues SAML tokens and how to configure issuer technical profiles—detailed token and metadata configuration. |
| String |
configuration |
0.86 |
Provides concrete examples of string transformation functions and their configuration, which are unique to Azure AD B2C. |
| StringCollection |
configuration |
0.86 |
Contains specific transformation function names and parameter usage for string collections in the IEF schema. |
| UserJourneys |
configuration |
0.86 |
Reference for UserJourneys element with orchestration steps, order, and attributes—core configuration of policy flow. |
| CAPTCHA |
configuration |
0.84 |
Details CAPTCHA technical profile configuration, including provider settings and metadata—specific configuration schema. |
| CAPTCHA verification |
configuration |
0.84 |
Explains CAPTCHA display control configuration including setting.enableCaptchaChallenge and related technical profile metadata—concrete config parameters. |
| SSO session |
configuration |
0.84 |
Explains SSO behavior configuration per technical profile, including SSO mode values and session settings—product-specific configuration options. |
| Troubleshooting and error handling |
troubleshooting |
0.84 |
Explicit troubleshooting guide; typically includes common error messages, causes, and resolutions specific to B2C policies and user flows. |
| Claim resolvers |
configuration |
0.83 |
Lists specific claim resolver tokens (like {policy}, {culture}) and how to configure them in claims—detailed, product-specific configuration tokens. |
| JWT token issuer |
configuration |
0.83 |
Reference for JWT issuer technical profiles with token types, signing keys, and metadata—detailed config not covered by generic JWT knowledge. |
| Localization string IDs |
configuration |
0.83 |
Lists specific string IDs tied to api.signuporsignin content definition and how to reference them—fine-grained, product-specific configuration identifiers. |
| Microsoft Entra ID |
configuration |
0.83 |
Details configuration of Entra-based technical profiles with protocol-specific parameters and metadata unique to Azure AD B2C. |
| Phone factor |
configuration |
0.83 |
Details enrollment and verification of phone numbers via technical profiles, including specific claims and metadata—product-specific config. |
| About validation technical profiles |
configuration |
0.82 |
Describes how to configure validation technical profiles, including required attributes and how they are invoked—product-specific config behavior. |
| Collect logs using Application Insights |
troubleshooting |
0.82 |
Troubleshooting article that configures Application Insights for tracing policy execution, likely mapping specific error behaviors and diagnostic settings. |
| Configure tokens |
configuration |
0.82 |
Provides token lifetime and compatibility settings with specific parameter names, default values, and ranges for ID/access/refresh tokens unique to Azure AD B2C. |
| ID token hint |
configuration |
0.82 |
Describes configuration for accepting and validating inbound JWT hints, including metadata and claim mapping—product-specific configuration. |
| OAuth2 custom error |
configuration |
0.82 |
Explains how to define a special technical profile to return custom OAuth2 errors, with specific metadata and behavior—product-specific config. |
| Password complexity |
configuration |
0.82 |
Lists password policy settings (length, character classes, history, lockout) with specific parameter names and allowed values unique to Azure AD B2C. |
| Secure phone-based MFA |
best-practices |
0.82 |
Describes concrete mitigation strategies, workbook usage, and alert configurations in Log Analytics to detect and reduce fraudulent phone MFA usage. These are product-specific security best practices with actionable guidance. |
| SubJourneys |
configuration |
0.82 |
Describes SubJourneys element and how to structure orchestration steps, including allowed attributes and usage—detailed config. |
| Time-based one-time password (TOTP) |
configuration |
0.82 |
Details specific display control IDs, metadata, and claim wiring for TOTP-based MFA—configuration schema not derivable from general OAuth/TOTP knowledge. |
| 7 - Make HTTP call from custom policy |
integrations |
0.80 |
Explains RESTful technical profile configuration, HTTP endpoints, claims mapping, and request/response handling in B2C policy XML. These are product-specific integration patterns and parameters. |
| AD FS (OpenID Connect) |
integrations |
0.80 |
Custom policy-based OIDC federation with AD FS; includes metadata URLs, claim mappings, and policy XML elements specific to this integration. |
| AD FS (SAML) |
integrations |
0.80 |
Covers SAML federation with AD FS via custom policies; likely details SAML endpoints, certificate configuration, and policy attributes unique to Azure AD B2C. |
| Asignio |
integrations |
0.80 |
Partner integration tutorial with specific configuration steps, endpoints, and technical profile settings to use Asignio as an MFA method in B2C. Contains detailed integration parameters. |
| Azure AD B2C |
integrations |
0.80 |
Shows how to use another Azure AD B2C tenant as an IdP; includes configuration of metadata endpoints, client IDs, and policy elements unique to cross-tenant B2C federation. |
| Azure AD B2C best practices |
best-practices |
0.80 |
Explicit best-practices article with product-specific recommendations for integrating Azure AD B2C into applications. |
| ClaimsProviders |
configuration |
0.80 |
Reference for ClaimsProvider element with child elements, attributes, and configuration for different party types—detailed schema-level configuration. |
| Conditional access |
configuration |
0.80 |
Reference for Conditional Access technical profiles with specific settings and how they integrate into custom policies—detailed config. |
| Configure Conditional Access |
security |
0.80 |
How-to for configuring Conditional Access policies and MFA enforcement for B2C user flows and custom policies, with specific settings and scopes. Product-specific security configuration. |
| Configure SAML application options |
configuration |
0.80 |
Explicitly about configuration options for SAML SP integration; likely includes parameter names, expected values, and assertion handling rules unique to Azure AD B2C. |
| Configure SAML identity provider options |
configuration |
0.80 |
Explicitly about parsing assertions and available configuration options; likely lists option names, meanings, and allowed values. |
| Configure a SAML identity provider |
integrations |
0.80 |
Shows how to enable sign-in with any SAML IdP; includes SAML endpoints, certificates, and policy configuration unique to Azure AD B2C. |
| Configure a custom domain |
configuration |
0.80 |
Includes DNS requirements, certificate bindings, and specific Azure AD B2C settings for using custom domains in redirect URLs. |
| Define custom attributes |
configuration |
0.80 |
Includes specific attribute schema names, data types, and how to register them in Azure AD B2C policies/user flows, which are configuration details. |
| Deploy with Azure Pipelines |
deployment |
0.80 |
CI/CD article describes product-specific deployment steps, pipeline configuration, and constraints for custom policy deployment using Azure Pipelines. |
| Deploy with GitHub Actions |
deployment |
0.80 |
Covers GitHub Actions workflow configuration and requirements specific to deploying Azure AD B2C custom policies, beyond generic CI/CD usage. |
| Enable CAPTCHA |
security |
0.80 |
How-to article for enabling CAPTCHA in B2C, with specific settings for user flows vs custom policies and configuration parameters. Product-specific security configuration. |
| Enrich tokens with external claims |
configuration |
0.80 |
Describes how to configure outbound calls and claims mapping to enrich tokens, including specific policy elements and settings unique to Azure AD B2C. |
| Facebook |
integrations |
0.80 |
Facebook integration includes app registration, redirect URIs, and policy configuration; these are concrete integration parameters. |
| Generic OpenId Connect |
integrations |
0.80 |
Generic OIDC IdP setup requires specifying discovery endpoints, client credentials, and claim mappings; article is integration-focused with detailed parameters. |
| Google |
integrations |
0.80 |
Google IdP integration includes client IDs, secrets, endpoints, and scopes; article provides product-specific integration parameters. |
| Localization |
configuration |
0.80 |
Describes the Localization element with specific XML structure, attributes, and allowed values for locales and language customization—detailed config schema. |
| Mailjet |
integrations |
0.80 |
Contains Mailjet-specific API/SMTP configuration, template IDs, and Azure AD B2C policy settings to route verification emails through Mailjet. |
| Manage directory quota |
limits-quotas |
0.80 |
Specifically about directory size quota expressed as number of objects; likely includes exact quota values and behavior when limits are reached. |
| Microsoft Entra ID (multitenant) |
integrations |
0.80 |
Custom policy integration for multitenant Entra ID; involves specific policy elements, authority URLs, and settings not generally known. |
| Microsoft Entra multifactor authentication |
configuration |
0.80 |
Reference for MFA technical profiles (phone, TOTP) with specific claim and metadata configuration—product-specific settings. |
| Modify sign-up experiences |
configuration |
0.80 |
Provides configuration fields (endpoint URL, authentication type, claims mapping) and how to attach connectors to specific steps in user flows. |
| OAuth1 identity provider |
configuration |
0.80 |
Shows how to integrate OAuth 1.0 providers via technical profiles with specific parameter names and values—product-specific integration config. |
| One-time password |
configuration |
0.80 |
Describes configuration for OTP generation and verification via technical profiles and claims—detailed, product-specific configuration pattern. |
| Roles and resource access control |
security |
0.80 |
Contains a table mapping B2C resources to specific administrative roles, implementing least-privilege access control. |
| Salesforce (SAML) |
integrations |
0.80 |
Describes SAML-specific settings (entity IDs, certificate, endpoints, claim mappings) for Salesforce and Azure AD B2C, including parameter names and formats unique to this integration. |
| Secure API Management API |
integrations |
0.80 |
Describes creating and testing an inbound policy in API Management that validates Azure AD B2C-issued tokens; includes policy XML, claim checks, and configuration parameters unique to this integration. |
| Secure an API connector |
security |
0.80 |
Covers authentication patterns for protecting REST endpoints called by B2C, including token validation, scopes, and configuration of app registrations and roles. |
| SendGrid |
integrations |
0.80 |
Provides SendGrid-specific configuration (API keys, templates) and B2C policy settings to send verification emails via SendGrid. |
| TLS and cipher suite requirements |
security |
0.80 |
Specifies required TLS versions and cipher suites for endpoints used by API connectors and identity providers—product-specific security configuration requirements. |
| UserInfo endpoint |
configuration |
0.80 |
Describes policy elements and configuration parameters to implement an OpenID Connect UserInfo endpoint, including claim mappings and endpoint definitions. |
| itsme |
integrations |
0.80 |
Describes integrating itsme via OIDC using client_secret user flow; includes specific endpoints, scopes, and policy configuration unique to this partner integration. |
| Claims transformation |
configuration |
0.79 |
Explains how to configure claims transformation technical profiles and call transformation methods—product-specific configuration schema. |
| 10 - Sign up and sign in (social account) |
integrations |
0.78 |
Provides concrete steps and XML configuration to federate with Facebook (or similar) as an IdP in B2C custom policies. Contains provider-specific technical profile settings and claims handling. |
| Configure user input |
configuration |
0.78 |
Describes configuration of user input fields and attribute collection in policies/user flows, including setting names and options unique to Azure AD B2C. |
| ContentDefinitions |
configuration |
0.78 |
Reference page for the ContentDefinitions element with schema details, element/attribute names, and allowed values for customizing self-asserted technical profiles—product-specific configuration not generally known. |
| Cookie definitions |
configuration |
0.78 |
Lists specific cookie names, purposes, and behaviors used by Azure AD B2C—low-level implementation details not generally known. |
| Customize language |
configuration |
0.78 |
Includes language customization settings, JSON resource keys, and policy configuration for localized strings, which are detailed configuration parameters. |
| Experian |
integrations |
0.78 |
Tutorial for Experian CrossCore integration will define specific API parameters, claims mappings, and policy configuration unique to this service. |
| Manage policies with PowerShell |
configuration |
0.78 |
Uses specific PowerShell cmdlets, parameters, and patterns for CRUD operations on custom policies that are unique to Azure AD B2C. |
| Microsoft Dynamics 365 Fraud Protection |
integrations |
0.78 |
Tutorial for using DFP risk assessments during B2C sign-up/sign-in, with specific configuration, API calls, and policy integration. Product-specific integration knowledge. |
| Microsoft Entra SSPR |
configuration |
0.78 |
Covers configuration of self-service password reset technical profiles with specific parameters and claims—detailed config reference. |
| Mitigate credential attacks |
best-practices |
0.78 |
Describes detection and mitigation techniques like smart lockout and other B2C-specific protections, with actionable guidance on configuration and usage. Product-specific security best practices. |
| Mobile ID |
integrations |
0.78 |
Step-by-step configuration of Mobile ID as an external IdP, including provider-specific endpoints, client IDs/secrets, and Azure AD B2C policy/claim mappings that are product- and provider-specific. |
| Multifactor authentication |
security |
0.78 |
How-to for enabling MFA in B2C user flows and custom policies, with specific settings, policy options, and configuration steps. Contains product-specific security configuration details. |
| Nok Nok |
integrations |
0.78 |
Integration article for Nok Nok S3 with B2C, including FIDO/WebAuthn-specific configuration, endpoints, and policy settings. Highly product-specific integration patterns. |
| Onfido |
integrations |
0.78 |
Onfido integration tutorial will include specific policy XML, claims, and API parameters unique to this verification provider. |
| Ping Identity |
integrations |
0.78 |
Partner integration tutorial with PingAccess/PingFederate typically includes product-specific endpoints, policy/config values, and XML/JSON snippets unique to this integration, which are not general knowledge. |
| PingOne (Ping Identity) |
integrations |
0.78 |
Contains concrete PingOne configuration (redirect URIs, metadata, client credentials) and Azure AD B2C IdP setup fields, which are specific integration parameters. |
| QQ |
integrations |
0.78 |
Provides QQ-specific app registration values, callback URLs, and Azure AD B2C IdP configuration fields, which are detailed integration parameters. |
| Salesforce |
integrations |
0.78 |
Includes Salesforce-connected app settings (callback URL, scopes, client ID/secret) and corresponding Azure AD B2C IdP configuration, which are product-specific integration details. |
| SwissID |
integrations |
0.78 |
Shows SwissID-specific configuration (redirect URLs, client credentials, endpoints) and Azure AD B2C IdP setup fields, which are detailed integration parameters. |
| Transmit Security for passwordless |
integrations |
0.78 |
Tutorial for configuring Transmit Security hosted passkeys with B2C, including specific technical profiles, endpoints, and claims mapping. Detailed integration knowledge. |
| Twilio |
integrations |
0.78 |
Walkthrough for integrating Twilio Verify API with a B2C-secured app, including API configuration, callbacks, and B2C policy settings. Detailed integration and coding pattern. |
| TypingDNA |
integrations |
0.78 |
Shows how B2C uses TypingDNA APIs and app for keystroke-based verification, including configuration and policy integration details. Product-specific integration patterns. |
| User data |
configuration |
0.78 |
Uses Microsoft Graph operations and specific endpoints to manage user data and audit logs for compliance, which is detailed configuration knowledge. |
| Verification |
configuration |
0.78 |
Shows how to configure verification display controls (email/phone) with specific technical profile and metadata settings—product-specific config patterns. |
| WeChat |
integrations |
0.78 |
Contains WeChat app registration details, callback URLs, and Azure AD B2C IdP configuration parameters that are specific to this integration. |
| Weibo |
integrations |
0.78 |
Provides Weibo-specific client/app settings and Azure AD B2C IdP configuration fields, including parameter names and URLs unique to this integration. |
| X |
integrations |
0.78 |
Includes X/Twitter app keys, callback URLs, and Azure AD B2C IdP configuration parameters, which are concrete integration settings. |
| Zscaler |
integrations |
0.78 |
ZPA integration requires specific configuration parameters, redirect URIs, and trust settings between Zscaler and Azure AD B2C that are unique to this pairing. |
| b2clogin.com overview |
configuration |
0.78 |
Provides concrete redirect URL formats, issuer/endpoint changes, and configuration steps to replace login.microsoftonline.com with b2clogin.com or custom domains. |
| 4 - Validate user input custom policy |
integrations |
0.76 |
Describes concrete validation mechanisms (DisplayClaim attributes, predicates, regex, validation technical profiles) with product-specific XML configuration patterns. This is detailed configuration/integration knowledge beyond generic validation concepts. |
| 9 - Sign up and sign in (local account) |
integrations |
0.76 |
Shows exact custom policy configuration for email/password local accounts, including technical profiles, user journeys, and claim mappings. These are specific integration/config patterns. |
| Akamai |
integrations |
0.76 |
Explains how to configure Akamai WAP in front of B2C using custom domains, including DNS, TLS, and routing specifics. Detailed integration configuration. |
| Akamai |
integrations |
0.76 |
Tutorial for integrating Akamai EAA with B2C for secure hybrid access, including federation, SSO, and access configuration. Detailed integration patterns. |
| Arkose Labs |
integrations |
0.76 |
Tutorial for wiring Arkose Protect into B2C authentication flows, with specific configuration and technical profile details. Product-specific risk/fraud integration. |
| Audit logs |
configuration |
0.76 |
Explains how to retrieve audit logs via portal and programmatically, including specific API endpoints, filters, and log schema details. |
| Azure WAF |
integrations |
0.76 |
Tutorial for enabling Azure WAF for B2C with custom domains, including resource configuration and routing. Product-specific integration and security configuration. |
| BioCatch |
integrations |
0.76 |
Explains how to integrate BioCatch with B2C, including API usage, endpoints, and policy configuration. Detailed integration and risk-detection patterns. |
| Cloudflare |
integrations |
0.76 |
Shows how to configure Cloudflare WAF for a B2C tenant with custom domain, including DNS and security settings. Detailed integration knowledge. |
| Configure age gating |
configuration |
0.76 |
Describes how to configure policies and claims to identify minors, including specific policy elements and conditions unique to B2C. |
| Configure session behavior |
configuration |
0.76 |
Contains concrete session configuration options (such as SSO scopes, session lifetimes, remember-me toggles) with setting names and allowed values specific to Azure AD B2C. |
| Configure web API domains |
integrations |
0.76 |
Shows concrete OWIN middleware configuration and issuer/audience validation settings to accept tokens from multiple B2C domains, which are code-level integration patterns. |
| Datawiza |
integrations |
0.76 |
Shows how to configure DAP with B2C for SSO and granular access control to on-prem apps, including product-specific configuration steps. Integration-focused expert knowledge. |
| Deduce |
integrations |
0.76 |
Sample integration guidance with Deduce will include concrete technical configuration (claims, endpoints, keys) specific to this product combination. |
| Disable email verification |
configuration |
0.76 |
Describes specific policy/user flow settings to turn off email verification, including configuration flags and their effects. |
| Enable JavaScript and page layouts |
configuration |
0.76 |
Explains configuration flags and layout version identifiers in policies/user flows to enable JS and choose layouts, including allowed values and constraints. |
| F5 |
integrations |
0.76 |
Tutorial for integrating F5 BIG-IP APM with B2C, including preauthentication, Conditional Access, and SSO configuration. Detailed integration and security patterns. |
| IDology |
integrations |
0.76 |
Covers concrete wiring of an online payment app and IDology ExpectID into Azure AD B2C, including non-generic configuration details. |
| Investigate risk with Identity Protection |
security |
0.76 |
Covers use of Identity Protection risk reports, investigation workflows, and remediation actions specific to B2C tenants. Product-specific security operations guidance. |
| LexisNexis |
integrations |
0.76 |
ThreatMetrix integration involves detailed configuration of profiling and risk assessment flows in Azure AD B2C, beyond generic SSO concepts. |
| Strata |
integrations |
0.76 |
Describes concrete steps and configuration details to connect Azure AD B2C with Strata Maverics Identity Orchestrator, including product-specific settings beyond generic OAuth/OIDC knowledge. |
| Transmit Security |
integrations |
0.76 |
Shows how to integrate Transmit Security DRS with B2C custom policies, including configuration parameters and technical profiles. Detailed risk-detection integration. |
| Trusona |
integrations |
0.76 |
Explains how to configure Trusona as an identity provider for B2C, with concrete configuration parameters and policy changes. Product-specific integration. |
| Usage analytics |
configuration |
0.76 |
Describes enabling and configuring event logging from B2C to Application Insights with specific settings and event schemas. |
| xID |
integrations |
0.76 |
Describes how to configure B2C with xID, including My Number Card-based verification, endpoints, and policy configuration. Product-specific integration details. |
| Amazon |
integrations |
0.75 |
Shows how to configure Amazon OAuth/OpenID details in Azure AD B2C; includes client IDs, secrets, endpoints, and policy settings. |
| Apple |
integrations |
0.75 |
Apple ID integration requires specific configuration (keys, redirect URIs, scopes); article likely lists these product-specific parameters. |
| Configure a sample Angular app |
integrations |
0.75 |
Uses MSAL Angular with module configuration, interceptor setup, and config fields (clientId, authority, redirectUri, protectedResourceMap), which are detailed integration patterns. |
| Configure a sample Node.js web API |
integrations |
0.75 |
Shows how a Node.js web app calls a Node.js web API protected by Azure AD B2C using access tokens; likely includes client IDs, authority URLs, scopes, and library options specific to this product integration. |
| Configure a sample Node.js web app |
integrations |
0.75 |
Uses MSAL Node with specific configuration objects, routes, and token handling patterns to integrate B2C, which are detailed integration patterns. |
| Configure a sample Python web app |
integrations |
0.75 |
Uses MSAL Python with specific configuration (clientId, authority, redirectUri) and web framework patterns to integrate B2C, which are detailed integration patterns. |
| Configure a sample React app |
integrations |
0.75 |
Uses MSAL React with specific component props, configuration objects, and API calls to secure a React SPA and call a protected API, which are detailed integration patterns. |
| Configure a sample web app |
integrations |
0.75 |
Shows concrete ASP.NET middleware configuration (OpenID Connect options, authority, clientId, callback paths) and B2C policy usage, which are detailed integration patterns. |
| Enable authentication in Node.js web API |
integrations |
0.75 |
Covers acquiring access tokens and sending them as bearer tokens from a Node.js web app to a protected API; typically includes concrete configuration and code patterns for Azure AD B2C token validation. |
| Enable authentication in Node.js web app |
integrations |
0.75 |
Shows how to configure MSAL Node and Express middleware with B2C-specific settings, which are product-specific integration details. |
| Enable authentication in a Python web app |
integrations |
0.75 |
Shows how to configure MSAL Python and web routes with B2C-specific settings, which are product-specific integration details. |
| Enable authentication in your Angular app |
integrations |
0.75 |
Shows how to wire MSAL Angular into a custom app with specific configuration and code patterns unique to this integration. |
| Enable authentication in your React app |
integrations |
0.75 |
Shows how to configure MSAL React in a custom app, including config fields, provider setup, and hook usage, which are product-specific integration details. |
| Enable authentication in your iOS app |
integrations |
0.75 |
Shows how to integrate MSAL for iOS with Azure AD B2C in a custom app; includes specific configuration keys, authority URLs, and code patterns unique to this product. |
| Enable authentication in your web app |
integrations |
0.75 |
Covers how to configure ASP.NET Core middleware with B2C-specific settings and endpoints, which are product-specific integration details. |
| Force password reset |
configuration |
0.75 |
Force-reset flows involve specific custom policy configuration, claims, and orchestration steps that are detailed B2C configuration knowledge. |
| GitHub |
integrations |
0.75 |
GitHub IdP integration requires specific OAuth configuration and Azure AD B2C policy settings; these are concrete integration details. |
| ID.me |
integrations |
0.75 |
ID.me integration requires specific OIDC/OAuth configuration and Azure AD B2C policy settings; these are detailed integration patterns. |
| LinkedIn |
integrations |
0.75 |
LinkedIn IdP integration requires concrete OAuth configuration and Azure AD B2C settings; article likely lists these parameters. |
| Local account identity provider |
configuration |
0.75 |
Defines identity types (email, username, phone) and how to configure them in policies/user flows; includes specific setting names and allowed values. |
| Microsoft Account |
integrations |
0.75 |
Configuring Microsoft account as an IdP involves specific endpoints, scopes, and policy configuration; these are product-specific integration details. |
| Microsoft Entra ID (single tenant) |
integrations |
0.75 |
Configures Azure AD (Entra ID) as an IdP; includes tenant IDs, endpoints, and policy configuration unique to this scenario. |
| Profile editing policy |
configuration |
0.75 |
Profile editing flows require selecting attributes, defining policy names, and configuring token output, which are concrete configuration parameters. |
| Register a SAML application |
configuration |
0.75 |
SAML IdP configuration requires exact claim mappings, metadata URLs, certificate settings, and policy references that are detailed, product-specific configuration values. |
| Resource owner password credentials policy |
configuration |
0.75 |
ROPC setup in B2C uses specific endpoints, policy names, and app registration settings that are detailed configuration values. |
| Self-service password reset |
configuration |
0.75 |
Password reset flows require specific policy configuration, endpoint names, and token behavior settings that are concrete and product-specific. |
| Sign-up or sign-in policy |
configuration |
0.75 |
User flow setup includes concrete policy names, attribute selections, token settings, and UI configuration options that are specific to B2C configuration. |
| User profile attributes |
configuration |
0.75 |
Details built-in and extension attributes, and their mapping to Microsoft Graph; product-specific attribute configuration reference. |
| eBay |
integrations |
0.75 |
Configures eBay as an external IdP; requires specific OAuth endpoints, scopes, and Azure AD B2C settings. |
| 6 - Validate custom policy files |
configuration |
0.74 |
Covers TrustFrameworkPolicy schema usage and XML extensions in VS Code, including schema references and navigation specifics for B2C policy files. This is detailed configuration tooling knowledge not generally known. |
| Grit |
integrations |
0.74 |
Explains how to use Grit's app proxy to migrate legacy header-based auth apps to B2C without code changes, including configuration details and migration patterns. Product-specific integration/migration knowledge. |
| Grit biometric authentication |
integrations |
0.74 |
Biometric integration requires concrete configuration of custom policies and technical parameters specific to Grit’s solution. |
| HYPR |
integrations |
0.74 |
Partner integration guide with specific settings and policy configuration to use HYPR as a passwordless IdP in B2C. Contains product-specific integration parameters. |
| Haventec |
integrations |
0.74 |
Shows how to wire Haventec into B2C authentication flows, with concrete configuration steps and technical profile details unique to this integration. |
| Jumio |
integrations |
0.74 |
Jumio integration requires specific callback URLs, policy configuration, and claims handling that constitute product-specific integration knowledge. |
| Keyless |
integrations |
0.74 |
Tutorial for integrating Keyless ZKB with B2C, including specific configuration steps and technical profile settings. Product-specific integration knowledge. |
| Nevis |
integrations |
0.74 |
Shows how to integrate Nevis Access app with B2C for PSD2-compliant passwordless auth, with concrete configuration and policy details. |
| WhoIAM |
integrations |
0.74 |
Tutorial for integrating WhoIAM BRIMS apps and services with B2C, including configuration steps and technical profile settings. Detailed integration knowledge. |
| 3 - Collect user input using custom policy |
integrations |
0.72 |
How-to article with concrete XML policy elements, claim types, and technical profile configuration specific to Azure AD B2C custom policies for collecting and returning user input as JWT claims. These schema details and patterns are product-specific integration/config knowledge. |
| BlokSec |
integrations |
0.72 |
Tutorial for integrating BlokSec with B2C, including product-specific configuration values, endpoints, and policy changes. This is detailed integration knowledge. |
| Microsoft Sentinel |
security |
0.72 |
Security-focused integration with Sentinel, including specific data connectors, table names, and configuration steps for B2C telemetry. |
| eID-Me |
integrations |
0.72 |
Identity verification integration with eID-Me requires product-specific configuration steps and parameters not covered by generic identity docs. |
| 1 - Create an Azure AD B2C tenant |
limits-quotas |
0.70 |
Tutorial includes a specific numeric limit of 20 tenants per subscription, which is a concrete quota value not generally known. |
| 2 - Create Hello World custom policies |
configuration |
0.70 |
Walks through constructing policy XML, defining keys, and uploading/testing in Azure AD B2C, including specific element names and configuration structure unique to custom policies. |
| 5 - Create branching in user journeys |
integrations |
0.70 |
Shows how to conditionally enable/disable technical profiles using preconditions and claim values in custom policy XML. Contains specific schema elements and flow control patterns unique to Azure AD B2C. |
| 8 - Create and read user record custom policy |
integrations |
0.70 |
Details how to use B2C technical profiles and claim types to store and retrieve user attributes (including custom attributes) in Entra ID. Contains concrete schema/config patterns unique to B2C. |
| Add an identity provider |
configuration |
0.70 |
Shows how to configure various external IdPs; typically includes configuration fields, endpoints, and protocol-specific parameters. |
| Authentication options |
configuration |
0.70 |
Describes optional Static Web Apps auth configuration fields and behaviors for B2C, which are concrete configuration parameters. |
| Authorization Code grant flow |
integrations |
0.70 |
Detailed description of authorization code flow with B2C-specific endpoints and parameters; integration-focused protocol guidance. |
| Azure Monitor |
integrations |
0.70 |
Describes configuration of diagnostic settings, categories, and destinations for B2C logs in Azure Monitor, including product-specific options. |
| Billing model |
decision-making |
0.70 |
Describes MAU billing model, free tier, and premium tier pricing with guidance on selecting appropriate tier—service selection and cost trade-off information. |
| Check tenant creation permission |
security |
0.70 |
Explains how Global Administrators restrict tenant creation for non-admins; includes security-focused configuration steps and role context. |
| Configure a sample Android app |
integrations |
0.70 |
Uses a sample Android app to add Azure AD B2C authentication; typically includes MSAL configuration, redirect URI formats, and manifest changes that are product-specific integration details. |
| Configure a sample SPA app |
integrations |
0.70 |
Shows concrete MSAL.js configuration (clientId, authority, redirectUri, scopes) and wiring of B2C policies into a SPA, which are product-specific integration patterns and parameters. |
| Configure a sample desktop app |
integrations |
0.70 |
Sample WPF desktop integration; likely includes MSAL configuration, redirect URIs, and app registration parameters specific to Azure AD B2C. |
| Configure a sample iOS app |
integrations |
0.70 |
Sample iOS Swift integration with Azure AD B2C; likely includes MSAL for iOS configuration, redirect URI schemes, and plist settings that are concrete integration parameters. |
| Configure a sample web app that calls a web API |
integrations |
0.70 |
How-to for wiring an ASP.NET web app to call a web API with bearer tokens via Azure AD B2C; typically includes app registration fields, redirect URIs, scopes, and middleware options that are product-specific integration parameters. |
| Configure an Azure Static Web App |
integrations |
0.70 |
Shows how to configure Static Web Apps custom auth with B2C-specific settings in configuration files and portal, which are product-specific integration details. |
| Configure an Azure Web App |
integrations |
0.70 |
Explains how to configure App Service authentication with B2C-specific OpenID Connect settings (issuer, clientId, secret, callback paths), which are detailed integration/configuration patterns. |
| Customize the UI |
configuration |
0.70 |
Contains specific UI customization settings (page layout, logo, background, CSS references) configured in Azure AD B2C policies/user flows. |
| Embedded sign-in with iframe |
integrations |
0.70 |
Shows specific custom policy configuration and redirect/iframe patterns to embed the B2C UI, including technical parameters unique to this feature. |
| Enable authentication in a web app |
integrations |
0.70 |
Describes building blocks and middleware configuration for OpenID Connect in ASP.NET Core with Azure AD B2C; likely includes specific config keys, options, and code patterns unique to this integration. |
| Enable authentication in an Android app |
integrations |
0.70 |
Guides integrating Azure AD B2C into a custom Android app; likely details MSAL parameters, authorities, scopes, and callback configuration unique to this service. |
| Enable authentication in an SPA app |
integrations |
0.70 |
Covers how to configure MSAL.js and B2C policies in a custom SPA with specific config object fields and API usage, which are detailed integration patterns. |
| Extensions app |
configuration |
0.70 |
Describes the special b2c-extensions-app that Azure AD B2C auto-creates, its role in storing user/custom attribute data, and the impact if it is deleted. This is product-specific operational/configuration knowledge about a hidden/managed app that an LLM is unlikely to know without the docs. |
| File based configuration |
configuration |
0.70 |
File-based configuration includes specific JSON/YAML fields and allowed values for B2C auth in App Service, which are detailed configuration parameters. |
| Funnel-based design |
architecture-patterns |
0.70 |
Covers funnel-based design approach with capabilities and performance considerations, helping choose and apply a specific architecture pattern. |
| Grit IAM B2B2C |
integrations |
0.70 |
Describes concrete configuration steps and parameters to connect Grit IAM with Azure AD B2C, including endpoints and claims specific to this integration. |
| Grit IEF editor |
configuration |
0.70 |
Describes product-specific configuration workflow and options in the Grit Visual IEF Editor for Azure AD B2C custom policies, including unique settings and behaviors. |
| IDEMIA |
integrations |
0.70 |
Covers how to configure B2C to consume IDEMIA Mobile ID, including endpoints, claims, and policy configuration. This is detailed integration guidance. |
| Identity Protection and Conditional Access |
security |
0.70 |
Describes configuring risk-based Conditional Access policies and using risk detections in B2C tenants; product-specific security configuration. |
| Manage emergency access |
security |
0.70 |
Describes emergency access accounts to prevent lockout, with product-specific security configuration guidance for admin access resilience. |
| Manage operation with Microsoft Graph API |
integrations |
0.70 |
Lists supported Microsoft Graph operations and likely includes specific endpoints, permissions, and request patterns unique to Azure AD B2C management. |
| N8identity |
integrations |
0.70 |
Tutorial for configuring TheAccessHub with Azure AD B2C, including specific configuration fields, endpoints, and mappings unique to this partner integration. |
| Pass through identity provider token |
configuration |
0.70 |
Describes specific user flow settings and claim configurations to include IdP access tokens in issued tokens, including parameter names and toggles unique to Azure AD B2C. |
| Phone sign-up and sign-in |
configuration |
0.70 |
Phone auth configuration includes specific identity provider settings, verification options, and user flow parameters that are product-specific configuration details. |
| Policy keys |
security |
0.70 |
Explains policy keys for signing/validating tokens, client secrets, certificates, and passwords with B2C-specific key management settings. |
| Region-based design |
architecture-patterns |
0.70 |
Describes region-based design approach with capabilities and performance trade-offs, a product-specific architecture pattern. |
| Register a Microsoft Graph application |
configuration |
0.70 |
Includes concrete Microsoft Graph permission names, consent types, and app registration settings required to manage B2C via Graph, which are specific configuration parameters. |
| Register a single-page application (SPA) |
configuration |
0.70 |
SPA registration guides usually specify exact portal settings such as redirect URI formats, SPA platform selection, and token configuration parameters that are product-specific configuration details. |
| Register a web API application |
configuration |
0.70 |
Web API registration in B2C involves defining scopes, application IDs, and specific portal configuration fields (expose an API, scope names, access token settings), which are detailed configuration parameters. |
| Register apps |
configuration |
0.70 |
App registration docs typically include product-specific fields (redirect URIs, reply URL types, implicit/hybrid flags, supported account types) and exact configuration values unique to Azure AD B2C, which are not just conceptual. |
| Register daemon apps (client credentials) |
configuration |
0.70 |
Client credentials flow setup in B2C requires specific policy names, endpoint URLs, app registration settings, and token configuration values that are product-specific configuration details. |
| Request access token |
integrations |
0.70 |
Shows how to request access tokens with specific parameters and HTTP patterns for web and native apps; product-specific integration details. |
| Saviynt |
integrations |
0.70 |
Provides product-specific configuration for Saviynt and Azure AD B2C, including connection parameters and application settings for cross-application integration. |
| Secure access to Web API (ASP.NET Core and Node.js) |
integrations |
0.70 |
Shows how to enforce access tokens on API endpoints; likely includes middleware or library configuration, token validation parameters, and API registration details specific to Azure AD B2C. |
| Security overview |
best-practices |
0.70 |
Article explicitly focuses on best practices for securing all components of an Azure AD B2C solution, likely including product-specific recommendations and patterns across services. |
| Self-service password change |
configuration |
0.70 |
The article describes detailed, product-specific configuration steps for enabling password change via Azure AD B2C custom policies, including specific policy elements, technical profile names, and configuration structure that go beyond generic knowledge. It is not just a tutorial; it encodes concrete configuration patterns unique to Azure AD B2C custom policies. |
| Set up direct sign-in |
configuration |
0.70 |
Uses specific query parameters and policy configuration options to prepopulate sign-in names or redirect to social IdPs, which are product-specific settings. |
| Sign-in policy |
configuration |
0.70 |
Similar to other user flow docs, this page defines specific policy configuration fields, identity providers, and settings that are detailed B2C configuration parameters. |
| User access |
configuration |
0.70 |
Covers concrete configuration of attributes (DOB, country), terms-of-use capture, and policy behavior for managing access, which are product-specific. |
| WhoIAM Rampart |
integrations |
0.70 |
Covers detailed setup of Rampart with Azure AD B2C, including RBAC-related configuration, endpoints, and app settings unique to this integration. |
| Frequently asked questions |
decision-making |
0.68 |
FAQ content for Azure AD B2C typically includes product-specific, time-bound information (such as purchase/retirement dates, supported scenarios, and guidance on what to use instead after deprecation). This is expert knowledge not reliably known from training and is used to make decisions about whether and how to adopt or migrate from Azure AD B2C. While it’s an FAQ, the deprecation and replacement guidance aligns most closely with decision-making (service selection and migration considerations), rather than limits, configuration, or troubleshooting. |
| Migrate users |
decision-making |
0.68 |
Explains when to use pre-migration vs seamless migration, including trade-offs, flows, and requirements (e.g., Graph API usage) to guide migration decisions. |
| Add administrator (work account) |
security |
0.65 |
Covers how to add and invite admin/guest accounts with role-based access; includes product-specific admin role usage and security configuration steps. |
| Authentication options |
configuration |
0.65 |
Describes enabling and customizing authentication experience for Android; option pages usually enumerate specific configuration switches and policy settings. |
| Authentication options |
configuration |
0.65 |
Describes optional Angular/MSAL/B2C settings and behaviors, which are concrete configuration parameters for the integration. |
| Authentication options |
configuration |
0.65 |
Covers optional Node/MSAL/B2C settings and behaviors, which are concrete configuration parameters for the integration. |
| Authentication options |
configuration |
0.65 |
Describes enabling and customizing authentication options for a Node.js web API; option articles usually list specific configuration flags, policy settings, and parameter values. |
| Authentication options |
configuration |
0.65 |
Focuses on enabling and customizing authentication options; such content typically lists policy and client configuration options with allowed values. |
| Authentication options |
configuration |
0.65 |
Describes optional Python/MSAL/B2C settings and behaviors, which are concrete configuration parameters for the integration. |
| Authentication options |
configuration |
0.65 |
Focuses on customizing and enhancing auth experience, likely listing specific MSAL/B2C options and flags, which are configuration parameters for the integration. |
| Authentication options |
configuration |
0.65 |
Describes specific optional settings (e.g., cache options, prompt behavior, redirect handling) for SPA auth, which are concrete configuration parameters for the integration. |
| Authentication options |
configuration |
0.65 |
Focuses on ways to customize and enhance the authentication experience; such option pages usually enumerate policy settings, parameters, and allowed values, which are configuration-centric. |
| Authentication options |
configuration |
0.65 |
Describes optional web app auth behaviors and settings (e.g., cookie options, redirect behavior, policy selection) that are concrete configuration parameters. |
| Authentication options |
configuration |
0.65 |
Describes ways to customize and enhance authentication; option pages usually detail configuration properties and policy settings. |
| Custom policy overview |
configuration |
0.65 |
Explains structure and behavior of custom policy configuration files, including policy elements and settings unique to B2C. |
| Funnel-based proof of concept |
architecture-patterns |
0.65 |
Shows how to implement funnel-based orchestration via custom policies; concrete realization of a specific architecture pattern. |
| Implicit flow |
integrations |
0.65 |
Covers SPA-specific implicit flow challenges and B2C configuration for OAuth 2.0, including protocol parameters. |
| OpenID Connect protocol |
integrations |
0.65 |
Protocol-level guide with concrete HTTP request/response patterns and B2C-specific parameters for OpenID Connect integration. |
| Publish app in Microsoft Entra app gallery |
configuration |
0.65 |
Publishing to the app gallery involves specific metadata fields, validation requirements, and configuration parameters unique to Entra/B2C that go beyond conceptual description. |
| Region availability & data residency |
decision-making |
0.65 |
Covers region availability, data residency, high availability, SLA, and preview tenant behavior. These topics typically include region lists, residency rules, and HA/SLA specifics that guide where and how to deploy tenants—product-specific decision criteria that go beyond generic knowledge. |
| Region-based proof of concept |
architecture-patterns |
0.65 |
Guides creation of region-based orchestration with custom policies; detailed pattern implementation for global identity. |
| Register native client (for mobile and desktop) |
configuration |
0.65 |
Native client registration requires specific configuration like public client flags, redirect URI schemes, and platform selection, which are concrete Azure AD B2C settings rather than conceptual content. |
| Release notes |
best-practices |
0.65 |
Aggregates product-specific notes on feature availability, behavior changes, and how to configure/maintain policies—contains gotchas and implementation guidance beyond generic concepts. |
| Tokens |
limits-quotas |
0.65 |
Token overview likely includes token size, lifetime defaults, and claim constraints, which are concrete numeric and structural limits. |
| API Connectors |
integrations |
0.60 |
Describes using REST APIs/outbound webhooks in user flows/custom policies with B2C-specific connector configuration. |
| Application types |
decision-making |
0.60 |
Explains supported app types and scenarios, helping decide which architecture (web, SPA, native, etc.) to use with B2C. |
| Global identity solutions |
architecture-patterns |
0.60 |
Describes a global identity framework for millions of users and billions of authentications with Azure AD B2C, including product-specific architectural guidance. |
| Legacy user flow versions |
configuration |
0.60 |
Explains the legacy versioning scheme (V1, V1.1, V2) and which environments still use it. This is detailed, product-specific version/configuration behavior, not generic concept, and is needed to correctly configure policies in non-public clouds. |
| User flow versions |
configuration |
0.60 |
Describes available user flow versions with tables. Version matrices for sign-up/sign-in, password reset, etc., are product-specific configuration knowledge (which versions exist, how they map to capabilities) that an LLM is unlikely to know precisely from training. |