diff --git a/education/docfx.json b/education/docfx.json index 105c802404..7aabd80dfc 100644 --- a/education/docfx.json +++ b/education/docfx.json @@ -17,7 +17,8 @@ "files": [ "**/*.png", "**/*.jpg", - "**/*.svg" + "**/*.svg", + "**/*.gif" ], "exclude": [ "**/obj/**", diff --git a/windows/application-management/docfx.json b/windows/application-management/docfx.json index 88a99ecd24..1f3a0d4e61 100644 --- a/windows/application-management/docfx.json +++ b/windows/application-management/docfx.json @@ -21,6 +21,7 @@ "files": [ "**/*.png", "**/*.jpg", + "**/*.svg", "**/*.gif" ], "exclude": [ diff --git a/windows/client-management/docfx.json b/windows/client-management/docfx.json index 6c35dc70a8..21740e86df 100644 --- a/windows/client-management/docfx.json +++ b/windows/client-management/docfx.json @@ -21,6 +21,7 @@ "files": [ "**/*.png", "**/*.jpg", + "**/*.svg", "**/*.gif" ], "exclude": [ diff --git a/windows/configuration/docfx.json b/windows/configuration/docfx.json index 18a8bd0b88..ee22abf878 100644 --- a/windows/configuration/docfx.json +++ b/windows/configuration/docfx.json @@ -21,6 +21,7 @@ "files": [ "**/*.png", "**/*.jpg", + "**/*.svg", "**/*.gif" ], "exclude": [ diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md index 61a5e35dfe..52256069b5 100644 --- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md +++ b/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. diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-update-management.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-update-management.md index 983a41a940..982440f7ea 100644 --- a/windows/deployment/windows-autopatch/operate/windows-autopatch-update-management.md +++ b/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 diff --git a/windows/privacy/docfx.json b/windows/privacy/docfx.json index a0c9217603..79774ab7cc 100644 --- a/windows/privacy/docfx.json +++ b/windows/privacy/docfx.json @@ -21,6 +21,7 @@ "files": [ "**/*.png", "**/*.jpg", + "**/*.svg", "**/*.gif" ], "exclude": [ diff --git a/windows/security/threat-protection/microsoft-defender-application-guard/reqs-md-app-guard.md b/windows/security/threat-protection/microsoft-defender-application-guard/reqs-md-app-guard.md index 33f69ede20..92960da468 100644 --- a/windows/security/threat-protection/microsoft-defender-application-guard/reqs-md-app-guard.md +++ b/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).| diff --git a/windows/whats-new/docfx.json b/windows/whats-new/docfx.json index 0c42863822..19bd51f371 100644 --- a/windows/whats-new/docfx.json +++ b/windows/whats-new/docfx.json @@ -21,6 +21,7 @@ "files": [ "**/**/*.png", "**/**/*.jpg", + "**/*.svg", "**/**/*.gif" ], "exclude": [