Skip to content

Ulysses Neves

Microsoft Entra ID, authentication, and hybrid identity troubleshooting.

Menu
  • Home
  • Microsoft Azure
  • Microsoft AD FS
  • Microsoft 365
  • Contact
  • Troubleshooting Index
Menu

Microsoft Entra Conditional Access Policy – Controlling browsing sessions using Conditional Access policies

Posted on April 17, 2020

Hi everyone. In today’s article, we’ll introduce the browser session management option available in Microsoft Entra Conditional Access policy. We’ll create a session control policy for administrator access to applications hosted in Azure. This policy, combined with second-factor control, ensures that whenever an administrator opens a new browser, they must authenticate using MFA.

Conditional Access persistent browser session (preview)

The persistent browser session allows the user to remain signed in to an application even after closing and reopening the browser. It presents the user with the “Stay signed in?” option after authenticating to Azure using a browser.

We’ll carry out the following activities throughout this article:
1 – Creating the Conditional Access policy requiring users with Global administrator privileges to present a second authentication factor for access to all applications in Azure.
2 – Access tests without session control enabled.
3 – Configuring session control in the Conditional Access policy.
4 – Access tests with session control enabled.

Creating the Conditional Access policy with MFA

We’ll create the Conditional Access policy by accessing the Conditional Access policies menu through this link.

Select the New policy option.

Enter the policy name in the Name field.

We’ll select the Global administrator role to be assigned to this policy by performing the steps below:
1 – Select the Users ans groups option.
2 – Select the Select users and groups option.
3 – Check the Directory roles (Preview) option.
4 – Select the Global administrator role from the list.

Click Done.

We’ll select all Azure applications by performing the following steps:
1 – Select the Clouds apps or actions menu.
2 – Select All cloud apps.

We’ll set the requirement to perform second-factor authentication by selecting the Grant option in the Access controls menu.

Check the Require multi-factor authentication option.

We’ll enable the Conditional Access policy by performing the steps below:
1 – In the Enable policy option, select On.
2 – Click Create.

First access to the Azure portal without session control

We’ll access the Azure portal at https://portal.azure.com using a credential with Global administrator privileges.

Access is redirected to the AD FS portal to enter the password.

MFA is requested, in this case, through an approval notification to the Microsoft authenticator app.

With the MFA step completed successfully, the “Stay signed in?” confirmation is requested, which uses cookies to store the user’s access information and avoid new credential prompts. For more information about this feature, check out this link.

Let’s click Yes.

We can see that access was granted to the Azure portal.

Let’s validate the user experience when accessing the Azure portal for the second time with the access information stored in the cookie.

Second access with keep me signed in

With the access information in the cookies, when accessing the URL https://portal.azure.com, access to the portal is immediately granted without the need to present credentials or a second authentication factor.

We’ll now disable “keep me signed in” through session control in the Conditional Access policy. This setting forces the user affected by the policy to present credentials and the second authentication factor every time they access an application in Azure.

Enabling session control in the Conditional Access policy

We’ll access the “CA – No session persisten session” policy created at the beginning of this article.

In the Access controls menu, select the Session option.

We’ll disable persistent browser sessions by performing the following steps:
1 – Check the Persistent browser session option.
2 – Select the Never persistent option.

Note: Session control requires that all cloud applications be selected in the Cloud Apps or actions menu.

Click Select and then Save.

Let’s now perform the same Azure portal access test, this time with session control enabled.

First access to the Azure portal with session control

Let’s access the Azure portal again at https://portal.azure.com using a credential with Global administrator privileges.

Access is redirected to the Ad FS portal for the user to enter the password.

MFA is requested again through an approval notification to the Microsoft authenticator app.

This time, the “keep me signed in” option is not presented to the user and access is granted to the Azure portal.

Let’s now perform the second access to the Azure portal.

Second access to the Azure portal without keep me signed in

When accessing the URL https://portal.azure.com, the last credential that accessed this application is displayed.

