Skip to content

Commit eab9192

Browse files
authored
Merge pull request #107263 from billmath/cloudfix
Cloudfix
2 parents e1e16a8 + e5a52f4 commit eab9192

File tree

3 files changed

+93
-6
lines changed

3 files changed

+93
-6
lines changed

articles/active-directory/hybrid/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -340,6 +340,8 @@
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
344+
href: reference-connect-government-cloud.md
343345
- name: Azure AD Connect user privacy
344346
href: reference-connect-user-privacy.md
345347
- name: Azure AD Connect Health user privacy

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

Lines changed: 11 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: 'Azure AD Pass-through Authentication - Quick start | Microsoft Docs'
2+
title: 'Azure AD Pass-through Authentication - Quickstart | Microsoft Docs'
33
description: This article describes how to get started with Azure Active Directory (Azure AD) Pass-through Authentication.
44
services: active-directory
55
keywords: Azure AD Connect Pass-through Authentication, install Active Directory, required components for Azure AD, SSO, Single Sign-on
@@ -12,13 +12,13 @@ ms.workload: identity
1212
ms.tgt_pltfrm: na
1313
ms.devlang: na
1414
ms.topic: conceptual
15-
ms.date: 04/15/2019
15+
ms.date: 04/13/2020
1616
ms.subservice: hybrid
1717
ms.author: billmath
1818
ms.collection: M365-identity-device-management
1919
---
2020

21-
# Azure Active Directory Pass-through Authentication: Quick start
21+
# Azure Active Directory Pass-through Authentication: Quickstart
2222

2323
## Deploy Azure AD Pass-through Authentication
2424

