Microsoft Entra hybrid join network requirements
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit 1b2aba2 · +4 −5 lines · also on GitHub
⋯ 4 unchanged lines
55
ms.service: entra-id
66
ms.subservice: devices
77
ms.topic: how-to
8
−ms.date: 02/26/2024
8
+ms.date: 11/25/2024
99
1010
ms.author: joflore
1111
author: MicrosoftGuyJFlo
⋯ 2 unchanged lines
1414
---
1515
# Configure Microsoft Entra hybrid join
1616
17
−Bringing your devices to Microsoft Entra ID maximizes user productivity through single sign-on (SSO) across your cloud and on-premises resources. You can secure access to your resources with [Conditional Access](~/identity/conditional-access/howto-conditional-access-policy-compliant-device.md) at the same time.
17
+Bringing your devices to Microsoft Entra ID maximizes user productivity through single sign-on (SSO) across your cloud and on-premises resources. You can secure access to your resources with [Conditional Access](~/identity/conditional-access/policy-alt-all-users-compliant-hybrid-or-mfa.md) at the same time.
1818
1919
> [!VIDEO https://www.youtube-nocookie.com/embed/hSCVR1oJhFI]
2020
⋯ 57 unchanged lines
7878
7979
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.
8080
81
−- **WIAORMULTIAUTHN claim:** This claim is required to do Microsoft Entra hybrid join for Windows down-level devices.
8281
- **WS-Trust protocol:** This protocol is required to authenticate Windows current Microsoft Entra hybrid joined devices with Microsoft Entra ID. When you're using AD FS, you need to enable the following WS-Trust endpoints:
8382
- `/adfs/services/trust/2005/windowstransport`
8483
- `/adfs/services/trust/13/windowstransport`
⋯ 26 unchanged lines
111110
112111
### Federation caveats
113112
114
−With Windows 10 1803 or newer, if instantaneous Microsoft Entra hybrid join for a federated environment using federation service fails, we rely on Microsoft Entra Connect to sync the computer object in Microsoft Entra ID to complete the device registration for Microsoft Entra hybrid join.
113
+With Windows 10 1803 or newer, if instantaneous Microsoft Entra hybrid join for a federated environment using AD FS fails, we rely on Microsoft Entra Connect to sync the computer object in Microsoft Entra ID to complete the device registration for Microsoft Entra hybrid join.
115114
116115
## Other scenarios
117116
⋯ 24 unchanged lines
142141
## Related content
143142
144143
- [Microsoft Entra hybrid join verification](how-to-hybrid-join-verify.yml)
145
−- [Use Conditional Access to require compliant or Microsoft Entra hybrid joined device](../conditional-access/howto-conditional-access-policy-compliant-device.md)
144
+- [Use Conditional Access to require compliant or Microsoft Entra hybrid joined device](../conditional-access/policy-alt-all-users-compliant-hybrid-or-mfa.md)
146145
- [Planning a Windows Hello for Business Deployment](/windows/security/identity-protection/hello-for-business/hello-planning-guide)
Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 04:17 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.