Merge pull request #8726 from MicrosoftDocs/main

Publish main to live on 10/11 @ 10:30 am

Author: v-stsavell

memdocs/autopilot/windows-autopilot-hybrid.md

@@ -174,6 +174,8 @@ If your devices aren't yet enrolled, you can register them yourself. For more in
 
 If you're buying new devices, some OEMs can register the devices for you. For more information, see [OEM registration](oem-registration.md).
 
+### Display registered Autopilot device
+
 Before they're enrolled in Intune, *registered* Autopilot devices are displayed in three places (with names set to their serial numbers):
 
 - The **Autopilot Devices** pane in the Intune in the Azure portal. Select **Device enrollment** > **Windows enrollment** > **Devices**.

memdocs/intune/protect/remove-certificates.md

@@ -50,7 +50,7 @@ Manual deletion of a certificate is a scenario that applies across platforms and
 In this scenario, after the certificate is deleted, the next time the device checks in with Intune it's found to be out of compliance as it is missing the expected certificate. Intune then issues a new certificate to restore the device to compliance. No other action is needed to restore the certificate.
 
 > [!NOTE]
-> SCEP certificates are [removed but not revoked](../certificate-authority-add-scep-overview#removing-certificates) when using a third-party certification authority.
+> SCEP certificates are [removed but not revoked](certificate-authority-add-scep-overview.md#removing-certificates) when using a third-party certification authority.
 
 ## Windows devices
 

memdocs/intune/protect/security-baselines.md

@@ -92,7 +92,7 @@ The following security baseline instances are available for use with Intune. Use
   - [Preview: October 2019 (Edge version 77 and later)](security-baseline-settings-edge.md?pivots=edge-october-2019)
 
 - **Windows 365 Security Baseline**
-  - [Windows 365 Security Baseline version 2101](security-baseline-settings-windows-365.md)
+  - [October 2021](security-baseline-settings-windows-365.md)
 
 After a new version for a profile releases, settings in profiles based on the older versions become read-only. You can continue using those older profiles, including editing their name, description, and assignments, but you won't be able to edit settings for them or create new profiles based on the older versions.
 

windows-365/enterprise/create-azure-network-connection.md

@@ -54,17 +54,18 @@ To create an ANC, you must:
 
 1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Devices** > **Windows 365** (under **Provisioning**) > **Azure network connection** > **Create**.
 2. Depending on the type of ANC you want to create, choose **Azure AD Join** or **Hybrid Azure AD Join**.
-![Screenshot of create connection dropdown](./media/create-azure-network-connection/create-connection-dropdown.png)
+    ![Screenshot of create connection dropdown](./media/create-azure-network-connection/create-connection-dropdown.png)
 3. On the **Network details** page, enter a **Name** for the new connection. The connection name must be unique within the customer tenant.
-![Screenshot of Name field](./media/create-azure-network-connection/connection-name.png)
+    ![Screenshot of Name field](./media/create-azure-network-connection/connection-name.png)
 4. Select a **Subscription** and **Resource group** for the new connection. Create a new resource group to contain your Cloud PC resources. Optionally, you can instead select an existing resource group in the list (which grant Windows 365 permissions to the existing resource group). If you don’t have a [healthy ANC](health-checks.md), you won't be able to proceed.
 5. Select a **Virtual network** and **Subnet**.
 6. Select **Next**.
 7. For hybrid Azure AD join ANCs, on the **AD domain** page, provide the following information:
+
     - **AD domain name**: The DNS name of the Active Directory domain that you want to use for connecting and provisioning Cloud PCs. For example, corp.contoso.com.
 
-  > [!NOTE]
- > If your on-premises Active Directory environment has more than one domain or parent-child domains, be sure to enter the specific domain in which the Cloud PCs need to be domain joined.
+      > [!NOTE]
+      > If your on-premises Active Directory environment has more than one domain or parent-child domains, be sure to enter the specific domain in which the Cloud PCs need to be domain joined.
  
     - **Organizational unit**: (Optional.) An organizational unit (OU) is a container within an Active Directory domain, which can hold users, groups, and computers. Make sure that this OU is enabled to sync with Azure AD Connect. Provisioning will fail if this OU isn't syncing.
     - **AD domain username**: The username, in user principal name (UPN) format, that you want to use for connecting the Cloud PCs to your Active Directory domain. For example, [email protected]. This service account must have permission to join computers to the domain and, if set, the target OU.