You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/hybrid/reference-connect-government-cloud.md
+20-19Lines changed: 20 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,59 +20,60 @@ This article describes considerations for integrating a hybrid environment with
20
20
> [!NOTE]
21
21
> To integrate an on-premises Microsoft Azure Active Directory (Azure AD) environment with the Azure Government cloud, you need to upgrade to the latest release of [Azure AD Connect](https://www.microsoft.com/download/details.aspx?id=47594).
22
22
23
-
> [!NOTE]
24
-
> For a full list of United States government Department of Defense endpoints, refer to the [documentation](https://docs.microsoft.com/office365/enterprise/office-365-u-s-government-dod-endpoints).
23
+
For a full list of United States government Department of Defense endpoints, refer to the [documentation](https://docs.microsoft.com/office365/enterprise/office-365-u-s-government-dod-endpoints).
25
24
26
25
## Azure AD Pass-through Authentication
27
26
28
-
The following information describes implementation of Azure AD Pass-through Authentication and the Azure Government cloud.
27
+
The following information describes implementation of Pass-through Authentication and the Azure Government cloud.
29
28
30
29
### Allow access to URLs
31
30
32
-
Before deploying the Pass-through Authentication agent, verify whether a firewall exists between your servers and Azure AD. If your firewall or proxy allows Domain Name System (DNS) whitelisting, add the following connections.
31
+
Before you deploy the Pass-through Authentication agent, verify whether a firewall exists between your servers and Azure AD. If your firewall or proxy allows Domain Name System (DNS) blocked or safe programs, add the following connections.
33
32
34
33
> [!NOTE]
35
34
> The following guidance also applies to installing the [Azure AD Application Proxy connector](https://aka.ms/whyappproxy) for Azure Government environments.
36
35
37
36
|URL |How it's used|
38
37
|-----|-----|
39
-
|.msappproxy.us</br>.servicebus.usgovcloudapi.net|The agent uses these URLs to communicate with the Azure AD Cloud Service. |
38
+
|*.msappproxy.us</br>*.servicebus.usgovcloudapi.net|The agent uses these URLs to communicate with the Azure AD cloud service. |
40
39
|mscrl.microsoft.us:80 </br>crl.microsoft.us:80 </br>ocsp.msocsp.us:80 </br>www.microsoft.us:80| The agent uses these URLs to verify certificates.|
41
-
|login.windows.us </br>secure.aadcdn.microsoftonline-p.com </br>.microsoftonline.us </br>.microsoftonline-p.us </br>.msauth.net </br>.msauthimages.net </br>.msecnd.net</br>.msftauth.net </br>.msftauthimages.net</br>.phonefactor.net </br>enterpriseregistration.windows.net</br>management.azure.com </br>policykeyservice.dc.ad.msft.net</br>ctdl.windowsupdate.us:80| The agent uses these URLs during the registration process.
40
+
|login.windows.us </br>secure.aadcdn.microsoftonline-p.com </br>*.microsoftonline.us </br>*.microsoftonline-p.us </br>*.msauth.net </br>*.msauthimages.net </br>*.msecnd.net</br>*.msftauth.net </br>*.msftauthimages.net</br>*.phonefactor.net </br>enterpriseregistration.windows.net</br>management.azure.com </br>policykeyservice.dc.ad.msft.net</br>ctdl.windowsupdate.us:80| The agent uses these URLs during the registration process.
42
41
43
42
### Install the agent for the Azure Government cloud
44
43
45
44
Follow these steps to install the agent for the Azure Government cloud:
46
45
47
-
1. In the commandline terminal, navigate to the folder that contains the executable that installs the agent.
46
+
1. In the command-line terminal, go to the folder that contains the executable file that installs the agent.
48
47
1. Run the following commands, which specify that the installation is for Azure Government.
If you use Pass-through Authentication as your sign-on method, no additional prerequisite check is required. If you use password hash synchronization as your sign-on method and there is a firewall between Azure AD Connect and Azure AD, ensure that:
67
66
68
67
- You use Azure AD Connect version 1.1.644.0 or later.
69
-
- If your firewall or proxy allows DNS whitelisting, add the connections to the *.msappproxy.us URLs over port 443.</br>If not, allow access to the Azure datacenter IP ranges, which are updated weekly. This prerequisite applies only when you enable the feature. It is not required for actual user sign-ons.
68
+
- If your firewall or proxy allows DNS blocked or safe programs, add the connections to the *.msappproxy.us URLs over port 443.
69
+
70
+
If not, allow access to the Azure datacenter IP ranges, which are updated weekly. This prerequisite applies only when you enable the feature. It isn't required for actual user sign-ons.
70
71
71
-
### Roll out Seamless SSO
72
+
### Roll out Seamless Single Sign-On
72
73
73
-
You can gradually roll out Azure AD Seamless Single Sign-On (Seamless SSO) to your users by using the following instructions. You start by adding the Azure AD URL [https://autologon.microsoft.us](https://autologon.microsoft.us) to all or selected users' Intranet zone settings by using Group Policy in Active Directory.
74
+
You can gradually roll out Azure AD Seamless Single Sign-On to your users by using the following instructions. You start by adding the Azure AD URL [https://autologon.microsoft.us](https://autologon.microsoft.us) to all or selected users' Intranet zone settings by using Group Policy in Active Directory.
74
75
75
-
You also need to enable the Intranet zone policy setting **Allow updates to status bar via script through Group Policy**.
76
+
You also need to enable the intranet zone policy setting **Allow updates to status bar via script through Group Policy**.
76
77
77
78
## Browser considerations
78
79
@@ -81,9 +82,9 @@ You also need to enable the Intranet zone policy setting **Allow updates to stat
81
82
Mozilla Firefox doesn't automatically use Kerberos authentication. Each user must manually add the Azure AD URL to their Firefox settings by following these steps:
82
83
83
84
1. Run Firefox and enter **about:config** in the address bar. Dismiss any notifications that you might see.
84
-
1. Search for the **network.negotiate-auth.trusted-uris** preference. </br>This preference lists the sites trusted by Firefox for Kerberos authentication.
85
-
1. Right-click and then select **Modify**.
86
-
1. Enter https://autologon.microsoft.us in the box.
85
+
1. Search for the **network.negotiate-auth.trusted-uris** preference. This preference lists the sites trusted by Firefox for Kerberos authentication.
86
+
1. Right-click the preference name and then select **Modify**.
87
+
1. Enter [**https://autologon.microsoft.us**](https://autologon.microsoft.us**) in the box.
87
88
1. Select **OK** and then reopen the browser.
88
89
89
90
### Microsoft Edge based on Chromium (all platforms)
@@ -96,5 +97,5 @@ If you have overridden the `AuthNegotiateDelegateWhitelist` or `AuthServerWh
0 commit comments