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/devices/overview.md
+3-2Lines changed: 3 additions & 2 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: overview
9
-
ms.date: 06/27/2019
9
+
ms.date: 03/26/2020
10
10
11
11
ms.author: joflore
12
12
author: MicrosoftGuyJFlo
@@ -44,6 +44,7 @@ To get a device in Azure AD, you have multiple options:
44
44
-**Azure AD joined**
45
45
- Devices that are Azure AD joined are owned by an organization, and are signed in with an Azure AD account belonging to that organization. They exist only in the cloud.
46
46
- Windows 10
47
+
- Windows Server 2019 (Server core is not supported)
47
48
-**Hybrid Azure AD joined**
48
49
- Devices that are hybrid Azure AD joined are owned by an organization, and are signed in with an Azure AD account belonging to that organization. They exist in the cloud and on-premises.
49
50
- Windows 7, 8.1, or 10
@@ -84,7 +85,7 @@ Getting devices in to Azure AD can be done in a self-service manner or a control
84
85
With device identity management in Azure AD, you can:
85
86
86
87
- Simplify the process of bringing and managing devices in Azure AD
87
-
- Provide your users with an easy to use access to your organization’s cloud-based resources
88
+
- Provide your users with an easy to use access to your organization's cloud-based resources
0 commit comments