deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-20 21:03:42 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Client Management/MDM: URL & text correction

Browse Source 
As outlined in issue ticket #8682 (3rd bullet point in Requirements section is confusing, and linked page is unrelated to the link's text), "The linked page contains basically no information about registering your "enterprise AD" with Azure AD. Instead, that page is a somewhat convoluted set of sections that are sort of unrelated to anything specific."

Thanks to Jeremy T. Bradshaw (JeremyTBradshaw) for identifying and reporting this issue.

Changes proposed:
- change the MDM page link URL to a more precise Azure AD page link
- change the 3rd bullet point text to refer to the new page link

Whitespace changes:
- remove end-of-line redundant whitespace (blanks)

Closes #8682
This commit is contained in:
Trond B. Krokli
2020-11-26 22:08:59 +01:00
committed by GitHub
parent 0bc3da4f6b
commit 8a7931d256
1 changed files with 39 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md
View File

@ -20,7 +20,7 @@ The enrollment into Intune is triggered by a group policy created on your local
Requirements:
- AD-joined PC running Windows 10, version 1709 or later
- The enterprise has configured a mobile device management (MDM) service
- The enterprise AD must be [registered with Azure Active Directory (Azure AD)](azure-active-directory-integration-with-mdm.md)
- The on-premises AD must be [integrated with Azure AD (via Azure AD Connect)](https://docs.microsoft.com/azure/architecture/reference-architectures/identity/azure-ad)
- The device should not already be enrolled in Intune using the classic agents (devices managed using agents will fail enrollment with `error 0x80180026`)
- The minimum Windows Server version requirement is based on the Hybrid Azure AD join requirement. See [How to plan your hybrid Azure Active Directory join implementation](https://docs.microsoft.com/azure/active-directory/devices/hybrid-azuread-join-plan) for more information.