Azure AD Connect: Special considerations for instances

Azure AD Connect is most commonly used with the world-wide instance of Azure AD and Microsoft 365. But there are also other instances and these have different requirements for URLs and other special considerations.

Microsoft Cloud Germany

The Microsoft Cloud Germany is a sovereign cloud operated by a German data trustee.

URLs to open in proxy server
+Certificate Revocation Lists

When you sign in to your Azure AD tenant, you must use an account in the domain.

Features currently not present in the Microsoft Cloud Germany:

  • Password writeback is available for preview with Azure AD Connect version 1.1.570.0 and after.
  • Other Azure AD Premium services are not available.

Microsoft Azure Government

The Microsoft Azure Government cloud is a cloud for US government.

This cloud has been supported by earlier releases of DirSync. From build 1.1.180 of Azure AD Connect, the next generation of the cloud is supported. This generation is using US-only based endpoints and has a different list of URLs to open in your proxy server.

URLs to open in proxy server
* (Required for automatic Azure Government tenant detection)
+Certificate Revocation Lists


As of Azure AD Connect version 1.1.647.0, setting the AzureInstance value in the registry is no longer required provided that * is open on your proxy server(s). However, for customers that do not allow Internet connectivity from their Azure AD Connect server(s), the following manual configuration can be used.

Manual Configuration

The following manual configuration steps are used to ensure Azure AD Connect uses Azure Government synchronization endpoints.

  1. Start the Azure AD Connect installation.
  2. When you see the first page where you are supposed to accept the EULA, do not continue but leave the installation wizard running.
  3. Start regedit and change the registry key HKLM\SOFTWARE\Microsoft\Azure AD Connect\AzureInstance to the value 4.
  4. Go back to the Azure AD Connect installation wizard, accept the EULA, and continue. During installation, make sure to use the custom configuration installation path (and not Express installation), then continue the installation as usual.

Next steps

Learn more about Integrating your on-premises identities with Azure Active Directory.