Skip to content

Commit dcb28a9

Browse files
committed
edit pass: reference-connect-government-cloud
1 parent a475dc7 commit dcb28a9

File tree

1 file changed

+20
-19
lines changed

1 file changed

+20
-19
lines changed

articles/active-directory/hybrid/reference-connect-government-cloud.md

Lines changed: 20 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -20,59 +20,60 @@ This article describes considerations for integrating a hybrid environment with
2020
> [!NOTE]
2121
> 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).
2222
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).
2524

2625
## Azure AD Pass-through Authentication
2726

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.
2928

3029
### Allow access to URLs
3130

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.
3332

3433
> [!NOTE]
3534
> The following guidance also applies to installing the [Azure AD Application Proxy connector](https://aka.ms/whyappproxy) for Azure Government environments.
3635
3736
|URL |How it's used|
3837
|-----|-----|
39-
|.msappproxy.us</br>.servicebus.usgovcloudapi.net|The agent uses these URLs to communicate with the Azure AD Cloud Service. |
38+
|&#42;.msappproxy.us</br>&#42;.servicebus.usgovcloudapi.net|The agent uses these URLs to communicate with the Azure AD cloud service. |
4039
|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>&#42;.microsoftonline.us </br>&#42;.microsoftonline-p.us </br>&#42;.msauth.net </br>&#42;.msauthimages.net </br>&#42;.msecnd.net</br>&#42;.msftauth.net </br>&#42;.msftauthimages.net</br>&#42;.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.
4241

4342
### Install the agent for the Azure Government cloud
4443

4544
Follow these steps to install the agent for the Azure Government cloud:
4645

47-
1. In the command line 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.
4847
1. Run the following commands, which specify that the installation is for Azure Government.
4948

50-
For Azure AD Pass-through Authentication:
49+
For Pass-through Authentication:
5150

5251
```
5352
AADConnectAuthAgentSetup.exe ENVIRONMENTNAME="AzureUSGovernment"
5453
```
5554

56-
For Azure AD Application Proxy:
55+
For Application Proxy:
5756

5857
```
5958
AADApplicationProxyConnectorInstaller.exe ENVIRONMENTNAME="AzureUSGovernment"
6059
```
6160

62-
## Single sign-on (SSO)
61+
## Single sign-on
6362

6463
### Set up your Azure AD Connect server
6564

6665
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:
6766

6867
- 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 &#42;.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.
7071

71-
### Roll out Seamless SSO
72+
### Roll out Seamless Single Sign-On
7273

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.
7475

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**.
7677

7778
## Browser considerations
7879

@@ -81,9 +82,9 @@ You also need to enable the Intranet zone policy setting **Allow updates to stat
8182
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:
8283

8384
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.
8788
1. Select **OK** and then reopen the browser.
8889

8990
### Microsoft Edge based on Chromium (all platforms)
@@ -96,5 +97,5 @@ If you have overridden the `AuthNegotiateDelegateWhitelist` or `AuthServerWh
9697

9798
## Next steps
9899

99-
[Pass-through Authentication](how-to-connect-pta-quick-start.md#step-1-check-the-prerequisites)
100-
[Single Sign-on](how-to-connect-sso-quick-start.md#step-1-check-the-prerequisites)
100+
- [Pass-through Authentication](how-to-connect-pta-quick-start.md#step-1-check-the-prerequisites)
101+
- [Single Sign-On](how-to-connect-sso-quick-start.md#step-1-check-the-prerequisites)

0 commit comments

Comments
 (0)