An organization wants Prisma Access Browser (PAB) users to authenticate to public cloud services, such...

Single sign-on for PAB users accessing public cloud SaaS applications is centrally brokered through the Cloud Identity Engine, which serves as the identity integration point between the organization ' s corporate IdP — Azure AD/Entra ID in this scenario — and the applications and services users access through PAB, rather than being handled by any browser-native or per-application mechanism. Establishing this Cloud Identity Engine-to-IdP integration is what allows the corporate authentication session and identity attributes to be recognized consistently and passed through automatically as the user navigates to sanctioned SaaS applications like Microsoft 365 via PAB, delivering the seamless SSO experience described in the question, which makes option D the essential, correct integration. There is no PAB feature involving direct integration with Microsoft ' s own Conditional Access policy engine as the SSO enablement mechanism (option A); Conditional Access is a Microsoft Entra-native capability that can complement an SSO deployment but is not itself the integration point that establishes SSO through PAB. A " browser-specific SSO extension " (option B) is not the documented architecture for how PAB delivers SSO to cloud applications — SSO is achieved through the identity broker relationship with Cloud Identity Engine, not through a separate extension component layered on top. Manually configuring individual user authentication tokens within the PAB profile (option C) is neither how SSO is designed to function nor a scalable or supported approach; it would defeat the purpose of automated, centrally managed single sign-on entirely.