This was a very handy trick for machines which weren’t joined to a domain and needed to authenticate to various sites or applications without requiring the user to type their password over and over throughout the day. The machine would pass the saved credentials automatically without the user seeing any kind of authentication prompt. To be more specific, defining a saved Windows credential in Credential Manager and then adding the same address to the Local Intranet Zone of Internet Explorer used to result in a SSO experience for the user. If your machine is joined to Azure AD the Enterprise Container is what Hello authentication unlocks, but Credential Manager only functions when the default (non-Enterprise) container is unlocked.Ĭredential Manager has been a part of Windows for a long time now and I’ve noticed it seems to have stopped behaving as expected in builds of Windows 10 Enterprise Edition. From what I can tell this has to do with how Microsoft Passport containers work and because Windows Hello will only unlock a single container. But if you bypass Hello (cover your face!) and use a password then Credential Manager is “unlocked” and works exactly as expected. If your machine is joined to Azure AD during the OOBE installation step and you sign in with a Hello method (face, fingerprint, PIN) then Credential Manager is busted.
Updated : Turns out this is not specific to Windows Enterprise or Professional, but actually related to Azure AD Join and Windows Hello.
Windows 10 Enterprise & Credential Manager MaTuesday
0 kommentar(er)
