SOLVED
Home

Running as different user in Domain joined desktop always uses current user.

%3CLINGO-SUB%20id%3D%22lingo-sub-410562%22%20slang%3D%22en-US%22%3ERunning%20as%20different%20user%20in%20Domain%20joined%20desktop%20always%20uses%20current%20user.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-410562%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20a%20machine%20is%20domain%20joined%2C%20and%20browser%20is%20InPrivate%20the%20current%20user%20credentials%20are%20continually%20used%20rather%20than%20prompting%20and%2For%20using%20new%20credentials.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20something%20Edge%20and%20IE%20can%20handle%20well%20that%20Chrome%20never%20could.%26nbsp%3B%20I%20see%20that%20the%20Chrome%20behavior%20has%20been%20inherited%20rendering%20it%20nearly%20unusable%20in%20scenarios%20where%20different%20accounts%20are%20used%20from%20the%20same%20desktop.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20chance%20that%20removing%20Chromes%20windows%20credentials%20and%20replacing%20with%20Edge%2FIE%20is%20on%20the%20roadmap%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-430507%22%20slang%3D%22en-US%22%3ERe%3A%20Running%20as%20different%20user%20in%20Domain%20joined%20desktop%20always%20uses%20current%20user.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-430507%22%20slang%3D%22en-US%22%3EThank%20you%20for%20your%20questoin%2C%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F316493%22%20target%3D%22_blank%22%3E%40imbusy2%3C%2FA%3E.%20I%20will%20pass%20on%20your%20four%20feedback.%20We%20are%20still%20making%20changes%20to%20the%20way%20we%20handle%20accounts%2C%20so%20keep%20updating%20and%20let%20us%20know%20what%20you%20think.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-430565%22%20slang%3D%22en-US%22%3ERe%3A%20Running%20as%20different%20user%20in%20Domain%20joined%20desktop%20always%20uses%20current%20user.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-430565%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F239638%22%20target%3D%22_blank%22%3E%40Elliot%20Kirk%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20a%20base%20test%2C%20use%20%3CA%20href%3D%22https%3A%2F%2Fportal.azure.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fportal.azure.com%3C%2FA%3E%20and%20use%20the%20switch%20user%20menu%20on%20a%20domain%20based%20workstation.%26nbsp%3B%20No%20matter%20how%20hard%20you%20try%20it%20always%20stays%20with%20the%20currently%20logged%20on%20user.%26nbsp%3B%20Even%20when%20InPrivate.%20Contrast%20that%20with%20a%20non-domain%20machine%2C%20or%20and%20Edge%20based%20InPrivate%20session%20which%20just%20work.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-430977%22%20slang%3D%22en-US%22%3ERe%3A%20Running%20as%20different%20user%20in%20Domain%20joined%20desktop%20always%20uses%20current%20user.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-430977%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F316493%22%20target%3D%22_blank%22%3E%40imbusy2%3C%2FA%3E%26nbsp%3BAre%20you%20using%20the%26nbsp%3B%3CSTRONG%3EDev%3C%2FSTRONG%3E%20build%3F%20Recently%2C%20the%20Edge%20Canary%20build%20was%20changed%20here%20to%20make%20it%20behave%20like%20legacy%20Edge%20such%20that%20Windows%20Authentication%20is%20set%20to%20manual%20in%20InPrivate%20mode.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-431007%22%20slang%3D%22en-US%22%3ERe%3A%20Running%20as%20different%20user%20in%20Domain%20joined%20desktop%20always%20uses%20current%20user.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-431007%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F317619%22%20target%3D%22_blank%22%3E%40ericlaw%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENice%2C%20assume%20that%20will%20be%20in%20the%20next%20dev%2C%20which%20is%20what%20I'm%20running.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOnce%20that%20is%20there%20it%20will%20be%20my%20default.%26nbsp%3B%20Nice%20job%20people.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-433230%22%20slang%3D%22en-US%22%3ERe%3A%20Running%20as%20different%20user%20in%20Domain%20joined%20desktop%20always%20uses%20current%20user.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-433230%22%20slang%3D%22en-US%22%3EI%20just%20tried%20on%20the%20latest%20Canary%20build%20and%20I%20see%20the%20behavior%20that%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F317619%22%20target%3D%22_blank%22%3E%40ericlaw%3C%2FA%3E%20is%20seeing%2C%20where%20Normal%20windows%20log%20me%20in%20automatically%2C%20and%20InPrivate%20windows%20ask%20for%20my%20creds.%20You%20can%20always%20install%20the%20Canary%20build%20side%20by%20side%20with%20the%20Dev%20build%20if%20you%20need%20this%20behavior%20today%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-433258%22%20slang%3D%22en-US%22%3ERe%3A%20Running%20as%20different%20user%20in%20Domain%20joined%20desktop%20always%20uses%20current%20user.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-433258%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F239638%22%20target%3D%22_blank%22%3E%40Elliot%20Kirk%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%20thanks.%26nbsp%3B%20I%20have%20also%20verified%20that%20I%20am%20now%20able%20to%20use%20alternate%20credentials%20in%20the%20canary%20build%20now.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20all%20in%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20'sign%20in%20with%20a%20different%20user'%20feature%20in%20the%20actual%20web%20site%20doesn't%20work%20still%2C%20but%20the%20InPrivate%20is%20an%20acceptable%20workaround.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%20I%20wasn't%20expecting%20this%20any%20time%20soon.%26nbsp%3B%20Expectations%20exceeded!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
imbusy2
New Contributor

When a machine is domain joined, and browser is InPrivate the current user credentials are continually used rather than prompting and/or using new credentials.

 

This is something Edge and IE can handle well that Chrome never could.  I see that the Chrome behavior has been inherited rendering it nearly unusable in scenarios where different accounts are used from the same desktop.

 

Any chance that removing Chromes windows credentials and replacing with Edge/IE is on the roadmap?

6 Replies
Thank you for your questoin, @imbusy2. I will pass on your four feedback. We are still making changes to the way we handle accounts, so keep updating and let us know what you think.

@Elliot Kirk 

 

As a base test, use https://portal.azure.com and use the switch user menu on a domain based workstation.  No matter how hard you try it always stays with the currently logged on user.  Even when InPrivate. Contrast that with a non-domain machine, or and Edge based InPrivate session which just work.

 

 

Solution

@imbusy2 Are you using the Dev build? Recently, the Edge Canary build was changed here to make it behave like legacy Edge such that Windows Authentication is set to manual in InPrivate mode.

@ericlaw 

 

Nice, assume that will be in the next dev, which is what I'm running.

 

Once that is there it will be my default.  Nice job people.

I just tried on the latest Canary build and I see the behavior that @ericlaw is seeing, where Normal windows log me in automatically, and InPrivate windows ask for my creds. You can always install the Canary build side by side with the Dev build if you need this behavior today :)

@Elliot Kirk 

 

Yes thanks.  I have also verified that I am now able to use alternate credentials in the canary build now.

 

I'm all in :)

 

The 'sign in with a different user' feature in the actual web site doesn't work still, but the InPrivate is an acceptable workaround.  

 

Thanks, I wasn't expecting this any time soon.  Expectations exceeded!