Merge branch 'main' into cmcatee-updateLinks

education/docfx.json

@@ -17,7 +17,8 @@
         "files": [
           "**/*.png",
           "**/*.jpg",
-          "**/*.svg"
+          "**/*.svg",
+          "**/*.gif"
         ],
         "exclude": [
           "**/obj/**",

windows/application-management/docfx.json

@@ -21,6 +21,7 @@
         "files": [
           "**/*.png",
           "**/*.jpg",
+          "**/*.svg",
           "**/*.gif"
         ],
         "exclude": [

windows/client-management/docfx.json

@@ -21,6 +21,7 @@
         "files": [
           "**/*.png",
           "**/*.jpg",
+          "**/*.svg",
           "**/*.gif"
         ],
         "exclude": [

windows/configuration/docfx.json

@@ -21,6 +21,7 @@
         "files": [
           "**/*.png",
           "**/*.jpg",
+          "**/*.svg",
           "**/*.gif"
         ],
         "exclude": [

windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md

@@ -117,8 +117,8 @@ Since existing Windows 365 Cloud PCs already have an existing Azure AD device ID
 **To register devices with Windows Autopatch:**
 
 1. Go to the [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/).
-2. Select **Windows Autopatch** from the left navigation menu.
-3. Select **Devices**.
+2. Select **Devices** from the left navigation menu.
+3. Under the **Windows Autopatch** section, select **Devices**.
 4. Select either the **Ready** or the **Not ready** tab, then select the **Windows Autopatch Device Registration** hyperlink. The Azure Active Directory group blade opens.
 5. Add either devices through direct membership, or other Azure AD dynamic or assigned groups as nested groups in the **Windows Autopatch Device Registration** group.
 

windows/deployment/windows-autopatch/operate/windows-autopatch-update-management.md

@@ -46,7 +46,7 @@ Each deployment ring has a different set of update deployment policies to contro
 Also, during the [device registration process](../deploy/windows-autopatch-device-registration-overview.md), Windows Autopatch assigns each device being registered to one of its deployment rings so that the service has the proper representation of the device diversity across the organization in each deployment ring. The deployment ring distribution is designed to release software update deployments to as few devices as possible to get the signals needed to make a quality evaluation of a given update deployment.
 
 > [!NOTE]
-> Windows Autopatch deployment rings only apply to Windows quality updates. Additionally, you can't create additional deployment rings or use your own for devices managed by the Windows Autopatch service.
+> You can't create additional deployment rings or use your own for devices managed by the Windows Autopatch service.
 
 ### Deployment ring calculation logic
 

windows/privacy/docfx.json

@@ -21,6 +21,7 @@
         "files": [
           "**/*.png",
           "**/*.jpg",
+          "**/*.svg",
           "**/*.gif"
         ],
         "exclude": [

windows/security/threat-protection/microsoft-defender-application-guard/reqs-md-app-guard.md

@@ -8,7 +8,7 @@ ms.pagetype: security
 ms.localizationpriority: medium
 author: denisebmsft
 ms.author: deniseb
-ms.date: 10/20/2021
+ms.date: 08/25/2022
 ms.reviewer: 
 manager: dansimp
 ms.custom: asr
@@ -31,6 +31,9 @@ The threat landscape is continually evolving. While hackers are busy developing
 
 Your environment must have the following hardware to run Microsoft Defender Application Guard.
 
+> [!NOTE]
+> Application Guard currently isn't supported on Windows 11 ARM64 devices.
+
 | Hardware | Description |
 |--------|-----------|
 | 64-bit CPU|A 64-bit computer with minimum four cores (logical processors) is required for hypervisor and virtualization-based security (VBS). For more info about Hyper-V, see [Hyper-V on Windows Server 2016](/windows-server/virtualization/hyper-v/hyper-v-on-windows-server) or [Introduction to Hyper-V on Windows 10](/virtualization/hyper-v-on-windows/about/). For more info about hypervisor, see [Hypervisor Specifications](/virtualization/hyper-v-on-windows/reference/tlfs).|

windows/whats-new/docfx.json

@@ -21,6 +21,7 @@
         "files": [
           "**/**/*.png",
           "**/**/*.jpg",
+          "**/*.svg",
           "**/**/*.gif"
         ],
         "exclude": [