Microsoft Entra ID
Conditional Access

Conditional Access: Session

In brief

The documentation now states that sign-in frequency applies to Microsoft-hosted and native authentication. For native authentication, reauthentication can prevent token issuance during refresh token grants, requiring the app to handle the failed refresh and prompt the user to sign in again.

What Entra admins need to know

Administrators should account for this behavior when applying sign-in frequency to native authentication scenarios.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Conditional Access: Session

  • Sign-in frequency
  • Persistent browser session

Sign-in frequency applies to both Microsoft-hosted and native authentication. For native authentication, the policy prevents token issuance during refresh token grants when reauthentication is required. Your app must handle the failed token refresh and prompt the user to sign in again. Persistent browser session controls apply to browser-based sessions. For more information, see Conditional Access and sign-in frequency.

Application enforced restrictions

Organizations can use this control to require Microsoft Entra ID to pass device information to the selected cloud apps. The device information allows cloud apps to know if a connection is from a compliant or domain-joined device and update the session experience. When selected, the cloud app uses the device information to provide users with a limited or full experience. Limited if the device isn't managed or compliant, and full if the device is managed and compliant.

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…