Share via

Why can't Edge handle two accounts, even when they are assigned to two different profiles?

Brian Hauge-Hansen 15 Reputation points
2025-05-16T08:07:21.72+00:00

What I did:

I have signed into Edge with the work AD account used for my PC (account A). This works fine and it signs into Sharepoint etc.

Then I created an additional work profile where I signed in with a different AD account (account B). Bookmarks etc. is synced and everything looks fine.

The problem:

If I use the second profile and go to a webpage that needs to use account B, that this profile is signed into, then it signs in with account A regardless.

This won't because I need it to use the AD account that I have signed into with the profile I'm currently using.

Microsoft Edge | Microsoft Edge development
0 comments No comments

Answer recommended by moderator

Damien Pham (WICLOUD CORPORATION) 1,755 Reputation points Microsoft External Staff Moderator
2025-08-18T03:30:34.4833333+00:00

Hello Brian Hauge-Hansen,

Thank you for reaching out to Microsoft Q&A

This is a common issue of Microsoft Edge + Entra ID (Azure AD) when using multiple work accounts. This happens because:

  • Windows tries single sign-on (SSO) across apps and browsers → tied to the logged-in Windows account.
  • Edge profiles are more about bookmarks, extensions, and sync separation, not full SSO token isolation.
  • Unless account B is also added to Windows under Access work or school (Settings → Accounts → Access work or school), Edge often won’t get a valid PRT for B → and defaults back to A.

Here are some workarounds you can try:

  1. Add account B at Windows level
    • Go to Settings → Accounts → Access work or school → Connect.
    • Add account B as a “work account” (not switching your PC’s main login, just attaching it).
    • This gives WAM a valid token for B, which Edge can then use when you’re in Profile B.
  2. Force profile-based account selection
    • In Edge, check under Settings → Profiles → Profile preferences → ensure "Default profile for external links" is set correctly.
    • For testing, try launching an InPrivate window in Profile B — if it still defaults to A, it’s definitely WAM overriding.
  3. Use “private” or “in-app” login instead of WAM
    • Some orgs configure Edge via policy to disable WAM sign-in (Authentication/EnableImplicitSignin or related ADMX).
    • Without WAM, Edge falls back to web-based auth per profile → isolation works, but you lose seamless SSO.
  4. Last resort isolation
    • If you must keep A and B fully separate, sometimes the only clean option is using one of these:
    • One account in Edge, the other in Chrome/Firefox.
    • Or run Edge in a separate OS user session (Windows fast user switching).

I hope this helps you get things back on track quickly! If you agree with our suggestion, feel free to interact with the system accordingly! 

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.