@@ -61,10 +61,15 @@ Ensure that the following prerequisites are in place.
6161
| **8080** (optional) | Authentication Agents report their status every ten minutes over port 8080, if port 443 is unavailable. This status is displayed on the Azure AD portal. Port 8080 is _not_ used for user sign-ins. |
6262
6363
If your firewall enforces rules according to the originating users, open these ports for traffic from Windows services that run as a network service.
64-
- If your firewall or proxy allows DNS whitelisting, whitelist connections to **\*.msappproxy.net** and **\*.servicebus.windows.net**. If not, allow access to the [Azure datacenter IP ranges](https://www.microsoft.com/download/details.aspx?id=41653), which are updated weekly.
64+
- If your firewall or proxy allows DNS whitelisting, add connections to **\*.msappproxy.net** and **\*.servicebus.windows.net**. If not, allow access to the [Azure datacenter IP ranges](https://www.microsoft.com/download/details.aspx?id=41653), which are updated weekly.
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
69+
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)
70+
71+
After downloading the latest release of the agent, proceed with the below instructions to configure Pass-Through Authentication through Azure AD Connect.
72+
6873
## Step 2: Enable the feature
6974

7075
Enable Pass-through Authentication through [Azure AD Connect](whatis-hybrid-identity.md).
@@ -109,8 +114,8 @@ If you plan to deploy Pass-through Authentication in a production environment, y
109114
Installing multiple Pass-through Authentication Agents ensures high availability, but not deterministic load balancing between the Authentication Agents. To determine how many Authentication Agents you need for your tenant, consider the peak and average load of sign-in requests that you expect to see on your tenant. As a benchmark, a single Authentication Agent can handle 300 to 400 authentications per second on a standard 4-core CPU, 16-GB RAM server.
110115

111116
To estimate network traffic, use the following sizing guidance:
112-
- Each request has a payload size of (0.5K + 1K * num_of_agents) bytes; i.e., data from Azure AD to the Authentication Agent. Here, "num_of_agents" indicates the number of Authentication Agents registered on your tenant.
113-
- Each response has a payload size of 1K bytes; i.e., data from the Authentication Agent to Azure AD.
117+
- Each request has a payload size of (0.5K + 1K * num_of_agents) bytes, that is, data from Azure AD to the Authentication Agent. Here, "num_of_agents" indicates the number of Authentication Agents registered on your tenant.
118+
- Each response has a payload size of 1K bytes, that is, data from the Authentication Agent to Azure AD.
114119

115120
For most customers, three Authentication Agents in total are sufficient for high availability and capacity. You should install Authentication Agents close to your domain controllers to improve sign-in latency.
116121

Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
---
2+
title: 'Azure AD Connect: Hybrid identity considerations for Azure Government'
3+
description: Special considerations for deploying Azure AD Connect with the government cloud.
4+
services: active-directory
5+
author: billmath
6+
manager: daveba
7+
ms.service: active-directory
8+
ms.workload: identity
9+
ms.topic: article
10+
ms.date: 04/14/2020
11+
ms.subservice: hybrid
12+
ms.author: billmath
13+
ms.collection: M365-identity-device-management
14+
---
15+
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 provided as reference for administrators and architects who are working with the Azure Government cloud.
18+
> [!NOTE]
19+
> In order to integrate an on-premises AD environment with the Azure Governemnt cloud, you need to upgrade to the latest release of [Azure AD Connect](https://www.microsoft.com/download/details.aspx?id=47594).
20+
21+
> [!NOTE]
22+
> 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)
23+
24+
## Pass-Through Authentication
25+
The following information is provided for implementation of pass-through authentication (PTA) and the Azure Government cloud.
26+
27+
### Allow access to URLs
28+
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, add the following connections:
29+
> [!NOTE]
30+
> The following guidance also applies to installing the [Application Proxy connector](https://aka.ms/whyappproxy) for Azure Government environments.
31+
32+
|URL |How it's used|
33+
|-----|-----|
34+
|*.msappproxy.us *.servicebus.usgovcloudapi.net|Communication between the agent and the Azure AD cloud service |
35+
|mscrl.microsoft.us:80 crl.microsoft.us:80 </br>ocsp.msocsp.us:80 www.microsoft.us:80| The agent uses these URLs to verify certificates.|
36+
|login.windows.us secure.aadcdn.microsoftonline-p.com *.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.|
37+
38+
### Install the agent for the Azure Government cloud
39+
In order to install the agent for the Azure Government cloud, you must follow these specific steps:
40+
In the command line terminal, navigate to folder where the executable for installing the agent is located.
41+
Run the following command which specifies the installation is for Azure Government.
42+
43+
For Passthrough Authentication:
44+
```
45+
AADConnectAuthAgentSetup.exe ENVIRONMENTNAME="AzureUSGovernment"
46+
```
47+
48+
For Application Proxy:
49+
```
50+
AADApplicationProxyConnectorInstaller.exe ENVIRONMENTNAME="AzureUSGovernment"
51+
```
52+
53+
## Single sign on
54+
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:
55+
- You use version 1.1.644.0 or later of Azure AD Connect.
56+
- If your firewall or proxy allows DNS whitelisting, add 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.
57+
58+
### Rolling out seamless SSO
59+
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:
60+
https://autologon.microsoft.us
61+
62+
In addition, you need to enable an Intranet zone policy setting called Allow updates to status bar via script through Group Policy.
63+
Browser considerations
64+
Mozilla Firefox (all platforms)
65+
Mozilla Firefox doesn't automatically use Kerberos authentication. Each user must manually add the Azure AD URL to their Firefox settings by using the following steps:
66+
1. Run Firefox and enter about:config in the address bar. Dismiss any notifications that you see.
67+
2. Search for the network.negotiate-auth.trusted-uris preference. This preference lists Firefox's trusted sites for Kerberos authentication.
68+
3. Right-click and select Modify.
69+
4. Enter https://autologon.microsoft.us in the field.
70+
5. Select OK and then reopen the browser.
71+
72+
### Microsoft Edge based on Chromium (all platforms)
73+
If you have overridden the `AuthNegotiateDelegateAllowlist` or the `AuthServerAllowlist` policy settings in your environment, ensure that you add Azure AD's URL (https://autologon.microsoft.us) to them as well.
74+
75+
### Google Chrome (all platforms)
76+
If you have overridden the `AuthNegotiateDelegateWhitelist` or the `AuthServerWhitelist` policy settings in your environment, ensure that you add Azure AD's URL (https://autologon.microsoft.us) to them as well.
77+
78+
## Next steps
79+
[Pass-through Authentication](how-to-connect-pta-quick-start.md#step-1-check-the-prerequisites)
80+
[Single Sign-on](how-to-connect-sso-quick-start.md#step-1-check-the-prerequisites)

0 commit comments

Comments
 (0)