You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] - MFA setup first time use (web login enabled) #143
Baseline Info (please complete the following information):
OS: Windows 11 Pro
Version: 25H2
Describe the bug
When weblogin is enabled and a new user is logging into the device. The more information is required pop-up comes up. But after pressing next the main display will display an error. In short "That it's not possible to setup MFA due to a security setting"
To Reproduce
Steps to reproduce the behaviour:
Go to 'weblogin"
Login to a new user (w/o known MFA methods)
Press continue to setup
See error
Expected behaviour
Redirection to the register security information page, so first time users can setup using a compliant (managed) device
Screenshots
If applicable, add screenshots of error messages or logs to help explain the problem.
*text is in dutch but basically says" this page can't be opened, due to security measures you need to view this page from a browser or different device...."
Additional context
Add any other context about the problem here.
I can replicate the issue, though I'll be honest and say I'm not quite sure what setting would actually be causing that behaviour.
I found you can work around the issue by issuing the account a Temporary Access Pass which then allows the login, and once the user is at the desktop they could go change their password/set up other MFA methods on their account.
Given this is quite a niche scenario and using web sign-in suggests this might be a shared device (which is a use-case I've not built for or tested specifically) if anyone wanted to investigate and feed back what might be causing it, as long as it doesn't impact anything else I'd be happy to bring changes into the next version.
I found some additional information regarding the web sign-in, i've yet to confirm if this is actually the case. But it appears that the web sign-in uses a embedded webbrowser and accessing the more information page isn't allowed trough this embedded browser.
Since the web sign-in was broken up untill the most recent Windows 11 version, Microsoft might fix this at some point.
In this example case it's not meant to be a shared desktop, but an OOBE setup laptop delivered to a new colleague.At this moment in this BL u can either use WHfB or Web and to setup WHfB I need to login trough web first.
I'll see if TAP could be a solution or have them enroll MFA trough their phones before recieving a device.
I'll update this if I could confirm this and-or find a solution / work-around.
If the user is taking the device through Autopilot they shouldn't need to use web sign-in and should get to the desktop either being required to configure MFA when initially putting their credentials in, or when going through the WHfB setup.
But yeah, knowing that it's been broken a few times, it wouldn't surprise me if it's just a different type of broken. My mind immediately goes to IE Zones configuration if they're using an embedded browser, but it could be all sorts of things tbh.
Could it be that a Conditional Access policy is configured to only allow registering/updating security information (authentication methods and/or password) when providing MFA?
I have seen this many times. It's a "chicken and egg" issue, you can't register/update MFA methods without providing a valid MFA authentication.
I have a couple of customers now, where the onboarding process involves using a TAP to onboard their phone where they will then have a Microsoft Authenticator app available.
TAP is the way. user shouldnt have a new device and no MFA there is no way for the system to confirm they are who they say they are. IT needs to give them a TAP to start the process.
I've just seen I hadn't sent an update on this, the issue isn't in a CA, as I've tested this with a user and a machine thats been excluded from any CA. It just seems to be that the embedded webbrowser used for this sign-in is either bugged or unsupported by Microsoft.
The work-around is simple, either TAP or login using a password. This can be closed from my end.
Hey, all. We are running into this issue as well. Rather than submit a duplicate issue, I'll respond here - please let me know if you would rather a new issue be opened.
We have found that configuring the setting Configure Web Sign In Allowed Urls with the value mysignins.microsoft.com resolves the issue.
However, it may be worth considering that if an attacker has intercepted the initial temporary password for an account, they may be able to hijack the account and set a new password and MFA before the real user is able to sign in to the computer.
I will submit a PR shortly for your review which includes that setting.
@coredotbin I also posted this reply against your Pull Request (#266). I'm posting here so everyone interested in this sees it.
I’m still not clear on the scenario where this becomes an issue.
With Passwordless Experience enabled, as it is in OIB, TAP is the only credential a user can use to sign in if they haven’t yet registered another authentication method, such as a hardware passkey. I haven’t encountered any issues signing in to Windows with a TAP and then being guided through WHfB setup. Similarly, a TAP can be used to bootstrap Microsoft Authenticator on a mobile device.
One use case I’m curious about is organizations that have gone strictly passwordless with hardware passkeys (with or without WHfB too). If Web Sign-in allows a new user to bootstrap hardware passkey registration directly from the Windows sign-in screen, I can see real value in that and would be supportive of the change.
The question I’d want answered before enabling this in a baseline, though, is whether this registration path remains subject to Conditional Access policies targeting Register security information. For example, if security-method registration is restricted to trusted corporate locations, is that restriction still enforced through Web Sign-in allowed MFA setup? If this path bypasses those controls, it could create a pinhole that a hardened baseline such as OIB should avoid.
Activity
SkipToTheEndpoint commentedon Oct 29, 2025
Hi @kbauwens
I can replicate the issue, though I'll be honest and say I'm not quite sure what setting would actually be causing that behaviour.
I found you can work around the issue by issuing the account a Temporary Access Pass which then allows the login, and once the user is at the desktop they could go change their password/set up other MFA methods on their account.
Given this is quite a niche scenario and using web sign-in suggests this might be a shared device (which is a use-case I've not built for or tested specifically) if anyone wanted to investigate and feed back what might be causing it, as long as it doesn't impact anything else I'd be happy to bring changes into the next version.
kbauwens commentedon Oct 29, 2025
Hi @SkipToTheEndpoint,
I found some additional information regarding the web sign-in, i've yet to confirm if this is actually the case. But it appears that the web sign-in uses a embedded webbrowser and accessing the more information page isn't allowed trough this embedded browser.
Since the web sign-in was broken up untill the most recent Windows 11 version, Microsoft might fix this at some point.
In this example case it's not meant to be a shared desktop, but an OOBE setup laptop delivered to a new colleague.At this moment in this BL u can either use WHfB or Web and to setup WHfB I need to login trough web first.
I'll see if TAP could be a solution or have them enroll MFA trough their phones before recieving a device.
I'll update this if I could confirm this and-or find a solution / work-around.
SkipToTheEndpoint commentedon Oct 29, 2025
If the user is taking the device through Autopilot they shouldn't need to use web sign-in and should get to the desktop either being required to configure MFA when initially putting their credentials in, or when going through the WHfB setup.
But yeah, knowing that it's been broken a few times, it wouldn't surprise me if it's just a different type of broken. My mind immediately goes to IE Zones configuration if they're using an embedded browser, but it could be all sorts of things tbh.
kaspersmjohansen commentedon May 17, 2026
Could it be that a Conditional Access policy is configured to only allow registering/updating security information (authentication methods and/or password) when providing MFA?
I have seen this many times. It's a "chicken and egg" issue, you can't register/update MFA methods without providing a valid MFA authentication.
I have a couple of customers now, where the onboarding process involves using a TAP to onboard their phone where they will then have a Microsoft Authenticator app available.
Michael-eit commentedon May 18, 2026
TAP is the way. user shouldnt have a new device and no MFA there is no way for the system to confirm they are who they say they are. IT needs to give them a TAP to start the process.
kbauwens commentedon May 18, 2026
I've just seen I hadn't sent an update on this, the issue isn't in a CA, as I've tested this with a user and a machine thats been excluded from any CA. It just seems to be that the embedded webbrowser used for this sign-in is either bugged or unsupported by Microsoft.
The work-around is simple, either TAP or login using a password. This can be closed from my end.
coredotbin commentedon Oct 28, 2026
Hey, all. We are running into this issue as well. Rather than submit a duplicate issue, I'll respond here - please let me know if you would rather a new issue be opened.
We have found that configuring the setting
Configure Web Sign In Allowed Urlswith the valuemysignins.microsoft.comresolves the issue.However, it may be worth considering that if an attacker has intercepted the initial temporary password for an account, they may be able to hijack the account and set a new password and MFA before the real user is able to sign in to the computer.
I will submit a PR shortly for your review which includes that setting.
Fix: Add setting 'Configure Web Sign In Allowed Urls'. Resolves SkipT…
CyberChelonian commentedon Oct 30, 2026
@coredotbin I also posted this reply against your Pull Request (#266). I'm posting here so everyone interested in this sees it.
I’m still not clear on the scenario where this becomes an issue.
With Passwordless Experience enabled, as it is in OIB, TAP is the only credential a user can use to sign in if they haven’t yet registered another authentication method, such as a hardware passkey. I haven’t encountered any issues signing in to Windows with a TAP and then being guided through WHfB setup. Similarly, a TAP can be used to bootstrap Microsoft Authenticator on a mobile device.
One use case I’m curious about is organizations that have gone strictly passwordless with hardware passkeys (with or without WHfB too). If Web Sign-in allows a new user to bootstrap hardware passkey registration directly from the Windows sign-in screen, I can see real value in that and would be supportive of the change.
The question I’d want answered before enabling this in a baseline, though, is whether this registration path remains subject to Conditional Access policies targeting Register security information. For example, if security-method registration is restricted to trusted corporate locations, is that restriction still enforced through Web Sign-in allowed MFA setup? If this path bypasses those controls, it could create a pinhole that a hardened baseline such as OIB should avoid.