You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/device-partner-university/introduction-to-entra-id/includes/6-recommendations.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,19 +19,19 @@ These devices are provisioned using Windows Autopilot, joined directly to Entra
19
19
>
20
20
>The recommended approach is to integrate devices with Microsoft Entra ID and manage them using cloud-based tools. This enables organizations to optimize resource management, improve operational efficiency, and maintain competitiveness.
21
21
22
-
The recommended approach is to integrate devices with Microsoft Entra ID and manage them using cloud-based tools. This enables organizations to optimize resource management, improve operational efficiency, and maintain competitiveness. Entra join does not prevent access to on-premises resources, and organizations transitioning to cloud-native Windows can continue to use on-premises Active Directory for applications or services that require it.
22
+
The recommended approach is to integrate devices with Microsoft Entra ID and manage them using cloud-based tools. This enables organizations to optimize resource management, improve operational efficiency, and maintain competitiveness. Entra join doesn't prevent access to on-premises resources, and organizations transitioning to cloud-native Windows can continue to use on-premises Active Directory for applications or services that require it.
23
23
24
24
## User scenarios
25
25
26
26
Entra join is the preferred choice for connecting devices to Microsoft Entra ID. It supports cloud-first management, enables modern provisioning with Windows Autopilot, and integrates seamlessly with Microsoft Intune and Microsoft 365 applications.
27
27
28
-
That said, some devices or environments may require on-premises or hybrid join, such as:
28
+
That said, some devices or environments might require on-premises or hybrid join, such as:
29
29
30
30
- Air-gapped networks or devices.
31
-
- Devices running applications with non-standard authentication mechanisms that depend on on-premises Active Directory.
31
+
- Devices running applications with nonstandard authentication mechanisms that depend on on-premises Active Directory.
32
32
- Organizational or regulatory requirements that mandate on-premises management.
33
33
34
-
Using on-premises or hybrid join for a subset of devices does not limit your entire environment. Organizations can mix device join types as needed while keeping Entra join as the default.
34
+
Using on-premises or hybrid join for a subset of devices doesn't limit your entire environment. Organizations can mix device join types as needed while keeping Entra join as the default.
35
35
36
36
| Feature / aspect | Entra Join (Azure AD Join) | Entra Hybrid Join (Hybrid Azure AD Join) |
0 commit comments