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: articles/active-directory/device-management-introduction.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,13 +79,13 @@ Implementing Azure AD joined devices provides you with the following benefits:
79
79
80
80
-**Enterprise compliant roaming** of user settings across joined devices. Users don’t need to connect a Microsoft account (for example, Hotmail) to see settings across devices.
81
81
82
-
-**Access to Windows Store for Business** using AAD account. Your users can choose from an inventory of applications pre-selected by the organization.
82
+
-**Access to Windows Store for Business** using an Azure AD account. Your users can choose from an inventory of applications pre-selected by the organization.
83
83
84
84
-**Windows Hello** support for secure and convenient access to work resources.
85
85
86
86
-**Restriction of access** to apps from only devices that meet compliance policy.
87
87
88
-
-**Seamless access to on-premise resources** when the device has line of sight to the on-premise domain controller.
88
+
-**Seamless access to on-premise resources** when the device has line of sight to the on-premises domain controller.
89
89
90
90
91
91
While Azure AD join is primarily intended for organizations that do not have an on-premises Windows Server Active Directory infrastructure, you can certainly also use it in scenarios where:
0 commit comments