Skip to content

Commit 3b65886

Browse files
acrolinx
1 parent 5337e85 commit 3b65886

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

learn-pr/device-partner-university/introduction-to-entra-id/includes/6-recommendations.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,19 +19,19 @@ These devices are provisioned using Windows Autopilot, joined directly to Entra
1919
>
2020
>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.
2121
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.
2323

2424
## User scenarios
2525

2626
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.
2727

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:
2929

3030
- 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.
3232
- Organizational or regulatory requirements that mandate on-premises management.
3333

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.
3535

3636
| Feature / aspect | Entra Join (Azure AD Join) | Entra Hybrid Join (Hybrid Azure AD Join) |
3737
| -------------------------- | -------------------------- | ----------------------------------------- |

0 commit comments

Comments
 (0)