How to improve the misunderstanding of conditional access causing an edge authentication loop on the htmd intune blog

Let’s discuss how to fix it Conditional access misunderstanding Causes of Edge Authentication Loop in Intune. Admin who faces problems with Azure Advertising Access Policy which seems to cause A circle When the user accesses Office 365 resources using Microsoft Edge In Windows 11 24H2 Byod device.

This policy is entitled “Requires Application Protection Policy for Edge in Windows for All Users During Browser and NonComplet-V1.0“And continuously asked the user to change the profile on the edge. This device Byod and deliberately excluded from full intune management (Not obey with design).

However, Edge repeatedly asked for authentication or switching profile, creating experience that frustrated. Admin applies this policy to a Windows device using a browser (especially the edge) and included Office 365 application. Admin does not include appropriate devices or those who have trusttype = Served.

To fix the problem, the admin tries several methods but the problem has not been resolved. Admin is confused, can this be a problem with how to deal with EDGE Profile authentication In conditional access scenarios? In this blog post, I will help you finish the problem.

How to improve the misunderstanding of conditional access causes the edge authentication loop in Intune

With this problem, the Admin goal is to secure access using the application protection policy (Mam) For the BYOD scenario without the need Full device registration In Intune. As mentioned above, the admin tried several resolution methods. The table below shows the method that is tried by the admin.

Causes of problems

There are various causes reason For this problem. EDGE may not be able to survive the correct work profile when switching between personal and company context. This leads to repeated instructions to replace the profile or reinuble, especially when Conditional access policy Requires application protection.

How to fix problems

You can follow several methods such as Verification of compliance Steps, configuration of the edge browser, login log analysis. Application Protection Policy adjustments etc. to solve this problem. The following are other methods.

Just use the report mode first

Set Conditional access policy for Report-Mode -To monitor the impact before upholding. This helps identify which users or devices trigger loops without blocking access.

Improve filter and policy assignments

Exclude Byod The user group explicitly from the policy. Use device filter To target devices that are not better managed without triggering MDM registration. Consider segmentation policies based on the type of device trust or Registration status.

Need further assistance or have technical questions?

Join LinkedIn page And TelegAGroup M. To get step -by -step guidelines and the latest news updates. Join us Meeting page to participate in the user group meeting. Also, join WhatsApp community To get the latest news about Microsoft Technologies. We were there Reddit as well.

Author

Anoop C Nair has been Microsoft MVP for 10 consecutive years from 2015 and so on. He is an architect of workplace solutions with more than 22 years of experience in workplace technology. He is a blogger, speaker, and leader of the local user group community. The main focus is on device management technology such as SCCM and Intune. He wrote about technology such as intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career, etc.