Skip to content

Commit 5f7a572

Browse files
committed
updating
1 parent 0d99e92 commit 5f7a572

File tree

3 files changed

+9
-8
lines changed

3 files changed

+9
-8
lines changed

articles/active-directory/hybrid/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -340,7 +340,7 @@
340340
href: reference-connect-faq.md
341341
- name: Azure AD Connect Health FAQ
342342
href: reference-connect-health-faq.md
343-
- name: Hybrid Identity Considerations for Azure Government
343+
- name: Hybrid identity considerations for Azure Government
344344
href: reference-connect-government-cloud.md
345345
- name: Azure AD Connect user privacy
346346
href: reference-connect-user-privacy.md

articles/active-directory/hybrid/how-to-connect-pta-quick-start.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ Ensure that the following prerequisites are in place.
6565
- Your Authentication Agents need access to **login.windows.net** and **login.microsoftonline.com** for initial registration. Open your firewall for those URLs as well.
6666
- For certificate validation, unblock the following URLs: **mscrl.microsoft.com:80**, **crl.microsoft.com:80**, **ocsp.msocsp.com:80**, and **www\.microsoft.com:80**. Since these URLs are used for certificate validation with other Microsoft products you may already have these URLs unblocked.
6767

68-
### Azure Government Cloud Prerequisite
68+
### Azure Government cloud prerequisite
6969
Prior to enabling Pass-through Authentication through Azure AD Connect with Step 2, download the latest release of the PTA agent from the Azure Portal. You need to ensure that your agent is versions **x.x.xxx.x** or later. To verify your agent see [Upgrade authentication agents](how-to-connect-pta-upgrade-preview-authentication-agents.md)
7070

7171
After downloading the latest release of the agent, proceed with the below instructions to configure Pass-Through Authentication through Azure AD Connect.

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

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,21 +7,22 @@ manager: daveba
77
ms.service: active-directory
88
ms.workload: identity
99
ms.topic: article
10-
ms.date: 04/13/2020
10+
ms.date: 04/14/2020
1111
ms.subservice: hybrid
1212
ms.author: billmath
1313
ms.collection: M365-identity-device-management
1414
---
1515

16-
# Hybrid Identity Considerations for Azure Government
17-
16+
# Hybrid identity considerations for Azure Government
17+
The following document describes the considerations for implementing a hybrid environment with the Azure Government cloud. This information is provide as reference for administrators and architects who are working with the Azure Government cloud.
1818
> [!NOTE]
1919
> Upgrade to the latest release of [Azure AD Connect](https://www.microsoft.com/download/details.aspx?id=47594).
2020
2121
> [!NOTE]
2222
> For a full list of U.S. Government DoD Endpoints, refer to the [documentation](https://docs.microsoft.com/office365/enterprise/office-365-u-s-government-dod-endpoints)
2323
24-
## Pass Through Authentication
24+
## Pass-Through Authentication
25+
The following information is provided for implementation of pass-through authentication (PTA) and the Azure Government cloud.
2526

2627
### Allow access to URLs
2728
Before deploying the pass-through authentication agent, verify if there is a firewall between your servers and Azure AD. If your firewall or proxy allows DNS whitelisting, whitelist the following connections:
@@ -49,12 +50,12 @@ For Application Proxy:
4950
AADApplicationProxyConnectorInstaller.exe ENVIRONMENTNAME="AzureUSGovernment"
5051
```
5152

52-
## Single Sign On
53+
## Single sign on
5354
Set up your Azure AD Connect server: If you use Pass-through Authentication as your sign-in method, no additional prerequisite check is required. If you use password hash synchronization as your sign-in method, and if there is a firewall between Azure AD Connect and Azure AD, ensure that:
5455
- You use version 1.1.644.0 or later of Azure AD Connect.
5556
- If your firewall or proxy allows DNS whitelisting, whitelist the connections to the *.msapproxy.us URLs over port 443. If not, allow access to the Azure datacenter IP ranges, which are updated weekly. This prerequisite is applicable only when you enable the feature. It is not required for actual user sign-ins.
5657

57-
### Rolling Out Seamless SSO
58+
### Rolling out seamless SSO
5859
You can gradually roll out Seamless SSO to your users using the instructions provided below. You start by adding the following Azure AD URL to all or selected users' Intranet zone settings by using Group Policy in Active Directory:
5960
https://autologon.microsoft.us
6061

0 commit comments

Comments
 (0)