Skip to content

Commit 7fd0957

Browse files
authored
Merge pull request #84159 from SanDeo-MSFT/patch-18
Update hybrid-azuread-join-plan.md
2 parents 8277c6a + ffaa34d commit 7fd0957

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/active-directory/devices/hybrid-azuread-join-plan.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -111,14 +111,14 @@ These scenarios don't require you to configure a federation server for authentic
111111
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 above requirements are already supported.
112112

113113
- **WIAORMULTIAUTHN claim:** This claim is required to do hybrid Azure AD join for Windows down-level devices.
114-
- **WS-Trust protocol:** This protocol is required to authenticate Windows current hybrid Azure AD joined devices with Azure AD.
115-
When you're using AD FS, you need to enable the following WS-Trust endpoints
116-
- /adfs/services/trust/2005/windowstransport
117-
- /adfs/services/trust/13/windowstransport
118-
- /adfs/services/trust/2005/usernamemixed
119-
- /adfs/services/trust/13/usernamemixed
120-
- /adfs/services/trust/2005/certificatemixed
121-
- /adfs/services/trust/13/certificatemixed
114+
- **WS-Trust protocol:** This protocol is required to authenticate Windows current hybrid Azure AD joined devices with Azure AD.
115+
When you're using AD FS, you need to enable the following WS-Trust endpoints:
116+
`/adfs/services/trust/2005/windowstransport`
117+
`/adfs/services/trust/13/windowstransport`
118+
`/adfs/services/trust/2005/usernamemixed`
119+
`/adfs/services/trust/13/usernamemixed`
120+
`/adfs/services/trust/2005/certificatemixed`
121+
`/adfs/services/trust/13/certificatemixed`
122122

123123
> [!WARNING]
124124
> 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**.

0 commit comments

Comments
 (0)