The support matrix now documents OnPasswordSubmit across the listed integration paths and its support for just-in-time password migration during sign-in. It also clarifies custom URL domain requirements for browser-based API V2 apps versus non-browser native clients, and updates recovery and verification labels.
Feature updateAction required The documentation now states that V2 requires a tenant-verified custom domain for browser-based apps and recommends planning a CORS proxy or edge policy. BYO UX guidance now emphasizes independently hosted, reusable authentication websites.
Feature updateAction required The documentation now states that browser-based apps using Native Authentication API V2 require a tenant-verified custom domain, while native non-browser clients do not. BYO UX still requires one.
Feature updateAction required Native Authentication API V2 requires a tenant-verified custom domain for browser-based apps such as SPAs, while non-browser iOS and Android clients using native HTTP transports do not require one.
The Microsoft-hosted authentication section now describes Email OTP and SMS as supported recovery methods and explains the password-reset flow after passcode verification.
The MFA comparison now states that availability through the Native Authentication API or SDK is scoped separately.
The documentation now directs Embedded native authentication and BYO UX users to follow the native authentication attribute contract, including exact returned `attributeId` values, current requirements, and validation metadata.
The CIAM samples documentation now lists minimum versions for MSAL JavaScript (5.29.1), Android (8.7.0), and Apple (2.18.1), and updates sample and release links.
Five related-topic links had trailing periods removed. Their destinations and topics are unchanged.
The reference page’s three related-document links were reformatted for consistent list and punctuation styling.