From c5bf71498c35cbf68dd5ecc6270e01a1e2f59db9 Mon Sep 17 00:00:00 2001 From: "Christian C." <46193840+ChristianCB83@users.noreply.github.com> Date: Thu, 21 May 2026 10:55:12 +0100 Subject: [PATCH] Update concept-authentication-qr-code.md Handling support case 2603141420000210 , we can see that the wording of "Known issue" caused false expectations to customer that Microsoft will fix this in the futured. Working internally with Engineering team (Jiju George Thundathil), it was confirmed that this is actually by design and no ETA was shared to change this behavior. --- docs/identity/authentication/concept-authentication-qr-code.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/identity/authentication/concept-authentication-qr-code.md b/docs/identity/authentication/concept-authentication-qr-code.md index 319e7335a46..47b19cd8a18 100644 --- a/docs/identity/authentication/concept-authentication-qr-code.md +++ b/docs/identity/authentication/concept-authentication-qr-code.md @@ -133,7 +133,7 @@ For more information about how to optimize the sign-in experience or suppress ca - Custom tenant endpoint for sign in - Configurable PIN protection policies that define account lockout threshold, duration, or PIN complexity -## Known issue +## Known limitation If you enable QR code authentication for a user, they need to sign-in with an existing authentication method before they can sign in with a QR code for the first time, or they see an **Incorrect QR code** error.