Good Afternoon Tech Community,

I’d like to understand more about how the process flows when adding a Work or School account to a company pc managed with Intune on both Windows 10 and 11 machine’s.

We have a local AD that’s syncs with Entra. We AutoPilot all our devices and manage with Intune. We utilize Okta for our corporate MFA. Taking a laptop out of the box we have the user sign in using MFA and go through the new computer setup. First thing we ensure, Settings > Accounts > Access work of School = “Connected to “Our Domain” AD domain”. We then go to Settings > Accounts > Email & accounts > Add a work or school account = sign the user in successfully using MFA.

Intune installs our approved software and the user is up and running.

The issue starts when it’s time to change their password. They’re sitting at their desk in the office, change their password, office suite requests they update their credentials, they sign in using MFA and they get the following blank pop up:

They close the window, try again, same outcome. Some employees have to do this 3-6 times before the window populates.

My question is, where in the process might the hang-up occur, keeping in mind some employees don’t get the error at all and some employees don’t get the blank screen more times than others.

1. AD to Entra sync?

2. Entra to Intune config sync?

3. Entra to MFA sync?

4. Intune to local device sync?

5. Network as a whole issue?

6. Windows error because why would any of the above cause a blank Windows notification error?

7. If a Windows error, why doesn’t the notification window not present us with an error code to research a resolution?

The only discussion I can find is: Users receiving blank “Stay signed in to all your apps” dialogue – Microsoft Q&A and the responder just stated it’s “an issue with your local device getting signed in to AAD”. No resolution offered, no starting point to troubleshoot, no hint as to where in the process the device getting signed in to AAD would cause a notification window to present to the user blank without an error code.

The inconsistency of the notification screen being blank is puzzling. If someone could please provide detailed clarification on how we can adjust our environment to permanently resolve this issue I would greatly appreciate it.

Thanks,

Ed

​Good Afternoon Tech Community, I’d like to understand more about how the process flows when adding a Work or School account to a company pc managed with Intune on both Windows 10 and 11 machine’s. We have a local AD that’s syncs with Entra. We AutoPilot all our devices and manage with Intune. We utilize Okta for our corporate MFA. Taking a laptop out of the box we have the user sign in using MFA and go through the new computer setup. First thing we ensure, Settings > Accounts > Access work of School = “Connected to “Our Domain” AD domain”. We then go to Settings > Accounts > Email & accounts > Add a work or school account = sign the user in successfully using MFA. Intune installs our approved software and the user is up and running. The issue starts when it’s time to change their password. They’re sitting at their desk in the office, change their password, office suite requests they update their credentials, they sign in using MFA and they get the following blank pop up: They close the window, try again, same outcome. Some employees have to do this 3-6 times before the window populates. My question is, where in the process might the hang-up occur, keeping in mind some employees don’t get the error at all and some employees don’t get the blank screen more times than others.1. AD to Entra sync?2. Entra to Intune config sync?3. Entra to MFA sync?4. Intune to local device sync?5. Network as a whole issue?6. Windows error because why would any of the above cause a blank Windows notification error?7. If a Windows error, why doesn’t the notification window not present us with an error code to research a resolution? The only discussion I can find is: Users receiving blank “Stay signed in to all your apps” dialogue – Microsoft Q&A and the responder just stated it’s “an issue with your local device getting signed in to AAD”. No resolution offered, no starting point to troubleshoot, no hint as to where in the process the device getting signed in to AAD would cause a notification window to present to the user blank without an error code. The inconsistency of the notification screen being blank is puzzling. If someone could please provide detailed clarification on how we can adjust our environment to permanently resolve this issue I would greatly appreciate it. Thanks,Ed  Read More

​