<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Microsoft Authenticator on JanBakker.tech</title><link>https://janbakker.tech/tags/microsoft-authenticator/</link><description>Recent content in Microsoft Authenticator on JanBakker.tech</description><generator>Hugo</generator><language>en-US</language><copyright>Jan Bakker</copyright><lastBuildDate>Thu, 29 Oct 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://janbakker.tech/tags/microsoft-authenticator/index.xml" rel="self" type="application/rss+xml"/><item><title>A new workaround for authentication strength Conditional Access policy loops: Microsoft Authenticator Credential Registration service principal</title><link>https://janbakker.tech/authentication-strength-conditional-access-policy-loops-microsoft-authenticator-credential-registration-service-principal/</link><pubDate>Thu, 29 Oct 2026 10:00:00 +0200</pubDate><guid>https://janbakker.tech/authentication-strength-conditional-access-policy-loops-microsoft-authenticator-credential-registration-service-principal/</guid><description>&lt;p&gt;Microsoft has added a new workaround for a specific Conditional Access loop that can stop users from registering a passkey in Microsoft Authenticator.&lt;/p&gt;&#10;&lt;p&gt;The loop can happen when a policy targets &lt;strong&gt;All resources&lt;/strong&gt; and requires users to authenticate with a passkey in Authenticator. The policy then requires a passkey when a user is trying to add that same passkey. They can&amp;rsquo;t satisfy the requirement until registration is complete, which causes a loop or lockout.&lt;/p&gt;</description></item></channel></rss>