diff --git a/windows/client-management/mdm/azure-ad-and-microsoft-intune-automatic-mdm-enrollment-in-the-new-portal.md b/windows/client-management/mdm/azure-ad-and-microsoft-intune-automatic-mdm-enrollment-in-the-new-portal.md
new file mode 100644
index 0000000000..ddd3fc482b
--- /dev/null
+++ b/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. 
diff --git a/windows/client-management/mdm/images/azure-intune-configure-scope.png b/windows/client-management/mdm/images/azure-intune-configure-scope.png
new file mode 100644
index 0000000000..822ff31511
Binary files /dev/null and b/windows/client-management/mdm/images/azure-intune-configure-scope.png differ
diff --git a/windows/client-management/mdm/images/azure-mdm-intune.png b/windows/client-management/mdm/images/azure-mdm-intune.png
new file mode 100644
index 0000000000..b0f08a51bd
Binary files /dev/null and b/windows/client-management/mdm/images/azure-mdm-intune.png differ
diff --git a/windows/client-management/mdm/mdm-enrollment-of-windows-devices.md b/windows/client-management/mdm/mdm-enrollment-of-windows-devices.md
index bdccbd501f..4fe82b932b 100644
--- a/windows/client-management/mdm/mdm-enrollment-of-windows-devices.md
+++ b/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)