Managing profiles and sync in Microsoft Edge on Windows 10
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have to connect to multiple directories and services to do my job. Edge only recognizes the last directory I signed into, not the one that my profile points to. So, I have to sign in, with MFA to the wrong directory, switch directories and then sign in again to the correct one. If I can get my different profiles to start InPrivate mode, my shortcuts will point me to the correct directories, and I can reduce the signin hassle.
Managing profiles and sync in Microsoft Edge on Windows 10
Hi mmcst33n,
I understand why you want to reduce the repeated directory switching and MFA prompts, especially when you regularly work across several Microsoft Entra tenants.
Using a separate Edge profile for each work account is the best starting point because each profile keeps its own browser data and sign-in session. From the relevant profile, you can then open Settings and more > New InPrivate window when you need a temporary session.
However, InPrivate browsing only clears browsing history, cookies, and site data after all InPrivate windows are closed. It does not provide complete identity isolation from Windows single sign-on. On Windows 10 and Windows 11, Edge can use the Windows Primary Refresh Token for Microsoft Entra SSO, so a website may still automatically select the Windows account or an unexpected directory even when the window is InPrivate.
For that reason, I would avoid adding external organizations’ accounts under Windows Settings > Accounts > Access work or school unless the relevant administrator has approved it, as doing so may register the device with that organization or apply its management policies.
If separate Edge profiles still redirect to the wrong tenant, consider using each organization’s tenant-specific sign-in URL and ask your organization’s Microsoft Entra administrator whether Windows SSO or tenant sign-in policies are controlling the account selection. For strict separation, separate Windows user sessions or another browser may be more reliable than InPrivate alone. Thank you so much for your understanding.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
AI answer
Create one Windows shortcut per Edge profile and add both the profile selector and -inprivate to each shortcut’s Target.
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --profile-directory="Default" -inprivate
For another profile:
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --profile-directory="Profile 1" -inprivate
Client A - InPrivate and Client B - InPrivate—and launch each one.msedge.exe and only append:--profile-directory="Profile 1" -inprivate
Microsoft documents -inprivate for making a shortcut always open Edge privately; combining it with --profile-directory targets a particular profile.^1^ ^2^
The directory value is normally Default, Profile 1, Profile 2, and so on; it is not necessarily the friendly profile name shown in Edge. Existing profile-specific shortcuts may already contain the correct --profile-directory value—copy that value and add -inprivate.
An InPrivate window can use favorites, saved passwords, and form-fill data from the profile that opened it, but Edge deletes that session’s cookies and site data after all InPrivate windows are closed.^3^
This setup isolates browser cookies, but it does not guarantee isolation from Windows single sign-on. On Windows 10/11, Edge can use the Windows Primary Refresh Token (PRT) to provide Microsoft Entra SSO by injecting the Windows identity into browser authentication requests.^4^ Edge also natively supports PRT-based SSO when signed into a browser profile.^5^
Therefore, test each shortcut:
If it still silently selects the Windows account or wrong directory, the issue is Windows/Edge SSO rather than a retained InPrivate cookie.
If company policy permits it, add the other work account to Windows:
This can make the additional identity available to Windows Web Account Manager rather than leaving only the primary Windows identity available to Edge.^6^
Do not add a customer or external organization’s account at the Windows level without its administrator’s approval, especially on a managed device. If adding the account is prohibited or InPrivate still receives the wrong Windows SSO identity, the supported isolation options are separate Windows user sessions or placing one identity in a different browser.
For organization-managed Edge devices, an administrator can also force InPrivate mode through the InPrivateModeAvailability policy. The value 2 means Forced, and the policy supports per-profile application, but this should be deployed by the organization rather than edited locally on a managed PC.^7^
References