Skip to content

Commit 5c4d654

Browse files
authored
Merge pull request #109207 from MicrosoftGuyJFlo/GitHubIssue50518
[Azure AD] Device identity - GitHub Issue 50518
2 parents 1fce816 + 973fa07 commit 5c4d654

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

articles/active-directory/devices/overview.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: devices
88
ms.topic: overview
9-
ms.date: 06/27/2019
9+
ms.date: 03/26/2020
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -44,6 +44,7 @@ To get a device in Azure AD, you have multiple options:
4444
- **Azure AD joined**
4545
- 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.
4646
- Windows 10
47+
- Windows Server 2019 (Server core is not supported)
4748
- **Hybrid Azure AD joined**
4849
- 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.
4950
- 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
8485
With device identity management in Azure AD, you can:
8586

8687
- Simplify the process of bringing and managing devices in Azure AD
87-
- Provide your users with an easy to use access to your organizations cloud-based resources
88+
- Provide your users with an easy to use access to your organization's cloud-based resources
8889

8990
## License requirements
9091

0 commit comments

Comments
 (0)