From b520d1391c6838a4d8a221d49f281af0b2edeec4 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Fri, 29 Apr 2022 09:08:25 -0700 Subject: [PATCH] edits --- .../update/update-compliance-v2-configuration-manual.md | 2 +- .../deployment/update/update-compliance-v2-configuration-mem.md | 2 +- windows/deployment/update/update-compliance-v2-enable.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/deployment/update/update-compliance-v2-configuration-manual.md b/windows/deployment/update/update-compliance-v2-configuration-manual.md index 41e40ffcac..c305ca5636 100644 --- a/windows/deployment/update/update-compliance-v2-configuration-manual.md +++ b/windows/deployment/update/update-compliance-v2-configuration-manual.md @@ -2,7 +2,7 @@ title: Manually configuring devices for Update Compliance (preview) ms.reviewer: manager: dougeby -description: Manually configuring devices for Update Compliance +description: Manually configuring devices for Update Compliance (preview) keywords: update compliance, oms, operations management suite, prerequisites, requirements, updates, upgrades, antivirus, antimalware, signature, log analytics, wdav ms.prod: w10 ms.mktglfcycl: deploy diff --git a/windows/deployment/update/update-compliance-v2-configuration-mem.md b/windows/deployment/update/update-compliance-v2-configuration-mem.md index 91da857807..30da7d5a9d 100644 --- a/windows/deployment/update/update-compliance-v2-configuration-mem.md +++ b/windows/deployment/update/update-compliance-v2-configuration-mem.md @@ -2,7 +2,7 @@ title: Configuring Microsoft Endpoint Manager devices for Update Compliance (preview) ms.reviewer: manager: dougeby -description: Configuring devices that are enrolled in Endpoint Manager for Update Compliance +description: Configuring devices that are enrolled in Endpoint Manager for Update Compliance (preview) keywords: update compliance, oms, operations management suite, prerequisites, requirements, updates, upgrades, antivirus, antimalware, signature, log analytics, wdav, intune, mem ms.prod: w10 ms.mktglfcycl: deploy diff --git a/windows/deployment/update/update-compliance-v2-enable.md b/windows/deployment/update/update-compliance-v2-enable.md index 3f5ef04c9b..f14f6d2bc0 100644 --- a/windows/deployment/update/update-compliance-v2-enable.md +++ b/windows/deployment/update/update-compliance-v2-enable.md @@ -25,7 +25,7 @@ After verifying the [prerequisites](update-compliance-v2-prerequisites.md) are m 1. [Add Update Compliance](#bkmk_add) to your Azure subscription. This step has the following two phases: 1. [Select or create a new Log Analytics workspace](#bkmk_workspace) for use with Update Compliance. - 1. [Add the Update Compliance solution](bkmk_solution) to the Log Analytics workspace. + 1. [Add the Update Compliance solution](#bkmk_solution) to the Log Analytics workspace. 1. Configure the clients to send data to Update compliance. You can configure clients in the following three ways: - Use a [script](update-compliance-configuration-script.md) - Use [Microsoft Endpoint Manager](update-compliance-configuration-mem.md)