When clicking the credential, the user is redirected to the AD FS portal to enter the password.

MFA is requested as if it were the first access to the portal.

With MFA validation completed, access is granted to the user in the Azure portal.

Summary

In today’s article, we explained what the Persistent browser session (Preview) option available in Microsoft Entra Conditional Access policies is and what it’s used for. We demonstrated the difference in an administrator’s access experience to the Azure portal with persistent session control disabled and enabled using a Conditional Access policy. For more information about this feature, check out this link.

I hope this content has helped enrich your knowledge of Microsoft Entra ID.

Did you like the post? Like and share it. 🙂

If you have any suggestions or comments, let us know.

[ ]’s

Ulysses Neves

Related guides: Browse the Microsoft Identity Troubleshooting Index or the Microsoft Entra multifactor authentication topic archive.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Conditional Access report-only: why a successful sign-in can show a policy failure October 9, 2026
  • Microsoft Entra SMS and Voice Retirement: An Admin Preparation Checklist September 24, 2026
  • Microsoft Defender for Identity domain investigation: six questions to ask first September 10, 2026
  • Microsoft Entra Kerberos key rotation: what changes—and what administrators should check September 6, 2026
  • Microsoft Authenticator Will Block Jailbroken Devices in 2026 — What You Need to Know March 17, 2026

Archives

  • October 2026
  • September 2026
  • March 2026
  • September 2024
  • April 2024
  • February 2024
  • December 2023
  • September 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019

Tags

#aaddownleveldevice #adfs #adfscertificate #adfscertificates #adfsmfaadapter #azureauth #azureCA #azuredevice #capolicy #cloudsummit2021 #conditionalaccess #conditionalaccesspolicy #deviceregistration #farmbehavior #gopasswordless #mfaserver #msidentity #namedlocation #securingazure #securingazuread #sslprivatekey #troubleshootingadfs #troubleshootingwaptrust #tshootadfs #waptrust #webapplicationproxy #WHFBcerttrust #whfbdeployment #WHfBhybridsetup #WHfBprovisioning #widdatabase adconnect AD FS authenticationstrength az500 azurepim Azure security cloudsecurity microsoft365 Microsoft Azure Microsoft Entra hybrid join Microsoft Entra ID Microsoft Entra MFA PowerShell WHfB
©2026 Ulysses Neves | Design: Newspaperly WordPress Theme
Ulysses Neves
Gerenciar Consentimento de Cookies
Para fornecer as melhores experiências, usamos tecnologias como cookies para armazenar e/ou acessar informações do dispositivo. O consentimento para essas tecnologias nos permitirá processar dados como comportamento de navegação ou IDs exclusivos neste site. Não consentir ou retirar o consentimento pode afetar negativamente certos recursos e funções.
Funcional Always active
O armazenamento ou acesso técnico é estritamente necessário para a finalidade legítima de permitir a utilização de um serviço específico explicitamente solicitado pelo assinante ou utilizador, ou com a finalidade exclusiva de efetuar a transmissão de uma comunicação através de uma rede de comunicações eletrónicas.
Preferências
O armazenamento ou acesso técnico é necessário para o propósito legítimo de armazenar preferências que não são solicitadas pelo assinante ou usuário.
Estatísticas
O armazenamento ou acesso técnico que é usado exclusivamente para fins estatísticos. O armazenamento técnico ou acesso que é usado exclusivamente para fins estatísticos anônimos. Sem uma intimação, conformidade voluntária por parte de seu provedor de serviços de Internet ou registros adicionais de terceiros, as informações armazenadas ou recuperadas apenas para esse fim geralmente não podem ser usadas para identificá-lo.
Marketing
O armazenamento ou acesso técnico é necessário para criar perfis de usuário para enviar publicidade ou para rastrear o usuário em um site ou em vários sites para fins de marketing semelhantes.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
Ver preferências
  • {title}
  • {title}
  • {title}