A city open-data portal team wants smoother sign-in experiences for 311 agents who switch among multiple Microsoft 365 apps during a shift. What should they highlight?

SSO benefits improve sign-in UX across integrated Microsoft 365 apps so 311 agents on a city open-data portal team can switch among workloads during a shift without constant re-authentication. Highlighting that smoother experience—while keeping authentication intact—matches the fundamentals SSO value proposition for busy municipal agents living in tab-switching workflows.

Highlighting self-service password policies fails because they address password recovery and reset controls, not session continuity across apps; agents would still face separate prompts when switching between Microsoft 365 apps without SSO. Highlighting Conditional Access policies fails because they enforce risk-based access conditions rather than enabling seamless continuity; they do not reduce sign-in repetition across the integrated workload set. Highlighting Entra security assignments fails because assignments scope what a signed-in user can access, not how often sign-in is required; they do not reduce re-authentication across the application set.

Exam caveat: AB-900 candidates should articulate SSO's UX and productivity benefit accurately without confusing self-service password policies, Conditional Access policies, or Entra security assignments with that cross-app sign-in benefit. Integration under one identity plane is the point. Municipal 311 operations still need auditable sign-in.

Operational check: Observe a 311 agent session spanning multiple Microsoft 365 apps under SSO, confirm repeated password prompts are minimized after the initial trusted sign-in, keep authentication enabled, and reject self-service password policies, Conditional Access policies, or Entra security assignments as the UX strategy. Document SSO as the highlighted benefit for shift efficiency.