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
||[Configuration Manager standalone or co-management with Microsoft Intune](/mem/configmgr/comanage/overview)|
41
41
|**Key capabilities**| SSO to both cloud and on-premises resources |
42
42
|| Conditional Access through Domain join or through Intune if co-managed |
43
-
|| Self-service Password Reset and Windows Hello PIN reset on lock screen |
44
-
|| Enterprise State Roaming across devices |
43
+
||[Self-service Password Reset and Windows Hello PIN reset on lock screen](../authentication/howto-sspr-windows.md)|
45
44
46
45
47
46
@@ -50,12 +49,13 @@ Hybrid Azure AD joined devices require network line of sight to your on-premises
50
49
Use Azure AD hybrid joined devices if:
51
50
52
51
- You support down-level devices running Windows 7 and 8.1.
53
-
- You want to continue to use Group Policy to manage device configuration.
52
+
- You want to continue to use [Group Policy](/mem/configmgr/comanage/faq#my-environment-has-too-many-group-policy-objects-and-legacy-authenticated-apps--do-i-have-to-use-hybrid-azure-ad-) to manage device configuration.
54
53
- You want to continue to use existing imaging solutions to deploy and configure devices.
55
54
- You have Win32 apps deployed to these devices that rely on Active Directory machine authentication.
56
55
57
56
## Next steps
58
57
59
58
-[Plan your hybrid Azure AD join implementation](hybrid-azuread-join-plan.md)
59
+
-[Co-management using Configuration Manager and Microsoft Intune](/mem/configmgr/comanage/overview)
60
60
-[Manage device identities using the Azure portal](device-management-azure-portal.md)
61
61
-[Manage stale devices in Azure AD](manage-stale-devices.md)
Copy file name to clipboardExpand all lines: articles/active-directory/devices/concept-azure-ad-join.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ services: active-directory
6
6
ms.service: active-directory
7
7
ms.subservice: devices
8
8
ms.topic: conceptual
9
-
ms.date: 06/10/2021
9
+
ms.date: 01/26/2022
10
10
11
11
ms.author: joflore
12
12
author: MicrosoftGuyJFlo
@@ -35,11 +35,10 @@ Any organization can deploy Azure AD joined devices no matter the size or indust
35
35
|| Windows Hello for Business |
36
36
|| FIDO2.0 security keys (preview) |
37
37
|**Device management**| Mobile Device Management (example: Microsoft Intune) |
38
-
||Co-management with Microsoft Intune and Microsoft Endpoint Configuration Manager|
38
+
||[Configuration Manager standalone or co-management with Microsoft Intune](/mem/configmgr/comanage/overview)|
39
39
|**Key capabilities**| SSO to both cloud and on-premises resources |
40
40
|| Conditional Access through MDM enrollment and MDM compliance evaluation |
41
-
|| Self-service Password Reset and Windows Hello PIN reset on lock screen |
42
-
|| Enterprise State Roaming across devices |
41
+
||[Self-service Password Reset and Windows Hello PIN reset on lock screen](../authentication/howto-sspr-windows.md)|
43
42
44
43
Azure AD joined devices are signed in to using an organizational Azure AD account. Access to resources in the organization can be further limited based on that Azure AD account and [Conditional Access policies](../conditional-access/howto-conditional-access-policy-compliant-device.md) applied to the device identity.
45
44
@@ -51,15 +50,15 @@ Azure AD joined devices can still maintain single sign-on access to on-premises
51
50
52
51
## Scenarios
53
52
54
-
While Azure AD join is primarily intended for organizations that do not have an on-premises Windows Server Active Directory infrastructure, you can certainly use it in scenarios where:
53
+
While Azure AD join can be used in a variety of scenarios like:
55
54
56
55
- You want to transition to cloud-based infrastructure using Azure AD and MDM like Intune.
57
56
- You can’t use an on-premises domain join, for example, if you need to get mobile devices such as tablets and phones under control.
58
57
- Your users primarily need to access Microsoft 365 or other SaaS apps integrated with Azure AD.
59
58
- You want to manage a group of users in Azure AD instead of in Active Directory. This scenario can apply, for example, to seasonal workers, contractors, or students.
60
-
- You want to provide joining capabilities to workers in remote branch offices with limited on-premises infrastructure.
59
+
- You want to provide joining capabilities to workers who work from home or are in remote branch offices with limited on-premises infrastructure.
61
60
62
-
You can configure Azure AD joined devices for all Windows 10 devices except for Windows 10 Home.
61
+
You can configure Azure AD join for all Windows 10 devices except for Windows 10 Home.
63
62
64
63
The goal of Azure AD joined devices is to simplify:
65
64
@@ -79,6 +78,7 @@ Azure AD Join can be deployed by using any of the following methods:
79
78
## Next steps
80
79
81
80
-[Plan your Azure AD join implementation](azureadjoin-plan.md)
81
+
-[Co-management using Configuration Manager and Microsoft Intune](/mem/configmgr/comanage/overview)
82
82
-[How to manage the local administrators group on Azure AD joined devices](assign-local-admin.md)
83
83
-[Manage device identities using the Azure portal](device-management-azure-portal.md)
84
84
-[Manage stale devices in Azure AD](manage-stale-devices.md)
The goal of Azure AD registered devices is to provide your users with support for the bring your own device (BYOD) or mobile device scenarios. In these scenarios, a user can access your organization’s resources using a personal device.
20
+
The goal of Azure AD registered devices is to provide your users with support for bring your own device (BYOD) or mobile device scenarios. In these scenarios, a user can access your organization’s resources using a personal device.
0 commit comments