Forum Discussion
Popup Window: Stay signed in to all your apps
MicrosoftFollowing MS document https://docs.microsoft.com/en-us/azure/active-directory/devices/faq#how-can-i-block-users-from-adding-more-work-accounts--azure-ad-registered--on-my-corporate-windows-10-devices
Highlights the following FAQ
How can I block users from adding more work accounts (Azure AD registered) on my corporate Windows 10 devices?
And the solution is to create the following registry key
HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin, "BlockAADWorkplaceJoin"=dword:00000001
This key will block your users from adding additional work accounts to your corporate domain joined, Azure AD joined, or hybrid Azure AD joined Windows 10 devices. This policy can also be used to block domain joined machines from inadvertently getting Azure AD registered with the same user account.
After creating this key you will not recevie this pop up anymore.
Alaa, thank you so much for pointing me towards this documentation. I've been looking for this so long as this has been a huge pain point for our front line help desk support! Our users keep clicking "OK" when that box pops up no matter how many times we train them not to.
- This is already known. I already mentioned the registry key in my initial post. See second link where this register key is mentioned.
The goal of this post was to prevent other systems who are not part of an organization or enterprise. For example, home computers, shared computers, or even worse public computers where you don’t have control of as an organization/enterprise.
I still see this “popup” as a potential security risk, because when people login to check their account temporarily on a system which is not their own personal system, then know the potential risks.
I will describe a scenario. User logs in on a friend’s computer system with Teams. User ignores the popup and press ok. User log offs. The owner of that system opens Teams and still see that his friend previous has logged in. When he would click on this account, he would be able to login without any password asked. This is an example of many ways it can occur.
Even though the user reads the popup, it is so unclear what is mentioned there that people would still press ok without understanding it. IT person would understand it, but a normal user often doesn’t.
This popup should not default join your account to the computer. The default should be an extra check box with an option to join and not the other way around.
Hope this helps the understanding of the security risk that exist with this very annoying popup.By the way. For the people who don’t know how to the delete a joined user account.
- Click the ‘Start’ button, and then click ‘Settings’.
- Click ‘Accounts’.
- Click ‘Access work or school’.
- Click on the user account and click ‘Disconnect’.
- SekoBayo
We are having exactly the samen issue when connecting to AvD using the remote desktop client.
The security issue that we see is as follows
1) A user (A) tries to connect to AvD on a PC that is not managed throght Intune.
2) the user (A) logs in AD and chose directly (OK) when getting the pop up.
3) From that moment the user (A) creds are saved on the PC.
4) Lets say another user (B) uses the same PC and browse to (for example) to office.com then are the data of user (A) exposed. That is a big data leak.
Just like you say Microsoft should change this to a default that wil not add the PC to Azure AD and also do not save the users creds op de PC.
(In our case we are using MFA also and that wil work against the data leak sitiuation)I do not have experience with AvD, but I would think that you can solve this by creating an intune configuration policy to run a powershell script that will add the regarding registry key. I have done this with one of my customers.
Of course, to be able to do this, you would need an intune subscription and the device need to join Azure instead of registering. If you don’t have intune, then your only option is to add the registry key manually by hand.
Correction on previous posts where I have mentioned that computers will join the device to Azure which is not correct. It will register the device to Azure instead of joining it like Jacob1 mentioned in a post above.
