Before we start with the integration process, we need to get the following ready:
- Valid Azure subscription: You need to have a valid Azure subscription. It can be a pay-as-you-go subscription or a partner subscription, where you have credits applied. For testing purposes, you also can have a free Azure demo account with £150 credits. More info can found at https://azure.microsoft.com/en-gb/offers/ms-azr-0044p/.
- Global administrator account: In order to set up Azure AD, you need to log in to Azure with an account that has global administrator account privileges.
- Access to domain DNS: As part of the Azure AD setup, we need to verify the domain name. This is done using a DNS record. Therefore, engineers need to have access to DNS servers. This is important if you using a public domain name (.com, .org, .net).
- Enterprise administrator account: In order to setup and configure Azure AD Connect, the engineers need to be members of the enterprise administrator group in the on-premises AD setup.
- Connectivity: The server running Azure AD Connect needs to have connectivity to Azure services. If your domain controllers do not have direct access to the internet, prior to deployment, firewall rules need to be modified to allow the Azure service access on recommended ports.
More information about ports can be found at https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-ports. The service URL and IP range information can found at https://support.office.com/en-gb/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-GB&ad=GB.