Popup Window: Stay signed in to all your apps

Copper Contributor



This post is maybe not the right place for the discussion, but feel free to place it in the right discussion board. The issue came to light when using Teams though.


When using Microsoft applications like Teams, after you login with your credentials the window "Stay signed in to all your apps" will popup.




I found this is a security risk when logging in from a public windows 10 system. The risk is that when the user doesn't pay attention and click "Ok" button, the device will be AAD joined. After this you will be able to logon Teams without a password.


I want to disable this popup, to prevent users from just pressing the ok button. Is this possible? And if yes, is this only possible for the Teams app?


Online people talk about conditional access, but this is a MEM(Intune) feature and not everyone have the license to do that.


Here is an article that explains very well regarding the "Stay signed in to all your apps" popup in Teams;



I found an article that describes a way to prevent the system from AAD joining with a registry setting;



Handy when you want to prevent this in your organisation. But users will login from there private home systems and maybe from public systems. What then?


If things are unclear, please let me know.

24 Replies

@SekoBayo Hi there did you get anywhere with this? This window is a liability.

Hi @brian_nfc,


Not at all. Opened a Microsoft support ticket and have been told it's by design.

Have also been referred to the Registry change what I have mentioned in my initial post, which only make sense if you are in your own organisation environment. And did get a link to raise up my voice; https://microsoftteams.uservoice.com/forums/555103-public/suggestions/40588795-please-stop-allow-my-... 


Didn’t do it yet, but now just did.

@SekoBayo Appreciate your response. Yes, the reg key is of no value on users' home computers. You can block enrolment of personal devices in Endpoint Manager but it doesn't stop this message and the user still gets an ugly error message that they don't understand.


I don't get why Microsoft wants personal computers to end up in Endpoint Manager. I still feel like there HAS to be a tenant level setting somewhere for blocking this window.

@brian_nfc great to hear that I am not the only one that is thinking this way.


You could check the setting below, but do not know if it will do the trick. I don't have have a tenant where I just can test this.

device settings.png

Also am not able to check it at all because this option is greyed on my customers tenant, cannot figure out why.


You can find this setting under Azure AD > Devices > Device settings.

You say it Joins the device to Azure AD but it registers.
I have the same grayed out issue. I found this saying how to get it enabled, however I get a command error about "-accoutnenabled" so I cannot do it.
Yes, you are right. Thanks for correcting.
In the past few days I had to learn as much as I could about difference in registering and joining!

Following MS document https://docs.microsoft.com/en-us/azure/active-directory/devices/faq#how-can-i-block-users-from-addin...

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.


  1. Click the ‘Start’ button, and then click ‘Settings’.
  2. Click ‘Accounts’.
  3. Click ‘Access work or school’.
  4. Click on the user account and click ‘Disconnect’.

user disconnect.png



Just having the same issue when connecting to AvD using the remote desktop client

Just wanted to say that its not adding the client to the eind point. Its adding the client to Azure Ad devices.

Any how hoorible

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)

@Wahé Yaghyazaryan 


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 @Jacob R  mentioned in a post above.

@Wahé Yaghyazaryan 


You wrote "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."


You are mentioning here with a web browser. When using Edge it will try to do SSO. But I think Edge will detect that an account is registered and ask if you want to synchronize your account. Here you will get asked in a normal way and get the option to choose ‘Synchronize’ or ‘No, thanks’.



Your right. Edge offers to synch.

even if you chose (NO) edge wil sign in with the cached creds. And that is not OK.

Any how it is a NoGo for our AvD project.


@SekoBayo I did some checking/testing recently on this between Windows CSP Vs. Registry Fix. I couldn't make Windows CSP - disallow workplace join work using MEM Intune. https://www.anoopcnair.com/disable-stay-signed-in-to-all-your-apps-intune/