Pass through windows authentication

Thanks in advance. Add a comment. Active Oldest Votes. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses.

Featured on Meta. Regards, D. Wu Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. Monday, August 31, AM. Saturday, August 22, AM. Thanks for your reply. Unfortunately both of those settings are already enabled on my workstation.

I'm still no closer to figuring out why integrated auth doesn't work at all for any site that previously worked! Something else has changed in Windows 10, jsut don't know what! Wednesday, August 26, PM. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services.

Privacy policy. Azure Active Directory Azure AD Pass-through Authentication allows your users to sign in to both on-premises and cloud-based applications using the same passwords. This feature provides your users a better experience - one less password to remember, and reduces IT helpdesk costs because your users are less likely to forget how to sign in.

When users sign in using Azure AD, this feature validates users' passwords directly against your on-premises Active Directory. The DC is the only entity, other than the client machine, that knows the user secret key ; that is, the user password.

After the logon request is delivered to the DC and the DC successfully validates the credentials, the DC refers back to the server those attributes of the user account that the server can use in authorization decisions such as granting the user access to a particular file.

It is the responsibility of the Netlogon Remote Protocol to deliver the logon request to the DC over a secure channel that is established from the server acting as the secure channel client to the DC acting as the secure channel server.

The secure channel is achieved by encrypting the communication traffic with a session key computed using a secret key called a server's machine account password shared by the server and the DC. Upon successful validation of the user credentials on the DC, the Netlogon Remote Protocol delivers the user authorization attributes referred to as user validation information back to the server over the secure channel.