Merge branch 'master' of https://github.com/MicrosoftDocs/windows-itpro-docs

windows/client-management/mdm/azure-ad-and-microsoft-intune-automatic-mdm-enrollment-in-the-new-portal.md

@@ -0,0 +1,11 @@
+# Azure AD and Microsoft Intune: Automatic MDM enrollment in the new Portal 
+
+Go to your Azure AD Blade, select the Mobility (MDM and MAM) and there should be the Microsoft Intune "App" Visible, select the Microsoft Intune and configure the Blade 
+
+![How to get to the Blade](images/azure-mdm-intune.png) 
+
+Configure the Blade                                                                      
+
+![Configure the Blade](images/azure-intune-configure-scope.png) 
+
+Select all for allow all users to enroll a Device and make it Intune ready, or Some, then you can add a Group of Users. 

windows/client-management/mdm/cm-cellularentries-csp.md

@@ -192,6 +192,7 @@ The following diagram shows the CM\_CellularEntries configuration service provid
 -   Purchase - 95522B2B-A6D1-4E40-960B-05E6D3F962AB  
 -   Administrative - 2FFD9261-C23C-4D27-8DCF-CDE4E14A3364  
 -   Application - 52D7654A-00A8-4140-806C-087D66705306
+-   eSIM provisioning - A36E171F-2377-4965-88FE-1F53EB4B47C0
 
 ## Additional information
 

windows/client-management/mdm/mdm-enrollment-of-windows-devices.md

@@ -112,7 +112,7 @@ All Windows devices can be connected to an Azure AD domain. These devices can be
 
     If the tenant is a cloud-only tenant, this page will change to show the organization's custom branding, and you will be able to enter your password directly on this page. If the tenant is part of a federated domain, you will be redirected to the organization's on-premises federation server, such as Active Directory Federation Services (AD FS) for authentication.
 
-    Based on IT policy, you may also be prompted to provide a second factor of authentication at this point. If your Azure AD tenant has auto-enrollment configured, your device will also be enrolled into MDM during this flow. For more information, see [this blog post](https://blogs.technet.microsoft.com/enterprisemobility/2015/08/14/windows-10-azure-ad-and-microsoft-intune-automatic-mdm-enrollment-powered-by-the-cloud/). If your tenant is not configured for auto-enrollment, you will have to go through the enrollment flow a second time to connect your device to MDM. After you complete the flow, your device will be connected to your organization’s Azure AD domain.
+    Based on IT policy, you may also be prompted to provide a second factor of authentication at this point. If your Azure AD tenant has auto-enrollment configured, your device will also be enrolled into MDM during this flow. For more information, see [these steps](azure-ad-and-microsoft-intune-automatic-mdm-enrollment-in-the-new-portal.md). If your tenant is not configured for auto-enrollment, you will have to go through the enrollment flow a second time to connect your device to MDM. After you complete the flow, your device will be connected to your organization’s Azure AD domain.
 
     ![azure ad signin](images/unifiedenrollment-rs1-13.png)
 

windows/client-management/mdm/mobile-device-enrollment.md

@@ -82,7 +82,7 @@ Value: DisableRegistration
 The following scenarios do not allow MDM enrollments:
 
 -   Built-in administrator accounts on Windows desktop cannot enroll into MDM.
--   Prior to Windows 10, version 1709, standard users on Windows desktop cannot enroll into MDM via the Work access page in **Settings**. Only admin users can enroll. To enroll a standard user into MDM, we recommend using a provisioning package or joining the device to Azure AD from **Settings** -> **System** -> **About**. Starting in Windows 10, version 1709, standard users can enroll in MDM.
+-   Standard users cannot enroll in MDM. Only admin users can enroll.
 -   Windows 8.1 devices enrolled into MDM via enroll-on-behalf-of (EOBO) can upgrade to Windows 10, but the enrollment is not supported. We recommend performing a server initiated unenroll to remove these enrollments and then enrolling after the upgrade to Windows 10 is completed.
 
 ## Enrollment migration