Skip to content

Commit 5c25667

Browse files
authored
Merge pull request #84179 from SanDeo-MSFT/patch-22
Update hybrid-azuread-join-federated-domains.md
2 parents 5f3916a + 55309c5 commit 5c25667

File tree

1 file changed

+16
-4
lines changed

1 file changed

+16
-4
lines changed

articles/active-directory/devices/hybrid-azuread-join-federated-domains.md

Lines changed: 16 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -27,10 +27,22 @@ Like a user in your organization, a device is a core identity you want to protec
2727

2828
Bringing your devices to Azure AD maximizes user productivity through single sign-on (SSO) across your cloud and on-premises resources. You can secure access to your cloud and on-premises resources with [Conditional Access](../active-directory-conditional-access-azure-portal.md) at the same time.
2929

30-
In this tutorial, you learn how to configure hybrid Azure AD join for Active Directory domain-joined computers devices in a federated environment by using Active Directory Federation Services (AD FS).
31-
32-
> [!NOTE]
33-
> If your federated environment uses an identity provider other than AD FS, you must ensure that your identity provider supports the WS-Trust protocol. WS-Trust is required to authenticate your Windows current hybrid Azure AD joined devices with Azure AD. If you have Windows downlevel devices that you want to hybrid Azure AD join, your identity provider must support the WIAORMULTIAUTHN claim.
30+
A federated environment should have an identity provider that supports the following requirements. If you have a federated environment using Active Directory Federation Services (AD FS), then the below requirements are already supported.
31+
32+
- **WIAORMULTIAUTHN claim:** This claim is required to do hybrid Azure AD join for Windows down-level devices.
33+
- **WS-Trust protocol:** This protocol is required to authenticate Windows current hybrid Azure AD joined devices with Azure AD.
34+
When you're using AD FS, you need to enable the following WS-Trust endpoints:
35+
`/adfs/services/trust/2005/windowstransport`
36+
`/adfs/services/trust/13/windowstransport`
37+
`/adfs/services/trust/2005/usernamemixed`
38+
`/adfs/services/trust/13/usernamemixed`
39+
`/adfs/services/trust/2005/certificatemixed`
40+
`/adfs/services/trust/13/certificatemixed`
41+
42+
> [!WARNING]
43+
> Both **adfs/services/trust/2005/windowstransport** or **adfs/services/trust/13/windowstransport** should be enabled as intranet facing endpoints only and must NOT be exposed as extranet facing endpoints through the Web Application Proxy. To learn more on how to disable WS-Trust WIndows endpoints, see [Disable WS-Trust Windows endpoints on the proxy](https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/best-practices-securing-ad-fs#disable-ws-trust-windows-endpoints-on-the-proxy-ie-from-extranet). You can see what endpoints are enabled through the AD FS management console under **Service** > **Endpoints**.
44+
45+
In this tutorial, you learn how to configure hybrid Azure AD join for Active Directory domain-joined computers devices in a federated environment by using AD FS.
3446

3547
You learn how to:
3648

0 commit comments

Comments
 (0)