Re: Microsoft Edge For Windows Server 2012 R2
Frank Belair
I love being able to create multiple profiles for the various accounts and services I have to use, I am now up to 7. It's great to be able to separate them and just utilize sso to do what I need without constantly having to login to each admin console.
The problem is that every once in a while, my "Connected to Windows" account get associated with a profile and it becomes a royal nuisance. The only way I have seen to fix it is to delete the profile and start over and that hasn't always worked.
On any profile, you can "Sign-Out" or "Sign-Out and Forget" a non-Connected to Windows account. I would like to see the option to "Remove from this Profile" option for the Connected to Windows account.
It would also be great if when setting up a new profile there was a more streamlined process to add a work account that won't let the company manage the pc and is only for this application. Perhaps after adding one work account to Edge, the default should be reversed?
Thanks for the feedback, we've heard this from other users too. Re: the connected to windows accounts, we are working to remove this but since it is cross group collaboration, it may take a while. We eventually would like to just sign you in with the profile account.
Re: Adding an account only to the app, if you select the "This app only" option in the sign in flow where you are asked to manage the device, the account won't be added to the computer and nor will your device get managed.
This is still an issue. When using multiple profiles signed in with Office 365 accounts, it still shows the one connected to windows. This makes it really easy to mess things up, like managing office 365 when your main account has some admin permissions and a secondary account has full permissions. Even when you launch your secondary profile, you get prompted for 'which account' you want to use... and I always seem to click the wrong one. Is there any setting for -not- passing through the 'connected to windows' accounts per profile? If not, what's the best place to up vote feedback?
This is really admin unfriendly, it makes me irrationally upset everytime i try and use my admin profile for admin tasks but Edge decides to use my Windows login details as the default. I get that this is nice for the majority of end users who are interested in syncing browser data with Microsoft but haven't we Administrators suffered enough? (its been a long day)
@josh_bodner Do you have any news on this 2-year old topic? Will this ever be resolved? I, too, use a separate profile to manage M365 and Azure with a different user account and it is really annoying being asked 30 times a day, what account I want to use to sign into Azure. When it really should just use the one account, I already signed in with in the morning.
I'm willing to do the dance, but I think it's what's breaking my ability to use Bookings with my tenant's account (where I am trying to publish my availability). Bookings breaks whenever I try to create a shared Bookings page (I get an 'ugh-oh' error, which is not idiomatic, but that's a different problem...).
The tenant in question is "Connected to Windows" and I am unable to disconnect it.
Hi,
My original setup was an AD hybrid joined device and I had no problems like this.
My new setup is one with an AAD only device linked to my AAD account, and both Edge and Firefox make use of the 'connected to windows' account by kindly logging me into each SSO session with that account.
Edge and Firefox were both used to maintain separation between tenant accounts, the same as @knyhus.
To resolve the issue of having the windows account auto login, the best solution I have found is below. It stops the SSO login and the presentation of credentials for the 'connected to windows account' during the creation of each profile in Edge. I am unsure of the effect on profiles that were configured before this change (I had deleted all mine in anger and swore off ever using Edge again!).
For firefox, in 'about:config', set the 'network.http.windows-sso.enabled' to false.
It disables SSO but does allow for individual container tabs to be logged in with the chosen account, instead of having the SSO login, logout and change chore.
For Edge, with reference to [ -us/deployedge/microsoft-edge-policies#nonremovableprofileenabled] (accessed 2023-03-04), the following registry entry was added:
HKCU:/Software/Microsoft/Policies/Edge
NonRemovableProfileEnabled = DWORD:0x00000000
Please read the product-specific details in this privacy statement, which provide additional relevant information. This statement applies to the interactions Microsoft has with you and the Microsoft products listed below, as well as other Microsoft products that display this statement.
For individuals in the United States, please refer to our U.S. State Data Privacy Notice and the Washington State Consumer Health Data Privacy Policy for additional information about the processing of your personal data, and your rights under applicable U.S. State data privacy laws.
Most Microsoft sites use cookies, small text files placed on your device which web servers utilize in the domain that placed the cookie can retrieve later. We use cookies to store your preferences and settings, help with sign-in, provide personalized ads, and analyze site operations. For more information, see the Cookies and similar technologies section of this privacy statement.
If you have a privacy concern, complaint, or question for the Microsoft Chief Privacy Officer or EU Data Protection Officer, please contact us by using our web form. For more information about contacting Microsoft, including Microsoft Ireland Operations Limited, see the How to contact us section of this privacy statement.
Microsoft collects data from you, through our interactions with you and through our products. You provide some of this data directly, and we get some of it by collecting data about your interactions, use, and experiences with our products. The data we collect depends on the context of your interactions with Microsoft and the choices you make, including your privacy settings and the products and features you use. We also obtain data about you from third parties.
If you represent an organization, such as a business or school, that utilizes Enterprise and Developer Products from Microsoft, please see the Enterprise and developer products section of this privacy statement to learn how we process your data. If you are an end user of a Microsoft product or a Microsoft account provided by your organization, please see the Products provided by your organization and the Microsoft account sections for more information.
You have choices when it comes to the technology you use and the data you share. When we ask you to provide personal data, you can decline. Many of our products require some personal data to provide you with a service. If you choose not to provide data -required to provide you with a product or feature, you cannot use that product or feature. Likewise, where we need to collect personal data by law or to enter into or carry out a contract with you, and you do not provide the data, we will not be able to enter into the contract; or if this relates to an existing product you are using, we may have to suspend or cancel it. We will notify you if this is the case at the time. Where providing the data is optional, and you choose not to share personal data, features like personalization that use such data will not work for you.
We also obtain data from third parties. We protect data obtained from third parties according to the practices described in this statement, plus any additional restrictions imposed by the source of the data. These third-party sources vary over time and include:
The data we collect depends on the context of your interactions with Microsoft and the choices you make (including your privacy settings), the products and features you use, your location, and applicable law.
Interactions. Data about your use of Microsoft products. In some cases, such as search queries, this is data you provide in order to make use of the products. In other cases, such as error reports, this is data we generate. Other examples of interactions data include:
Content. Content of your files and communications you input, upload, receive, create, and control. For example, if you transmit a file using Skype to another Skype user, we need to collect the content of that file to display it to you and the other user. If you receive an email using Outlook.com, we need to collect the content of that email to deliver it to your inbox, display it to you, enable you to reply to it, and store it for you until you choose to delete it. Other content we collect when providing products to you include:
Video or recordings. Recordings of events and activities at Microsoft buildings, retail spaces, and other locations. If you enter Microsoft Store locations or other facilities, or attend a Microsoft event that is recorded, we may process your image and voice data.
d3342ee215