Azure AD Connect will integrate your on-premises directories with Azure Active Directory. This allows you to provide a common identity for your users for Office 365, Azure, and SaaS applications integrated with Azure AD. This topic will guide you through the planning, deployment, and operation steps. It is a collection of links to the topics related to this area.
Azure AD Connect is the best way to connect your on-premises directory with Azure AD and Office 365. This is a great time to upgrade to Azure AD Connect from Windows Azure Active Directory Sync (DirSync) or Azure AD Sync as these tools are now deprecated and will reach end of support on April 13, 2017.
Why use Azure AD Connect
Integrating your on-premises directories with Azure AD makes your users more productive by providing a common identity for accessing both cloud and on-premises resources. Users and organizations can take advantage of the following:
- Users can use a single identity to access on-premises applications and cloud services such as Office 365.
- Single tool to provide an easy deployment experience for synchronization and sign-in.
- Provides the newest capabilities for your scenarios. Azure AD Connect replaces older versions of identity integration tools such as DirSync and Azure AD Sync. For more information, see Hybrid Identity directory integration tools comparison.
How Azure AD Connect works
Azure Active Directory Connect is made up of three primary components: the synchronization services, the optional Active Directory Federation Services component, and the monitoring component named Azure AD Connect Health.
- Synchronization - This component is responsible for creating users, groups, and other objects. It is also responsible for making sure identity information for your on-premises users and groups is matching the cloud.
- AD FS - Federation is an optional part of Azure AD Connect and can be used to configure a hybrid environment using an on-premises AD FS infrastructure. This can be used by organizations to address complex deployments, such as domain join SSO, enforcement of AD sign-in policy, and smart card or 3rd party MFA.
- Health Monitoring - Azure AD Connect Health can provide robust monitoring and provide a central location in the Azure portal to view this activity. For additional information, see Azure Active Directory Connect Health.
Install Azure AD Connect
You can find the download for Azure AD Connect on Microsoft Download Center.
|Before you start - Hardware and prerequisites|
|Upgrade from DirSync|
|Upgrade from Azure AD Sync or Azure AD Connect|
After installation you should verify it is working as expected and assign licenses to the users.
Next steps to Install Azure AD Connect
|Download Azure AD Connect||Download Azure AD Connect|
|Install using Express settings||Express installation of Azure AD Connect|
|Install using Customized settings||Custom installation of Azure AD Connect|
|Upgrade from DirSync||Upgrade from Azure AD sync tool (DirSync)|
|After installation||Verify the installation and assign licenses|
Learn more about Install Azure AD Connect
You also want to prepare for operational concerns. You might want to have a stand-by server so you easily can fall over if there is a disaster. If you plan to make frequent configuration changes, you should plan for a staging mode server.
|Supported topologies||Topologies for Azure AD Connect|
|Design concepts||Azure AD Connect design concepts|
|Accounts used for installation||More about Azure AD Connect credentials and permissions|
|Operational planning||Azure AD Connect sync: Operational tasks and considerations|
|User sign-in options||Azure AD Connect User sign-in options|
Configure sync features
Azure AD Connect comes with several features you can optionally turn on or are enabled by default. Some features might sometimes require more configuration in certain scenarios and topologies.
Filtering is used when you want to limit which objects are synchronized to Azure AD. By default all users, contacts, groups, and Windows 10 computers are synchronized. You can change the filtering based on domains, OUs, or attributes.
Password synchronization synchronizes the password hash in Active Directory to Azure AD. The end-user can use the same password on-premises and in the cloud but only manage it in one location. Since it uses your on-premises Active Directory as the authority, you can also use your own password policy.
Password writeback will allow your users to change and reset their passwords in the cloud and have your on-premises password policy applied.
Device writeback will allow a device registered in Azure AD to be written back to on-premises Active Directory so it can be used for conditional access.
The prevent accidental deletes feature is turned on by default and protects your cloud directory from numerous deletes at the same time. By default it allows 500 deletes per run. You can change this setting depending on your organization size.
Automatic upgrade is enabled by default for express settings installations and ensures your Azure AD Connect is always up to date with the latest release.
Next steps to configure sync features
|Configure filtering||Azure AD Connect sync: Configure filtering|
|Password synchronization||Azure AD Connect sync: Implement password synchronization|
|Password writeback||Getting started with password management|
|Device writeback||Enabling device writeback in Azure AD Connect|
|Prevent accidental deletes||Azure AD Connect sync: Prevent accidental deletes|
|Automatic upgrade||Azure AD Connect: Automatic upgrade|
Customize Azure AD Connect sync
Azure AD Connect sync comes with a default configuration that is intended to work for most customers and topologies. But there are always situations where the default configuration does not work and must be adjusted. It is supported to make changes as documented in this section and linked topics.
If you have not worked with a synchronization topology before you want to start to understand the basics and the terms used as described in the technical concepts. Azure AD Connect is the evolution of MIIS2003, ILM2007, and FIM2010. Even if some things are identical, a lot has changed as well.
The default configuration assumes there might be more than one forest in the configuration. In those topologies a user object might be represented as a contact in another forest. The user might also have a linked mailbox in another resource forest. The behavior of the default configuration is described in users and contacts.
The configuration model in sync is called declarative provisioning. The advanced attribute flows are using functions to express attribute transformations. You can see and examine the entire configuration using tools which comes with Azure AD Connect. If you need to make configuration changes, make sure you follow the best practices so it is easier to adopt new releases.
Next steps to customize Azure AD Connect sync
|All Azure AD Connect sync articles||Azure AD Connect sync|
|Technical concepts||Azure AD Connect sync: Technical Concepts|
|Understanding the default configuration||Azure AD Connect sync: Understanding the default configuration|
|Understanding users and contacts||Azure AD Connect sync: Understanding Users and Contacts|
|Declarative provisioning||Azure AD Connect Sync: Understanding Declarative Provisioning Expressions|
|Change the default configuration||Best practices for changing the default configuration|
Configure federation features
ADFS can be configured to support multiple domains. For example you might have multiple top domains you need to use for federation.
if your ADFS server has not been configured to automatically update certificates from Azure AD or if you use a non-ADFS solution, then you will be notified when you have to update certificates.
Next steps to configure federation features
|All AD FS articles||Azure AD Connect and federation|
|Configure ADFS with subdomains||Multiple Domain Support for Federating with Azure AD|
|Manage AD FS farm||AD FS management and customizaton with Azure AD Connect|
|Manually updating federation certificates||Renewing Federation Certificates for Office 365 and Azure AD|
More information and references
|Version history||Version history|
|Compare DirSync, Azure ADSync, and Azure AD Connect||Directory integration tools comparison|
|Non-ADFS compatibility list for Azure AD||Azure AD federation compatibility list|
|Configuring a SAML 2.0 Idp||Using a SAML 2.0 Identity Provider (IdP) for Single Sign On|
|Attributes synchronized||Attributes synchronized|
|Monitoring using Azure AD Connect Health||Azure AD Connect Health|
|Frequently Asked Questions||Azure AD Connect FAQ|
Ignite 2015 presentation on extending your on-premises directories to the cloud.