Hi everyone, today we have a post by Intune Support Engineer Saurabh Sarkar where he talks about some of the options available when setting up Azure AD Connect to enable hybrid identify for the Azure cloud services used in your environment. If you have any feedback for Saurabh be sure to leave it in the comments section below.
Please note that Azure AD Connect is supported by our Azure Active Directory team, however some Intune scenarios rely on it so we thought it would be worth a mention here.
When helping customers deploy Intune as their MDM solution, a question I often get goes something like this:
“How can we integrate our on-premises users with the cloud so they can use the same credentials to access on-prem as well as cloud resources?”
The answer is Azure AD Connect, a lightweight tool that enables hybrid identity so that your users can have one set of credentials that works for both on-premises as well as cloud resources. With Azure AD Connect, users have one less password to remember, and it helps reduce IT helpdesk costs because users are less likely to need assistance and training getting signed in to their cloud-based resources and services. While there’s no question that Azure AD Connect is easy to setup and use, there are a few options available during the setup that you should be knowledgeable about so you can make the best decisions for your environment. In this post I briefly review some of these options, explaining what they do and how they might impact how you use Intune.
Before I begin, I want to preface this by saying that I won’t go into all the details of Azure AD Connect and how it works to deliver a hybrid identify solution. If you need to brush up on this, I’d suggest you start by reading our overview here:
Decisions to be made when installing Azure AD Connect
As I mentioned, I won’t go into all the details and options available when setting up Azure AD Connect, however I do want to talk about the ones below as they’re the ones that come up the most often and they’re the ones that are most likely to effect Intune.
Pass-Through Authentication allows users to sign in to both on-premises and cloud-based applications using the same password, and is used mostly by organizations that want to enforce their on-premises Active Directory security and password policies. The authentication in this case is done by the on-prem domain controller, thus the user's account is subjected to all the password policies created by the on-prem domain administrator. Pass-Through Authentication can be integrated seamlessly with Azure AD conditional access and multi-factor authentication. What’s unique about Pass-Through Authentication is that the passwords are never stored in the cloud in any form, offering protection for on-premises accounts against brute force password attacks in the cloud.
For complete details on Pass-Through Authentication, including the benefits, limitations and details on how it all works, see the following:
Password Hash Synchronization
With Password Hash Synchronization, when a user logs into a computer, the password is subjected to a 1-way hashing process and an RSA key is generated. The main difference in this scenario compared to Pass-Through Authentication is that Azure AD Connect synchronizes a hash of the hash of a user’s password from an on-premises Active Directory instance to Azure AD. The SHA256 password data stored in Azure AD--a hash of the original MD4 hash--is more secure than what is stored in Active Directory. Further, because this SHA256 hash cannot be decrypted, it cannot be brought back to the organization's Active Directory environment and presented as a valid user password in a pass-the-hash attack. Using this is secure because the plain-text version of the password is not exposed.
This is typically used to sign into services like Office 365. In this scenario, the Azure AD instance authenticates users in the cloud, and in contrast to Pass-Through Authentication, the authentication request is not sent to the on-premises DC. When you install Azure AD Connect using the Express Settings option, Password Hash Synchronization is enabled by default.
For complete details on Password Hash Synchronization, see the following:
Choosing a cloud authentication method
Determining which method is best for your environment can involve many variables and organizational preferences so you’ll want to examine all requirements before making a final choice. With that said, here’s a quick look at the main differences between the two:
Pass-Through Authentication provides password validation using a software agent that runs on one or more of your on-prem servers. This agent validates the users directly with your on-premises Active Directory which ensures that the password validation does not happen in the cloud. Companies with a security requirement to immediately enforce on-premises user account states, password policies and sign-in hours might want to use this authentication method.
Password Hash Synchronization is the simplest way to enable authentication for on-premises directory objects in Azure AD because it doesn’t require the deployment of any additional infrastructure. Also, some premium features of Azure AD like Identity Protection and Azure AD Domain Services require Password Hash Synchronization.
For more information on these authentication methods and the considerations when choosing which to employ, see the following:
Device writeback is used to enable device-based conditional access for ADFS-protected devices. This provides additional security as well as assurance that access to applications is granted only to trusted devices. Device writeback enables this by synchronizing all devices registered in Azure back to the on-premises Active Directory. When configured during setup, the following operations are performed to prepare the AD forest:
Note that this only needs to be run on one forest even if Azure AD Connect is being installed in multiple forests.
For more details on Device writeback, see the following:
Password writeback is a feature that allows password changes in the cloud to be securely written back to your existing on-premises Active Directory. When a user resets their cloud password, it also gets checked to ensure it meets your on-premises policy before committing it to the local AD. This is optional during the Azure AD Connect setup process and you can find more information here:
Hybrid Azure AD Join
Hybrid Azure AD joined devices are joined to the on-prem domain as well as to Azure AD. When configured, Azure AD Connect will add a Service Connection Point (SCP) to your on-premises Active Directory which is used to discover your Azure AD tenant information. With that information, a device can then register in Azure AD automatically. This is a great option if your environment has an on-premises AD footprint and you also want the benefits of Azure AD. This is optional and can be enabled during Azure AD Connect setup. You can find more details about configuring hybrid Azure AD join here:
Azure AD Connect has a variety of options that allows it to be customized to the exact requirements of your organization and environment. The ones mentioned here do not represent a comprehensive list of all the capabilities, however it will give you a jump start on some of things that should be considered when developing your own implementation plan. For more information on all the capabilities of Azure AD Connect and how to use it to accomplish your hybrid identity goals, see our product docs beginning here:
Microsoft Intune Support Team
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.