Since the new feature update policies setting the minimum Windows 10 OS version are in place, the policies above can be removed from your tenant.
+
## Test Windows 11 feature updates
-You can test Windows 11 deployments by adding devices either through direct membership or by bulk importing them into the Modern Workplace - Windows 11 Pre-Release Test Devices Azure AD group. There’s a separate Windows feature update policy (**Modern Workplace DSS Policy [Windows 11]**) targeted to this Azure AD group, and its configuration is set as follows:
+You can test Windows 11 deployments by adding devices either through direct membership or by bulk importing them into the **Modern Workplace - Windows 11 Pre-Release Test Devices** Azure AD group. There’s a separate Windows feature update policy (**Modern Workplace DSS Policy [Windows 11]**) targeted to this Azure AD group, and its configuration is set as follows:
| Policy name | Feature update version | Rollout options | First deployment ring availability | Final deployment ring availability | Day between deployment rings | Support end date |
| ----- | ----- | ----- | ----- | ----- | ----- | ----- |
| Modern Workplace DSS Policy [Windows 11] | Windows 11 22H2 | Make update available as soon as possible | N/A | N/A | N/A | 10/13/2025, 7:00PM |
+> [!IMPORTANT]
+> Windows Autopatch neither applies its deployment ring distribution, nor configure [Windows Update for Business gradual rollout settings](https://learn.microsoft.com/mem/intune/protect/windows-update-rollout-options) in the Feature update policy **Modern Workplace DSS Policy [Windows 11]**.Once devices are added into the **Modern Workplace - Windows 11 Pre-Release Test Devices** Azure AD group, they can all apply the Windows 11 22H2 feature update with no gradual rollout or deployment ring capabilities.
+
## Manage Windows feature update deployments
-Windows Autopatch uses Microsoft Intune’s built-in solution, which uses configuration service providers (CSPs), for pausing and resuming both [Windows quality](windows-autopatch-wqu-overview.md#pausing-and-resuming-a-release) and feature updates.
+Windows Autopatch uses Microsoft Intune’s built-in solution, which uses configuration service providers (CSPs), for pausing and resuming both [Windows quality and feature updates](windows-autopatch-wqu-overview.md#pausing-and-resuming-a-release).
Windows Autopatch provides a permanent pause of a Windows feature update deployment. The Windows Autopatch service automatically extends the 35 day pause limit (permanent pause) established by Microsoft Intune on your behalf. The deployment remains permanently paused until you decide to resume it.
@@ -86,7 +91,7 @@ Windows Autopatch provides a permanent pause of a Windows feature update deploym
Windows Autopatch doesn’t support the rollback of Windows Feature updates.
> [!CAUTION]
-> It’s not recommended to use [Microsoft Intune’s capabilities](/mem/intune/protect/windows-10-update-rings#manage-your-windows-update-rings) to pause and rollback a Windows feature update. However, if you choose to pause, resume and/or roll back from Intune, Windows Autopatch is **not** responsible for any problems that arise from rolling back the feature update.
+> It’s not recommended to use [Microsoft Intune’s capabilities](/mem/intune/protect/windows-10-update-rings#manage-your-windows-update-rings) to pause and rollback a Windows feature update. However, if you choose to pause, resume and/or roll back from Intune, Windows Autopatch is **not** responsible for any problems that arise from rolling back the Windows feature update.
## Contact support
From 0d5112966455ae88d50e37a42ff8ece18c3ae782 Mon Sep 17 00:00:00 2001
From: Andre Della Monica
Date: Wed, 1 Feb 2023 15:46:24 -0600
Subject: [PATCH 35/98] More updates
---
.../operate/windows-autopatch-fu-overview.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-fu-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-fu-overview.md
index c29fcd0299..12c9c732f1 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-fu-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-fu-overview.md
@@ -50,7 +50,7 @@ If your tenant is enrolled with Windows Autopatch, you can see the following pol
> If you’re ahead of the current minimum OS version enforced by Windows Autopatch in your organization, you can [edit Windows Autopatch’s default Windows feature update policy and select your desired targeted version](/mem/intune/protect/windows-10-feature-updates#create-and-assign-feature-updates-for-windows-10-and-later-policy).
> [!NOTE]
-> The four minimum Windows 10 OS version feature update policies were introduced in Windows Autopatch in the 2212 release milestone. Its creation automatically unassigns the previous four feature update policies targeting Windows 10 21H2 from all four Windows Autopatch deployment rings:**Modern Workplace DSS Policy [Test]**
**Modern Workplace DSS Policy [First]**
**Modern Workplace DSS Policy [Fast]**
**Modern Workplace DSS Policy [Broad]**
Since the new feature update policies setting the minimum Windows 10 OS version are in place, the policies above can be removed from your tenant.
+> The four minimum Windows 10 OS version feature update policies were introduced in Windows Autopatch in the 2212 release milestone. Its creation automatically unassigns the previous four feature update policies targeting Windows 10 21H2 from all four Windows Autopatch deployment rings:**Modern Workplace DSS Policy [Test]**
**Modern Workplace DSS Policy [First]**
**Modern Workplace DSS Policy [Fast]**
**Modern Workplace DSS Policy [Broad]**
Since the new feature update policies setting the minimum Windows 10 OS version are already in place, the policies above can be safely removed from your tenant.
## Test Windows 11 feature updates
@@ -67,7 +67,7 @@ You can test Windows 11 deployments by adding devices either through direct memb
Windows Autopatch uses Microsoft Intune’s built-in solution, which uses configuration service providers (CSPs), for pausing and resuming both [Windows quality and feature updates](windows-autopatch-wqu-overview.md#pausing-and-resuming-a-release).
-Windows Autopatch provides a permanent pause of a Windows feature update deployment. The Windows Autopatch service automatically extends the 35 day pause limit (permanent pause) established by Microsoft Intune on your behalf. The deployment remains permanently paused until you decide to resume it.
+Windows Autopatch provides a permanent pause of a Windows feature update deployment. The Windows Autopatch service automatically extends the 35-day pause limit (permanent pause) established by Microsoft Intune on your behalf. The deployment remains permanently paused until you decide to resume it.
## Pausing and resuming a release
@@ -84,7 +84,7 @@ Windows Autopatch provides a permanent pause of a Windows feature update deploym
9. Select **Okay**.
> [!NOTE]
-> Pausing an update can take up to eight hours to be applied to devices. This happens because Windows Autopatch uses Microsoft Intune as its management solution, and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
+> Pausing or resuming an update can take up to eight hours to be applied to devices. This happens because Windows Autopatch uses Microsoft Intune as its management solution, and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
## Rollback
From 12f09b4ff04b32078eee6485480b9adf1ec3fa36 Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Wed, 1 Feb 2023 14:03:50 -0800
Subject: [PATCH 36/98] Update windows-autopatch-fu-overview.md
---
.../operate/windows-autopatch-fu-overview.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-fu-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-fu-overview.md
index 12c9c732f1..b8c1b604fe 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-fu-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-fu-overview.md
@@ -50,7 +50,7 @@ If your tenant is enrolled with Windows Autopatch, you can see the following pol
> If you’re ahead of the current minimum OS version enforced by Windows Autopatch in your organization, you can [edit Windows Autopatch’s default Windows feature update policy and select your desired targeted version](/mem/intune/protect/windows-10-feature-updates#create-and-assign-feature-updates-for-windows-10-and-later-policy).
> [!NOTE]
-> The four minimum Windows 10 OS version feature update policies were introduced in Windows Autopatch in the 2212 release milestone. Its creation automatically unassigns the previous four feature update policies targeting Windows 10 21H2 from all four Windows Autopatch deployment rings:**Modern Workplace DSS Policy [Test]**
**Modern Workplace DSS Policy [First]**
**Modern Workplace DSS Policy [Fast]**
**Modern Workplace DSS Policy [Broad]**
Since the new feature update policies setting the minimum Windows 10 OS version are already in place, the policies above can be safely removed from your tenant.
+> The four minimum Windows 10 OS version feature update policies were introduced in Windows Autopatch in the 2212 release milestone. Its creation automatically unassigns the previous four feature update policies targeting Windows 10 21H2 from all four Windows Autopatch deployment rings:- **Modern Workplace DSS Policy [Test]**
- **Modern Workplace DSS Policy [First]**
- **Modern Workplace DSS Policy [Fast]**
- **Modern Workplace DSS Policy [Broad]**
Since the new Windows feature update policies that set the minimum Windows 10 OS version are already in place, the Modern Workplace DSS policies can be safely removed from your tenant.
## Test Windows 11 feature updates
@@ -61,11 +61,11 @@ You can test Windows 11 deployments by adding devices either through direct memb
| Modern Workplace DSS Policy [Windows 11] | Windows 11 22H2 | Make update available as soon as possible | N/A | N/A | N/A | 10/13/2025, 7:00PM |
> [!IMPORTANT]
-> Windows Autopatch neither applies its deployment ring distribution, nor configure [Windows Update for Business gradual rollout settings](https://learn.microsoft.com/mem/intune/protect/windows-update-rollout-options) in the Feature update policy **Modern Workplace DSS Policy [Windows 11]**.Once devices are added into the **Modern Workplace - Windows 11 Pre-Release Test Devices** Azure AD group, they can all apply the Windows 11 22H2 feature update with no gradual rollout or deployment ring capabilities.
+> Windows Autopatch neither applies its deployment ring distribution, nor configures the [Windows Update for Business gradual rollout settings](/mem/intune/protect/windows-update-rollout-options) in the **Modern Workplace DSS Policy [Windows 11]** policy.Once devices are added to the **Modern Workplace - Windows 11 Pre-Release Test Devices** Azure AD group, the devices can be offered the Windows 11 22H2 feature update at the same time.
## Manage Windows feature update deployments
-Windows Autopatch uses Microsoft Intune’s built-in solution, which uses configuration service providers (CSPs), for pausing and resuming both [Windows quality and feature updates](windows-autopatch-wqu-overview.md#pausing-and-resuming-a-release).
+Windows Autopatch uses Microsoft Intune’s built-in solution, which uses configuration service providers (CSPs), for pausing and resuming both [Windows quality](windows-autopatch-wqu-overview.md#pausing-and-resuming-a-release) and [Windows feature updates](#pausing-and-resuming-a-release).
Windows Autopatch provides a permanent pause of a Windows feature update deployment. The Windows Autopatch service automatically extends the 35-day pause limit (permanent pause) established by Microsoft Intune on your behalf. The deployment remains permanently paused until you decide to resume it.
From fd3a80d1d5652335e0c8e3741fe2eb538dd192e1 Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Wed, 1 Feb 2023 14:09:03 -0800
Subject: [PATCH 37/98] Update windows-autopatch-fu-overview.md
---
.../operate/windows-autopatch-fu-overview.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-fu-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-fu-overview.md
index b8c1b604fe..64f6442d2d 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-fu-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-fu-overview.md
@@ -14,10 +14,10 @@ msreviewer: andredm7
# Windows feature updates
-Microsoft provides robust mobile device management (MDM) solutions such as Microsoft Intune, Windows Update for Business, Configuration Manager etc. However, the administration of these solutions to keep Windows devices up to date with the latest Windows feature releases rests on your organization’s IT admins. The Windows feature update process is considered one of the most expensive and time consuming tasks for IT since it requires incremental rollout and validation.
+Microsoft provides robust mobile device management (MDM) solutions such as Microsoft Intune, Windows Update for Business, Configuration Manager etc. However, the administration of these solutions to keep Windows devices up to date with the latest Windows feature releases rests on your organization’s IT admins. The Windows feature update process is considered one of the most expensive and time consuming tasks for IT since it requires incremental rollout and validation. Windows feature updates:
-- Fixes known bugs to keep Windows devices protected against behavioral issues.
-- New features to boost end-user productivity.
+- Keep Windows devices protected against behavioral issues.
+- Provide new features to boost end-user productivity.
Windows Autopatch makes it easier and less expensive for you to keep your Windows devices up to date so you can focus on running your core businesses while Windows Autopatch runs update management on your behalf.
From 88ca572ece1a27f46b1590e7dd81fcdff59dee41 Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Wed, 1 Feb 2023 14:39:00 -0800
Subject: [PATCH 38/98] Tweak from Harman.
---
.../prepare/windows-autopatch-fix-issues.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md b/windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md
index 8e9d0f1a63..776fb296c0 100644
--- a/windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md
+++ b/windows/deployment/windows-autopatch/prepare/windows-autopatch-fix-issues.md
@@ -45,13 +45,13 @@ This setting must be turned on to avoid a "lack of permissions" error when we in
| ----- | ----- |
| Not ready | Allow access to unlicensed admins should be turned on. Without this setting enabled, errors can occur when we try to access your Azure AD organization for service. You can safely enable this setting without worrying about security implications. The scope of access is defined by the roles assigned to users, including our operations staff.For more information, see [Unlicensed admins](/mem/intune/fundamentals/unlicensed-admins). |
-### Deployment rings for Windows 10 or later
+### Windows 10 and later update rings
-Your "Windows 10 deployment ring" policy in Intune must not target any Windows Autopatch devices.
+Your "Windows 10 and later update ring" policy in Intune must not target any Windows Autopatch devices.
| Result | Meaning |
| ----- | ----- |
-| Not ready | You have an "update ring" policy that targets all devices, all users, or both.
To resolve, change the policy to use an assignment that targets a specific Azure Active Directory (AD) group that doesn't include any Windows Autopatch devices.
For more information, see [Manage Windows 10 software updates in Intune](/mem/intune/protect/windows-update-for-business-configure).
|
+| Not ready | You have an "update ring" policy that targets all devices, all users, or both.To resolve, change the policy to use an assignment that targets a specific Azure Active Directory (AD) group that doesn't include any Windows Autopatch devices.
For more information, see [Manage Windows 10 and later software updates in Intune](/mem/intune/protect/windows-update-for-business-configure).
|
| Advisory | Both the **Modern Workplace Devices - All** and **Modern Workplace - All** Azure AD groups are groups that we create after you enroll in Windows Autopatch.You can continue with enrollment. However, you must resolve the advisory prior to deploying your first device. To resolve the advisory, see [Maintain the Windows Autopatch environment](../operate/windows-autopatch-maintain-environment.md).
|
## Azure Active Directory settings
From b7ad1499d9eeb181607a09a8ec1a06da83c0dcc4 Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Wed, 1 Feb 2023 17:18:53 -0800
Subject: [PATCH 39/98] Removed silly period
---
.../whats-new/windows-autopatch-whats-new-2023.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md
index 5f09e58ac0..13f228bf15 100644
--- a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md
+++ b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md
@@ -25,7 +25,7 @@ Minor corrections such as typos, style, or formatting issues aren't listed.
| Article | Description |
| ----- | ----- |
| [Changes made at tenant enrollment](../references/windows-autopatch-changes-to-tenant.md) | Updated Feature update policies section with Windows Autopatch - DSS Policy [deployment ring] |
-| [Register your devices](../deploy/windows-autopatch-register-devices.md) |- Updated the Built-in roles required for registration section.
- Added more information about assigning less-privileged user accounts
|
+| [Register your devices](../deploy/windows-autopatch-register-devices.md) |- Updated the Built-in roles required for registration section
- Added more information about assigning less-privileged user accounts
|
## January 2023
From 05a787077c858c12fa864bf93d475caa063f8f17 Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Wed, 1 Feb 2023 17:28:50 -0800
Subject: [PATCH 40/98] Tweaks
---
.openpublishing.redirection.json | 10 ++++++++++
windows/deployment/windows-autopatch/TOC.yml | 4 ++--
...> windows-autopatch-feature-update-end-user-exp.md} | 0
...md => windows-autopatch-feature-update-overview.md} | 0
4 files changed, 12 insertions(+), 2 deletions(-)
rename windows/deployment/windows-autopatch/operate/{windows-autopatch-fu-end-user-exp.md => windows-autopatch-feature-update-end-user-exp.md} (100%)
rename windows/deployment/windows-autopatch/operate/{windows-autopatch-fu-overview.md => windows-autopatch-feature-update-overview.md} (100%)
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
index 711942e1d6..7e4e331ff7 100644
--- a/.openpublishing.redirection.json
+++ b/.openpublishing.redirection.json
@@ -20449,6 +20449,16 @@
"source_path": "windows/security/identity-protection/hello-for-business/hello-event-300.md",
"redirect_url": "/windows/security/identity-protection/hello-for-business/hello-faq",
"redirect_document_id": false
+ },
+ {
+ "source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-fu-overview.md",
+ "redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-feature-update-overview",
+ "redirect_document_id": true
+ },
+ {
+ "source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-fu-end-user-exp.md",
+ "redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-feature-update-end-user-exp",
+ "redirect_document_id": true
}
]
}
diff --git a/windows/deployment/windows-autopatch/TOC.yml b/windows/deployment/windows-autopatch/TOC.yml
index 718c174a5f..7c75aa20cb 100644
--- a/windows/deployment/windows-autopatch/TOC.yml
+++ b/windows/deployment/windows-autopatch/TOC.yml
@@ -70,10 +70,10 @@
- name: Ineligible devices report—historical
href: operate/windows-autopatch-wqu-ineligible-devices-historical-report.md
- name: Windows feature updates
- href: operate/windows-autopatch-fu-overview.md
+ href: operate/windows-autopatch-feature-update-overview.md
items:
- name: Windows feature update end user experience
- href: operate/windows-autopatch-fu-end-user-exp.md
+ href: operate/windows-autopatch-feature-update-end-user-exp.md
- name: Microsoft 365 Apps for enterprise
href: operate/windows-autopatch-microsoft-365-apps-enterprise.md
- name: Microsoft Edge
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-fu-end-user-exp.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-feature-update-end-user-exp.md
similarity index 100%
rename from windows/deployment/windows-autopatch/operate/windows-autopatch-fu-end-user-exp.md
rename to windows/deployment/windows-autopatch/operate/windows-autopatch-feature-update-end-user-exp.md
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-fu-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-feature-update-overview.md
similarity index 100%
rename from windows/deployment/windows-autopatch/operate/windows-autopatch-fu-overview.md
rename to windows/deployment/windows-autopatch/operate/windows-autopatch-feature-update-overview.md
From 10dac852930a2bcd0507e63d64447ce0a437cfc2 Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Wed, 1 Feb 2023 17:58:38 -0800
Subject: [PATCH 41/98] Fixing broken links due to file renaming
---
.openpublishing.redirection.json | 59 ++++++++++++++++++-
windows/deployment/windows-autopatch/TOC.yml | 24 ++++----
.../windows-autopatch-update-management.md | 4 +-
...ch-windows-feature-update-end-user-exp.md} | 0
...opatch-windows-feature-update-overview.md} | 2 +-
...y-update-all-devices-historical-report.md} | 0
...dows-quality-update-all-devices-report.md} | 0
...-windows-quality-update-communications.md} | 0
...ate-eligible-devices-historical-report.md} | 0
...ch-windows-quality-update-end-user-exp.md} | 0
...e-ineligible-devices-historical-report.md} | 0
...opatch-windows-quality-update-overview.md} | 8 +--
...indows-quality-update-reports-overview.md} | 14 ++---
...topatch-windows-quality-update-signals.md} | 0
...ndows-quality-update-summary-dashboard.md} | 0
.../overview/windows-autopatch-faq.yml | 10 ++--
.../overview/windows-autopatch-overview.md | 6 +-
...ch-windows-update-unsupported-policies.md} | 0
18 files changed, 91 insertions(+), 36 deletions(-)
rename windows/deployment/windows-autopatch/operate/{windows-autopatch-feature-update-end-user-exp.md => windows-autopatch-windows-feature-update-end-user-exp.md} (100%)
rename windows/deployment/windows-autopatch/operate/{windows-autopatch-feature-update-overview.md => windows-autopatch-windows-feature-update-overview.md} (97%)
rename windows/deployment/windows-autopatch/operate/{windows-autopatch-wqu-all-devices-historical-report.md => windows-autopatch-windows-quality-update-all-devices-historical-report.md} (100%)
rename windows/deployment/windows-autopatch/operate/{windows-autopatch-wqu-all-devices-report.md => windows-autopatch-windows-quality-update-all-devices-report.md} (100%)
rename windows/deployment/windows-autopatch/operate/{windows-autopatch-wqu-communications.md => windows-autopatch-windows-quality-update-communications.md} (100%)
rename windows/deployment/windows-autopatch/operate/{windows-autopatch-wqu-eligible-devices-historical-report.md => windows-autopatch-windows-quality-update-eligible-devices-historical-report.md} (100%)
rename windows/deployment/windows-autopatch/operate/{windows-autopatch-wqu-end-user-exp.md => windows-autopatch-windows-quality-update-end-user-exp.md} (100%)
rename windows/deployment/windows-autopatch/operate/{windows-autopatch-wqu-ineligible-devices-historical-report.md => windows-autopatch-windows-quality-update-ineligible-devices-historical-report.md} (100%)
rename windows/deployment/windows-autopatch/operate/{windows-autopatch-wqu-overview.md => windows-autopatch-windows-quality-update-overview.md} (93%)
rename windows/deployment/windows-autopatch/operate/{windows-autopatch-wqu-reports-overview.md => windows-autopatch-windows-quality-update-reports-overview.md} (81%)
rename windows/deployment/windows-autopatch/operate/{windows-autopatch-wqu-signals.md => windows-autopatch-windows-quality-update-signals.md} (100%)
rename windows/deployment/windows-autopatch/operate/{windows-autopatch-wqu-summary-dashboard.md => windows-autopatch-windows-quality-update-summary-dashboard.md} (100%)
rename windows/deployment/windows-autopatch/references/{windows-autopatch-wqu-unsupported-policies.md => windows-autopatch-windows-update-unsupported-policies.md} (100%)
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
index 7e4e331ff7..e6a9c13cf5 100644
--- a/.openpublishing.redirection.json
+++ b/.openpublishing.redirection.json
@@ -20452,12 +20452,67 @@
},
{
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-fu-overview.md",
- "redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-feature-update-overview",
+ "redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview",
"redirect_document_id": true
},
{
"source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-fu-end-user-exp.md",
- "redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-feature-update-end-user-exp",
+ "redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-end-user-exp",
+ "redirect_document_id": true
+ },
+ {
+ "source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md",
+ "redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview",
+ "redirect_document_id": true
+ },
+ {
+ "source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-end-user-exp.md",
+ "redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-end-user-exp",
+ "redirect_document_id": true
+ },
+ {
+ "source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-signals.md",
+ "redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-signals",
+ "redirect_document_id": true
+ },
+ {
+ "source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-communications.md",
+ "redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-communications",
+ "redirect_document_id": true
+ },
+ {
+ "source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-reports-overview.md",
+ "redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-reports-overview",
+ "redirect_document_id": true
+ },
+ {
+ "source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-summary-dashboard.md",
+ "redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-summary-dashboard",
+ "redirect_document_id": true
+ },
+ {
+ "source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-all-devices-report.md",
+ "redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-all-devices-report",
+ "redirect_document_id": true
+ },
+ {
+ "source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-all-devices-historical-report.md",
+ "redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-all-devices-historical-report",
+ "redirect_document_id": true
+ },
+ {
+ "source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-eligible-devices-historical-report.md",
+ "redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-eligible-devices-historical-report",
+ "redirect_document_id": true
+ },
+ {
+ "source_path": "windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-ineligible-devices-historical-report.md",
+ "redirect_url": "/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-ineligible-devices-historical-report",
+ "redirect_document_id": true
+ },
+ {
+ "source_path": "windows/deployment/windows-autopatch/references/windows-autopatch-wqu-unsupported-policies.md",
+ "redirect_url": "/windows/deployment/windows-autopatch/references/windows-autopatch-windows-update-unsupported-policies",
"redirect_document_id": true
}
]
diff --git a/windows/deployment/windows-autopatch/TOC.yml b/windows/deployment/windows-autopatch/TOC.yml
index 7c75aa20cb..9f479471e4 100644
--- a/windows/deployment/windows-autopatch/TOC.yml
+++ b/windows/deployment/windows-autopatch/TOC.yml
@@ -48,32 +48,32 @@
href:
items:
- name: Windows quality updates
- href: operate/windows-autopatch-wqu-overview.md
+ href: operate/windows-autopatch-windows-quality-update-overview.md
items:
- name: Windows quality update end user experience
- href: operate/windows-autopatch-wqu-end-user-exp.md
+ href: operate/windows-autopatch-windows-quality-update-end-user-exp.md
- name: Windows quality update signals
- href: operate/windows-autopatch-wqu-signals.md
+ href: operate/windows-autopatch-windows-quality-update-signals.md
- name: Windows quality update communications
- href: operate/windows-autopatch-wqu-communications.md
+ href: operate/windows-autopatch-windows-quality-update-communications.md
- name: Windows quality update reports
- href: operate/windows-autopatch-wqu-reports-overview.md
+ href: operate/windows-autopatch-windows-quality-update-reports-overview.md
items:
- name: Summary dashboard
- href: operate/windows-autopatch-wqu-summary-dashboard.md
+ href: operate/windows-autopatch-windows-quality-update-summary-dashboard.md
- name: All devices report
- href: operate/windows-autopatch-wqu-all-devices-report.md
+ href: operate/windows-autopatch-windows-quality-update-all-devices-report.md
- name: All devices report—historical
- href: operate/windows-autopatch-wqu-all-devices-historical-report.md
+ href: operate/windows-autopatch-windows-quality-update-all-devices-historical-report.md
- name: Eligible devices report—historical
- href: operate/windows-autopatch-wqu-eligible-devices-historical-report.md
+ href: operate/windows-autopatch-windows-quality-update-eligible-devices-historical-report.md
- name: Ineligible devices report—historical
- href: operate/windows-autopatch-wqu-ineligible-devices-historical-report.md
+ href: operate/windows-autopatch-windows-quality-update-ineligible-devices-historical-report.md
- name: Windows feature updates
- href: operate/windows-autopatch-feature-update-overview.md
+ href: operate/windows-autopatch-windows-feature-update-overview.md
items:
- name: Windows feature update end user experience
- href: operate/windows-autopatch-feature-update-end-user-exp.md
+ href: operate/windows-autopatch-windows-feature-update-end-user-exp.md
- name: Microsoft 365 Apps for enterprise
href: operate/windows-autopatch-microsoft-365-apps-enterprise.md
- name: Microsoft Edge
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 c250ba4502..3c5bb1f346 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-update-management.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-update-management.md
@@ -20,8 +20,8 @@ Keeping your devices up to date is a balance of speed and stability. Windows Aut
| Software update workload | Description |
| ----- | ----- |
-| Windows quality update | Windows Autopatch uses four deployment rings to manage Windows quality updates. For more detailed information, see [Windows quality updates](../operate/windows-autopatch-wqu-overview.md). |
-| Windows feature update | Windows Autopatch uses four deployment rings to manage Windows feature updates. For more detailed information, see [Windows feature updates](windows-autopatch-fu-overview.md).
+| Windows quality update | Windows Autopatch uses four deployment rings to manage Windows quality updates. For more detailed information, see [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md). |
+| Windows feature update | Windows Autopatch uses four deployment rings to manage Windows feature updates. For more detailed information, see [Windows feature updates](windows-autopatch-windows-feature-update-overview.md).
| Anti-virus definition | Updated with each scan. |
| Microsoft 365 Apps for enterprise | For more information, see [Microsoft 365 Apps for enterprise](windows-autopatch-microsoft-365-apps-enterprise.md). |
| Microsoft Edge | For more information, see [Microsoft Edge](../operate/windows-autopatch-edge.md). |
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-feature-update-end-user-exp.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-end-user-exp.md
similarity index 100%
rename from windows/deployment/windows-autopatch/operate/windows-autopatch-feature-update-end-user-exp.md
rename to windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-end-user-exp.md
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-feature-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
similarity index 97%
rename from windows/deployment/windows-autopatch/operate/windows-autopatch-feature-update-overview.md
rename to windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
index 64f6442d2d..fb5db5fcd8 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-feature-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
@@ -65,7 +65,7 @@ You can test Windows 11 deployments by adding devices either through direct memb
## Manage Windows feature update deployments
-Windows Autopatch uses Microsoft Intune’s built-in solution, which uses configuration service providers (CSPs), for pausing and resuming both [Windows quality](windows-autopatch-wqu-overview.md#pausing-and-resuming-a-release) and [Windows feature updates](#pausing-and-resuming-a-release).
+Windows Autopatch uses Microsoft Intune’s built-in solution, which uses configuration service providers (CSPs), for pausing and resuming both [Windows quality](windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release) and [Windows feature updates](#pausing-and-resuming-a-release).
Windows Autopatch provides a permanent pause of a Windows feature update deployment. The Windows Autopatch service automatically extends the 35-day pause limit (permanent pause) established by Microsoft Intune on your behalf. The deployment remains permanently paused until you decide to resume it.
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-all-devices-historical-report.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-all-devices-historical-report.md
similarity index 100%
rename from windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-all-devices-historical-report.md
rename to windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-all-devices-historical-report.md
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-all-devices-report.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-all-devices-report.md
similarity index 100%
rename from windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-all-devices-report.md
rename to windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-all-devices-report.md
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-communications.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-communications.md
similarity index 100%
rename from windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-communications.md
rename to windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-communications.md
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-eligible-devices-historical-report.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-eligible-devices-historical-report.md
similarity index 100%
rename from windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-eligible-devices-historical-report.md
rename to windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-eligible-devices-historical-report.md
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-end-user-exp.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-end-user-exp.md
similarity index 100%
rename from windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-end-user-exp.md
rename to windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-end-user-exp.md
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-ineligible-devices-historical-report.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-ineligible-devices-historical-report.md
similarity index 100%
rename from windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-ineligible-devices-historical-report.md
rename to windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-ineligible-devices-historical-report.md
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
similarity index 93%
rename from windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md
rename to windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
index 7fdb0ac0d9..59cc60bb90 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
@@ -30,8 +30,8 @@ For a device to be eligible for Windows quality updates as a part of Windows Aut
| Deployed | Windows Autopatch doesn't update devices that haven't yet been deployed. |
| Internet connectivity | Devices must have a steady internet connection, and access to Windows [update endpoints](../prepare/windows-autopatch-configure-network.md). |
| Windows edition | Devices must be on a Windows edition supported by Windows Autopatch. For more information, see [Prerequisites](../prepare/windows-autopatch-prerequisites.md). |
-| Mobile device management (MDM) policy conflict | Devices must not have deployed any policies that would prevent device management. For more information, see [Conflicting and unsupported policies](../operate/windows-autopatch-wqu-unsupported-policies.md). |
-| Group policy conflict | Devices must not have group policies deployed which would prevent device management. For more information, see [Group policy](windows-autopatch-wqu-unsupported-policies.md#group-policy-and-other-policy-managers) |
+| Mobile device management (MDM) policy conflict | Devices must not have deployed any policies that would prevent device management. For more information, see [Conflicting and unsupported policies](../references/windows-autopatch-windows-update-unsupported-policies.md). |
+| Group policy conflict | Devices must not have group policies deployed which would prevent device management. For more information, see [Group policy](../references/windows-autopatch-windows-update-unsupported-policies.md#group-policy-and-other-policy-managers) |
## Windows quality update releases
@@ -108,7 +108,7 @@ Windows Autopatch schedules and deploys required Out of Band (OOB) updates relea
### Pausing and resuming a release
-If Windows Autopatch detects a [significant issue with a release](../operate/windows-autopatch-wqu-signals.md), we may decide to pause that release.
+If Windows Autopatch detects a [significant issue with a release](../operate/windows-autopatch-windows-quality-update-signals.md), we may decide to pause that release.
In the [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Release management** > in the **Release schedule** tab, you can pause or resume a Windows quality update.
@@ -121,4 +121,4 @@ There are two statuses associated with paused quality updates, **Service Paused*
## Remediating Ineligible and/or Not up to Date devices
-To ensure your devices receive Windows quality updates, Windows Autopatch provides information on how you can remediate [Ineligible Devices (Customer Actions)](../operate/windows-autopatch-wqu-reports-overview.md#ineligible-devices-customer-action). In addition, the Windows Autopatch service may remediate [Not up to Date devices](../operate/windows-autopatch-wqu-reports-overview.md#not-up-to-date-microsoft-action) to bring them back into compliance.
+To ensure your devices receive Windows quality updates, Windows Autopatch provides information on how you can remediate [Ineligible Devices (Customer Actions)](../operate/windows-autopatch-windows-quality-update-reports-overview.md#ineligible-devices-customer-action). In addition, the Windows Autopatch service may remediate [Not up to Date devices](../operate/windows-autopatch-windows-quality-update-reports-overview.md#not-up-to-date-microsoft-action) to bring them back into compliance.
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-reports-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-reports-overview.md
similarity index 81%
rename from windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-reports-overview.md
rename to windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-reports-overview.md
index 2e61770efe..e73bb77716 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-reports-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-reports-overview.md
@@ -26,8 +26,8 @@ The report types are organized into the following focus areas:
| Focus area | Description |
| ----- | ----- |
-| Operational detail | - [Summary dashboard](windows-autopatch-wqu-summary-dashboard.md): Provides the current update status summary for all devices.
- [All devices report](windows-autopatch-wqu-all-devices-report.md): Provides the current update status of all devices at the device level.
|
-| Device trends | - [All devices report – historical](windows-autopatch-wqu-all-devices-historical-report.md): Provides the update status trend of all devices over the last 90 days.
- [Eligible devices report – historical](windows-autopatch-wqu-eligible-devices-historical-report.md): Provides the update status trend of all eligible devices to receive quality updates over the last 90 days.
- [Ineligible devices report – historical](windows-autopatch-wqu-ineligible-devices-historical-report.md): Provides a trending view of why ineligible devices haven’t received quality updates over the last 90 days.
|
+| Operational detail | - [Summary dashboard](windows-autopatch-windows-quality-update-summary-dashboard.md): Provides the current update status summary for all devices.
- [All devices report](windows-autopatch-windows-quality-update-all-devices-report.md): Provides the current update status of all devices at the device level.
|
+| Device trends | - [All devices report – historical](windows-autopatch-windows-quality-update-all-devices-historical-report.md): Provides the update status trend of all devices over the last 90 days.
- [Eligible devices report – historical](windows-autopatch-windows-quality-update-eligible-devices-historical-report.md): Provides the update status trend of all eligible devices to receive quality updates over the last 90 days.
- [Ineligible devices report – historical](windows-autopatch-windows-quality-update-ineligible-devices-historical-report.md): Provides a trending view of why ineligible devices haven’t received quality updates over the last 90 days.
|
## Who can access the reports?
@@ -57,16 +57,16 @@ Healthy devices are devices that meet all of the following prerequisites:
- [Prerequisites](../prepare/windows-autopatch-prerequisites.md)
- [Prerequisites for device registration](../deploy/windows-autopatch-register-devices.md#prerequisites-for-device-registration)
-- [Windows quality update device eligibility](../operate/windows-autopatch-wqu-overview.md#device-eligibility)
+- [Windows quality update device eligibility](../operate/windows-autopatch-windows-quality-update-overview.md#device-eligibility)
> [!NOTE]
> Healthy devices will remain with the **In Progress** status for the 21-day service level objective period. Devices which are **Paused** are also considered healthy.
| Sub status | Description |
| ----- | ----- |
-| Up to Date | Devices are up to date with the latest quality update deployed through the [Windows Autopatch release schedule](../operate/windows-autopatch-wqu-overview.md#windows-quality-update-releases). |
-| In Progress | Devices are currently installing the latest quality update deployed through the [Windows Autopatch release schedule](../operate/windows-autopatch-wqu-overview.md#windows-quality-update-releases). |
-| Paused | Devices that are currently paused due to a Windows Autopatch or customer-initiated Release Management pause. For more information, see [Pausing and resuming a release](../operate/windows-autopatch-wqu-overview.md#pausing-and-resuming-a-release). |
+| Up to Date | Devices are up to date with the latest quality update deployed through the [Windows Autopatch release schedule](../operate/windows-autopatch-windows-quality-update-overview.md#windows-quality-update-releases). |
+| In Progress | Devices are currently installing the latest quality update deployed through the [Windows Autopatch release schedule](../operate/windows-autopatch-windows-quality-update-overview.md#windows-quality-update-releases). |
+| Paused | Devices that are currently paused due to a Windows Autopatch or customer-initiated Release Management pause. For more information, see [Pausing and resuming a release](../operate/windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release). |
### Not Up to Date (Microsoft Action)
@@ -76,7 +76,7 @@ Not Up to Date means a device isn’t up to date when the:
- Device is more than 21 days overdue from the last release.
> [!NOTE]
-> Microsoft Action refers to the responsibility of the Windows Autopatch Service Engineering Team to carry out the appropriate action to resolve the reported device state. Windows Autopatch aims to keep at least [95% of eligible devices on the latest Windows quality update 21 days after release](../operate/windows-autopatch-wqu-overview.md#service-level-objective).
+> Microsoft Action refers to the responsibility of the Windows Autopatch Service Engineering Team to carry out the appropriate action to resolve the reported device state. Windows Autopatch aims to keep at least [95% of eligible devices on the latest Windows quality update 21 days after release](../operate/windows-autopatch-windows-quality-update-overview.md#service-level-objective).
| Sub status | Description |
| ----- | ----- |
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-signals.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-signals.md
similarity index 100%
rename from windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-signals.md
rename to windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-signals.md
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-summary-dashboard.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-summary-dashboard.md
similarity index 100%
rename from windows/deployment/windows-autopatch/operate/windows-autopatch-wqu-summary-dashboard.md
rename to windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-summary-dashboard.md
diff --git a/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml b/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml
index 0c377a7e69..c1121c22df 100644
--- a/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml
+++ b/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml
@@ -92,26 +92,26 @@ sections:
- question: What happens if there's an issue with an update?
answer: |
Autopatch relies on the following capabilities to help resolve update issues:
- - Pausing and resuming: If Windows Autopatch detects an issue with a Windows quality release, we may decide that it's necessary to pause that release. Once the issue is resolved, the release will be resumed. For more information, see [Pausing and resuming a Windows quality release](../operate/windows-autopatch-wqu-overview.md#pausing-and-resuming-a-release).
+ - Pausing and resuming: If Windows Autopatch detects an issue with a Windows quality release, we may decide that it's necessary to pause that release. Once the issue is resolved, the release will be resumed. For more information, see [Pausing and resuming a Windows quality release](../operate/windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release).
- Rollback: If Windows Autopatch detects issues between versions of Microsoft 365 Apps for enterprise, we might force all devices to roll back to the previous version. For more information, see [Update controls for Microsoft 365 Apps for enterprise](../operate/windows-autopatch-microsoft-365-apps-enterprise.md#update-controls).
- question: Can I permanently pause a Windows feature update deployment?
answer: |
- Yes. Windows Autopatch provides a [permanent pause of either a feature update deployment](../operate/windows-autopatch-fu-overview.md#pausing-and-resuming-a-release).
+ Yes. Windows Autopatch provides a [permanent pause of either a feature update deployment](../operate/windows-autopatch-feature-update-overview.md#pausing-and-resuming-a-release).
- question: Will Windows quality updates be released more quickly after vulnerabilities are identified, or what is the regular cadence of updates?
answer: |
- For zero-day threats, Autopatch will have an [expedited release cadence](../operate/windows-autopatch-wqu-overview.md#expedited-releases). For normal updates Autopatch, uses a [regular release cadence](../operate/windows-autopatch-wqu-overview.md#windows-quality-update-releases) starting with devices in the Test ring and completing with general rollout to the Broad ring.
+ For zero-day threats, Autopatch will have an [expedited release cadence](../operate/windows-autopatch-windows-quality-update-overview.md#expedited-releases). For normal updates Autopatch, uses a [regular release cadence](../operate/windows-autopatch-wqu-overview.md#windows-quality-update-releases) starting with devices in the Test ring and completing with general rollout to the Broad ring.
- question: Can customers configure when to move to the next ring or is it controlled by Windows Autopatch?
answer: |
The decision of when to move to the next ring is handled by Windows Autopatch; it isn't customer configurable.
- question: Can you customize the scheduling of an update rollout to only install on certain days and times?
answer: |
- No, you can't customize update scheduling. However, you can specify [active hours](../operate/windows-autopatch-wqu-end-user-exp.md#servicing-window) to prevent users from updating during business hours.
+ No, you can't customize update scheduling. However, you can specify [active hours](../operate/windows-autopatch-windows-quality-update-end-user-exp.md#servicing-window) to prevent users from updating during business hours.
- question: Does Autopatch support include and exclude groups, or dynamic groups to define deployment ring membership?
answer: |
Windows Autopatch doesn't support managing update deployment ring membership using your Azure AD groups. For more information, see [Moving devices in between deployment rings](../operate/windows-autopatch-update-management.md#moving-devices-in-between-deployment-rings).
- question: Does Autopatch have two release cadences per update or are there two release cadences per-ring?
answer: |
- The release cadences are defined based on the update type. For example, a [regular cadence](../operate/windows-autopatch-wqu-overview.md#windows-quality-update-releases) (for a Windows quality update would be a gradual rollout from the Test ring to the Broad ring over 14 days whereas an [expedited release](../operate/windows-autopatch-wqu-overview.md#expedited-releases) would roll out more rapidly.
+ The release cadences are defined based on the update type. For example, a [regular cadence](../operate/windows-autopatch-windows-quality-update-overview.md#windows-quality-update-releases) (for a Windows quality update would be a gradual rollout from the Test ring to the Broad ring over 14 days whereas an [expedited release](../operate/windows-autopatch-windows-quality-update-overview.md#expedited-releases) would roll out more rapidly.
- name: Support
questions:
- question: What support is available for customers who need help with onboarding to Windows Autopatch?
diff --git a/windows/deployment/windows-autopatch/overview/windows-autopatch-overview.md b/windows/deployment/windows-autopatch/overview/windows-autopatch-overview.md
index 8ed02530ce..33c47e3fa1 100644
--- a/windows/deployment/windows-autopatch/overview/windows-autopatch-overview.md
+++ b/windows/deployment/windows-autopatch/overview/windows-autopatch-overview.md
@@ -37,8 +37,8 @@ The goal of Windows Autopatch is to deliver software updates to registered devic
| Management area | Service level objective |
| ----- | ----- |
-| [Windows quality updates](../operate/windows-autopatch-wqu-overview.md) | Windows Autopatch aims to keep at least 95% of eligible devices on the latest Windows quality update 21 days after release. |
-| [Windows feature updates](../operate/windows-autopatch-fu-overview.md) | Windows Autopatch aims to keep at least 99% of eligible devices on a supported version of Windows so that they can continue receiving Windows feature updates. |
+| [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md) | Windows Autopatch aims to keep at least 95% of eligible devices on the latest Windows quality update 21 days after release. |
+| [Windows feature updates](../operate/windows-autopatch-feature-update-overview.md) | Windows Autopatch aims to keep at least 99% of eligible devices on a supported version of Windows so that they can continue receiving Windows feature updates. |
| [Microsoft 365 Apps for enterprise](../operate/windows-autopatch-microsoft-365-apps-enterprise.md) | Windows Autopatch aims to keep at least 90% of eligible devices on a supported version of the Monthly Enterprise Channel (MEC). |
| [Microsoft Edge](../operate/windows-autopatch-edge.md) | Windows Autopatch configures eligible devices to benefit from Microsoft Edge's progressive rollouts on the Stable channel. |
| [Microsoft Teams](../operate/windows-autopatch-teams.md) | Windows Autopatch allows eligible devices to benefit from the standard automatic update channel. |
@@ -64,7 +64,7 @@ Microsoft remains committed to the security of your data and the [accessibility]
| Prepare | The following articles describe the mandatory steps to prepare and enroll your tenant into Windows Autopatch:- [Prerequisites](../prepare/windows-autopatch-prerequisites.md)
- [Configure your network](../prepare/windows-autopatch-configure-network.md)
- [Enroll your tenant](../prepare/windows-autopatch-enroll-tenant.md)
- [Fix issues found by the Readiness assessment tool](../prepare/windows-autopatch-fix-issues.md)
|
| Deploy | Once you've enrolled your tenant, this section instructs you to:- [Add and verify admin contacts](../deploy/windows-autopatch-admin-contacts.md)
- [Register your devices](../deploy/windows-autopatch-register-devices.md)
|
| Operate | This section includes the following information about your day-to-day life with the service:- [Update management](../operate/windows-autopatch-update-management.md)
- [Maintain your Windows Autopatch environment](../operate/windows-autopatch-maintain-environment.md)
- [Submit a support request](../operate/windows-autopatch-support-request.md)
- [Deregister a device](../operate/windows-autopatch-deregister-devices.md)
-| References | This section includes the following articles:- [Windows update policies](../operate/windows-autopatch-wqu-unsupported-policies.md)
- [Microsoft 365 Apps for enterprise update policies](../references/windows-autopatch-microsoft-365-policies.md)
- [Privacy](../references/windows-autopatch-privacy.md)
- [Windows Autopatch Preview Addendum](../references/windows-autopatch-preview-addendum.md)
|
+| References | This section includes the following articles:- [Windows update policies](../operate/windows-autopatch-windows-update-unsupported-policies.md)
- [Microsoft 365 Apps for enterprise update policies](../references/windows-autopatch-microsoft-365-policies.md)
- [Privacy](../references/windows-autopatch-privacy.md)
- [Windows Autopatch Preview Addendum](../references/windows-autopatch-preview-addendum.md)
|
### Have feedback or would like to start a discussion?
diff --git a/windows/deployment/windows-autopatch/references/windows-autopatch-wqu-unsupported-policies.md b/windows/deployment/windows-autopatch/references/windows-autopatch-windows-update-unsupported-policies.md
similarity index 100%
rename from windows/deployment/windows-autopatch/references/windows-autopatch-wqu-unsupported-policies.md
rename to windows/deployment/windows-autopatch/references/windows-autopatch-windows-update-unsupported-policies.md
From 86d425c1c93fffa3e49bc4b03f371641309494c4 Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Wed, 1 Feb 2023 18:00:54 -0800
Subject: [PATCH 42/98] Fix toc broken link.
---
windows/deployment/windows-autopatch/TOC.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/TOC.yml b/windows/deployment/windows-autopatch/TOC.yml
index 9f479471e4..fa4844aef5 100644
--- a/windows/deployment/windows-autopatch/TOC.yml
+++ b/windows/deployment/windows-autopatch/TOC.yml
@@ -95,7 +95,7 @@
href:
items:
- name: Windows update policies
- href: operate/windows-autopatch-wqu-unsupported-policies.md
+ href: references/windows-autopatch-windows-update-unsupported-policies.md
- name: Microsoft 365 Apps for enterprise update policies
href: references/windows-autopatch-microsoft-365-policies.md
- name: Changes made at tenant enrollment
From 54aa47a334ef24e9f5af835ded1104f38a350901 Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Wed, 1 Feb 2023 19:35:40 -0800
Subject: [PATCH 43/98] Fixed broken links.
---
.../windows-autopatch/overview/windows-autopatch-faq.yml | 2 +-
.../windows-autopatch/overview/windows-autopatch-overview.md | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml b/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml
index c1121c22df..fd6ef0d1ef 100644
--- a/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml
+++ b/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml
@@ -96,7 +96,7 @@ sections:
- Rollback: If Windows Autopatch detects issues between versions of Microsoft 365 Apps for enterprise, we might force all devices to roll back to the previous version. For more information, see [Update controls for Microsoft 365 Apps for enterprise](../operate/windows-autopatch-microsoft-365-apps-enterprise.md#update-controls).
- question: Can I permanently pause a Windows feature update deployment?
answer: |
- Yes. Windows Autopatch provides a [permanent pause of either a feature update deployment](../operate/windows-autopatch-feature-update-overview.md#pausing-and-resuming-a-release).
+ Yes. Windows Autopatch provides a [permanent pause of either a feature update deployment](../operate/windows-autopatch-windows-feature-update-overview.md#pausing-and-resuming-a-release).
- question: Will Windows quality updates be released more quickly after vulnerabilities are identified, or what is the regular cadence of updates?
answer: |
For zero-day threats, Autopatch will have an [expedited release cadence](../operate/windows-autopatch-windows-quality-update-overview.md#expedited-releases). For normal updates Autopatch, uses a [regular release cadence](../operate/windows-autopatch-wqu-overview.md#windows-quality-update-releases) starting with devices in the Test ring and completing with general rollout to the Broad ring.
diff --git a/windows/deployment/windows-autopatch/overview/windows-autopatch-overview.md b/windows/deployment/windows-autopatch/overview/windows-autopatch-overview.md
index 33c47e3fa1..6458591d05 100644
--- a/windows/deployment/windows-autopatch/overview/windows-autopatch-overview.md
+++ b/windows/deployment/windows-autopatch/overview/windows-autopatch-overview.md
@@ -38,7 +38,7 @@ The goal of Windows Autopatch is to deliver software updates to registered devic
| Management area | Service level objective |
| ----- | ----- |
| [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md) | Windows Autopatch aims to keep at least 95% of eligible devices on the latest Windows quality update 21 days after release. |
-| [Windows feature updates](../operate/windows-autopatch-feature-update-overview.md) | Windows Autopatch aims to keep at least 99% of eligible devices on a supported version of Windows so that they can continue receiving Windows feature updates. |
+| [Windows feature updates](../operate/windows-autopatch-windows-feature-update-overview.md) | Windows Autopatch aims to keep at least 99% of eligible devices on a supported version of Windows so that they can continue receiving Windows feature updates. |
| [Microsoft 365 Apps for enterprise](../operate/windows-autopatch-microsoft-365-apps-enterprise.md) | Windows Autopatch aims to keep at least 90% of eligible devices on a supported version of the Monthly Enterprise Channel (MEC). |
| [Microsoft Edge](../operate/windows-autopatch-edge.md) | Windows Autopatch configures eligible devices to benefit from Microsoft Edge's progressive rollouts on the Stable channel. |
| [Microsoft Teams](../operate/windows-autopatch-teams.md) | Windows Autopatch allows eligible devices to benefit from the standard automatic update channel. |
@@ -64,7 +64,7 @@ Microsoft remains committed to the security of your data and the [accessibility]
| Prepare | The following articles describe the mandatory steps to prepare and enroll your tenant into Windows Autopatch:- [Prerequisites](../prepare/windows-autopatch-prerequisites.md)
- [Configure your network](../prepare/windows-autopatch-configure-network.md)
- [Enroll your tenant](../prepare/windows-autopatch-enroll-tenant.md)
- [Fix issues found by the Readiness assessment tool](../prepare/windows-autopatch-fix-issues.md)
|
| Deploy | Once you've enrolled your tenant, this section instructs you to:- [Add and verify admin contacts](../deploy/windows-autopatch-admin-contacts.md)
- [Register your devices](../deploy/windows-autopatch-register-devices.md)
|
| Operate | This section includes the following information about your day-to-day life with the service:- [Update management](../operate/windows-autopatch-update-management.md)
- [Maintain your Windows Autopatch environment](../operate/windows-autopatch-maintain-environment.md)
- [Submit a support request](../operate/windows-autopatch-support-request.md)
- [Deregister a device](../operate/windows-autopatch-deregister-devices.md)
-| References | This section includes the following articles:- [Windows update policies](../operate/windows-autopatch-windows-update-unsupported-policies.md)
- [Microsoft 365 Apps for enterprise update policies](../references/windows-autopatch-microsoft-365-policies.md)
- [Privacy](../references/windows-autopatch-privacy.md)
- [Windows Autopatch Preview Addendum](../references/windows-autopatch-preview-addendum.md)
|
+| References | This section includes the following articles:- [Windows update policies](../references/windows-autopatch-windows-update-unsupported-policies.md)
- [Microsoft 365 Apps for enterprise update policies](../references/windows-autopatch-microsoft-365-policies.md)
- [Privacy](../references/windows-autopatch-privacy.md)
- [Windows Autopatch Preview Addendum](../references/windows-autopatch-preview-addendum.md)
|
### Have feedback or would like to start a discussion?
From c859ffda767062954bab43957e4f9759152dfaea Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Wed, 1 Feb 2023 19:41:51 -0800
Subject: [PATCH 44/98] Fixing more broken links
---
.../whats-new/windows-autopatch-whats-new-2022.md | 6 +++---
.../whats-new/windows-autopatch-whats-new-2023.md | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2022.md b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2022.md
index 5e36572e92..4692d775fd 100644
--- a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2022.md
+++ b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2022.md
@@ -24,12 +24,12 @@ Minor corrections such as typos, style, or formatting issues aren't listed.
| Article | Description |
| ----- | ----- |
-| [Windows quality updates](../operate/windows-autopatch-wqu-overview.md) | Added information about: - Turning off service-driven expedited quality update releases
- [MC482178](https://admin.microsoft.com/adminportal/home#/MessageCenter)
- Viewing deployed out of band releases
- [MC484915](https://admin.microsoft.com/adminportal/home#/MessageCenter)
|
+| [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md) | Added information about: - Turning off service-driven expedited quality update releases
- [MC482178](https://admin.microsoft.com/adminportal/home#/MessageCenter)
- Viewing deployed out of band releases
- [MC484915](https://admin.microsoft.com/adminportal/home#/MessageCenter)
|
| [Roles and responsibilities](../overview/windows-autopatch-roles-responsibilities.md) | Added Roles and responsibilities article |
| [Prerequisites](../prepare/windows-autopatch-prerequisites.md) | Added more licenses to the More about licenses section- [MC452168](https://admin.microsoft.com/adminportal/home#/MessageCenter) |
-| [Unsupported policies](../operate/windows-autopatch-wqu-unsupported-policies.md) | Updated to include other policy managers in the Group policy section |
+| [Unsupported policies](../operate/windows-autopatch-windows-quality-update-unsupported-policies.md) | Updated to include other policy managers in the Group policy section |
| [Changes made at tenant enrollment](../references/windows-autopatch-changes-to-tenant.md) | Updated the Device configuration, Microsoft Office and Edge policies |
-| [Windows quality update reports](../operate/windows-autopatch-wqu-reports-overview.md) | Added Windows quality update reports |
+| [Windows quality update reports](../operate/windows-autopatch-windows-quality-update-reports-overview.md) | Added Windows quality update reports |
### December service release
diff --git a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md
index 13f228bf15..d65d8a0e54 100644
--- a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md
+++ b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md
@@ -33,7 +33,7 @@ Minor corrections such as typos, style, or formatting issues aren't listed.
| Article | Description |
| ----- | ----- |
-| [Windows feature update](../operate/windows-autopatch-fu-overview.md) | Updated Windows feature update information |
+| [Windows feature update](../operate/windows-autopatch-windows-feature-update-overview.md) | Updated Windows feature update information |
| [Submit a tenant enrollment support request](../prepare/windows-autopatch-enrollment-support-request.md) | Added the Submit a tenant enrollment support request section. You can submit a tenant enrollment support request through the Tenant enrollment tool if you're running into issues with enrollment |
| [Submit a support request](../operate/windows-autopatch-support-request.md) | Added Premier and Unified support options section |
From fa0a4e67b85f8db14cb11a5b31d5a62af4841921 Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Wed, 1 Feb 2023 19:54:43 -0800
Subject: [PATCH 45/98] Fixed broken links.
---
.../windows-autopatch-register-devices.md | 4 +--
...ty-update-all-devices-historical-report.md | 2 +-
...ndows-quality-update-all-devices-report.md | 4 +--
...date-eligible-devices-historical-report.md | 2 +-
...te-ineligible-devices-historical-report.md | 2 +-
...utopatch-windows-quality-update-signals.md | 2 +-
...indows-quality-update-summary-dashboard.md | 2 +-
...indows-autopatch-roles-responsibilities.md | 34 +++++++++----------
8 files changed, 26 insertions(+), 26 deletions(-)
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 2a1201f79a..17cf0bb228 100644
--- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
+++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
@@ -20,8 +20,8 @@ Before Microsoft can manage your devices in Windows Autopatch, you must have dev
Windows Autopatch can take over software update management control of devices that meet software-based prerequisites as soon as an IT admin decides to have their tenant managed by the service. The Windows Autopatch software update management scope includes the following software update workloads:
-- [Windows quality updates](../operate/windows-autopatch-wqu-overview.md)
-- [Windows feature updates](../operate/windows-autopatch-fu-overview.md)
+- [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md)
+- [Windows feature updates](../operate/windows-autopatch-windows-feature-update-overview.md)
- [Microsoft 365 Apps for enterprise updates](../operate/windows-autopatch-microsoft-365-apps-enterprise.md)
- [Microsoft Edge updates](../operate/windows-autopatch-edge.md)
- [Microsoft Teams updates](../operate/windows-autopatch-teams.md)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-all-devices-historical-report.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-all-devices-historical-report.md
index 3808dd45a7..1aeecfd623 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-all-devices-historical-report.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-all-devices-historical-report.md
@@ -37,4 +37,4 @@ The following options are available:
| Export | Select **Export devices** at the top of the page to export data from this report into a CSV file. |
| Filter | Select either the **Update status** or **Deployment rings** filters at the top of the report to filter the results. Then, select **Generate trend**. |
-For a description of the displayed device status trends, see [Windows quality update statuses](windows-autopatch-wqu-reports-overview.md#windows-quality-update-statuses).
+For a description of the displayed device status trends, see [Windows quality update statuses](windows-autopatch-windows-quality-update-reports-overview.md#windows-quality-update-statuses).
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-all-devices-report.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-all-devices-report.md
index 5536a42c04..beb945d17e 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-all-devices-report.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-all-devices-report.md
@@ -38,8 +38,8 @@ The following information is available in the All devices report:
| Azure Active Directory (AD) device ID | The current Azure AD recorded device ID for the device. |
| Serial number | The current Intune recorded serial number for the device. |
| Deployment ring | The currently assigned Windows Autopatch deployment ring for the device. |
-| Update status | The current update status for the device (see [Windows quality update statuses](windows-autopatch-wqu-reports-overview.md#windows-quality-update-statuses)). |
-| Update sub status | The current update sub status for the device (see [Windows quality update statuses](windows-autopatch-wqu-reports-overview.md#windows-quality-update-statuses)) |
+| Update status | The current update status for the device (see [Windows quality update statuses](windows-autopatch-windows-quality-update-reports-overview.md#windows-quality-update-statuses)). |
+| Update sub status | The current update sub status for the device (see [Windows quality update statuses](windows-autopatch-windows-quality-update-reports-overview.md#windows-quality-update-statuses)) |
| OS version | The current version of Windows installed on the device. |
| OS revision | The current revision of Windows installed on the device. |
| Intune last check in time | The last time the device checked in to Intune. |
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-eligible-devices-historical-report.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-eligible-devices-historical-report.md
index 4e4e383213..8b2577d48c 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-eligible-devices-historical-report.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-eligible-devices-historical-report.md
@@ -37,4 +37,4 @@ The following options are available:
| Export | Select **Export devices** at the top of the page to export data from this report into a CSV file. |
| Filter | Select either the **Update status** or **Deployment rings** filters at the top of the report to filter the results. Then, select **Generate trend**. |
-For a description of the displayed device status trends, see [Windows quality update statuses](windows-autopatch-wqu-reports-overview.md#windows-quality-update-statuses).
+For a description of the displayed device status trends, see [Windows quality update statuses](windows-autopatch-windows-quality-update-reports-overview.md#windows-quality-update-statuses).
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-ineligible-devices-historical-report.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-ineligible-devices-historical-report.md
index 733ee98e88..dbcc2d106f 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-ineligible-devices-historical-report.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-ineligible-devices-historical-report.md
@@ -40,4 +40,4 @@ The following options are available:
| Export | Select **Export devices** at the top of the page to export data from this report into a CSV file. |
| Filter | Select either the **Update status** or **Deployment rings** filters at the top of the report to filter the results. Then, select **Generate trend**. |
-For a description of the displayed device status trends, see [Windows quality update statuses](windows-autopatch-wqu-reports-overview.md#windows-quality-update-statuses).
+For a description of the displayed device status trends, see [Windows quality update statuses](windows-autopatch-windows-quality-update-reports-overview.md#windows-quality-update-statuses).
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-signals.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-signals.md
index c715c4e960..fb93cc88c6 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-signals.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-signals.md
@@ -24,7 +24,7 @@ Before being released to the Test ring, Windows Autopatch reviews several data s
| Pre-release signal | Description |
| ----- | ----- |
-| Windows Payload Review | The contents of the B release are reviewed to help focus your update testing on areas that have changed. If any relevant changes are detected, a [customer advisory](../operate/windows-autopatch-wqu-communications.md#communications-during-release) will be sent out. |
+| Windows Payload Review | The contents of the B release are reviewed to help focus your update testing on areas that have changed. If any relevant changes are detected, a [customer advisory](../operate/windows-autopatch-windows-quality-update-communications.md#communications-during-release) will be sent out. |
| C-Release Review - Internal Signals | Windows Autopatch reviews active incidents associated with the previous C release to understand potential risks in the B release. |
| C-Release Review - Social Signals | Windows Autopatch monitors social signals to better understand potential risks associated with the B release. |
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-summary-dashboard.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-summary-dashboard.md
index 735136be22..88f6e4ec66 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-summary-dashboard.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-summary-dashboard.md
@@ -32,7 +32,7 @@ The following information is available in the Summary dashboard:
| Column name | Description |
| ----- | ----- |
-| Windows quality update status | The device update state. For more information, see [Windows quality update status](windows-autopatch-wqu-reports-overview.md#windows-quality-update-statuses). |
+| Windows quality update status | The device update state. For more information, see [Windows quality update status](windows-autopatch-windows-quality-update-reports-overview.md#windows-quality-update-statuses). |
| Devices | The number of devices showing as applicable for the state. |
## Report options
diff --git a/windows/deployment/windows-autopatch/overview/windows-autopatch-roles-responsibilities.md b/windows/deployment/windows-autopatch/overview/windows-autopatch-roles-responsibilities.md
index ec8c9d7ece..6e707c4ca8 100644
--- a/windows/deployment/windows-autopatch/overview/windows-autopatch-roles-responsibilities.md
+++ b/windows/deployment/windows-autopatch/overview/windows-autopatch-roles-responsibilities.md
@@ -28,7 +28,7 @@ This article outlines your responsibilities and Windows Autopatch's responsibili
| [Review the service data platform and privacy compliance details](../references/windows-autopatch-privacy.md) | :heavy_check_mark: | :x: |
| Ensure device [prerequisites](../prepare/windows-autopatch-prerequisites.md) are met and in place prior to enrollment | :heavy_check_mark: | :x: |
| Ensure [infrastructure and environment prerequisites](../prepare/windows-autopatch-configure-network.md) are met and in place prior to enrollment | :heavy_check_mark: | :x: |
-| Prepare to remove your devices from existing unsupported [Windows update](../references/windows-autopatch-wqu-unsupported-policies.md) and [Microsoft 365](../references/windows-autopatch-microsoft-365-policies.md) policies | :heavy_check_mark: | :x: |
+| Prepare to remove your devices from existing unsupported [Windows update](../references/windows-autopatch-windows-update-unsupported-policies.md) and [Microsoft 365](../references/windows-autopatch-microsoft-365-policies.md) policies | :heavy_check_mark: | :x: |
| [Configure required network endpoints](../prepare/windows-autopatch-configure-network.md#required-microsoft-product-endpoints) | :heavy_check_mark: | :x: |
| [Fix issues identified by the Readiness assessment tool](../prepare/windows-autopatch-fix-issues.md) | :heavy_check_mark: | :x: |
| [Enroll tenant into the Windows Autopatch service](../prepare/windows-autopatch-enroll-tenant.md) | :heavy_check_mark: | :x: |
@@ -40,8 +40,8 @@ This article outlines your responsibilities and Windows Autopatch's responsibili
| ----- | :-----: | :-----: |
| [Add and verify admin contacts](../deploy/windows-autopatch-admin-contacts.md) in Microsoft Endpoint Manager | :heavy_check_mark: | :x: |
| [Deploy and configure Windows Autopatch service configuration](../references/windows-autopatch-changes-to-tenant.md) | :x: | :heavy_check_mark: |
-| Educate users on the Windows Autopatch end user update experience
- [Windows quality update end user experience](../operate/windows-autopatch-wqu-end-user-exp.md)
- [Windows feature update end user experience](../operate/windows-autopatch-fu-end-user-exp.md)
- [Microsoft 365 Apps for enterprise end user experience](../operate/windows-autopatch-microsoft-365-apps-enterprise.md#end-user-experience)
- [Microsoft Teams end user experience](../operate/windows-autopatch-teams.md#end-user-experience)
| :heavy_check_mark: | :x: |
-| Remove your devices from existing unsupported [Windows update](../references/windows-autopatch-wqu-unsupported-policies.md) and [Microsoft 365](../references/windows-autopatch-microsoft-365-policies.md) policies | :heavy_check_mark: | :x: |
+| Educate users on the Windows Autopatch end user update experience- [Windows quality update end user experience](../operate/windows-autopatch-windows-quality-update-end-user-exp.md)
- [Windows feature update end user experience](../operate/windows-autopatch-windows-feature-update-end-user-exp.md)
- [Microsoft 365 Apps for enterprise end user experience](../operate/windows-autopatch-microsoft-365-apps-enterprise.md#end-user-experience)
- [Microsoft Teams end user experience](../operate/windows-autopatch-teams.md#end-user-experience)
| :heavy_check_mark: | :x: |
+| Remove your devices from existing unsupported [Windows update](../references/windows-autopatch-windows-update-unsupported-policies.md) and [Microsoft 365](../references/windows-autopatch-microsoft-365-policies.md) policies | :heavy_check_mark: | :x: |
| [Register devices/add devices to the Windows Autopatch Device Registration group](../deploy/windows-autopatch-register-devices.md#steps-to-register-devices) | :heavy_check_mark: | :x: |
| [Run the pre-registration device readiness checks](../deploy/windows-autopatch-register-devices.md#about-the-ready-not-ready-and-not-registered-tabs) | :x: | :heavy_check_mark: |
| [Automatically assign devices to First, Fast & Broad deployment rings at device registration](../operate/windows-autopatch-update-management.md#deployment-ring-calculation-logic) | :x: | :heavy_check_mark: |
@@ -61,29 +61,29 @@ This article outlines your responsibilities and Windows Autopatch's responsibili
| [Maintain customer configuration to align with the Windows Autopatch service configuration](../operate/windows-autopatch-maintain-environment.md) | :heavy_check_mark: | :x: |
| [Run on-going checks to ensure devices are only present in one deployment ring](../operate/windows-autopatch-update-management.md#automated-deployment-ring-remediation-functions) | :x: | :heavy_check_mark: |
| [Maintain the Test deployment ring membership](../operate/windows-autopatch-update-management.md#deployment-ring-calculation-logic) | :heavy_check_mark: | :x: |
-| Monitor [Windows update signals](../operate/windows-autopatch-wqu-signals.md) for safe update release | :x: | :heavy_check_mark: |
-| Test specific [business update scenarios](../operate/windows-autopatch-wqu-signals.md) | :heavy_check_mark: | :x: |
-| [Define and implement release schedule](../operate/windows-autopatch-wqu-overview.md) | :x: | :heavy_check_mark: |
-| Communicate the update [release schedule](../operate/windows-autopatch-wqu-communications.md) | :x: | :heavy_check_mark: |
-| Release updates (as scheduled)- [Windows quality updates](../operate/windows-autopatch-wqu-overview.md#windows-quality-update-releases)
- [Microsoft 365 Apps for enterprise](../operate/windows-autopatch-microsoft-365-apps-enterprise.md#update-release-schedule)
- [Microsoft Edge](../operate/windows-autopatch-edge.md#update-release-schedule)
- [Microsoft Teams](../operate/windows-autopatch-teams.md#update-release-schedule)
| :x: | :heavy_check_mark: |
-| [Release updates (expedited)](../operate/windows-autopatch-wqu-overview.md#expedited-releases) | :x: | :heavy_check_mark: |
+| Monitor [Windows update signals](../operate/windows-autopatch-windows-quality-update-signals.md) for safe update release | :x: | :heavy_check_mark: |
+| Test specific [business update scenarios](../operate/windows-autopatch-windows-quality-update-signals.md) | :heavy_check_mark: | :x: |
+| [Define and implement release schedule](../operate/windows-autopatch-windows-quality-update-overview.md) | :x: | :heavy_check_mark: |
+| Communicate the update [release schedule](../operate/windows-autopatch-windows-quality-update-communications.md) | :x: | :heavy_check_mark: |
+| Release updates (as scheduled)- [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md#windows-quality-update-releases)
- [Microsoft 365 Apps for enterprise](../operate/windows-autopatch-microsoft-365-apps-enterprise.md#update-release-schedule)
- [Microsoft Edge](../operate/windows-autopatch-edge.md#update-release-schedule)
- [Microsoft Teams](../operate/windows-autopatch-teams.md#update-release-schedule)
| :x: | :heavy_check_mark: |
+| [Release updates (expedited)](../operate/windows-autopatch-windows-quality-update-overview.md#expedited-releases) | :x: | :heavy_check_mark: |
| [Deploy updates to devices](../operate/windows-autopatch-update-management.md) | :x: | :heavy_check_mark: |
-| Monitor [Windows quality](../operate/windows-autopatch-wqu-overview.md) or [feature updates](../operate/windows-autopatch-fu-overview.md) through the release cycle | :x: | :heavy_check_mark: |
-| Review [update reports](../operate/windows-autopatch-wqu-reports-overview.md) | :heavy_check_mark: | :x: |
-| [Pause updates (Windows Autopatch initiated)](../operate/windows-autopatch-wqu-signals.md) | :x: | :heavy_check_mark: |
-| [Pause updates (initiated by you)](../operate/windows-autopatch-wqu-overview.md#pausing-and-resuming-a-release) | :heavy_check_mark: | :x: |
+| Monitor [Windows quality](../operate/windows-autopatch-windows-quality-update-overview.md) or [feature updates](../operate/windows-autopatch-windows-feature-update-overview.md) through the release cycle | :x: | :heavy_check_mark: |
+| Review [update reports](../operate/windows-autopatch-windows-quality-update-reports-overview.md) | :heavy_check_mark: | :x: |
+| [Pause updates (Windows Autopatch initiated)](../operate/windows-autopatch-windows-quality-update-signals.md) | :x: | :heavy_check_mark: |
+| [Pause updates (initiated by you)](../operate/windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release) | :heavy_check_mark: | :x: |
| Run [on-going post-registration device readiness checks](../deploy/windows-autopatch-post-reg-readiness-checks.md) | :x: | :heavy_check_mark: |
| [Remediate devices displayed in the **Not ready** tab](../deploy/windows-autopatch-post-reg-readiness-checks.md#about-the-three-tabs-in-the-devices-blade) | :heavy_check_mark: | :x: |
-| Resolve any conflicting and unsupported [Windows update](../references/windows-autopatch-wqu-unsupported-policies.md) and [Microsoft 365](../references/windows-autopatch-microsoft-365-policies.md) policies | :heavy_check_mark: | :x: |
-| [Investigate devices that aren't up to date within the service level objective (Microsoft action)](../operate/windows-autopatch-wqu-reports-overview.md#not-up-to-date-microsoft-action) | :x: | :heavy_check_mark: |
-| [Investigate and remediate devices that are marked as ineligible (Customer action)](../operate/windows-autopatch-wqu-reports-overview.md#ineligible-devices-customer-action) | :heavy_check_mark: | :x: |
+| Resolve any conflicting and unsupported [Windows update](../references/windows-autopatch-windows-update-unsupported-policies.md) and [Microsoft 365](../references/windows-autopatch-microsoft-365-policies.md) policies | :heavy_check_mark: | :x: |
+| [Investigate devices that aren't up to date within the service level objective (Microsoft action)](../operate/windows-autopatch-windows-quality-update-reports-overview.md#not-up-to-date-microsoft-action) | :x: | :heavy_check_mark: |
+| [Investigate and remediate devices that are marked as ineligible (Customer action)](../operate/windows-autopatch-windows-quality-update-reports-overview.md#ineligible-devices-customer-action) | :heavy_check_mark: | :x: |
| [Raise, manage and resolve a service incident if an update management area isn't meeting the service level objective](windows-autopatch-overview.md#update-management) | :x: | :heavy_check_mark: |
| [Deregister devices](../operate/windows-autopatch-deregister-devices.md) | :heavy_check_mark: | :x: |
| [Register a device that was previously deregistered (upon customers request)](../operate/windows-autopatch-deregister-devices.md#excluded-devices) | :x: | :heavy_check_mark: |
| [Request unenrollment from Windows Autopatch](../operate/windows-autopatch-unenroll-tenant.md) | :heavy_check_mark: | :x: |
| [Remove Windows Autopatch data from the service and deregister devices](../operate/windows-autopatch-unenroll-tenant.md#microsofts-responsibilities-during-unenrollment) | :x: | :heavy_check_mark: |
| [Maintain update configuration & update devices post unenrollment from Windows Autopatch](../operate/windows-autopatch-unenroll-tenant.md#your-responsibilities-after-unenrolling-your-tenant) | :heavy_check_mark: | :x: |
-| Review and respond to Message Center and Service Health Dashboard notifications- [Windows quality and feature update communications](../operate/windows-autopatch-wqu-communications.md)
- [Add and verify admin contacts](../deploy/windows-autopatch-admin-contacts.md)
| :heavy_check_mark: | :x: |
+| Review and respond to Message Center and Service Health Dashboard notifications- [Windows quality and feature update communications](../operate/windows-autopatch-windows-quality-update-communications.md)
- [Add and verify admin contacts](../deploy/windows-autopatch-admin-contacts.md)
| :heavy_check_mark: | :x: |
| [Highlight Windows Autopatch Tenant management alerts that require customer action](../operate/windows-autopatch-maintain-environment.md#windows-autopatch-tenant-actions) | :x: | :heavy_check_mark: |
| [Review and respond to Windows Autopatch Tenant management alerts](../operate/windows-autopatch-maintain-environment.md#windows-autopatch-tenant-actions) | :heavy_check_mark: | :x: |
| [Raise and respond to support requests](../operate/windows-autopatch-support-request.md) | :heavy_check_mark: | :x: |
From 099940b12463660c3e63662645af67778246bd3b Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Wed, 1 Feb 2023 20:01:01 -0800
Subject: [PATCH 46/98] Last broken link i think
---
.../whats-new/windows-autopatch-whats-new-2022.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2022.md b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2022.md
index 4692d775fd..b79ce348b0 100644
--- a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2022.md
+++ b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2022.md
@@ -27,7 +27,7 @@ Minor corrections such as typos, style, or formatting issues aren't listed.
| [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md) | Added information about: - Turning off service-driven expedited quality update releases
- [MC482178](https://admin.microsoft.com/adminportal/home#/MessageCenter)
- Viewing deployed out of band releases
- [MC484915](https://admin.microsoft.com/adminportal/home#/MessageCenter)
|
| [Roles and responsibilities](../overview/windows-autopatch-roles-responsibilities.md) | Added Roles and responsibilities article |
| [Prerequisites](../prepare/windows-autopatch-prerequisites.md) | Added more licenses to the More about licenses section- [MC452168](https://admin.microsoft.com/adminportal/home#/MessageCenter) |
-| [Unsupported policies](../operate/windows-autopatch-windows-quality-update-unsupported-policies.md) | Updated to include other policy managers in the Group policy section |
+| [Unsupported policies](../references/windows-autopatch-windows-update-unsupported-policies.md) | Updated to include other policy managers in the Group policy section |
| [Changes made at tenant enrollment](../references/windows-autopatch-changes-to-tenant.md) | Updated the Device configuration, Microsoft Office and Edge policies |
| [Windows quality update reports](../operate/windows-autopatch-windows-quality-update-reports-overview.md) | Added Windows quality update reports |
From be15eeeef4da6260fa18ad9c0dfe6bb700966042 Mon Sep 17 00:00:00 2001
From: Frank Rojas <45807133+frankroj@users.noreply.github.com>
Date: Thu, 2 Feb 2023 11:40:10 -0500
Subject: [PATCH 47/98] Spelling correction
Corrected Replated to Related
---
.../bitlocker-use-bitlocker-recovery-password-viewer.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/security/information-protection/bitlocker/bitlocker-use-bitlocker-recovery-password-viewer.md b/windows/security/information-protection/bitlocker/bitlocker-use-bitlocker-recovery-password-viewer.md
index 315672e456..fe24fac2a4 100644
--- a/windows/security/information-protection/bitlocker/bitlocker-use-bitlocker-recovery-password-viewer.md
+++ b/windows/security/information-protection/bitlocker/bitlocker-use-bitlocker-recovery-password-viewer.md
@@ -63,7 +63,7 @@ The following procedures describe the most common tasks performed by using the B
By completing the procedures in this scenario, the recovery passwords for a computer have been viewed and copied and a password ID was used to locate a recovery password.
-## Replated articles
+## Related articles
- [BitLocker Overview](bitlocker-overview.md)
- [BitLocker frequently asked questions (FAQ)](bitlocker-frequently-asked-questions.yml)
From b45ca6d9b9c28bfc4493f5b838b04bdb1bab3ddb Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Thu, 2 Feb 2023 11:17:03 -0800
Subject: [PATCH 48/98] Added additional resources to Diagnostic data section
as per Harman.
---
.../references/windows-autopatch-privacy.md | 7 ++++++-
.../whats-new/windows-autopatch-whats-new-2023.md | 1 +
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/references/windows-autopatch-privacy.md b/windows/deployment/windows-autopatch/references/windows-autopatch-privacy.md
index 60f5f47988..50f23ad38a 100644
--- a/windows/deployment/windows-autopatch/references/windows-autopatch-privacy.md
+++ b/windows/deployment/windows-autopatch/references/windows-autopatch-privacy.md
@@ -1,7 +1,7 @@
---
title: Privacy
description: This article provides details about the data platform and privacy compliance for Autopatch
-ms.date: 11/08/2022
+ms.date: 02/02/2023
ms.prod: windows-client
ms.technology: itpro-updates
ms.topic: reference
@@ -61,6 +61,11 @@ Windows Autopatch only processes and stores system-level data from Windows 10 op
For more information about the diagnostic data collection of Microsoft Windows 10, see the [Where we store and process data](https://privacy.microsoft.com/privacystatement#mainwherewestoreandprocessdatamodule) section of the Microsoft Privacy Statement.
+For more information about how Windows diagnostic data is used, see:
+
+- [Windows diagnostic data in your organization](/windows/privacy/configure-windows-diagnostic-data-in-your-organization#enable-windows-diagnostic-data-processor-configuration)
+- [Features that require Windows diagnostic data](/mem/intune/protect/data-enable-windows-data)
+
## Tenant access
Windows Autopatch creates an enterprise application in your tenant. This enterprise application is a first party application used to run the Windows Autopatch service.
diff --git a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md
index d65d8a0e54..9fe0664758 100644
--- a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md
+++ b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md
@@ -24,6 +24,7 @@ Minor corrections such as typos, style, or formatting issues aren't listed.
| Article | Description |
| ----- | ----- |
+| [Privacy](../references/windows-autopatch-privacy.md) | Added additional resources to Microsoft Windows 10/11 diagnostic data section |
| [Changes made at tenant enrollment](../references/windows-autopatch-changes-to-tenant.md) | Updated Feature update policies section with Windows Autopatch - DSS Policy [deployment ring] |
| [Register your devices](../deploy/windows-autopatch-register-devices.md) |
- Updated the Built-in roles required for registration section
- Added more information about assigning less-privileged user accounts
|
From 12bf703ba648b8d5d09a94d827e2454f03bba1d2 Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Thu, 2 Feb 2023 11:22:47 -0800
Subject: [PATCH 49/98] Tweak
---
.../references/windows-autopatch-privacy.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/windows/deployment/windows-autopatch/references/windows-autopatch-privacy.md b/windows/deployment/windows-autopatch/references/windows-autopatch-privacy.md
index 50f23ad38a..f3e41c6ebe 100644
--- a/windows/deployment/windows-autopatch/references/windows-autopatch-privacy.md
+++ b/windows/deployment/windows-autopatch/references/windows-autopatch-privacy.md
@@ -25,7 +25,7 @@ The sources include Azure Active Directory (Azure AD), Microsoft Intune, and Mic
| Data source | Purpose |
| ------ | ------ |
| [Microsoft Windows 10/11 Enterprise](/windows/windows-10/) | Management of device setup experience, managing connections to other services, and operational support for IT pros. |
-| [Windows Update for Business](/windows/deployment/update/waas-manage-updates-wufb) | Uses Windows 10 Enterprise diagnostic data to provide additional information on Windows 10/11 update. |
+| [Windows Update for Business](/windows/deployment/update/waas-manage-updates-wufb) | Uses Windows 10/11 Enterprise diagnostic data to provide additional information on Windows 10/11 update. |
| [Microsoft Intune](/mem/intune/fundamentals/what-is-intune) | Device management and to keep your data secure. The following endpoint management data sources are used:
- [Microsoft Azure Active Directory](/azure/active-directory/): Authentication and identification of all user accounts.
- [Microsoft Intune](/mem/intune/): Distributing device configurations, device management and application management.
| [Windows Autopatch](https://go.microsoft.com/fwlink/?linkid=2109431) | Data provided by the customer or generated by the service during running of the service. |
| [Microsoft 365 Apps for enterprise](https://www.microsoft.com/microsoft-365/enterprise/compare-office-365-plans)| Management of Microsoft 365 Apps. |
@@ -53,13 +53,13 @@ Windows Autopatch Service Engineering Team is in the United States, India and Ro
Windows Autopatch uses [Windows 10/11 Enhanced diagnostic data](/windows/privacy/windows-diagnostic-data) to keep Windows secure, up to date, fix problems, and make product improvements.
-The enhanced diagnostic data setting includes more detailed information about the devices enrolled in Windows Autopatch and their settings, capabilities, and device health. When enhanced diagnostic data is selected, data, including required diagnostic data, are collected. For more information, see [Changes to Windows diagnostic data collection](/windows/privacy/changes-to-windows-diagnostic-data-collection) about the Windows 10 diagnostic data setting and data collection.
+The enhanced diagnostic data setting includes more detailed information about the devices enrolled in Windows Autopatch and their settings, capabilities, and device health. When enhanced diagnostic data is selected, data, including required diagnostic data, are collected. For more information, see [Changes to Windows diagnostic data collection](/windows/privacy/changes-to-windows-diagnostic-data-collection) about the Windows 10/11 diagnostic data setting and data collection.
The diagnostic data terminology will change in future versions of Windows. Windows Autopatch is committed to processing only the data that the service needs. The diagnostic level will change to **Optional**, but Windows Autopatch will implement the limited diagnostic policies to fine-tune diagnostic data collection required for the service. For more information, see [Changes to Windows diagnostic data collection](/windows/privacy/changes-to-windows-diagnostic-data-collection).
-Windows Autopatch only processes and stores system-level data from Windows 10 optional diagnostic data that originates from enrolled devices such as application and device reliability, and performance information. Windows Autopatch doesn't process and store customers' data such as chat and browser history, voice, text, or speech data.
+Windows Autopatch only processes and stores system-level data from Windows 10/11 optional diagnostic data that originates from enrolled devices such as application and device reliability, and performance information. Windows Autopatch doesn't process and store customers' data such as chat and browser history, voice, text, or speech data.
-For more information about the diagnostic data collection of Microsoft Windows 10, see the [Where we store and process data](https://privacy.microsoft.com/privacystatement#mainwherewestoreandprocessdatamodule) section of the Microsoft Privacy Statement.
+For more information about the diagnostic data collection of Microsoft Windows 10/11, see the [Where we store and process data](https://privacy.microsoft.com/privacystatement#mainwherewestoreandprocessdatamodule) section of the Microsoft Privacy Statement.
For more information about how Windows diagnostic data is used, see:
From c8f02def3d107554ca7124835d5a466543458173 Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Thu, 2 Feb 2023 11:28:14 -0800
Subject: [PATCH 50/98] tweak
---
.../whats-new/windows-autopatch-whats-new-2023.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md
index 9fe0664758..ceede02bef 100644
--- a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md
+++ b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2023.md
@@ -24,7 +24,7 @@ Minor corrections such as typos, style, or formatting issues aren't listed.
| Article | Description |
| ----- | ----- |
-| [Privacy](../references/windows-autopatch-privacy.md) | Added additional resources to Microsoft Windows 10/11 diagnostic data section |
+| [Privacy](../references/windows-autopatch-privacy.md) | Added additional resources to the Microsoft Windows 10/11 diagnostic data section |
| [Changes made at tenant enrollment](../references/windows-autopatch-changes-to-tenant.md) | Updated Feature update policies section with Windows Autopatch - DSS Policy [deployment ring] |
| [Register your devices](../deploy/windows-autopatch-register-devices.md) |- Updated the Built-in roles required for registration section
- Added more information about assigning less-privileged user accounts
|
From 866f0b1d4c788f9ec7ba0f5117835ad725b5ebec Mon Sep 17 00:00:00 2001
From: jsuther1974
Date: Thu, 2 Feb 2023 11:42:56 -0800
Subject: [PATCH 51/98] Added warnings for applocker event volumes and script
enforcement on server 2016
---
.../applocker/using-event-viewer-with-applocker.md | 13 ++++++++-----
...orized-apps-deployed-with-a-managed-installer.md | 5 ++++-
.../design/script-enforcement.md | 11 ++++++++---
.../operations/known-issues.md | 7 +++----
4 files changed, 23 insertions(+), 13 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/applocker/using-event-viewer-with-applocker.md b/windows/security/threat-protection/windows-defender-application-control/applocker/using-event-viewer-with-applocker.md
index 4c9e95f7c1..ed7b6721dc 100644
--- a/windows/security/threat-protection/windows-defender-application-control/applocker/using-event-viewer-with-applocker.md
+++ b/windows/security/threat-protection/windows-defender-application-control/applocker/using-event-viewer-with-applocker.md
@@ -1,6 +1,6 @@
---
title: Using Event Viewer with AppLocker (Windows)
-description: This topic lists AppLocker events and describes how to use Event Viewer with AppLocker.
+description: This article lists AppLocker events and describes how to use Event Viewer with AppLocker.
ms.assetid: 109abb10-78b1-4c29-a576-e5a17dfeb916
ms.reviewer:
ms.author: vinpa
@@ -14,7 +14,7 @@ manager: aaroncz
audience: ITPro
ms.topic: conceptual
ms.technology: itpro-security
-ms.date: 12/31/2017
+ms.date: 02/02/2023
---
# Using Event Viewer with AppLocker
@@ -28,7 +28,7 @@ ms.date: 12/31/2017
>[!NOTE]
>Some capabilities of Windows Defender Application Control are only available on specific Windows versions. Learn more about the [Windows Defender Application Control feature availability](/windows/security/threat-protection/windows-defender-application-control/feature-availability).
-This topic lists AppLocker events and describes how to use Event Viewer with AppLocker.
+This article lists AppLocker events and describes how to use Event Viewer with AppLocker.
The AppLocker log contains information about applications that are affected by AppLocker rules. Each event in the log contains detailed info about:
@@ -43,10 +43,13 @@ Review the entries in the Event Viewer to determine if any applications aren't i
For info about what to look for in the AppLocker event logs, see [Monitor app usage with AppLocker](monitor-application-usage-with-applocker.md).
+> [!NOTE]
+> The AppLocker event logs are very verbose and can result in a large number of events depending on the policies deployed, particularly in the *AppLocker - EXE and DLL* event log. If you're using an event forwarding and collection service, like LogAnalytics, you may want to adjust the configuration for that event log to only collect Error events or stop collecting events from that log altogether.
+
**To review the AppLocker log in Event Viewer**
1. Open Event Viewer.
-2. In the console tree under **Application and Services Logs\\Microsoft\\Windows**, click **AppLocker**.
+2. In the console tree under **Application and Services Logs\\Microsoft\\Windows**, select **AppLocker**.
The following table contains information about the events that you can use to determine which apps are affected by AppLocker rules.
@@ -83,7 +86,7 @@ The following table contains information about the events that you can use to de
| 8040 | Error | Package family name * version * was prevented from installing or updating due to Config CI policy | Added in Windows Server 2016 and Windows 10.|
-## Related topics
+## Related articles
- [Tools to use with AppLocker](tools-to-use-with-applocker.md)
diff --git a/windows/security/threat-protection/windows-defender-application-control/configure-authorized-apps-deployed-with-a-managed-installer.md b/windows/security/threat-protection/windows-defender-application-control/configure-authorized-apps-deployed-with-a-managed-installer.md
index c15b97399b..2b03d8a6f4 100644
--- a/windows/security/threat-protection/windows-defender-application-control/configure-authorized-apps-deployed-with-a-managed-installer.md
+++ b/windows/security/threat-protection/windows-defender-application-control/configure-authorized-apps-deployed-with-a-managed-installer.md
@@ -13,7 +13,7 @@ author: jsuther1974
ms.reviewer: jogeurte
ms.author: vinpa
manager: aaroncz
-ms.date: 08/26/2022
+ms.date: 02/02/2023
ms.technology: itpro-security
ms.topic: article
---
@@ -62,6 +62,9 @@ To turn on managed installer tracking, you must:
- Create and deploy an AppLocker policy that defines your managed installer rules and enables services enforcement for executables and DLLs.
- Enable AppLocker's Application Identity and AppLockerFltr services.
+> [!NOTE]
+> The managed installer AppLocker policy below is designed to be safely merged with any pre-existing AppLocker policies and won't change the behavior of those policies. However, if applied on a device that doesn't currently have any AppLocker policy, you will see a large increase in warning events generated in the *AppLocker - EXE and DLL* event log. If you're using an event forwarding and collection service, like LogAnalytics, you may want to adjust the configuration for that event log to only collect Error events or stop collecting events from that log altogether.
+
> [!NOTE]
> MEMCM will automatically configure itself as a managed installer, and enable the required AppLocker components, if you deploy one of its inbox WDAC policies. If you are configuring MEMCM as a managed installer using any other method, additional setup is required. Use the [**ManagedInstaller** cmdline switch in your ccmsetup.exe setup](/mem/configmgr/core/clients/deploy/about-client-installation-properties#managedinstaller). Or you can deploy one of the MEMCM inbox audit mode policies alongside your custom policy.
diff --git a/windows/security/threat-protection/windows-defender-application-control/design/script-enforcement.md b/windows/security/threat-protection/windows-defender-application-control/design/script-enforcement.md
index 2414d5dd4e..29174ef291 100644
--- a/windows/security/threat-protection/windows-defender-application-control/design/script-enforcement.md
+++ b/windows/security/threat-protection/windows-defender-application-control/design/script-enforcement.md
@@ -9,7 +9,7 @@ ms.reviewer: jogeurte
ms.author: jogeurte
ms.manager: jsuther
manager: aaroncz
-ms.date: 11/02/2022
+ms.date: 02/02/2023
ms.technology: itpro-security
ms.topic: article
ms.localizationpriority: medium
@@ -26,13 +26,18 @@ ms.localizationpriority: medium
> [!NOTE]
> Some capabilities of Windows Defender Application Control are only available on specific Windows versions. Learn more about the [Application Control feature availability](/windows/security/threat-protection/windows-defender-application-control/feature-availability).
+> [!IMPORTANT]
+> Option **11 Disabled:Script Enforcement** is not supported on **Windows Server 2016** and should not be used on that platform. Doing so may result in unexpected script enforcement behaviors.
+
## Script enforcement overview
By default, script enforcement is enabled for all WDAC policies unless the option **11 Disabled:Script Enforcement** is set in the policy. WDAC script enforcement involves a handshake between an enlightened script host, such as PowerShell, and WDAC. The actual enforcement behavior, however, is handled entirely by the script host. Some script hosts, like the Microsoft HTML Application Host (mshta.exe), simply block all code execution if any WDAC UMCI policy is active. Most script hosts first ask WDAC whether a script should be allowed to run based on the WDAC policies currently active. The script host then either blocks, allows, or changes *how* the script is run to best protect the user and the device.
+Validation for signed scripts is done using the [WinVerifyTrust API](/windows/win32/api/wintrust/nf-wintrust-winverifytrust). To pass validation, the signature root must be present in the trusted root store on the device and be allowed by your WDAC policy. This behavior is different from WDAC validation for executable files, which doesn't require installation of the root certificate.
+
WDAC shares the *AppLocker - MSI and Script* event log for all script enforcement events. Whenever a script host asks WDAC if a script should be allowed, an event will be logged with the answer WDAC returned to the script host. For more information on WDAC script enforcement events, see [Understanding Application Control events](/windows/security/threat-protection/windows-defender-application-control/event-id-explanations#windows-applocker-msi-and-script-log).
-> [!IMPORTANT]
+> [!NOTE]
> When a script runs that is not allowed by policy, WDAC raises an event indicating that the script was "blocked". However, the actual script enforcement behavior is handled by the script host and may not actually completely block the file from running.
>
> Also be aware that some script hosts may change how they behave even if a WDAC policy is in audit mode only. You should review the information below for each script host and test thoroughly within your environment to ensure the scripts you need to run are working properly.
@@ -43,7 +48,7 @@ WDAC shares the *AppLocker - MSI and Script* event log for all script enforcemen
All PowerShell scripts (.ps1), modules (.psm1), and manifests (.psd1) must be allowed by WDAC policy in order to run with Full Language rights.
-Any **dependent modules** that are loaded by an allowed module must also be allowed by WDAC policy, and module functions must be exported explicitly by name when WDAC is enforced. Modules that do not specify any exported functions (no export name list) will still load but no module functions will be accessible. Modules that use wildcards (\*) in their name will fail to load.
+Any **dependent modules** that are loaded by an allowed module must also be allowed by WDAC policy, and module functions must be exported explicitly by name when WDAC is enforced. Modules that don't specify any exported functions (no export name list) will still load but no module functions will be accessible. Modules that use wildcards (\*) in their name will fail to load.
Any PowerShell script that isn't allowed by WDAC policy will still run, but only in Constrained Language Mode.
diff --git a/windows/security/threat-protection/windows-defender-application-control/operations/known-issues.md b/windows/security/threat-protection/windows-defender-application-control/operations/known-issues.md
index 9a7322339f..a5642a032c 100644
--- a/windows/security/threat-protection/windows-defender-application-control/operations/known-issues.md
+++ b/windows/security/threat-protection/windows-defender-application-control/operations/known-issues.md
@@ -9,7 +9,7 @@ ms.reviewer: jogeurte
ms.author: jogeurte
ms.manager: jsuther
manager: aaroncz
-ms.date: 07/01/2022
+ms.date: 02/02/2023
ms.technology: itpro-security
ms.topic: article
ms.localizationpriority: medium
@@ -19,7 +19,6 @@ ms.localizationpriority: medium
**Applies to:**
-
- Windows 10
- Windows 11
- Windows Server 2016 and above
@@ -27,11 +26,11 @@ ms.localizationpriority: medium
> [!NOTE]
> Some capabilities of Windows Defender Application Control are only available on specific Windows versions. Learn more about the [Application Control feature availability](/windows/security/threat-protection/windows-defender-application-control/feature-availability).
-This topic covers tips and tricks for admins and known issues with Windows Defender Application Control (WDAC). Test this configuration in your lab before enabling it in production.
+This article covers tips and tricks for admins and known issues with Windows Defender Application Control (WDAC). Test this configuration in your lab before enabling it in production.
## Managed Installer and ISG will cause garrulous events
-When Managed Installer and ISG are enabled, 3091 and 3092 events will be logged when a file didn't have Managed Installer or ISG authorization, regardless of whether the file was allowed. Beginning with the September 2022 C release, these events will be moved to the verbose channel since the events don't indicate an issue with the policy.
+When Managed Installer and ISG are enabled, 3091 and 3092 events will be logged when a file didn't have Managed Installer or ISG authorization, regardless of whether the file was allowed. These events have been moved to the verbose channel beginning with the September 2022 Update Preview since the events don't indicate an issue with the policy.
## .NET native images may generate false positive block events
From 43f1d1c26f0e3977e6b5db1077a3c514602ecd51 Mon Sep 17 00:00:00 2001
From: Andre Della Monica
Date: Thu, 2 Feb 2023 13:51:18 -0600
Subject: [PATCH 52/98] More changes
---
...topatch-windows-feature-update-overview.md | 22 +++++++++++++++----
1 file changed, 18 insertions(+), 4 deletions(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
index fb5db5fcd8..99ba4fc377 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
@@ -1,7 +1,7 @@
---
title: Windows feature updates
description: This article explains how Windows feature updates are managed in Autopatch
-ms.date: 02/01/2023
+ms.date: 02/02/2023
ms.prod: windows-client
ms.technology: itpro-updates
ms.topic: conceptual
@@ -14,10 +14,12 @@ msreviewer: andredm7
# Windows feature updates
-Microsoft provides robust mobile device management (MDM) solutions such as Microsoft Intune, Windows Update for Business, Configuration Manager etc. However, the administration of these solutions to keep Windows devices up to date with the latest Windows feature releases rests on your organization’s IT admins. The Windows feature update process is considered one of the most expensive and time consuming tasks for IT since it requires incremental rollout and validation. Windows feature updates:
+Microsoft provides robust mobile device management (MDM) solutions such as Microsoft Intune, Windows Update for Business, Configuration Manager etc. However, the administration of these solutions to keep Windows devices up to date with the latest Windows feature releases rests on your organization’s IT admins. The Windows feature update process is considered one of the most expensive and time consuming tasks for IT since it requires incremental rollout and validation.
-- Keep Windows devices protected against behavioral issues.
-- Provide new features to boost end-user productivity.
+Windows feature updates consist of:
+
+- Keeping Windows devices protected against behavioral issues.
+- Providing new features to boost end-user productivity.
Windows Autopatch makes it easier and less expensive for you to keep your Windows devices up to date so you can focus on running your core businesses while Windows Autopatch runs update management on your behalf.
@@ -86,6 +88,18 @@ Windows Autopatch provides a permanent pause of a Windows feature update deploym
> [!NOTE]
> Pausing or resuming an update can take up to eight hours to be applied to devices. This happens because Windows Autopatch uses Microsoft Intune as its management solution, and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
+### Pause statuses
+
+There are two statuses: **Service Paused** and **Customer Paused**.
+
+| Status | Description |
+| ----- | ------ |
+| Service Paused | If the Windows Autopatch service has paused an update, the release will have the **Service Paused** status. You must [submit a support request](windows-autopatch-support-request.md) to resume the update. |
+| Customer Paused | If you've paused an update, the release will have the **Customer Paused** status. The Windows Autopatch service can't overwrite a customer-initiated pause. You must select **Resume** to resume the update. |
+
+> [!IMPORTANT]
+> Service pause is only available for [Windows Quality Updates](windows-autopatch-windows-quality-update-overview.md). Windows Autopatch does not pause Windows Feature Updates on behalf of your organization.
+
## Rollback
Windows Autopatch doesn’t support the rollback of Windows Feature updates.
From ddcc4053f952838416d49759c181bde15f847940 Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Thu, 2 Feb 2023 12:04:06 -0800
Subject: [PATCH 53/98] Update
windows-autopatch-windows-feature-update-overview.md
---
...topatch-windows-feature-update-overview.md | 19 ++++++-------------
1 file changed, 6 insertions(+), 13 deletions(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
index 99ba4fc377..922597bb73 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
@@ -73,6 +73,9 @@ Windows Autopatch provides a permanent pause of a Windows feature update deploym
## Pausing and resuming a release
+> [!IMPORTANT]
+> Pausing or resuming an update can take up to eight hours to be applied to devices. This happens because Windows Autopatch uses Microsoft Intune as its management solution, and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
+
**To pause or resume a feature update:**
1. Go to the [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
@@ -85,20 +88,10 @@ Windows Autopatch provides a permanent pause of a Windows feature update deploym
8. If you're resuming an update, you can select one or more deployment rings.
9. Select **Okay**.
+If you've paused an update, the specified release will have the **Customer Paused** status. The Windows Autopatch service can't overwrite a customer-initiated pause. You must select **Resume** to resume the update.
+
> [!NOTE]
-> Pausing or resuming an update can take up to eight hours to be applied to devices. This happens because Windows Autopatch uses Microsoft Intune as its management solution, and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
-
-### Pause statuses
-
-There are two statuses: **Service Paused** and **Customer Paused**.
-
-| Status | Description |
-| ----- | ------ |
-| Service Paused | If the Windows Autopatch service has paused an update, the release will have the **Service Paused** status. You must [submit a support request](windows-autopatch-support-request.md) to resume the update. |
-| Customer Paused | If you've paused an update, the release will have the **Customer Paused** status. The Windows Autopatch service can't overwrite a customer-initiated pause. You must select **Resume** to resume the update. |
-
-> [!IMPORTANT]
-> Service pause is only available for [Windows Quality Updates](windows-autopatch-windows-quality-update-overview.md). Windows Autopatch does not pause Windows Feature Updates on behalf of your organization.
+> The Service Paused status only applies to [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release). Windows Autopatch doesn't pause Windows feature updates on your behalf.
## Rollback
From 2cb041666424d6ed1aa5464f144a820c179fd9b2 Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Thu, 2 Feb 2023 12:13:42 -0800
Subject: [PATCH 54/98] Update
windows-autopatch-windows-feature-update-overview.md
---
.../windows-autopatch-windows-feature-update-overview.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
index 922597bb73..f1cba8f922 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
@@ -74,7 +74,7 @@ Windows Autopatch provides a permanent pause of a Windows feature update deploym
## Pausing and resuming a release
> [!IMPORTANT]
-> Pausing or resuming an update can take up to eight hours to be applied to devices. This happens because Windows Autopatch uses Microsoft Intune as its management solution, and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
+> Pausing or resuming an update can take up to eight hours to be applied to devices, because Windows Autopatch uses Microsoft Intune as its management solution and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
**To pause or resume a feature update:**
From 93f2f5c2a0a1398bf9736e622ec0dc360346b26e Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Thu, 2 Feb 2023 12:40:38 -0800
Subject: [PATCH 55/98] Updated WQU release mgmt section with similar
instructions as feature updates.
---
...s-autopatch-windows-quality-update-overview.md | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
index 59cc60bb90..eb56d18767 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
@@ -110,7 +110,20 @@ Windows Autopatch schedules and deploys required Out of Band (OOB) updates relea
If Windows Autopatch detects a [significant issue with a release](../operate/windows-autopatch-windows-quality-update-signals.md), we may decide to pause that release.
-In the [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Release management** > in the **Release schedule** tab, you can pause or resume a Windows quality update.
+> [!IMPORTANT]
+> Pausing or resuming an update can take up to eight hours to be applied to devices, because Windows Autopatch uses Microsoft Intune as its management solution and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
+
+**To pause or resume a quality update:**
+
+1. Go to the [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
+1. Select **Devices** from the left navigation menu.
+1. Under the **Windows Autopatch** section, select **Release management**.
+1. In the **Release management** blade, select either: **Pause** or **Resume**.
+1. Select the update type you would like to pause or resume.
+1. Select a reason from the dropdown menu.
+1. Optional. Enter details about why you're pausing or resuming the selected update.
+1. If you're resuming an update, you can select one or more deployment rings.
+1. Select **Okay**.
There are two statuses associated with paused quality updates, **Service Paused** and **Customer Paused**.
From c688efc7542d1c598e684bca5d63d89e80b1f28c Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Thu, 2 Feb 2023 12:45:22 -0800
Subject: [PATCH 56/98] Tweak
---
...-autopatch-windows-quality-update-overview.md | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
index eb56d18767..4d4570df39 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
@@ -116,14 +116,14 @@ If Windows Autopatch detects a [significant issue with a release](../operate/win
**To pause or resume a quality update:**
1. Go to the [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
-1. Select **Devices** from the left navigation menu.
-1. Under the **Windows Autopatch** section, select **Release management**.
-1. In the **Release management** blade, select either: **Pause** or **Resume**.
-1. Select the update type you would like to pause or resume.
-1. Select a reason from the dropdown menu.
-1. Optional. Enter details about why you're pausing or resuming the selected update.
-1. If you're resuming an update, you can select one or more deployment rings.
-1. Select **Okay**.
+2. Select **Devices** from the left navigation menu.
+3. Under the **Windows Autopatch** section, select **Release management**.
+4. In the **Release management** blade, select either: **Pause** or **Resume**.
+5. Select the update type you would like to pause or resume.
+6. Select a reason from the dropdown menu.
+7. Optional. Enter details about why you're pausing or resuming the selected update.
+8. If you're resuming an update, you can select one or more deployment rings.
+9. Select **Okay**.
There are two statuses associated with paused quality updates, **Service Paused** and **Customer Paused**.
From a688e3437ee0aa5725f845f14bdc735dd06f8264 Mon Sep 17 00:00:00 2001
From: Angela Fleischmann
Date: Thu, 2 Feb 2023 14:24:14 -0700
Subject: [PATCH 57/98] Update using-event-viewer-with-applocker.md
Line 58: Remove extra spaces.
---
.../using-event-viewer-with-applocker.md | 39 +++++++++----------
1 file changed, 19 insertions(+), 20 deletions(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/applocker/using-event-viewer-with-applocker.md b/windows/security/threat-protection/windows-defender-application-control/applocker/using-event-viewer-with-applocker.md
index ed7b6721dc..d10ebcfc03 100644
--- a/windows/security/threat-protection/windows-defender-application-control/applocker/using-event-viewer-with-applocker.md
+++ b/windows/security/threat-protection/windows-defender-application-control/applocker/using-event-viewer-with-applocker.md
@@ -30,16 +30,16 @@ ms.date: 02/02/2023
This article lists AppLocker events and describes how to use Event Viewer with AppLocker.
-The AppLocker log contains information about applications that are affected by AppLocker rules. Each event in the log contains detailed info about:
+The AppLocker log contains information about applications that are affected by AppLocker rules. Each event in the log contains details such as the following information:
-- Which file is affected and the path of that file
-- Which packaged app is affected and the package identifier of the app
-- Whether the file or packaged app is allowed or blocked
-- The rule type (path, file hash, or publisher)
-- The rule name
-- The security identifier (SID) for the user or group identified in the rule
+- Which file is affected and the path of that file
+- Which packaged app is affected and the package identifier of the app
+- Whether the file or packaged app is allowed or blocked
+- The rule type (path, file hash, or publisher)
+- The rule name
+- The security identifier (SID) for the user or group identified in the rule
-Review the entries in the Event Viewer to determine if any applications aren't included in the rules that you automatically generated. For instance, some line-of-business apps are installed to non-standard locations, such as the root of the active drive (for example: %SystemDrive%).
+Review the entries in the Event Viewer to determine if any applications aren't included in the rules that you automatically generated. For instance, some line-of-business apps are installed to non-standard locations, such as the root of the active drive (for example, `%SystemDrive%`).
For info about what to look for in the AppLocker event logs, see [Monitor app usage with AppLocker](monitor-application-usage-with-applocker.md).
@@ -48,24 +48,24 @@ For info about what to look for in the AppLocker event logs, see [Monitor app us
**To review the AppLocker log in Event Viewer**
-1. Open Event Viewer.
-2. In the console tree under **Application and Services Logs\\Microsoft\\Windows**, select **AppLocker**.
+1. Open Event Viewer.
+2. In the console tree under **Application and Services Logs\\Microsoft\\Windows**, select **AppLocker**.
The following table contains information about the events that you can use to determine which apps are affected by AppLocker rules.
| Event ID | Level | Event message | Description |
-| - | - | - | - |
-| 8000 | Error| Application Identity Policy conversion failed. Status *<%1> *| Indicates that the policy wasn't applied correctly to the computer. The status message is provided for troubleshooting purposes.|
+| --- | --- | --- | --- |
+| 8000 | Error| Application Identity Policy conversion failed. Status *<%1>*| Indicates that the policy wasn't applied correctly to the computer. The status message is provided for troubleshooting purposes.|
| 8001 | Information| The AppLocker policy was applied successfully to this computer.| Indicates that the AppLocker policy was successfully applied to the computer.|
-| 8002 | Information| *<File name> * was allowed to run.| Specifies that the .exe or .dll file is allowed by an AppLocker rule.|
-| 8003 | Warning| *<File name> * was allowed to run but would have been prevented from running if the AppLocker policy was enforced.| Applied only when the **Audit only** enforcement mode is enabled. Specifies that the .exe or .dll file would be blocked if the **Enforce rules** enforcement mode were enabled. |
-| 8004 | Error| *<File name> * was not allowed to run.| Access to *<file name>* is restricted by the administrator. Applied only when the **Enforce rules** enforcement mode is set either directly or indirectly through Group Policy inheritance. The .exe or .dll file can't run.|
-| 8005| Information| *<File name> * was allowed to run.| Specifies that the script or .msi file is allowed by an AppLocker rule.|
-| 8006 | Warning| *<File name> * was allowed to run but would have been prevented from running if the AppLocker policy was enforced.| Applied only when the **Audit only** enforcement mode is enabled. Specifies that the script or .msi file would be blocked if the **Enforce rules** enforcement mode were enabled. |
-| 8007 | Error| *<File name> * was not allowed to run.| Access to *<file name>* is restricted by the administrator. Applied only when the **Enforce rules** enforcement mode is set either directly or indirectly through Group Policy inheritance. The script or .msi file can't run.|
+| 8002 | Information| *<File name> * was allowed to run.| Specifies that the .exe or .dll file is allowed by an AppLocker rule.|
+| 8003 | Warning| *<File name> * was allowed to run but would have been prevented from running if the AppLocker policy was enforced.| Applied only when the **Audit only** enforcement mode is enabled. Specifies that the .exe or .dll file would be blocked if the **Enforce rules** enforcement mode were enabled. |
+| 8004 | Error| *<File name> * was not allowed to run.| Access to *<file name>* is restricted by the administrator. Applied only when the **Enforce rules** enforcement mode is set either directly or indirectly through Group Policy inheritance. The .exe or .dll file can't run.|
+| 8005| Information| *<File name> * was allowed to run.| Specifies that the script or .msi file is allowed by an AppLocker rule.|
+| 8006 | Warning| *<File name> * was allowed to run but would have been prevented from running if the AppLocker policy was enforced.| Applied only when the **Audit only** enforcement mode is enabled. Specifies that the script or .msi file would be blocked if the **Enforce rules** enforcement mode were enabled. |
+| 8007 | Error| *<File name> * was not allowed to run.| Access to *<file name>* is restricted by the administrator. Applied only when the **Enforce rules** enforcement mode is set either directly or indirectly through Group Policy inheritance. The script or .msi file can't run.|
| 8008| Error| AppLocker disabled on the SKU.| Added in Windows Server 2012 and Windows 8.|
| 8020| Information| Packaged app allowed.| Added in Windows Server 2012 and Windows 8.|
-| 8021| Information| Packaged app audited.| Added in Windows Server 2012 and Windows 8.|
+| 8021| Information| Packaged app audited.| Added in Windows Server 2012 and Windows 8.|
| 8022| Information| Packaged app disabled.| Added in Windows Server 2012 and Windows 8.|
| 8023 | Information| Packaged app installation allowed.| Added in Windows Server 2012 and Windows 8.|
| 8024 | Information| Packaged app installation audited.| Added in Windows Server 2012 and Windows 8.|
@@ -90,4 +90,3 @@ The following table contains information about the events that you can use to de
- [Tools to use with AppLocker](tools-to-use-with-applocker.md)
-
From bb17ce2c681b089b05ae0fb631ba673c1841af8b Mon Sep 17 00:00:00 2001
From: Angela Fleischmann
Date: Thu, 2 Feb 2023 14:26:49 -0700
Subject: [PATCH 58/98] Update
windows/security/threat-protection/windows-defender-application-control/design/script-enforcement.md
Line 41: Correct the placement of a period.
---
.../design/script-enforcement.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/design/script-enforcement.md b/windows/security/threat-protection/windows-defender-application-control/design/script-enforcement.md
index 29174ef291..d8598308cd 100644
--- a/windows/security/threat-protection/windows-defender-application-control/design/script-enforcement.md
+++ b/windows/security/threat-protection/windows-defender-application-control/design/script-enforcement.md
@@ -38,7 +38,7 @@ Validation for signed scripts is done using the [WinVerifyTrust API](/windows/wi
WDAC shares the *AppLocker - MSI and Script* event log for all script enforcement events. Whenever a script host asks WDAC if a script should be allowed, an event will be logged with the answer WDAC returned to the script host. For more information on WDAC script enforcement events, see [Understanding Application Control events](/windows/security/threat-protection/windows-defender-application-control/event-id-explanations#windows-applocker-msi-and-script-log).
> [!NOTE]
-> When a script runs that is not allowed by policy, WDAC raises an event indicating that the script was "blocked". However, the actual script enforcement behavior is handled by the script host and may not actually completely block the file from running.
+> When a script runs that is not allowed by policy, WDAC raises an event indicating that the script was "blocked." However, the actual script enforcement behavior is handled by the script host and may not actually completely block the file from running.
>
> Also be aware that some script hosts may change how they behave even if a WDAC policy is in audit mode only. You should review the information below for each script host and test thoroughly within your environment to ensure the scripts you need to run are working properly.
From 78db741ab05034a92db5a5e0b624c6b51bc56d61 Mon Sep 17 00:00:00 2001
From: Angela Fleischmann
Date: Thu, 2 Feb 2023 14:29:57 -0700
Subject: [PATCH 59/98] Update
windows/security/threat-protection/windows-defender-application-control/applocker/using-event-viewer-with-applocker.md
Line 58: Replace extra spaces.
---
.../applocker/using-event-viewer-with-applocker.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/security/threat-protection/windows-defender-application-control/applocker/using-event-viewer-with-applocker.md b/windows/security/threat-protection/windows-defender-application-control/applocker/using-event-viewer-with-applocker.md
index d10ebcfc03..00a6cb48d3 100644
--- a/windows/security/threat-protection/windows-defender-application-control/applocker/using-event-viewer-with-applocker.md
+++ b/windows/security/threat-protection/windows-defender-application-control/applocker/using-event-viewer-with-applocker.md
@@ -55,7 +55,7 @@ The following table contains information about the events that you can use to de
| Event ID | Level | Event message | Description |
| --- | --- | --- | --- |
-| 8000 | Error| Application Identity Policy conversion failed. Status *<%1>*| Indicates that the policy wasn't applied correctly to the computer. The status message is provided for troubleshooting purposes.|
+| 8000 | Error| Application Identity Policy conversion failed. Status * <%1> *| Indicates that the policy wasn't applied correctly to the computer. The status message is provided for troubleshooting purposes.|
| 8001 | Information| The AppLocker policy was applied successfully to this computer.| Indicates that the AppLocker policy was successfully applied to the computer.|
| 8002 | Information| *<File name> * was allowed to run.| Specifies that the .exe or .dll file is allowed by an AppLocker rule.|
| 8003 | Warning| *<File name> * was allowed to run but would have been prevented from running if the AppLocker policy was enforced.| Applied only when the **Audit only** enforcement mode is enabled. Specifies that the .exe or .dll file would be blocked if the **Enforce rules** enforcement mode were enabled. |
From ac76087c4ce36c585371c5fcf6e3bebf7f6c7274 Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Thu, 2 Feb 2023 13:43:28 -0800
Subject: [PATCH 60/98] Tweak
---
.../windows-autopatch-windows-feature-update-overview.md | 2 +-
.../windows-autopatch-windows-quality-update-overview.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
index f1cba8f922..4cc1f4a6ab 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
@@ -76,7 +76,7 @@ Windows Autopatch provides a permanent pause of a Windows feature update deploym
> [!IMPORTANT]
> Pausing or resuming an update can take up to eight hours to be applied to devices, because Windows Autopatch uses Microsoft Intune as its management solution and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
-**To pause or resume a feature update:**
+**To pause or resume a Windows feature update:**
1. Go to the [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
2. Select **Devices** from the left navigation menu.
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
index 4d4570df39..75c2765189 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
@@ -113,7 +113,7 @@ If Windows Autopatch detects a [significant issue with a release](../operate/win
> [!IMPORTANT]
> Pausing or resuming an update can take up to eight hours to be applied to devices, because Windows Autopatch uses Microsoft Intune as its management solution and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
-**To pause or resume a quality update:**
+**To pause or resume a Windows quality update:**
1. Go to the [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
2. Select **Devices** from the left navigation menu.
From 449ef376cd6d427c4f70977d68d1fa08106604d1 Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Thu, 2 Feb 2023 13:45:40 -0800
Subject: [PATCH 61/98] Tweak
---
.../windows-autopatch-windows-feature-update-overview.md | 2 +-
.../windows-autopatch-windows-quality-update-overview.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
index 4cc1f4a6ab..e63ff0668b 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
@@ -74,7 +74,7 @@ Windows Autopatch provides a permanent pause of a Windows feature update deploym
## Pausing and resuming a release
> [!IMPORTANT]
-> Pausing or resuming an update can take up to eight hours to be applied to devices, because Windows Autopatch uses Microsoft Intune as its management solution and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
+> Pausing or resuming an update can take up to eight hours to be applied to devices. Windows Autopatch uses Microsoft Intune as its management solution and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
**To pause or resume a Windows feature update:**
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
index 75c2765189..52eb955e6c 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
@@ -111,7 +111,7 @@ Windows Autopatch schedules and deploys required Out of Band (OOB) updates relea
If Windows Autopatch detects a [significant issue with a release](../operate/windows-autopatch-windows-quality-update-signals.md), we may decide to pause that release.
> [!IMPORTANT]
-> Pausing or resuming an update can take up to eight hours to be applied to devices, because Windows Autopatch uses Microsoft Intune as its management solution and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
+> Pausing or resuming an update can take up to eight hours to be applied to devices. Windows Autopatch uses Microsoft Intune as its management solution and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
**To pause or resume a Windows quality update:**
From a5d38138e53544ff6bae3c632176c8bd97cb11e2 Mon Sep 17 00:00:00 2001
From: Sunny Zankharia <67922512+sazankha@users.noreply.github.com>
Date: Thu, 2 Feb 2023 15:47:50 -0800
Subject: [PATCH 62/98] Update faq-md-app-guard.yml
Added a section explaining how to open a support case
---
.../faq-md-app-guard.yml | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml b/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml
index 816d5da3f4..49e6301d05 100644
--- a/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml
+++ b/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml
@@ -223,7 +223,12 @@ sections:
What does the _Allow users to trust files that open in Microsoft Defender Application Guard_ option in the Group policy do?
answer: |
This policy was present in Windows 10 prior to version 2004. It was removed from later versions of Windows as it doesn't enforce anything for either Edge or Office.
-
+
+ - question: |
+ How do I open a support ticket for Microsoft Defender Application Guard?
+ answer: |
+ Go to this link: https://support.serviceshub.microsoft.com/supportforbusiness/create
+ Under the Product Family, select Windows. Select the product and the product version you need help with. For the category that best desribes the issue, select, 'Windows Security Tecnologies'. In the final option, select, 'Windows Defender Application Guard'.
additionalContent: |
From 23e905f44f72161a78d85753cbaf8ea926d911a4 Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Thu, 2 Feb 2023 17:24:44 -0800
Subject: [PATCH 63/98] MEM not EM
---
.../windows-autopatch-windows-feature-update-overview.md | 2 +-
.../windows-autopatch-windows-quality-update-overview.md | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
index e63ff0668b..59b3f9d138 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
@@ -78,7 +78,7 @@ Windows Autopatch provides a permanent pause of a Windows feature update deploym
**To pause or resume a Windows feature update:**
-1. Go to the [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
+1. Go to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
2. Select **Devices** from the left navigation menu.
3. Under the **Windows Autopatch** section, select **Release management**.
4. In the **Release management** blade, select either: **Pause** or **Resume**.
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
index 52eb955e6c..d4fc020a8f 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
@@ -88,7 +88,7 @@ By default, the service expedites quality updates as needed. For those organizat
**To turn off service-driven expedited quality updates:**
-1. Go to **[Microsoft Endpoint Manager portal](https://go.microsoft.com/fwlink/?linkid=2109431)** > **Devices**.
+1. Go to **[Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431)** > **Devices**.
2. Under **Windows Autopatch** > **Release management**, go to the **Release settings** tab and turn off the **Expedited Quality Updates** setting.
> [!NOTE]
@@ -100,7 +100,7 @@ Windows Autopatch schedules and deploys required Out of Band (OOB) updates relea
**To view deployed Out of Band quality updates:**
-1. Go to [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Devices** > **Windows Autopatch** > **Release management**.
+1. Go to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Devices** > **Windows Autopatch** > **Release management**.
2. Under the **Release Announcements** tab, you can view the knowledge base (KB) articles corresponding to deployed OOB and regular Windows quality updates.
> [!NOTE]
@@ -115,7 +115,7 @@ If Windows Autopatch detects a [significant issue with a release](../operate/win
**To pause or resume a Windows quality update:**
-1. Go to the [Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
+1. Go to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
2. Select **Devices** from the left navigation menu.
3. Under the **Windows Autopatch** section, select **Release management**.
4. In the **Release management** blade, select either: **Pause** or **Resume**.
From 2e1f63aeafd85cd4bf8dd817a0a46d2b4c0d360a Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Thu, 2 Feb 2023 17:38:04 -0800
Subject: [PATCH 64/98] Tiara you twit.
---
.../windows-autopatch-windows-quality-update-overview.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
index d4fc020a8f..c8ab6062c6 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
@@ -100,7 +100,7 @@ Windows Autopatch schedules and deploys required Out of Band (OOB) updates relea
**To view deployed Out of Band quality updates:**
-1. Go to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Devices** > **Windows Autopatch** > **Release management**.
+1. Go to [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Devices** > **Windows Autopatch** > **Release management**.
2. Under the **Release Announcements** tab, you can view the knowledge base (KB) articles corresponding to deployed OOB and regular Windows quality updates.
> [!NOTE]
From caf39b5a087c6455fb8f99e2b71e93d3f384ecd1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Rafa=C5=82=20Fitt?=
<36852431+rafalfitt@users.noreply.github.com>
Date: Fri, 3 Feb 2023 10:13:18 +0100
Subject: [PATCH 65/98] Update
user-account-control-behavior-of-the-elevation-prompt-for-standard-users.md
sync with best practices, see https://github.com/MicrosoftDocs/windows-itpro-docs/commit/c66f5f99b1ee002661c50a9faa0adebe380d5c7f
---
...ntrol-behavior-of-the-elevation-prompt-for-standard-users.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/security/threat-protection/security-policy-settings/user-account-control-behavior-of-the-elevation-prompt-for-standard-users.md b/windows/security/threat-protection/security-policy-settings/user-account-control-behavior-of-the-elevation-prompt-for-standard-users.md
index 2bbf3a6015..1d3ea2ed65 100644
--- a/windows/security/threat-protection/security-policy-settings/user-account-control-behavior-of-the-elevation-prompt-for-standard-users.md
+++ b/windows/security/threat-protection/security-policy-settings/user-account-control-behavior-of-the-elevation-prompt-for-standard-users.md
@@ -78,7 +78,7 @@ One of the risks that the UAC feature tries to mitigate is that of malicious pro
### Countermeasure
-Configure the **User Account Control: Behavior of the elevation prompt for standard users** to **Automatically deny elevation requests**. This setting requires the user to sign in with an administrative account to run programs that require elevation of privilege. As a security best practice, standard users shouldn't have knowledge of administrative passwords. However, if your users have both standard and administrator-level accounts, we recommend setting **Prompt for credentials** so that the users don't choose to always sign in with their administrator accounts, and they shift their behavior to use the standard user account.
+Configure the **User Account Control: Behavior of the elevation prompt for standard users** to **Automatically deny elevation requests**. This setting requires the user to sign in with an administrative account to run programs that require elevation of privilege. As a security best practice, standard users shouldn't have knowledge of administrative passwords. However, if your users have both standard and administrator-level accounts, we recommend setting **Prompt for credentials on the secure desktop** so that the users don't choose to always sign in with their administrator accounts, and they shift their behavior to use the standard user account.
### Potential impact
From 85b9ad323629942d53e26d6da3c7a01da461207a Mon Sep 17 00:00:00 2001
From: Sunny Zankharia <67922512+sazankha@users.noreply.github.com>
Date: Fri, 3 Feb 2023 08:13:16 -0800
Subject: [PATCH 66/98] Update
windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml
Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
.../microsoft-defender-application-guard/faq-md-app-guard.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml b/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml
index 49e6301d05..3933bfc00f 100644
--- a/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml
+++ b/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml
@@ -227,7 +227,7 @@ sections:
- question: |
How do I open a support ticket for Microsoft Defender Application Guard?
answer: |
- Go to this link: https://support.serviceshub.microsoft.com/supportforbusiness/create
+ [Create a new support request](https://support.serviceshub.microsoft.com/supportforbusiness/create).
Under the Product Family, select Windows. Select the product and the product version you need help with. For the category that best desribes the issue, select, 'Windows Security Tecnologies'. In the final option, select, 'Windows Defender Application Guard'.
additionalContent: |
From e4e86344229fba0f81ac28593bf79be563c087b1 Mon Sep 17 00:00:00 2001
From: Sunny Zankharia <67922512+sazankha@users.noreply.github.com>
Date: Fri, 3 Feb 2023 08:13:27 -0800
Subject: [PATCH 67/98] Update
windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml
Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>
---
.../microsoft-defender-application-guard/faq-md-app-guard.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml b/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml
index 3933bfc00f..d7bbb33704 100644
--- a/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml
+++ b/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml
@@ -228,7 +228,7 @@ sections:
How do I open a support ticket for Microsoft Defender Application Guard?
answer: |
[Create a new support request](https://support.serviceshub.microsoft.com/supportforbusiness/create).
- Under the Product Family, select Windows. Select the product and the product version you need help with. For the category that best desribes the issue, select, 'Windows Security Tecnologies'. In the final option, select, 'Windows Defender Application Guard'.
+ Under the Product Family, select Windows. Select the product and the product version you need help with. For the category that best describes the issue, select, **Windows Security Technologies**. In the final option, select **Windows Defender Application Guard**.
additionalContent: |
From b6ea2673755d1f8a80af9f1ea3e547762f7180b7 Mon Sep 17 00:00:00 2001
From: Andre Della Monica
Date: Fri, 3 Feb 2023 10:20:14 -0600
Subject: [PATCH 68/98] More changes
---
.../deploy/windows-autopatch-register-devices.md | 5 ++++-
.../windows-autopatch-windows-feature-update-overview.md | 2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
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 17cf0bb228..8750604713 100644
--- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
+++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
@@ -1,7 +1,7 @@
---
title: Register your devices
description: This article details how to register devices in Autopatch
-ms.date: 09/07/2022
+ms.date: 02/03/2023
ms.prod: windows-client
ms.technology: itpro-updates
ms.topic: how-to
@@ -39,6 +39,9 @@ Windows Autopatch automatically runs its discover devices function every hour to
> [!NOTE]
> Devices that are intended to be managed by the Windows Autopatch service **must** be added into the **Windows Autopatch Device Registration** Azure AD assigned group. Devices can only be added to this group if they have an Azure AD device ID. Windows Autopatch scans the Azure AD group hourly to discover newly added devices to be registered. You can also use the **Discover devices** button in either the **Ready** or **Not ready** tab to register devices on demand.
+> [!IMPORTANT]
+> Windows Autopatch supports only one level of group-nesting in the **Windows Autopatch Device Registration** Azure AD group.
+
#### Supported scenarios when nesting other Azure AD groups
Windows Autopatch also supports the following Azure AD nested group scenarios:
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
index 59b3f9d138..b58aa2938f 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
@@ -91,7 +91,7 @@ Windows Autopatch provides a permanent pause of a Windows feature update deploym
If you've paused an update, the specified release will have the **Customer Paused** status. The Windows Autopatch service can't overwrite a customer-initiated pause. You must select **Resume** to resume the update.
> [!NOTE]
-> The Service Paused status only applies to [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release). Windows Autopatch doesn't pause Windows feature updates on your behalf.
+> The **Service Paused** status only applies to [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release). Windows Autopatch doesn't pause Windows feature updates on your behalf.
## Rollback
From 5d608ab8a48daac23c40b4197ec542efedda197a Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Fri, 3 Feb 2023 08:29:34 -0800
Subject: [PATCH 69/98] Update windows-autopatch-register-devices.md
---
.../deploy/windows-autopatch-register-devices.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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 8750604713..ca625dc2d8 100644
--- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
+++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
@@ -55,7 +55,7 @@ Azure AD groups synced up from:
> It isn't recommended to sync Configuration Manager collections straight to the **Windows Autopatch Device Registration** Azure AD group. Use a different Azure AD group when syncing Configuration Manager collections to Azure AD groups then you can nest this or these groups into the **Windows Autopatch Device Registration** Azure AD group.
> [!IMPORTANT]
-> The **Windows Autopatch Device Registration** Azure AD group only supports one level of Azure AD nested groups.
+> The **Windows Autopatch Device Registration** Azure AD group only supports **one level** of Azure AD nested groups.
### Clean up dual state of Hybrid Azure AD joined and Azure registered devices in your Azure AD tenant
From 9a7f5b54e206ca0d5cf898d268c0657c8aa9e5ef Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Fri, 3 Feb 2023 08:42:56 -0800
Subject: [PATCH 70/98] Update windows-autopatch-register-devices.md
---
.../deploy/windows-autopatch-register-devices.md | 3 ---
1 file changed, 3 deletions(-)
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 ca625dc2d8..a6540780aa 100644
--- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
+++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md
@@ -39,9 +39,6 @@ Windows Autopatch automatically runs its discover devices function every hour to
> [!NOTE]
> Devices that are intended to be managed by the Windows Autopatch service **must** be added into the **Windows Autopatch Device Registration** Azure AD assigned group. Devices can only be added to this group if they have an Azure AD device ID. Windows Autopatch scans the Azure AD group hourly to discover newly added devices to be registered. You can also use the **Discover devices** button in either the **Ready** or **Not ready** tab to register devices on demand.
-> [!IMPORTANT]
-> Windows Autopatch supports only one level of group-nesting in the **Windows Autopatch Device Registration** Azure AD group.
-
#### Supported scenarios when nesting other Azure AD groups
Windows Autopatch also supports the following Azure AD nested group scenarios:
From b7791e02072c87c14da2238db282c5337684ed34 Mon Sep 17 00:00:00 2001
From: Vinay Pamnani <37223378+vinaypamnani-msft@users.noreply.github.com>
Date: Fri, 3 Feb 2023 11:50:33 -0500
Subject: [PATCH 71/98] Update faq-md-app-guard.yml
Fix indentation
---
.../faq-md-app-guard.yml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml b/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml
index d7bbb33704..a2c40f975e 100644
--- a/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml
+++ b/windows/security/threat-protection/microsoft-defender-application-guard/faq-md-app-guard.yml
@@ -222,13 +222,13 @@ sections:
- question: |
What does the _Allow users to trust files that open in Microsoft Defender Application Guard_ option in the Group policy do?
answer: |
- This policy was present in Windows 10 prior to version 2004. It was removed from later versions of Windows as it doesn't enforce anything for either Edge or Office.
+ This policy was present in Windows 10 prior to version 2004. It was removed from later versions of Windows as it doesn't enforce anything for either Edge or Office.
- - question: |
+ - question: |
How do I open a support ticket for Microsoft Defender Application Guard?
answer: |
- [Create a new support request](https://support.serviceshub.microsoft.com/supportforbusiness/create).
- Under the Product Family, select Windows. Select the product and the product version you need help with. For the category that best describes the issue, select, **Windows Security Technologies**. In the final option, select **Windows Defender Application Guard**.
+ - Visit [Create a new support request](https://support.serviceshub.microsoft.com/supportforbusiness/create).
+ - Under the Product Family, select Windows. Select the product and the product version you need help with. For the category that best describes the issue, select, **Windows Security Technologies**. In the final option, select **Windows Defender Application Guard**.
additionalContent: |
From d85300ca59615b806e5a9aa48fd6b0a642cc51a8 Mon Sep 17 00:00:00 2001
From: Vinay Pamnani <37223378+vinaypamnani-msft@users.noreply.github.com>
Date: Fri, 3 Feb 2023 12:33:18 -0500
Subject: [PATCH 72/98] Update Update CSP
---
.../mdm/policies-in-policy-csp-supported-by-group-policy.md | 3 ++-
windows/client-management/mdm/policy-csp-update.md | 5 ++++-
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/windows/client-management/mdm/policies-in-policy-csp-supported-by-group-policy.md b/windows/client-management/mdm/policies-in-policy-csp-supported-by-group-policy.md
index e6748d67f8..2b636d3e4f 100644
--- a/windows/client-management/mdm/policies-in-policy-csp-supported-by-group-policy.md
+++ b/windows/client-management/mdm/policies-in-policy-csp-supported-by-group-policy.md
@@ -4,7 +4,7 @@ description: Learn about the policies in Policy CSP supported by Group Policy.
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa
-ms.date: 01/30/2023
+ms.date: 02/03/2023
ms.localizationpriority: medium
ms.prod: windows-client
ms.technology: itpro-manage
@@ -814,6 +814,7 @@ This article lists the policies in Policy CSP that have a group policy mapping.
- [SetPolicyDrivenUpdateSourceForOtherUpdates](policy-csp-update.md)
- [SetEDURestart](policy-csp-update.md)
- [AllowAutoWindowsUpdateDownloadOverMeteredNetwork](policy-csp-update.md)
+- [AllowTemporaryEnterpriseFeatureControl](policy-csp-update.md)
- [SetDisableUXWUAccess](policy-csp-update.md)
- [SetDisablePauseUXAccess](policy-csp-update.md)
- [UpdateNotificationLevel](policy-csp-update.md)
diff --git a/windows/client-management/mdm/policy-csp-update.md b/windows/client-management/mdm/policy-csp-update.md
index 7a183cb82b..434acb5dde 100644
--- a/windows/client-management/mdm/policy-csp-update.md
+++ b/windows/client-management/mdm/policy-csp-update.md
@@ -4,7 +4,7 @@ description: Learn more about the Update Area in Policy CSP.
author: vinaypamnani-msft
manager: aaroncz
ms.author: vinpa
-ms.date: 01/31/2023
+ms.date: 02/03/2023
ms.localizationpriority: medium
ms.prod: windows-client
ms.technology: itpro-manage
@@ -16,6 +16,9 @@ ms.topic: reference
# Policy CSP - Update
+> [!IMPORTANT]
+> This CSP contains preview policies that are under development and only applicable for [Windows Insider Preview builds](/windows-insider/). These policies are subject to change and may have dependencies on other features or services in preview.
+
From 570db9497514aff2d94c59e5e602442aad7fd6e6 Mon Sep 17 00:00:00 2001
From: Evan Miller
Date: Fri, 3 Feb 2023 10:31:27 -0800
Subject: [PATCH 73/98] Update HL2 Policies
---
...es-in-policy-csp-supported-by-hololens2.md | 27 ++++++++++++++++---
1 file changed, 23 insertions(+), 4 deletions(-)
diff --git a/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md
index ee5e75bc24..7545fd6751 100644
--- a/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md
+++ b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md
@@ -9,7 +9,7 @@ ms.prod: windows-client
ms.technology: itpro-manage
author: vinaypamnani-msft
ms.localizationpriority: medium
-ms.date: 08/01/2022
+ms.date: 02/03/2023
---
# Policies in Policy CSP supported by HoloLens 2
@@ -31,7 +31,20 @@ ms.date: 08/01/2022
- [Browser/AllowSearchSuggestionsinAddressBar](policy-csp-browser.md#allowsearchsuggestionsinaddressbar)
- [Browser/AllowSmartScreen](policy-csp-browser.md#allowsmartscreen)
- [Connectivity/AllowBluetooth](policy-csp-connectivity.md#allowbluetooth)
+- [Connectivity/AllowConnectedDevices](policy-csp-connectivity.md#allowconnecteddevices)
- [Connectivity/AllowUSBConnection](policy-csp-connectivity.md#allowusbconnection)
+- [DeliveryOptimization/DOCacheHost](policy-csp-deliveryoptimization.md#docachehost) 10
+- [DeliveryOptimization/DOCacheHostSource](policy-csp-deliveryoptimization.md#docachehostsource) 10
+- [DeliveryOptimization/DODelayCacheServerFallbackBackground](policy-csp-deliveryoptimization.md#dodelaycacheserverfallbackbackground) 10
+- [DeliveryOptimization/DODelayCacheServerFallbackForeground](policy-csp-deliveryoptimization.md#dodelaycacheserverfallbackforeground) 10
+- [DeliveryOptimization/DODownloadMode](policy-csp-deliveryoptimization.md#dodownloadmode) 10
+- [DeliveryOptimization/DOMaxBackgroundDownloadBandwidth](policy-csp-deliveryoptimization.md#domaxbackgrounddownloadbandwidth) 10
+- [DeliveryOptimization/DOMaxForegroundDownloadBandwidth](policy-csp-deliveryoptimization.md#domaxforegrounddownloadbandwidth) 10
+- [DeliveryOptimization/DOPercentageMaxBackgroundBandwidth](policy-csp-deliveryoptimization.md#dopercentagemaxbackgroundbandwidth) 10
+- [DeliveryOptimization/DOPercentageMaxForegroundBandwidth](policy-csp-deliveryoptimization.md#dopercentagemaxforegroundbandwidth) 10
+- [DeliveryOptimization/DOSetHoursToLimitForegroundDownloadBandwidth](policy-csp-deliveryoptimization.md#dosethourstolimitforegrounddownloadbandwidth) 10
+- [DeliveryOptimization/DOSetHoursToLimitBackgroundDownloadBandwidth](policy-csp-deliveryoptimization.md#dosethourstolimitbackgrounddownloadbandwidth) 10
+- [DeliveryOptimization/DOSetHoursToLimitBackgroundDownloadBandwidth](policy-csp-deliveryoptimization.md#dosethourstolimitbackgrounddownloadbandwidth) 10
- [DeviceLock/AllowIdleReturnWithoutPassword](policy-csp-devicelock.md#allowidlereturnwithoutpassword)
- [DeviceLock/AllowSimpleDevicePassword](policy-csp-devicelock.md#allowsimpledevicepassword)
- [DeviceLock/AlphanumericDevicePasswordRequired](policy-csp-devicelock.md#alphanumericdevicepasswordrequired)
@@ -44,7 +57,8 @@ ms.date: 08/01/2022
- [DeviceLock/MinDevicePasswordLength](policy-csp-devicelock.md#mindevicepasswordlength)
- [Experience/AllowCortana](policy-csp-experience.md#allowcortana)
- [Experience/AllowManualMDMUnenrollment](policy-csp-experience.md#allowmanualmdmunenrollment)
-- [MixedReality/AADGroupMembershipCacheValidityInDays](policy-csp-mixedreality.md#aadgroupmembershipcachevalidityindays)
+- [MemoryDump/AllowCrashDump](policy-csp-memorydump.md#allowcrashdump)
+- [MemoryDump/AllowLivehDump](policy-csp-memorydump.md#allowlivedump)
- [MixedReality/AADGroupMembershipCacheValidityInDays](./policy-csp-mixedreality.md#aadgroupmembershipcachevalidityindays) 9
- [MixedReality/AllowCaptivePortalBeforeLogon](./policy-csp-mixedreality.md#allowcaptiveportalbeforelogon) 12
- [MixedReality/AllowLaunchUriInSingleAppKiosk](./policy-csp-mixedreality.md#allowlaunchuriinsingleappkiosk)10
@@ -78,6 +92,7 @@ ms.date: 08/01/2022
- [Privacy/LetAppsAccessBackgroundSpatialPerception_ForceAllowTheseApps](policy-csp-privacy.md#letappsaccessbackgroundspatialperception_forceallowtheseapps)
- [Privacy/LetAppsAccessBackgroundSpatialPerception_ForceDenyTheseApps](policy-csp-privacy.md#letappsaccessbackgroundspatialperception_forcedenytheseapps)
- [Privacy/LetAppsAccessBackgroundSpatialPerception_UserInControlOfTheseApps](policy-csp-privacy.md#letappsaccessbackgroundspatialperception_userincontroloftheseapps)
+- [Privacy/LetAppsAccessCamera](policy-csp-privacy.md#letappsaccesscamera)
- [Privacy/LetAppsAccessCamera_ForceAllowTheseApps](policy-csp-privacy.md#letappsaccesscamera_forceallowtheseapps) 8
- [Privacy/LetAppsAccessCamera_ForceDenyTheseApps](policy-csp-privacy.md#letappsaccesscamera_forcedenytheseapps) 8
- [Privacy/LetAppsAccessCamera_UserInControlOfTheseApps](policy-csp-privacy.md#letappsaccesscamera_userincontroloftheseapps) 8
@@ -85,13 +100,11 @@ ms.date: 08/01/2022
- [Privacy/LetAppsAccessGazeInput_ForceAllowTheseApps](policy-csp-privacy.md#letappsaccessgazeinput_forceallowtheseapps) 8
- [Privacy/LetAppsAccessGazeInput_ForceDenyTheseApps](policy-csp-privacy.md#letappsaccessgazeinput_forcedenytheseapps) 8
- [Privacy/LetAppsAccessGazeInput_UserInControlOfTheseApps](policy-csp-privacy.md#letappsaccessgazeinput_userincontroloftheseapps) 8
-- [Privacy/LetAppsAccessCamera](policy-csp-privacy.md#letappsaccesscamera)
- [Privacy/LetAppsAccessLocation](policy-csp-privacy.md#letappsaccesslocation)
- [Privacy/LetAppsAccessMicrophone](policy-csp-privacy.md#letappsaccessmicrophone)
- [Privacy/LetAppsAccessMicrophone_ForceAllowTheseApps](policy-csp-privacy.md#letappsaccessmicrophone_forceallowtheseapps) 8
- [Privacy/LetAppsAccessMicrophone_ForceDenyTheseApps](policy-csp-privacy.md#letappsaccessmicrophone_forcedenytheseapps) 8
- [Privacy/LetAppsAccessMicrophone_UserInControlOfTheseApps](policy-csp-privacy.md#letappsaccessmicrophone_userincontroloftheseapps) 8
-- [RemoteLock/Lock](./remotelock-csp.md) 9
- [Search/AllowSearchToUseLocation](policy-csp-search.md#allowsearchtouselocation)
- [Security/AllowAddProvisioningPackage](policy-csp-security.md#allowaddprovisioningpackage) 9
- [Security/AllowRemoveProvisioningPackage](policy-csp-security.md#allowremoveprovisioningpackage) 9
@@ -105,9 +118,15 @@ ms.date: 08/01/2022
- [Storage/ConfigStorageSenseDownloadsCleanupThreshold](policy-csp-storage.md#configstoragesensedownloadscleanupthreshold) 12
- [Storage/ConfigStorageSenseGlobalCadence](policy-csp-storage.md#configstoragesenseglobalcadence) 12
- [System/AllowCommercialDataPipeline](policy-csp-system.md#allowcommercialdatapipeline)
+- [System/AllowDeviceNameInDiagnosticData](policy-csp-system.md#allowdevicenameindiagnosticdata)
- [System/AllowLocation](policy-csp-system.md#allowlocation)
- [System/AllowStorageCard](policy-csp-system.md#allowstoragecard)
- [System/AllowTelemetry](policy-csp-system.md#allowtelemetry)
+- [System/ConfigureTelemetryOptInSettingsUx](policy-csp-system.md#configuretelemetryoptinsettingsux)
+- [System/DisableDeviceDelete](policy-csp-system.md#disabledevicedelete)
+- [System/FeedbackHubAlwaysSaveDiagnosticsLocally](policy-csp-system.md#feedbackhubalwayssavediagnosticslocally)
+- [System/LimitDiagnosticLogCollection](policy-csp-system.md#limitdumpcollection)
+- [System/LimitDumpCollection](policy-csp-system.md#limitdumpcollection)
- [TimeLanguageSettings/ConfigureTimeZone](./policy-csp-timelanguagesettings.md#configuretimezone) 9
- [Update/ActiveHoursEnd](./policy-csp-update.md#activehoursend) 9
- [Update/ActiveHoursMaxRange](./policy-csp-update.md#activehoursmaxrange) 9
From 7e5f1d94241d4e2bdf494ba5723e5e57ff36de77 Mon Sep 17 00:00:00 2001
From: Evan Miller
Date: Fri, 3 Feb 2023 12:50:04 -0800
Subject: [PATCH 74/98] smart retry
---
.../mdm/policies-in-policy-csp-supported-by-hololens2.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md
index 7545fd6751..77fc83e9b7 100644
--- a/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md
+++ b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md
@@ -19,6 +19,7 @@ ms.date: 02/03/2023
- [ApplicationManagement/AllowAppStoreAutoUpdate](policy-csp-applicationmanagement.md#allowappstoreautoupdate)
- [ApplicationManagement/AllowDeveloperUnlock](policy-csp-applicationmanagement.md#allowdeveloperunlock)
- [ApplicationManagement/RequirePrivateStoreOnly](policy-csp-applicationmanagement.md#requireprivatestoreonly) 11
+- [ApplicationManagement/ScheduleForceRestartForUpdateFailures](policy-csp-applicationmanagement.md#smart-retry-for-app-updates)
- [Authentication/AllowFastReconnect](policy-csp-authentication.md#allowfastreconnect)
- [Authentication/PreferredAadTenantDomainName](policy-csp-authentication.md#preferredaadtenantdomainname)
- [Bluetooth/AllowDiscoverableMode](policy-csp-bluetooth.md#allowdiscoverablemode)
From e9bcec3340493a4eee30d6d7c60ce8e712b67138 Mon Sep 17 00:00:00 2001
From: Evan Miller
Date: Fri, 3 Feb 2023 15:01:49 -0800
Subject: [PATCH 75/98] DO policies only
---
.../mdm/policies-in-policy-csp-supported-by-hololens2.md | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md
index 77fc83e9b7..ba9efea9af 100644
--- a/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md
+++ b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md
@@ -32,7 +32,6 @@ ms.date: 02/03/2023
- [Browser/AllowSearchSuggestionsinAddressBar](policy-csp-browser.md#allowsearchsuggestionsinaddressbar)
- [Browser/AllowSmartScreen](policy-csp-browser.md#allowsmartscreen)
- [Connectivity/AllowBluetooth](policy-csp-connectivity.md#allowbluetooth)
-- [Connectivity/AllowConnectedDevices](policy-csp-connectivity.md#allowconnecteddevices)
- [Connectivity/AllowUSBConnection](policy-csp-connectivity.md#allowusbconnection)
- [DeliveryOptimization/DOCacheHost](policy-csp-deliveryoptimization.md#docachehost) 10
- [DeliveryOptimization/DOCacheHostSource](policy-csp-deliveryoptimization.md#docachehostsource) 10
@@ -58,8 +57,6 @@ ms.date: 02/03/2023
- [DeviceLock/MinDevicePasswordLength](policy-csp-devicelock.md#mindevicepasswordlength)
- [Experience/AllowCortana](policy-csp-experience.md#allowcortana)
- [Experience/AllowManualMDMUnenrollment](policy-csp-experience.md#allowmanualmdmunenrollment)
-- [MemoryDump/AllowCrashDump](policy-csp-memorydump.md#allowcrashdump)
-- [MemoryDump/AllowLivehDump](policy-csp-memorydump.md#allowlivedump)
- [MixedReality/AADGroupMembershipCacheValidityInDays](./policy-csp-mixedreality.md#aadgroupmembershipcachevalidityindays) 9
- [MixedReality/AllowCaptivePortalBeforeLogon](./policy-csp-mixedreality.md#allowcaptiveportalbeforelogon) 12
- [MixedReality/AllowLaunchUriInSingleAppKiosk](./policy-csp-mixedreality.md#allowlaunchuriinsingleappkiosk)10
@@ -119,15 +116,9 @@ ms.date: 02/03/2023
- [Storage/ConfigStorageSenseDownloadsCleanupThreshold](policy-csp-storage.md#configstoragesensedownloadscleanupthreshold) 12
- [Storage/ConfigStorageSenseGlobalCadence](policy-csp-storage.md#configstoragesenseglobalcadence) 12
- [System/AllowCommercialDataPipeline](policy-csp-system.md#allowcommercialdatapipeline)
-- [System/AllowDeviceNameInDiagnosticData](policy-csp-system.md#allowdevicenameindiagnosticdata)
- [System/AllowLocation](policy-csp-system.md#allowlocation)
- [System/AllowStorageCard](policy-csp-system.md#allowstoragecard)
- [System/AllowTelemetry](policy-csp-system.md#allowtelemetry)
-- [System/ConfigureTelemetryOptInSettingsUx](policy-csp-system.md#configuretelemetryoptinsettingsux)
-- [System/DisableDeviceDelete](policy-csp-system.md#disabledevicedelete)
-- [System/FeedbackHubAlwaysSaveDiagnosticsLocally](policy-csp-system.md#feedbackhubalwayssavediagnosticslocally)
-- [System/LimitDiagnosticLogCollection](policy-csp-system.md#limitdumpcollection)
-- [System/LimitDumpCollection](policy-csp-system.md#limitdumpcollection)
- [TimeLanguageSettings/ConfigureTimeZone](./policy-csp-timelanguagesettings.md#configuretimezone) 9
- [Update/ActiveHoursEnd](./policy-csp-update.md#activehoursend) 9
- [Update/ActiveHoursMaxRange](./policy-csp-update.md#activehoursmaxrange) 9
From 114800510e628934b17cd8be078c16d6a3a5c312 Mon Sep 17 00:00:00 2001
From: Evan Miller
Date: Fri, 3 Feb 2023 15:46:13 -0800
Subject: [PATCH 76/98] fix link
---
.../mdm/policies-in-policy-csp-supported-by-hololens2.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md
index ba9efea9af..b34eebfedb 100644
--- a/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md
+++ b/windows/client-management/mdm/policies-in-policy-csp-supported-by-hololens2.md
@@ -19,7 +19,7 @@ ms.date: 02/03/2023
- [ApplicationManagement/AllowAppStoreAutoUpdate](policy-csp-applicationmanagement.md#allowappstoreautoupdate)
- [ApplicationManagement/AllowDeveloperUnlock](policy-csp-applicationmanagement.md#allowdeveloperunlock)
- [ApplicationManagement/RequirePrivateStoreOnly](policy-csp-applicationmanagement.md#requireprivatestoreonly) 11
-- [ApplicationManagement/ScheduleForceRestartForUpdateFailures](policy-csp-applicationmanagement.md#smart-retry-for-app-updates)
+- [ApplicationManagement/ScheduleForceRestartForUpdateFailures](policy-csp-applicationmanagement.md#scheduleforcerestartforupdatefailures)
- [Authentication/AllowFastReconnect](policy-csp-authentication.md#allowfastreconnect)
- [Authentication/PreferredAadTenantDomainName](policy-csp-authentication.md#preferredaadtenantdomainname)
- [Bluetooth/AllowDiscoverableMode](policy-csp-bluetooth.md#allowdiscoverablemode)
From f45f167b9be4f7d7c50098cfcf19ff63fd67e466 Mon Sep 17 00:00:00 2001
From: Vinay Pamnani <37223378+vinaypamnani-msft@users.noreply.github.com>
Date: Mon, 6 Feb 2023 12:59:17 -0500
Subject: [PATCH 77/98] Draft for CSP DDF files
---
.../mdm/configuration-service-provider-ddf.md | 575 +++++++++++++++++-
1 file changed, 572 insertions(+), 3 deletions(-)
diff --git a/windows/client-management/mdm/configuration-service-provider-ddf.md b/windows/client-management/mdm/configuration-service-provider-ddf.md
index 4a903492c4..0825b38037 100644
--- a/windows/client-management/mdm/configuration-service-provider-ddf.md
+++ b/windows/client-management/mdm/configuration-service-provider-ddf.md
@@ -1,7 +1,7 @@
---
title: Configuration service provider DDF files
description: Learn more about the OMA DM device description framework (DDF) for various configuration service providers
-ms.reviewer:
+ms.reviewer:
manager: aaroncz
ms.author: vinpa
ms.topic: article
@@ -14,7 +14,565 @@ ms.collection: highpri
# Configuration service provider DDF files
-This topic shows the OMA DM device description framework (DDF) for various configuration service providers. DDF files are used only with OMA DM provisioning XML.
+This article lists the OMA DM device description framework (DDF) files for various configuration service providers. DDF files are used only with OMA DM provisioning XML.
+
+As of December 2022, DDF files schema was updated to include additional information such as OS build applicability. DDF v2 files for Windows 10 and Windows 11 are combined, and provided in a single download:
+
+- [DDF v2 Files, December 2022](https://download.microsoft.com/download/7/4/c/74c6daca-983e-4f16-964a-eef65b553a37/DDFv2December2022.zip)
+
+## DDF v2 schema
+
+DDF v2 schema is listed below:
+
+```xml
+
+
+
+
+
+ Starting point for DDF
+
+
+
+
+
+
+
+
+
+
+
+
+ Main Recurring XML tag describing nodes of the CSP
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+DDF v2 files also include a reference to the `MSFT` namespace. Schema for the `MSFT` namespace is listed below:
+
+```xml
+
+
+
+
+ This node contains an XML blob that can be used as an argument to the DiagnosticsLogCSP to pull diagnostics for a feature.
+
+
+
+
+ This node marks that a feature is deprecated. If included, OsBuildDeprecated gives the OS Build version that the node is no longer recommended to be set.
+
+
+
+
+
+
+
+ This node contains information on how to dynamically name the node such that the name is valid.
+
+
+
+
+
+ This indicates that the server should generate a unique identifier for the node.
+
+
+
+
+ This indicates that the client will generate the name of the node based on the device state (such as inventorying apps).
+
+
+
+
+ This indicates that the server should name the node, and the value listed gives a regex to define what is allowed.
+
+
+
+
+
+
+
+
+ The type of the conflict resolution.
+
+
+
+
+ No policy merge.
+
+
+
+
+ The lowest value is the most secure policy value.
+
+
+
+
+ The highest value is the most secure policy value.
+
+
+
+
+ The last written value is current value
+
+
+
+
+ The lowest value is the most secure policy value unless the value is zero.
+
+
+
+
+ The highest value is the most secure policy value unless the value is zero.
+
+
+
+
+
+
+
+ These tags indicate what are required on the device for the node to be applicable to configured. These tags can be inherited by children nodes.
+
+
+
+
+
+ This tag describes the first build that a feature is released to. If the feature was backported, multiple OS versions will be listed, such that the OS build version without a minor number is the first "major release."
+
+
+
+
+ This tag describes the lowest CSP Version that the node was released to.
+
+
+
+
+ This tag describes the list of Edition IDs that the features is allowed on. 0x88* refers to Windows Holographic for Business.
+
+
+
+
+ This tag indicates that the node requires the device to be Azure Active Directory Joined to be applicable.
+
+
+
+
+
+
+
+ These tags describe what values are allowed to be set for this particular node.
+
+
+
+
+
+
+
+
+
+ This attribute describes what kind of Allowed Values tag this is.
+
+
+
+
+
+ This attribute indicates that the Value tag contains an XSD for the node.
+
+
+
+
+ This attribute indicates that the Value tag contains a RegEx for the node.
+
+
+
+
+ This attribute indicates that the node can be described by an external ADMX file.
+
+
+
+
+ This attribute indicates that the node can be described by a JSON schema.
+
+
+
+
+ This attribute indicates that the allowed values are an enumeration.
+
+
+
+
+ This attribute indicates that the allowed values can be combined into a bitwise flag.
+
+
+
+
+ This attribute indicates that the allowed values are a numerical range.
+
+
+
+
+ This attribute indicates that the allowed values are a string in the SDDL format.
+
+
+
+
+ This attribute indicates there is no data-driven way to define the allowed values of the node. This potentially means that all string values are valid values.
+
+
+
+
+
+
+
+
+
+
+
+ This tag indicates that the node input can contain multiple, delimited values.
+
+
+
+
+ This attribute details the delimeter used for the list of values.
+
+
+
+
+
+
+
+
+
+
+ This tag indicates an allowed value.
+
+
+
+
+ This tag gives further description to an allowed value, such as for an enumeration.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This tag gives details for one particular enumeration of the allowed values.
+
+
+
+
+
+
+
+
+
+ This tag indicates the relevent details for the corresponding ADMX policy for this node.
+
+
+
+
+ This attribute gives the area path of the ADMX policy.
+
+
+
+
+ This attribute gives the name of the ADMX policy.
+
+
+
+
+ This attribute gives the filename for the ADMX policy.
+
+
+
+
+
+
+ This tag details the replace behavior of the node.
+
+
+
+
+
+ When performing a replace operation on this node, the value is appending to the existing node data.
+
+
+
+
+ When performing a replace operation on this node, the existing node data is removed before new data is added.
+
+
+
+
+
+
+
+ This tag describes the reboot behavior of the node.
+
+
+
+
+
+ No reboot is required for this node.
+
+
+
+
+ This node will automatically perform a reboot to take effect.
+
+
+
+
+ This node needs a reboot initiated from an external source to take effect.
+
+
+
+
+
+
+
+ This tag details the information necessary to map this node to an existing group policy.
+
+
+
+
+ This attribute details the English name of the GP.
+
+
+
+
+ This attribute details the area path of the GP.
+
+
+
+
+ This attribute details a particular element of a GP that the CSP node maps to.
+
+
+
+
+
+
+ This tag lists out common error HRESULTS reported by the CSP and English text to associate with them.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This tag indicates that this node and all children nodes should be enclosed by an Atomic tag when being sent to the client.
+
+
+
+
+ These tags detail potential dependencies that the current CSP node has on other nodes in the same CSP.
+
+
+
+
+
+
+
+
+
+ This tag describes a dependency that the current CSP node has on another nodes in the same CSP.
+
+
+
+
+
+ The URI that the current CSP node has a dependency on.
+
+
+
+
+
+
+ This tag details the kind of dependency.
+
+
+
+
+
+ The current node depends on the dependency holding a certain value.
+
+
+
+
+ The current node depends on the dependency not holding a certain value.
+
+
+
+
+
+
+
+
+
+ This tag details one specific dependency. A node might have multiple different dependencies.
+
+
+
+
+
+
+
+
+ This attribute gives a friendly ID to the dependency, to differentiate it from other dependencies.
+
+
+
+
+
+
+ This tag details the values that the dependency must be set to for the dependency to be satisfied.
+
+
+
+
+
+
+
+
+ This tag details a change to the current node's allowed values if the dependency is satisfied.
+
+
+
+
+
+
+
+```
+
+## Older DDF files
You can download the DDF files for various CSPs from the links below:
@@ -26,4 +584,15 @@ You can download the DDF files for various CSPs from the links below:
- [Download all the DDF files for Windows 10, version 1703](https://download.microsoft.com/download/C/7/C/C7C94663-44CF-4221-ABCA-BC895F42B6C2/Windows10_1703_DDF_download.zip)
- [Download all the DDF files for Windows 10, version 1607](https://download.microsoft.com/download/2/3/E/23E27D6B-6E23-4833-B143-915EDA3BDD44/Windows10_1607_DDF.zip)
-You can download DDF file for Policy CSP from [Policy DDF file](policy-ddf-file.md).
+You can view various Policy area DDF files by clicking the following links:
+
+- [View the Policy DDF file for Windows 10, version 20H2](https://download.microsoft.com/download/4/0/f/40f9ec45-3bea-442c-8afd-21edc1e057d8/PolicyDDF_all_20H2.xml)
+- [View the Policy DDF file for Windows 10, version 2004](https://download.microsoft.com/download/4/0/f/40f9ec45-3bea-442c-8afd-21edc1e057d8/PolicyDDF_all_2004.xml)
+- [View the Policy DDF file for Windows 10, version 1903](https://download.microsoft.com/download/0/C/D/0CD61812-8B9C-4846-AC4A-1545BFD201EE/PolicyDDF_all_1903.xml)
+- [View the Policy DDF file for Windows 10, version 1809](https://download.microsoft.com/download/7/3/5/735B8537-82F4-4CD1-B059-93984F9FAAC5/Policy_DDF_all_1809.xml)
+- [View the Policy DDF file for Windows 10, version 1803](https://download.microsoft.com/download/4/9/6/496534EE-8F0C-4F12-B084-A8502DA22430/PolicyDDF_all.xml)
+- [View the Policy DDF file for Windows 10, version 1803 release C](https://download.microsoft.com/download/4/9/6/496534EE-8F0C-4F12-B084-A8502DA22430/PolicyDDF_all_1809C_release.xml)
+- [View the Policy DDF file for Windows 10, version 1709](https://download.microsoft.com/download/8/C/4/8C43C116-62CB-470B-9B69-76A3E2BC32A8/PolicyDDF_all.xml)
+- [View the Policy DDF file for Windows 10, version 1703](https://download.microsoft.com/download/7/2/C/72C36C37-20F9-41BF-8E23-721F6FFC253E/PolicyDDF_all.xml)
+- [View the Policy DDF file for Windows 10, version 1607](https://download.microsoft.com/download/6/1/C/61C022FD-6F5D-4F73-9047-17F630899DC4/PolicyDDF_all_version1607.xml)
+- [View the Policy DDF file for Windows 10, version 1607 release 8C](https://download.microsoft.com/download/6/1/C/61C022FD-6F5D-4F73-9047-17F630899DC4/PolicyDDF_all_version1607_8C.xml)
From 22ab373428424a3e15682609b2aa8f970761557c Mon Sep 17 00:00:00 2001
From: Vinay Pamnani <37223378+vinaypamnani-msft@users.noreply.github.com>
Date: Mon, 6 Feb 2023 14:11:04 -0500
Subject: [PATCH 78/98] Update
---
.openpublishing.redirection.json | 27 +-
.../mdm/configuration-service-provider-ddf.md | 1058 +++++++++--------
.../client-management/mdm/policy-ddf-file.md | 32 -
3 files changed, 547 insertions(+), 570 deletions(-)
delete mode 100644 windows/client-management/mdm/policy-ddf-file.md
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
index e6a9c13cf5..22639222c2 100644
--- a/.openpublishing.redirection.json
+++ b/.openpublishing.redirection.json
@@ -19463,7 +19463,7 @@
{
"source_path": "windows/security/threat-protection/intelligence/rootkits-malware.md",
"redirect_url": "/microsoft-365/security/intelligence/rootkits-malware",
- "redirect_document_id": false
+ "redirect_document_id": false
},
{
"source_path": "windows/security/threat-protection/intelligence/safety-scanner-download.md",
@@ -20114,7 +20114,7 @@
"source_path": "windows/deployment/update/update-compliance-v2-enable.md",
"redirect_url": "/windows/deployment/update/wufb-reports-enable",
"redirect_document_id": false
- },
+ },
{
"source_path": "windows/deployment/update/update-compliance-v2-help.md",
"redirect_url": "/windows/deployment/update/wufb-reports-help",
@@ -20124,22 +20124,22 @@
"source_path": "windows/deployment/update/update-compliance-v2-overview.md",
"redirect_url": "/windows/deployment/update/wufb-reports-overview",
"redirect_document_id": false
- },
+ },
{
"source_path": "windows/deployment/update/update-compliance-v2-prerequisites.md",
"redirect_url": "/windows/deployment/update/wufb-reports-prerequisites",
"redirect_document_id": false
- },
+ },
{
"source_path": "windows/deployment/update/update-compliance-v2-schema-ucclient.md",
"redirect_url": "/windows/deployment/update/wufb-reports-schema-ucclient",
"redirect_document_id": false
- },
+ },
{
"source_path": "windows/deployment/update/update-compliance-v2-schema-ucclientreadinessstatus.md",
"redirect_url": "/windows/deployment/update/wufb-reports-schema-ucclientreadinessstatus",
"redirect_document_id": false
- },
+ },
{
"source_path": "windows/deployment/update/update-compliance-v2-schema-ucclientupdatestatus.md",
"redirect_url": "/windows/deployment/update/wufb-reports-schema-ucclientupdatestatus",
@@ -20149,17 +20149,17 @@
"source_path": "windows/deployment/update/update-compliance-v2-schema-ucdevicealert.md",
"redirect_url": "/windows/deployment/update/wufb-reports-schema-ucdevicealert",
"redirect_document_id": false
- },
+ },
{
"source_path": "windows/deployment/update/update-compliance-v2-schema-ucserviceupdatestatus.md",
"redirect_url": "/windows/deployment/update/wufb-reports-schema-ucserviceupdatestatus",
"redirect_document_id": false
- },
+ },
{
"source_path": "windows/deployment/update/update-compliance-v2-schema-ucupdatealert.md",
"redirect_url": "/windows/deployment/update/wufb-reports-schema-ucupdatealert",
"redirect_document_id": false
- },
+ },
{
"source_path": "windows/deployment/update/update-compliance-v2-schema.md",
"redirect_url": "/windows/deployment/update/wufb-reports-schema",
@@ -20194,7 +20194,7 @@
"source_path": "windows/deployment/planning/features-lifecycle.md",
"redirect_url": "/windows/whats-new/feature-lifecycle",
"redirect_document_id": false
- },
+ },
{
"source_path": "windows/deployment/planning/windows-10-deprecated-features.md",
"redirect_url": "/windows/whats-new/deprecated-features",
@@ -20205,7 +20205,7 @@
"redirect_url": "/windows/whats-new/removed-features",
"redirect_document_id": false
},
- {
+ {
"source_path": "windows/deployment/usmt/usmt-common-issues.md",
"redirect_url": "/troubleshoot/windows-client/deployment/usmt-common-issues",
"redirect_document_id": false
@@ -20514,6 +20514,11 @@
"source_path": "windows/deployment/windows-autopatch/references/windows-autopatch-wqu-unsupported-policies.md",
"redirect_url": "/windows/deployment/windows-autopatch/references/windows-autopatch-windows-update-unsupported-policies",
"redirect_document_id": true
+ },
+ {
+ "source_path": "windows-docs-pr/windows/client-management/mdm/policy-ddf-file.md",
+ "redirect_url": "/windows/client-management/mdm/configuration-service-provider-ddf",
+ "redirect_document_id": true
}
]
}
diff --git a/windows/client-management/mdm/configuration-service-provider-ddf.md b/windows/client-management/mdm/configuration-service-provider-ddf.md
index 0825b38037..b55b3ce963 100644
--- a/windows/client-management/mdm/configuration-service-provider-ddf.md
+++ b/windows/client-management/mdm/configuration-service-provider-ddf.md
@@ -16,565 +16,569 @@ ms.collection: highpri
This article lists the OMA DM device description framework (DDF) files for various configuration service providers. DDF files are used only with OMA DM provisioning XML.
-As of December 2022, DDF files schema was updated to include additional information such as OS build applicability. DDF v2 files for Windows 10 and Windows 11 are combined, and provided in a single download:
+As of December 2022, DDF XML schema was updated to include additional information such as OS build applicability. DDF v2 XML files for Windows 10 and Windows 11 are combined, and provided in a single download:
- [DDF v2 Files, December 2022](https://download.microsoft.com/download/7/4/c/74c6daca-983e-4f16-964a-eef65b553a37/DDFv2December2022.zip)
## DDF v2 schema
-DDF v2 schema is listed below:
+DDF v2 XML schema definition is listed below along with the schema definition for the referenced `MSFT` namespace.
-```xml
-
-
-
-
-
- Starting point for DDF
-
-
-
-
-
-
-
-
-
-
-
-
- Main Recurring XML tag describing nodes of the CSP
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
+- Schema definition for DDF v2:
-DDF v2 files also include a reference to the `MSFT` namespace. Schema for the `MSFT` namespace is listed below:
-
-```xml
-
-
-
-
- This node contains an XML blob that can be used as an argument to the DiagnosticsLogCSP to pull diagnostics for a feature.
-
-
-
-
- This node marks that a feature is deprecated. If included, OsBuildDeprecated gives the OS Build version that the node is no longer recommended to be set.
-
-
-
-
-
-
-
- This node contains information on how to dynamically name the node such that the name is valid.
-
-
-
-
-
- This indicates that the server should generate a unique identifier for the node.
-
-
-
-
- This indicates that the client will generate the name of the node based on the device state (such as inventorying apps).
-
-
-
-
- This indicates that the server should name the node, and the value listed gives a regex to define what is allowed.
-
-
-
-
-
-
-
-
- The type of the conflict resolution.
-
-
-
-
- No policy merge.
-
-
-
-
- The lowest value is the most secure policy value.
-
-
-
-
- The highest value is the most secure policy value.
-
-
-
-
- The last written value is current value
-
-
-
-
- The lowest value is the most secure policy value unless the value is zero.
-
-
-
-
- The highest value is the most secure policy value unless the value is zero.
-
-
-
-
-
-
-
- These tags indicate what are required on the device for the node to be applicable to configured. These tags can be inherited by children nodes.
-
-
-
-
-
- This tag describes the first build that a feature is released to. If the feature was backported, multiple OS versions will be listed, such that the OS build version without a minor number is the first "major release."
-
-
-
-
- This tag describes the lowest CSP Version that the node was released to.
-
-
-
-
- This tag describes the list of Edition IDs that the features is allowed on. 0x88* refers to Windows Holographic for Business.
-
-
-
-
- This tag indicates that the node requires the device to be Azure Active Directory Joined to be applicable.
-
-
-
-
-
-
-
- These tags describe what values are allowed to be set for this particular node.
-
-
-
-
-
-
-
-
-
- This attribute describes what kind of Allowed Values tag this is.
-
-
-
-
-
- This attribute indicates that the Value tag contains an XSD for the node.
-
-
-
-
- This attribute indicates that the Value tag contains a RegEx for the node.
-
-
-
-
- This attribute indicates that the node can be described by an external ADMX file.
-
-
-
-
- This attribute indicates that the node can be described by a JSON schema.
-
-
-
-
- This attribute indicates that the allowed values are an enumeration.
-
-
-
-
- This attribute indicates that the allowed values can be combined into a bitwise flag.
-
-
-
-
- This attribute indicates that the allowed values are a numerical range.
-
-
-
-
- This attribute indicates that the allowed values are a string in the SDDL format.
-
-
-
-
- This attribute indicates there is no data-driven way to define the allowed values of the node. This potentially means that all string values are valid values.
-
-
-
-
-
-
-
-
-
-
+ ```xml
+
+
+
+
- This tag indicates that the node input can contain multiple, delimited values.
+ Starting point for DDF
-
-
- This attribute details the delimeter used for the list of values.
-
-
+
+
+
+
+
-
-
-
-
-
+
+
- This tag indicates an allowed value.
+ Main Recurring XML tag describing nodes of the CSP
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ```
+
+- Schema definition for the `MSFT` namespace:
+
+ ```xml
+
+
+
+
+ This node contains an XML blob that can be used as an argument to the DiagnosticsLogCSP to pull diagnostics for a feature.
-
+
- This tag gives further description to an allowed value, such as for an enumeration.
+ This node marks that a feature is deprecated. If included, OsBuildDeprecated gives the OS Build version that the node is no longer recommended to be set.
+
+
+
-
-
-
-
-
-
-
-
-
-
-
- This tag gives details for one particular enumeration of the allowed values.
-
-
-
-
-
-
-
-
-
- This tag indicates the relevent details for the corresponding ADMX policy for this node.
-
-
-
+
- This attribute gives the area path of the ADMX policy.
+ This node contains information on how to dynamically name the node such that the name is valid.
-
-
-
- This attribute gives the name of the ADMX policy.
-
-
-
-
- This attribute gives the filename for the ADMX policy.
-
-
-
-
-
-
- This tag details the replace behavior of the node.
-
-
-
-
-
- When performing a replace operation on this node, the value is appending to the existing node data.
-
-
-
-
- When performing a replace operation on this node, the existing node data is removed before new data is added.
-
-
-
-
-
-
-
- This tag describes the reboot behavior of the node.
-
-
-
-
-
- No reboot is required for this node.
-
-
-
-
- This node will automatically perform a reboot to take effect.
-
-
-
-
- This node needs a reboot initiated from an external source to take effect.
-
-
-
-
-
-
-
- This tag details the information necessary to map this node to an existing group policy.
-
-
-
-
- This attribute details the English name of the GP.
-
-
-
-
- This attribute details the area path of the GP.
-
-
-
-
- This attribute details a particular element of a GP that the CSP node maps to.
-
-
-
-
-
-
- This tag lists out common error HRESULTS reported by the CSP and English text to associate with them.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- This tag indicates that this node and all children nodes should be enclosed by an Atomic tag when being sent to the client.
-
-
-
-
- These tags detail potential dependencies that the current CSP node has on other nodes in the same CSP.
-
-
-
-
-
-
-
-
-
- This tag describes a dependency that the current CSP node has on another nodes in the same CSP.
-
-
-
-
-
- The URI that the current CSP node has a dependency on.
-
-
-
-
-
-
- This tag details the kind of dependency.
-
-
-
-
+
+
+
- The current node depends on the dependency holding a certain value.
+ This indicates that the server should generate a unique identifier for the node.
+
+
+
+
+ This indicates that the client will generate the name of the node based on the device state (such as inventorying apps).
+
+
+
+
+ This indicates that the server should name the node, and the value listed gives a regex to define what is allowed.
+
+
+
+
+
+
+
+
+ The type of the conflict resolution.
+
+
+
+
+ No policy merge.
-
+
- The current node depends on the dependency not holding a certain value.
+ The lowest value is the most secure policy value.
+
+
+
+
+ The highest value is the most secure policy value.
+
+
+
+
+ The last written value is current value
+
+
+
+
+ The lowest value is the most secure policy value unless the value is zero.
+
+
+
+
+ The highest value is the most secure policy value unless the value is zero.
-
-
-
-
-
- This tag details one specific dependency. A node might have multiple different dependencies.
-
-
-
-
-
-
-
+
+
- This attribute gives a friendly ID to the dependency, to differentiate it from other dependencies.
+ These tags indicate what are required on the device for the node to be applicable to configured. These tags can be inherited by children nodes.
-
-
-
-
-
- This tag details the values that the dependency must be set to for the dependency to be satisfied.
-
-
-
-
-
-
-
-
- This tag details a change to the current node's allowed values if the dependency is satisfied.
-
-
-
-
-
-
-
-```
+
+
+
+
+ This tag describes the first build that a feature is released to. If the feature was backported, multiple OS versions will be listed, such that the OS build version without a minor number is the first "major release."
+
+
+
+
+ This tag describes the lowest CSP Version that the node was released to.
+
+
+
+
+ This tag describes the list of Edition IDs that the features is allowed on. 0x88* refers to Windows Holographic for Business.
+
+
+
+
+ This tag indicates that the node requires the device to be Azure Active Directory Joined to be applicable.
+
+
+
+
+
+
+
+ These tags describe what values are allowed to be set for this particular node.
+
+
+
+
+
+
+
+
+
+ This attribute describes what kind of Allowed Values tag this is.
+
+
+
+
+
+ This attribute indicates that the Value tag contains an XSD for the node.
+
+
+
+
+ This attribute indicates that the Value tag contains a RegEx for the node.
+
+
+
+
+ This attribute indicates that the node can be described by an external ADMX file.
+
+
+
+
+ This attribute indicates that the node can be described by a JSON schema.
+
+
+
+
+ This attribute indicates that the allowed values are an enumeration.
+
+
+
+
+ This attribute indicates that the allowed values can be combined into a bitwise flag.
+
+
+
+
+ This attribute indicates that the allowed values are a numerical range.
+
+
+
+
+ This attribute indicates that the allowed values are a string in the SDDL format.
+
+
+
+
+ This attribute indicates there is no data-driven way to define the allowed values of the node. This potentially means that all string values are valid values.
+
+
+
+
+
+
+
+
+
+
+
+ This tag indicates that the node input can contain multiple, delimited values.
+
+
+
+
+ This attribute details the delimeter used for the list of values.
+
+
+
+
+
+
+
+
+
+
+ This tag indicates an allowed value.
+
+
+
+
+ This tag gives further description to an allowed value, such as for an enumeration.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This tag gives details for one particular enumeration of the allowed values.
+
+
+
+
+
+
+
+
+
+ This tag indicates the relevent details for the corresponding ADMX policy for this node.
+
+
+
+
+ This attribute gives the area path of the ADMX policy.
+
+
+
+
+ This attribute gives the name of the ADMX policy.
+
+
+
+
+ This attribute gives the filename for the ADMX policy.
+
+
+
+
+
+
+ This tag details the replace behavior of the node.
+
+
+
+
+
+ When performing a replace operation on this node, the value is appending to the existing node data.
+
+
+
+
+ When performing a replace operation on this node, the existing node data is removed before new data is added.
+
+
+
+
+
+
+
+ This tag describes the reboot behavior of the node.
+
+
+
+
+
+ No reboot is required for this node.
+
+
+
+
+ This node will automatically perform a reboot to take effect.
+
+
+
+
+ This node needs a reboot initiated from an external source to take effect.
+
+
+
+
+
+
+
+ This tag details the information necessary to map this node to an existing group policy.
+
+
+
+
+ This attribute details the English name of the GP.
+
+
+
+
+ This attribute details the area path of the GP.
+
+
+
+
+ This attribute details a particular element of a GP that the CSP node maps to.
+
+
+
+
+
+
+ This tag lists out common error HRESULTS reported by the CSP and English text to associate with them.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This tag indicates that this node and all children nodes should be enclosed by an Atomic tag when being sent to the client.
+
+
+
+
+ These tags detail potential dependencies that the current CSP node has on other nodes in the same CSP.
+
+
+
+
+
+
+
+
+
+ This tag describes a dependency that the current CSP node has on another nodes in the same CSP.
+
+
+
+
+
+ The URI that the current CSP node has a dependency on.
+
+
+
+
+
+
+ This tag details the kind of dependency.
+
+
+
+
+
+ The current node depends on the dependency holding a certain value.
+
+
+
+
+ The current node depends on the dependency not holding a certain value.
+
+
+
+
+
+
+
+
+
+ This tag details one specific dependency. A node might have multiple different dependencies.
+
+
+
+
+
+
+
+
+ This attribute gives a friendly ID to the dependency, to differentiate it from other dependencies.
+
+
+
+
+
+
+ This tag details the values that the dependency must be set to for the dependency to be satisfied.
+
+
+
+
+
+
+
+
+ This tag details a change to the current node's allowed values if the dependency is satisfied.
+
+
+
+
+
+
+
+ ```
## Older DDF files
-You can download the DDF files for various CSPs from the links below:
+You can download the older DDF files for various CSPs from the links below:
- [Download all the DDF files for Windows 10, version 2004](https://download.microsoft.com/download/4/0/f/40f9ec45-3bea-442c-8afd-21edc1e057d8/Windows10_2004_DDF_download.zip)
- [Download all the DDF files for Windows 10, version 1903](https://download.microsoft.com/download/6/F/0/6F019079-6EB0-41B5-88E8-D1CE77DBA27B/Windows10_1903_DDF_download.zip)
@@ -584,7 +588,7 @@ You can download the DDF files for various CSPs from the links below:
- [Download all the DDF files for Windows 10, version 1703](https://download.microsoft.com/download/C/7/C/C7C94663-44CF-4221-ABCA-BC895F42B6C2/Windows10_1703_DDF_download.zip)
- [Download all the DDF files for Windows 10, version 1607](https://download.microsoft.com/download/2/3/E/23E27D6B-6E23-4833-B143-915EDA3BDD44/Windows10_1607_DDF.zip)
-You can view various Policy area DDF files by clicking the following links:
+You can download the older Policy area DDF files by clicking the following links:
- [View the Policy DDF file for Windows 10, version 20H2](https://download.microsoft.com/download/4/0/f/40f9ec45-3bea-442c-8afd-21edc1e057d8/PolicyDDF_all_20H2.xml)
- [View the Policy DDF file for Windows 10, version 2004](https://download.microsoft.com/download/4/0/f/40f9ec45-3bea-442c-8afd-21edc1e057d8/PolicyDDF_all_2004.xml)
diff --git a/windows/client-management/mdm/policy-ddf-file.md b/windows/client-management/mdm/policy-ddf-file.md
deleted file mode 100644
index 07c6ded973..0000000000
--- a/windows/client-management/mdm/policy-ddf-file.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Policy DDF file
-description: Learn about the OMA DM device description framework (DDF) for the Policy configuration service provider.
-ms.reviewer:
-manager: aaroncz
-ms.author: vinpa
-ms.topic: article
-ms.prod: windows-client
-ms.technology: itpro-manage
-author: vinaypamnani-msft
-ms.localizationpriority: medium
-ms.date: 10/28/2020
----
-
-# Policy DDF file
-
-This topic shows the OMA DM device description framework (DDF) for the **Policy** configuration service provider. DDF files are used only with OMA DM provisioning XML.
-
-You can view various Policy DDF files by clicking the following links:
-
-- [View the Policy DDF file for Windows 10, version 20H2](https://download.microsoft.com/download/4/0/f/40f9ec45-3bea-442c-8afd-21edc1e057d8/PolicyDDF_all_20H2.xml)
-- [View the Policy DDF file for Windows 10, version 2004](https://download.microsoft.com/download/4/0/f/40f9ec45-3bea-442c-8afd-21edc1e057d8/PolicyDDF_all_2004.xml)
-- [View the Policy DDF file for Windows 10, version 1903](https://download.microsoft.com/download/0/C/D/0CD61812-8B9C-4846-AC4A-1545BFD201EE/PolicyDDF_all_1903.xml)
-- [View the Policy DDF file for Windows 10, version 1809](https://download.microsoft.com/download/7/3/5/735B8537-82F4-4CD1-B059-93984F9FAAC5/Policy_DDF_all_1809.xml)
-- [View the Policy DDF file for Windows 10, version 1803](https://download.microsoft.com/download/4/9/6/496534EE-8F0C-4F12-B084-A8502DA22430/PolicyDDF_all.xml)
-- [View the Policy DDF file for Windows 10, version 1803 release C](https://download.microsoft.com/download/4/9/6/496534EE-8F0C-4F12-B084-A8502DA22430/PolicyDDF_all_1809C_release.xml)
-- [View the Policy DDF file for Windows 10, version 1709](https://download.microsoft.com/download/8/C/4/8C43C116-62CB-470B-9B69-76A3E2BC32A8/PolicyDDF_all.xml)
-- [View the Policy DDF file for Windows 10, version 1703](https://download.microsoft.com/download/7/2/C/72C36C37-20F9-41BF-8E23-721F6FFC253E/PolicyDDF_all.xml)
-- [View the Policy DDF file for Windows 10, version 1607](https://download.microsoft.com/download/6/1/C/61C022FD-6F5D-4F73-9047-17F630899DC4/PolicyDDF_all_version1607.xml)
-- [View the Policy DDF file for Windows 10, version 1607 release 8C](https://download.microsoft.com/download/6/1/C/61C022FD-6F5D-4F73-9047-17F630899DC4/PolicyDDF_all_version1607_8C.xml)
-
-You can download DDF files for various CSPs from [CSP DDF files download](configuration-service-provider-ddf.md).
From 7c4072364c07f884a57c5acf3dc4c6d74adc71d2 Mon Sep 17 00:00:00 2001
From: Vinay Pamnani <37223378+vinaypamnani-msft@users.noreply.github.com>
Date: Mon, 6 Feb 2023 14:12:19 -0500
Subject: [PATCH 79/98] Update TOC
---
windows/client-management/mdm/toc.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/client-management/mdm/toc.yml b/windows/client-management/mdm/toc.yml
index 919e4cac79..d35962adb6 100644
--- a/windows/client-management/mdm/toc.yml
+++ b/windows/client-management/mdm/toc.yml
@@ -34,7 +34,7 @@ items:
href: policy-configuration-service-provider.md
items:
- name: Policy CSP DDF file
- href: policy-ddf-file.md
+ href: configuration-service-provider-ddf.md
- name: Policy CSP support scenarios
items:
- name: ADMX policies in Policy CSP
From 8607282adad6d98f8843d5dcc5180b0cb9955e14 Mon Sep 17 00:00:00 2001
From: Vinay Pamnani <37223378+vinaypamnani-msft@users.noreply.github.com>
Date: Mon, 6 Feb 2023 14:20:41 -0500
Subject: [PATCH 80/98] Fix broken links
---
.../change-history-for-mdm-documentation.md | 8 ++++----
windows/client-management/mdm/index.yml | 2 +-
.../mdm/policy-csp-controlpolicyconflict.md | 2 +-
.../mdm/policy-csp-localpoliciessecurityoptions.md | 2 +-
4 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/windows/client-management/change-history-for-mdm-documentation.md b/windows/client-management/change-history-for-mdm-documentation.md
index b77a1761a8..5b7f08ac50 100644
--- a/windows/client-management/change-history-for-mdm-documentation.md
+++ b/windows/client-management/change-history-for-mdm-documentation.md
@@ -185,7 +185,7 @@ As of November 2020 This page will no longer be updated. This article lists new
|[RemoteWipe CSP](mdm/remotewipe-csp.md)|Added new settings in Windows 10, version 1809.|
|[TenantLockdown CSP](mdm/tenantlockdown-csp.md)|Added new CSP in Windows 10, version 1809.|
|[WindowsDefenderApplicationGuard CSP](mdm/windowsdefenderapplicationguard-csp.md)|Added new settings in Windows 10, version 1809.|
-|[Policy DDF file](mdm/policy-ddf-file.md)|Posted an updated version of the Policy DDF for Windows 10, version 1809.|
+|[Policy DDF file](mdm/configuration-service-provider-ddf.md)|Posted an updated version of the Policy DDF for Windows 10, version 1809.|
|[Policy CSP](mdm/policy-configuration-service-provider.md)|Added the following new policies in Windows 10, version 1809:- Browser/AllowFullScreenMode
- Browser/AllowPrelaunch
- Browser/AllowPrinting
- Browser/AllowSavingHistory
- Browser/AllowSideloadingOfExtensions
- Browser/AllowTabPreloading
- Browser/AllowWebContentOnNewTabPage
- Browser/ConfigureFavoritesBar
- Browser/ConfigureHomeButton
- Browser/ConfigureKioskMode
- Browser/ConfigureKioskResetAfterIdleTimeout
- Browser/ConfigureOpenMicrosoftEdgeWith
- Browser/ConfigureTelemetryForMicrosoft365Analytics
- Browser/PreventCertErrorOverrides
- Browser/SetHomeButtonURL
- Browser/SetNewTabPageURL
- Browser/UnlockHomeButton
- Experience/DoNotSyncBrowserSettings
- Experience/PreventUsersFromTurningOnBrowserSyncing
- Kerberos/UPNNameHints
- Privacy/AllowCrossDeviceClipboard
- Privacy
- DisablePrivacyExperience
- Privacy/UploadUserActivities
- System/AllowDeviceNameInDiagnosticData
- System/ConfigureMicrosoft365UploadEndpoint
- System/DisableDeviceDelete
- System/DisableDiagnosticDataViewer
- Storage/RemovableDiskDenyWriteAccess
- Update/UpdateNotificationLevel
Start/DisableContextMenus - added in Windows 10, version 1803.
RestrictedGroups/ConfigureGroupMembership - added new schema to apply and retrieve the policy.|
## July 2018
@@ -217,7 +217,7 @@ As of November 2020 This page will no longer be updated. This article lists new
|New or updated article|Description|
|--- |--- |
-|[Policy DDF file](mdm/policy-ddf-file.md)|Updated the DDF files in the Windows 10 version 1703 and 1709. - [Download the Policy DDF file for Windows 10, version 1709](https://download.microsoft.com/download/8/C/4/8C43C116-62CB-470B-9B69-76A3E2BC32A8/PolicyDDF_all.xml)
- [Download the Policy DDF file for Windows 10, version 1703](https://download.microsoft.com/download/7/2/C/72C36C37-20F9-41BF-8E23-721F6FFC253E/PolicyDDF_all.xml)|
+|[Policy DDF file](mdm/configuration-service-provider-ddf.md)|Updated the DDF files in the Windows 10 version 1703 and 1709.
- [Download the Policy DDF file for Windows 10, version 1709](https://download.microsoft.com/download/8/C/4/8C43C116-62CB-470B-9B69-76A3E2BC32A8/PolicyDDF_all.xml)
- [Download the Policy DDF file for Windows 10, version 1703](https://download.microsoft.com/download/7/2/C/72C36C37-20F9-41BF-8E23-721F6FFC253E/PolicyDDF_all.xml)|
## April 2018
@@ -281,7 +281,7 @@ As of November 2020 This page will no longer be updated. This article lists new
| New or updated article | Description |
| --- | --- |
-| [Policy DDF file](mdm/policy-ddf-file.md) | Updated the DDF content for Windows 10 version 1709. Added a link to the download of Policy DDF for Windows 10, version 1709. |
+| [Policy DDF file](mdm/configuration-service-provider-ddf.md) | Updated the DDF content for Windows 10 version 1709. Added a link to the download of Policy DDF for Windows 10, version 1709. |
| [Policy CSP](mdm/policy-configuration-service-provider.md) | Updated the following policies:
- Defender/ControlledFolderAccessAllowedApplications - string separator is `|`
- Defender/ControlledFolderAccessProtectedFolders - string separator is `|` |
| [eUICCs CSP](mdm/euiccs-csp.md) | Added new CSP in Windows 10, version 1709. |
| [AssignedAccess CSP](mdm/assignedaccess-csp.md) | Added SyncML examples for the new Configuration node. |
@@ -313,5 +313,5 @@ As of November 2020 This page will no longer be updated. This article lists new
|[Office CSP](mdm/office-csp.md)|Added the following setting in Windows 10, version 1709: - Installation/CurrentStatus|
|[BitLocker CSP](mdm/bitlocker-csp.md)|Added information to the ADMX-backed policies. Changed the minimum personal identification number (PIN) length to four digits in SystemDrivesRequireStartupAuthentication and SystemDrivesMinimumPINLength in Windows 10, version 1709.|
|[Firewall CSP](mdm/firewall-csp.md)|Updated the CSP and DDF topics. Here are the changes:
- Removed the two settings - FirewallRules/FirewallRuleName/FriendlyName and FirewallRules/FirewallRuleName/IcmpTypesAndCodes.
- Changed some data types from integer to bool.
- Updated the list of supported operations for some settings.
- Added default values.|
-|[Policy DDF file](mdm/policy-ddf-file.md)|Added another Policy DDF file [download](https://download.microsoft.com/download/6/1/C/61C022FD-6F5D-4F73-9047-17F630899DC4/PolicyDDF_all_version1607_8C.xml) for the 8C release of Windows 10, version 1607, which added the following policies:
- Browser/AllowMicrosoftCompatibilityList
- Update/DisableDualScan
- Update/FillEmptyContentUrls|
+|[Policy DDF file](mdm/configuration-service-provider-ddf.md)|Added another Policy DDF file [download](https://download.microsoft.com/download/6/1/C/61C022FD-6F5D-4F73-9047-17F630899DC4/PolicyDDF_all_version1607_8C.xml) for the 8C release of Windows 10, version 1607, which added the following policies:
- Browser/AllowMicrosoftCompatibilityList
- Update/DisableDualScan
- Update/FillEmptyContentUrls|
|[Policy CSP](mdm/policy-configuration-service-provider.md)|Added the following new policies for Windows 10, version 1709:
- Browser/ProvisionFavorites
- Browser/LockdownFavorites
- ExploitGuard/ExploitProtectionSettings
- Games/AllowAdvancedGamingServices
- LocalPoliciesSecurityOptions/Accounts_BlockMicrosoftAccounts
- LocalPoliciesSecurityOptions/Accounts_LimitLocalAccountUseOfBlankPasswordsToConsoleLogonOnly
- LocalPoliciesSecurityOptions/Accounts_RenameAdministratorAccount
- LocalPoliciesSecurityOptions/Accounts_RenameGuestAccount
- LocalPoliciesSecurityOptions/InteractiveLogon_DisplayUserInformationWhenTheSessionIsLocked
- LocalPoliciesSecurityOptions/Interactivelogon_DoNotDisplayLastSignedIn
- LocalPoliciesSecurityOptions/Interactivelogon_DoNotDisplayUsernameAtSignIn
- LocalPoliciesSecurityOptions/Interactivelogon_DoNotRequireCTRLALTDEL
- LocalPoliciesSecurityOptions/InteractiveLogon_MachineInactivityLimit
- LocalPoliciesSecurityOptions/InteractiveLogon_MessageTextForUsersAttemptingToLogOn
- LocalPoliciesSecurityOptions/InteractiveLogon_MessageTitleForUsersAttemptingToLogOn
- LocalPoliciesSecurityOptions/NetworkSecurity_AllowPKU2UAuthenticationRequests
- LocalPoliciesSecurityOptions/Shutdown_AllowSystemToBeShutDownWithoutHavingToLogOn
- LocalPoliciesSecurityOptions/UserAccountControl_AllowUIAccessApplicationsToPromptForElevation
- LocalPoliciesSecurityOptions/UserAccountControl_BehaviorOfTheElevationPromptForAdministrators
- LocalPoliciesSecurityOptions/UserAccountControl_BehaviorOfTheElevationPromptForStandardUsers
- LocalPoliciesSecurityOptions/UserAccountControl_OnlyElevateExecutableFilesThatAreSignedAndValidated
- LocalPoliciesSecurityOptions/UserAccountControl_OnlyElevateUIAccessApplicationsThatAreInstalledInSecureLocations
- LocalPoliciesSecurityOptions/UserAccountControl_RunAllAdministratorsInAdminApprovalMode
- LocalPoliciesSecurityOptions/UserAccountControl_SwitchToTheSecureDesktopWhenPromptingForElevation
- LocalPoliciesSecurityOptions/UserAccountControl_VirtualizeFileAndRegistryWriteFailuresToPerUserLocations
- Privacy/EnableActivityFeed
- Privacy/PublishUserActivities
- Update/DisableDualScan
- Update/AllowAutoWindowsUpdateDownloadOverMeteredNetwork
Changed the name of new policy to CredentialProviders/DisableAutomaticReDeploymentCredentials from CredentialProviders/EnableWindowsAutopilotResetCredentials.
Changed the names of the following policies: - Defender/GuardedFoldersAllowedApplications to Defender/ControlledFolderAccessAllowedApplications
- Defender/GuardedFoldersList to Defender/ControlledFolderAccessProtectedFolders
- Defender/EnableGuardMyFolders to Defender/EnableControlledFolderAccess
Added links to the extra [ADMX-backed BitLocker policies](mdm/policy-csp-bitlocker.md).
There were issues reported with the previous release of the following policies. These issues were fixed in Windows 10, version 1709: - Privacy/AllowAutoAcceptPairingAndPrivacyConsentPrompts
- Start/HideAppList|
diff --git a/windows/client-management/mdm/index.yml b/windows/client-management/mdm/index.yml
index d8bd8ed982..db2be7efaf 100644
--- a/windows/client-management/mdm/index.yml
+++ b/windows/client-management/mdm/index.yml
@@ -47,7 +47,7 @@ landingContent:
- text: Policy CSP
url: policy-configuration-service-provider.md
- text: Policy DDF file
- url: policy-ddf-file.md
+ url: configuration-service-provider-ddf.md
- text: Policy CSP - Start
url: policy-csp-start.md
- text: Policy CSP - Update
diff --git a/windows/client-management/mdm/policy-csp-controlpolicyconflict.md b/windows/client-management/mdm/policy-csp-controlpolicyconflict.md
index f955123b29..b6865f7b07 100644
--- a/windows/client-management/mdm/policy-csp-controlpolicyconflict.md
+++ b/windows/client-management/mdm/policy-csp-controlpolicyconflict.md
@@ -58,7 +58,7 @@ This ensures that:
- The current Policy Manager policies are refreshed from what MDM has set
- Any values set by scripts/user outside of GP that conflict with MDM are removed
-The [Policy DDF](policy-ddf-file.md) contains the following tags to identify the policies with equivalent GP:
+The [Policy DDF](configuration-service-provider-ddf.md) contains the following tags to identify the policies with equivalent GP:
- \
- \
diff --git a/windows/client-management/mdm/policy-csp-localpoliciessecurityoptions.md b/windows/client-management/mdm/policy-csp-localpoliciessecurityoptions.md
index 459b035faf..075a1bd389 100644
--- a/windows/client-management/mdm/policy-csp-localpoliciessecurityoptions.md
+++ b/windows/client-management/mdm/policy-csp-localpoliciessecurityoptions.md
@@ -19,7 +19,7 @@ ms.topic: reference
> [!NOTE]
-> To find data formats (and other policy-related details), see [Policy DDF file](./policy-ddf-file.md).
+> To find data formats (and other policy-related details), see [Policy DDF file](./configuration-service-provider-ddf.md).
From fd9d7ac6ef6ee08dd128111579a334c9f1528a15 Mon Sep 17 00:00:00 2001
From: Vinay Pamnani <37223378+vinaypamnani-msft@users.noreply.github.com>
Date: Mon, 6 Feb 2023 14:21:48 -0500
Subject: [PATCH 81/98] Fix redirect
---
.openpublishing.redirection.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
index 22639222c2..645db60d9e 100644
--- a/.openpublishing.redirection.json
+++ b/.openpublishing.redirection.json
@@ -20516,7 +20516,7 @@
"redirect_document_id": true
},
{
- "source_path": "windows-docs-pr/windows/client-management/mdm/policy-ddf-file.md",
+ "source_path": "windows/client-management/mdm/policy-ddf-file.md",
"redirect_url": "/windows/client-management/mdm/configuration-service-provider-ddf",
"redirect_document_id": true
}
From 929412537593106e322a22679bda52e23c372a5c Mon Sep 17 00:00:00 2001
From: Tarun Maganur <104856032+Tarun-Edu@users.noreply.github.com>
Date: Mon, 6 Feb 2023 13:51:19 -0800
Subject: [PATCH 82/98] Update windows-11-se-overview.md
---
education/windows/windows-11-se-overview.md | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/education/windows/windows-11-se-overview.md b/education/windows/windows-11-se-overview.md
index 8a63a27c99..bf2de408fe 100644
--- a/education/windows/windows-11-se-overview.md
+++ b/education/windows/windows-11-se-overview.md
@@ -93,6 +93,7 @@ The following applications can also run on Windows 11 SE, and can be deployed us
| `Class Policy` | 114.0.0 | Win32 | `Class Policy` |
| `Classroom.cloud` | 1.40.0004 | Win32 | `NetSupport` |
| `CoGat Secure Browser` | 11.0.0.19 | Win32 | `Riverside Insights` |
+| `ContentKeeper Cloud` | 9.01.45 | Win32 | `ContentKeeper Technologies` |
| `Dragon Professional Individual` | 15.00.100 | Win32 | `Nuance Communications` |
| `DRC INSIGHT Online Assessments` | 12.0.0.0 | `Store` | `Data recognition Corporation` |
| `Duo from Cisco` | 3.0.0 | Win32 | `Cisco` |
@@ -104,7 +105,7 @@ The following applications can also run on Windows 11 SE, and can be deployed us
| `Free NaturalReader` | 16.1.2 | Win32 | `Natural Soft` |
| `Ghotit Real Writer & Reader` | 10.14.2.3 | Win32 | `Ghotit Ltd` |
| `GoGuardian` | 1.4.4 | Win32 | `GoGuardian` |
-| `Google Chrome` | 102.0.5005.115 | Win32 | `Google` |
+| `Google Chrome` | 109.0.5414.75 | Win32 | `Google` |
| `Illuminate Lockdown Browser` | 2.0.5 | Win32 | `Illuminate Education` |
| `Immunet` | 7.5.8.21178 | Win32 | `Immunet` |
| `Impero Backdrop Client` | 4.4.86 | Win32 | `Impero Software` |
@@ -137,10 +138,10 @@ The following applications can also run on Windows 11 SE, and can be deployed us
| `Respondus Lockdown Browser` | 2.0.9.03 | Win32 | `Respondus` |
| `Safe Exam Browser` | 3.4.1.505 | Win32 | `Safe Exam Browser` |
| `Senso.Cloud` | 2021.11.15.0 | Win32 | `Senso.Cloud` |
-| `Smoothwall Monitor` | 2.8.0 | Win32 | `Smoothwall Ltd` |
+| `Smoothwall Monitor` | 2.9.2 | Win32 | `Smoothwall Ltd` |
| `SuperNova Magnifier & Screen Reader` | 21.02 | Win32 | `Dolphin Computer Access` |
| `SuperNova Magnifier & Speech` | 21.02 | Win32 | `Dolphin Computer Access` |
-|`TX Secure Browser` | 15.0.0 | Win32 | `Cambium Development`
+|`TX Secure Browser` | 15.0.0 | Win32 | `Cambium Development` |
| `VitalSourceBookShelf` | 10.2.26.0 | Win32 | `VitalSource Technologies Inc` |
| `Winbird` | 19 | Win32 | `Winbird Co., Ltd.` |
| `WordQ` | 5.4.23 | Win32 | `Mathetmots` |
From 9719a245a7fec2c5cfc7fb2eb3f3244308bcd858 Mon Sep 17 00:00:00 2001
From: Andre Della Monica
Date: Mon, 6 Feb 2023 20:03:28 -0600
Subject: [PATCH 83/98] Doc updates to Feature and Quality updates
---
...autopatch-windows-feature-update-overview.md | 6 +++---
...autopatch-windows-quality-update-overview.md | 17 ++++++++++++-----
2 files changed, 15 insertions(+), 8 deletions(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
index b58aa2938f..5f3cf42951 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
@@ -1,7 +1,7 @@
---
title: Windows feature updates
description: This article explains how Windows feature updates are managed in Autopatch
-ms.date: 02/02/2023
+ms.date: 02/07/2023
ms.prod: windows-client
ms.technology: itpro-updates
ms.topic: conceptual
@@ -88,7 +88,7 @@ Windows Autopatch provides a permanent pause of a Windows feature update deploym
8. If you're resuming an update, you can select one or more deployment rings.
9. Select **Okay**.
-If you've paused an update, the specified release will have the **Customer Paused** status. The Windows Autopatch service can't overwrite a customer-initiated pause. You must select **Resume** to resume the update.
+If you've paused an update, the specified release will have the **Customer Pause** status. The Windows Autopatch service can't overwrite IT admin's pause. You must select **Resume** to resume the update.
> [!NOTE]
> The **Service Paused** status only applies to [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release). Windows Autopatch doesn't pause Windows feature updates on your behalf.
@@ -98,7 +98,7 @@ If you've paused an update, the specified release will have the **Customer Pause
Windows Autopatch doesn’t support the rollback of Windows Feature updates.
> [!CAUTION]
-> It’s not recommended to use [Microsoft Intune’s capabilities](/mem/intune/protect/windows-10-update-rings#manage-your-windows-update-rings) to pause and rollback a Windows feature update. However, if you choose to pause, resume and/or roll back from Intune, Windows Autopatch is **not** responsible for any problems that arise from rolling back the Windows feature update.
+> It's only recommended to use Windows Autopatch's end-user experience to pause and resume [Windows quality](windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release) and [Windows feature updates](#pausing-and-resuming-a-release). If you need assistance with pausing and resuming updates, please [submit a support request](../operate/windows-autopatch-support-request.md).
## Contact support
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
index c8ab6062c6..2ed89e8d06 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
@@ -1,7 +1,7 @@
---
title: Windows quality updates
description: This article explains how Windows quality updates are managed in Autopatch
-ms.date: 12/15/2022
+ms.date: 02/07/2023
ms.prod: windows-client
ms.technology: itpro-updates
ms.topic: conceptual
@@ -9,7 +9,7 @@ ms.localizationpriority: medium
author: tiaraquan
ms.author: tiaraquan
manager: dougeby
-msreviewer: hathind
+msreviewer: andredm7
---
# Windows quality updates
@@ -125,12 +125,19 @@ If Windows Autopatch detects a [significant issue with a release](../operate/win
8. If you're resuming an update, you can select one or more deployment rings.
9. Select **Okay**.
-There are two statuses associated with paused quality updates, **Service Paused** and **Customer Paused**.
+> [!CAUTION]
+> It's only recommended to use Windows Autopatch's end-user experience to pause and resume [Windows quality](windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release) and [Windows feature updates](#pausing-and-resuming-a-release). If you need assistance with pausing and resuming updates, please [submit a support request](../operate/windows-autopatch-support-request.md).
+
+There are three statuses associated with paused quality updates, **Service Paused**, **Customer Paused** and **Customer & Service pause**.
| Status | Description |
| ----- | ------ |
-| Service Paused | If the Windows Autopatch service has paused an update, the release will have the **Service Paused** status. You must [submit a support request](windows-autopatch-support-request.md) to resume the update. |
-| Customer Paused | If you've paused an update, the release will have the **Customer Paused** status. The Windows Autopatch service can't overwrite a customer-initiated pause. You must select **Resume** to resume the update. |
+| Service Pause | If the Windows Autopatch service has paused an update, the release will have the **Service Pause** status. You must [submit a support request](windows-autopatch-support-request.md) to resume the update. |
+| Customer Pause | If you've paused an update, the release will have the **Customer Pause** status. The Windows Autopatch service can't overwrite a customer-initiated pause. You must select **Resume** to resume the update. |
+| Customer & Service Pause | If you and Microsoft (Windows Autopatch service) have both paused an update, the release will have the **Customer & Service pause** status. If you plan on resuming an update deployment under this mixed state, you must first [submit a support request](windows-autopatch-support-request.md) for Windows Autopatch service engineers to resume the update deployment on your behalf, this will change your update deployment status to **Customer pause**, once this happens, you can resume the update deployment in Windows Autopatch Release management blade yourself. |
+
+> [!NOTE]
+> The service-level pause of updates is driven by the various software update deployment-related signals Windows Autopatch receive from Windows Update for Business several other product groups within Microsoft.
## Remediating Ineligible and/or Not up to Date devices
From 6050b7cd71e4802c908a12c71ecfa182c09563ea Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Mon, 6 Feb 2023 19:41:41 -0800
Subject: [PATCH 84/98] Update
windows-autopatch-windows-feature-update-overview.md
---
.../windows-autopatch-windows-feature-update-overview.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
index 5f3cf42951..0d53f7c783 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
@@ -91,14 +91,14 @@ Windows Autopatch provides a permanent pause of a Windows feature update deploym
If you've paused an update, the specified release will have the **Customer Pause** status. The Windows Autopatch service can't overwrite IT admin's pause. You must select **Resume** to resume the update.
> [!NOTE]
-> The **Service Paused** status only applies to [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release). Windows Autopatch doesn't pause Windows feature updates on your behalf.
+> The **Service Pause** status only applies to [Windows quality updates](../operate/windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release). Windows Autopatch doesn't pause Windows feature updates on your behalf.
## Rollback
Windows Autopatch doesn’t support the rollback of Windows Feature updates.
> [!CAUTION]
-> It's only recommended to use Windows Autopatch's end-user experience to pause and resume [Windows quality](windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release) and [Windows feature updates](#pausing-and-resuming-a-release). If you need assistance with pausing and resuming updates, please [submit a support request](../operate/windows-autopatch-support-request.md).
+> It's only recommended to use Windows Autopatch's end-user experience to pause and resume [Windows quality](../operate/windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release) and [Windows feature updates](#pausing-and-resuming-a-release). If you need assistance with pausing and resuming updates, please [submit a support request](../operate/windows-autopatch-support-request.md).
## Contact support
From 4735447f4381f2a9c62fe0cda6915f096e61a44f Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Mon, 6 Feb 2023 19:45:04 -0800
Subject: [PATCH 85/98] Update
windows-autopatch-windows-quality-update-overview.md
---
.../windows-autopatch-windows-quality-update-overview.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
index 2ed89e8d06..ee7cad09af 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
@@ -128,13 +128,13 @@ If Windows Autopatch detects a [significant issue with a release](../operate/win
> [!CAUTION]
> It's only recommended to use Windows Autopatch's end-user experience to pause and resume [Windows quality](windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release) and [Windows feature updates](#pausing-and-resuming-a-release). If you need assistance with pausing and resuming updates, please [submit a support request](../operate/windows-autopatch-support-request.md).
-There are three statuses associated with paused quality updates, **Service Paused**, **Customer Paused** and **Customer & Service pause**.
+The three following statuses are associated with paused quality updates:
| Status | Description |
| ----- | ------ |
-| Service Pause | If the Windows Autopatch service has paused an update, the release will have the **Service Pause** status. You must [submit a support request](windows-autopatch-support-request.md) to resume the update. |
+| Service Pause | If the Windows Autopatch service has paused an update, the release will have the **Service Pause** status. You must [submit a support request](../operate/windows-autopatch-support-request.md) to resume the update. |
| Customer Pause | If you've paused an update, the release will have the **Customer Pause** status. The Windows Autopatch service can't overwrite a customer-initiated pause. You must select **Resume** to resume the update. |
-| Customer & Service Pause | If you and Microsoft (Windows Autopatch service) have both paused an update, the release will have the **Customer & Service pause** status. If you plan on resuming an update deployment under this mixed state, you must first [submit a support request](windows-autopatch-support-request.md) for Windows Autopatch service engineers to resume the update deployment on your behalf, this will change your update deployment status to **Customer pause**, once this happens, you can resume the update deployment in Windows Autopatch Release management blade yourself. |
+| Customer & Service Pause | If you and Windows Autopatch have both paused an update, the release will have the **Customer & Service Pause** status. If you plan on resuming an update deployment under this mixed state, you must first [submit a support request](../operate/windows-autopatch-support-request.md) for Windows Autopatch to resume the update deployment on your behalf. After approval, the update deployment status will change to **Customer Pause**. Once this happens, you can resume the update deployment in Windows Autopatch Release management blade. |
> [!NOTE]
> The service-level pause of updates is driven by the various software update deployment-related signals Windows Autopatch receive from Windows Update for Business several other product groups within Microsoft.
From 3540e551d428c21eeed3cd59845043d6983cb727 Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Mon, 6 Feb 2023 19:45:37 -0800
Subject: [PATCH 86/98] Update
windows-autopatch-windows-feature-update-overview.md
---
.../windows-autopatch-windows-feature-update-overview.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
index 0d53f7c783..5289b2b06f 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
@@ -95,7 +95,7 @@ If you've paused an update, the specified release will have the **Customer Pause
## Rollback
-Windows Autopatch doesn’t support the rollback of Windows Feature updates.
+Windows Autopatch doesn’t support the rollback of Windows feature updates.
> [!CAUTION]
> It's only recommended to use Windows Autopatch's end-user experience to pause and resume [Windows quality](../operate/windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release) and [Windows feature updates](#pausing-and-resuming-a-release). If you need assistance with pausing and resuming updates, please [submit a support request](../operate/windows-autopatch-support-request.md).
From dada47a33c1a22c74b66abc8995cfe8d1e562c4a Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Tue, 7 Feb 2023 06:49:19 -0800
Subject: [PATCH 87/98] Update
windows-autopatch-windows-feature-update-overview.md
---
.../windows-autopatch-windows-feature-update-overview.md | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
index 5289b2b06f..fb14accf70 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
@@ -73,6 +73,10 @@ Windows Autopatch provides a permanent pause of a Windows feature update deploym
## Pausing and resuming a release
+> [!CAUTION]
+> It's only recommended to use Windows Autopatch's end-user experience to pause and resume [Windows quality](../operate/windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release) and [Windows feature updates](#pausing-and-resuming-a-release). If you need assistance with pausing and resuming updates, please [submit a support request](../operate/windows-autopatch-support-request.md).
+
+
> [!IMPORTANT]
> Pausing or resuming an update can take up to eight hours to be applied to devices. Windows Autopatch uses Microsoft Intune as its management solution and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.
For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
From bb140fa7c3411341ad07904d39f372992e9f7e8e Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Tue, 7 Feb 2023 06:50:04 -0800
Subject: [PATCH 88/98] Update
windows-autopatch-windows-feature-update-overview.md
---
.../operate/windows-autopatch-windows-feature-update-overview.md | 1 -
1 file changed, 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
index fb14accf70..7425935a04 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
@@ -76,7 +76,6 @@ Windows Autopatch provides a permanent pause of a Windows feature update deploym
> [!CAUTION]
> It's only recommended to use Windows Autopatch's end-user experience to pause and resume [Windows quality](../operate/windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release) and [Windows feature updates](#pausing-and-resuming-a-release). If you need assistance with pausing and resuming updates, please [submit a support request](../operate/windows-autopatch-support-request.md).
-
> [!IMPORTANT]
> Pausing or resuming an update can take up to eight hours to be applied to devices. Windows Autopatch uses Microsoft Intune as its management solution and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
From ba077c67462cb50bb07b6ce8cb8e5522cec934fa Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Tue, 7 Feb 2023 07:03:49 -0800
Subject: [PATCH 89/98] Update
windows-autopatch-windows-quality-update-overview.md
---
.../windows-autopatch-windows-quality-update-overview.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
index ee7cad09af..f585127b25 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
@@ -108,6 +108,9 @@ Windows Autopatch schedules and deploys required Out of Band (OOB) updates relea
### Pausing and resuming a release
+> [!CAUTION]
+> It's only recommended to use Windows Autopatch's end-user experience to pause and resume [Windows quality](windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release) and [Windows feature updates](#pausing-and-resuming-a-release). If you need assistance with pausing and resuming updates, please [submit a support request](../operate/windows-autopatch-support-request.md).
+
If Windows Autopatch detects a [significant issue with a release](../operate/windows-autopatch-windows-quality-update-signals.md), we may decide to pause that release.
> [!IMPORTANT]
@@ -125,9 +128,6 @@ If Windows Autopatch detects a [significant issue with a release](../operate/win
8. If you're resuming an update, you can select one or more deployment rings.
9. Select **Okay**.
-> [!CAUTION]
-> It's only recommended to use Windows Autopatch's end-user experience to pause and resume [Windows quality](windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release) and [Windows feature updates](#pausing-and-resuming-a-release). If you need assistance with pausing and resuming updates, please [submit a support request](../operate/windows-autopatch-support-request.md).
-
The three following statuses are associated with paused quality updates:
| Status | Description |
From 13f46a695fda77ee3e10c66b6425571f379d2d4f Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Tue, 7 Feb 2023 08:16:34 -0800
Subject: [PATCH 90/98] Update
windows-autopatch-windows-quality-update-overview.md
---
.../windows-autopatch-windows-quality-update-overview.md | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
index f585127b25..d0f0148818 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
@@ -111,7 +111,7 @@ Windows Autopatch schedules and deploys required Out of Band (OOB) updates relea
> [!CAUTION]
> It's only recommended to use Windows Autopatch's end-user experience to pause and resume [Windows quality](windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release) and [Windows feature updates](#pausing-and-resuming-a-release). If you need assistance with pausing and resuming updates, please [submit a support request](../operate/windows-autopatch-support-request.md).
-If Windows Autopatch detects a [significant issue with a release](../operate/windows-autopatch-windows-quality-update-signals.md), we may decide to pause that release.
+The service-level pause of updates is driven by the various software update deployment-related signals Windows Autopatch receive from Windows Update for Business several other product groups within Microsoft. If Windows Autopatch detects a [significant issue with a release](../operate/windows-autopatch-windows-quality-update-signals.md), we may decide to pause that release.
> [!IMPORTANT]
> Pausing or resuming an update can take up to eight hours to be applied to devices. Windows Autopatch uses Microsoft Intune as its management solution and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
@@ -136,9 +136,6 @@ The three following statuses are associated with paused quality updates:
| Customer Pause | If you've paused an update, the release will have the **Customer Pause** status. The Windows Autopatch service can't overwrite a customer-initiated pause. You must select **Resume** to resume the update. |
| Customer & Service Pause | If you and Windows Autopatch have both paused an update, the release will have the **Customer & Service Pause** status. If you plan on resuming an update deployment under this mixed state, you must first [submit a support request](../operate/windows-autopatch-support-request.md) for Windows Autopatch to resume the update deployment on your behalf. After approval, the update deployment status will change to **Customer Pause**. Once this happens, you can resume the update deployment in Windows Autopatch Release management blade. |
-> [!NOTE]
-> The service-level pause of updates is driven by the various software update deployment-related signals Windows Autopatch receive from Windows Update for Business several other product groups within Microsoft.
-
## Remediating Ineligible and/or Not up to Date devices
To ensure your devices receive Windows quality updates, Windows Autopatch provides information on how you can remediate [Ineligible Devices (Customer Actions)](../operate/windows-autopatch-windows-quality-update-reports-overview.md#ineligible-devices-customer-action). In addition, the Windows Autopatch service may remediate [Not up to Date devices](../operate/windows-autopatch-windows-quality-update-reports-overview.md#not-up-to-date-microsoft-action) to bring them back into compliance.
From ccdf23dececf81ea2f04491a26bfbf44204be7e2 Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Tue, 7 Feb 2023 11:09:39 -0800
Subject: [PATCH 91/98] Update
windows-autopatch-windows-quality-update-overview.md
---
.../windows-autopatch-windows-quality-update-overview.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
index d0f0148818..5c89498b75 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
@@ -134,7 +134,7 @@ The three following statuses are associated with paused quality updates:
| ----- | ------ |
| Service Pause | If the Windows Autopatch service has paused an update, the release will have the **Service Pause** status. You must [submit a support request](../operate/windows-autopatch-support-request.md) to resume the update. |
| Customer Pause | If you've paused an update, the release will have the **Customer Pause** status. The Windows Autopatch service can't overwrite a customer-initiated pause. You must select **Resume** to resume the update. |
-| Customer & Service Pause | If you and Windows Autopatch have both paused an update, the release will have the **Customer & Service Pause** status. If you plan on resuming an update deployment under this mixed state, you must first [submit a support request](../operate/windows-autopatch-support-request.md) for Windows Autopatch to resume the update deployment on your behalf. After approval, the update deployment status will change to **Customer Pause**. Once this happens, you can resume the update deployment in Windows Autopatch Release management blade. |
+| Customer & Service Pause | If you and Windows Autopatch have both paused an update, the release will have the Customer & Service Pause status. If you resume the update, and the Service Pause status still remains, you must [submit a support request](../operate/windows-autopatch-support-request.md) for Windows Autopatch to resume the update deployment on your behalf. |
## Remediating Ineligible and/or Not up to Date devices
From 974834f1de9ee341caa655285cc0290b84232e35 Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Tue, 7 Feb 2023 11:19:13 -0800
Subject: [PATCH 92/98] Update
windows-autopatch-windows-quality-update-overview.md
---
.../windows-autopatch-windows-quality-update-overview.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
index 5c89498b75..0651acb3f9 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
@@ -134,7 +134,7 @@ The three following statuses are associated with paused quality updates:
| ----- | ------ |
| Service Pause | If the Windows Autopatch service has paused an update, the release will have the **Service Pause** status. You must [submit a support request](../operate/windows-autopatch-support-request.md) to resume the update. |
| Customer Pause | If you've paused an update, the release will have the **Customer Pause** status. The Windows Autopatch service can't overwrite a customer-initiated pause. You must select **Resume** to resume the update. |
-| Customer & Service Pause | If you and Windows Autopatch have both paused an update, the release will have the Customer & Service Pause status. If you resume the update, and the Service Pause status still remains, you must [submit a support request](../operate/windows-autopatch-support-request.md) for Windows Autopatch to resume the update deployment on your behalf. |
+| Customer & Service Pause | If you and Windows Autopatch have both paused an update, the release will have the **Customer & Service Pause** status. If you resume the update, and the **Service Pause** status still remains, you must [submit a support request](../operate/windows-autopatch-support-request.md) for Windows Autopatch to resume the update deployment on your behalf. |
## Remediating Ineligible and/or Not up to Date devices
From 09b3ec450ac84e2166805231457053254f432da4 Mon Sep 17 00:00:00 2001
From: Tiara Quan <95256667+tiaraquan@users.noreply.github.com>
Date: Tue, 7 Feb 2023 11:46:39 -0800
Subject: [PATCH 93/98] Update
windows-autopatch-windows-quality-update-overview.md
---
.../windows-autopatch-windows-quality-update-overview.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
index 0651acb3f9..107c863015 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
@@ -133,7 +133,7 @@ The three following statuses are associated with paused quality updates:
| Status | Description |
| ----- | ------ |
| Service Pause | If the Windows Autopatch service has paused an update, the release will have the **Service Pause** status. You must [submit a support request](../operate/windows-autopatch-support-request.md) to resume the update. |
-| Customer Pause | If you've paused an update, the release will have the **Customer Pause** status. The Windows Autopatch service can't overwrite a customer-initiated pause. You must select **Resume** to resume the update. |
+| Customer Pause | If you've paused an update, the release will have the **Customer Pause** status. The Windows Autopatch service can't overwrite an IT admin's pause. You must select **Resume** to resume the update. |
| Customer & Service Pause | If you and Windows Autopatch have both paused an update, the release will have the **Customer & Service Pause** status. If you resume the update, and the **Service Pause** status still remains, you must [submit a support request](../operate/windows-autopatch-support-request.md) for Windows Autopatch to resume the update deployment on your behalf. |
## Remediating Ineligible and/or Not up to Date devices
From d01dc9e1527cbc680f99eb7496db281fb74f72f0 Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Wed, 8 Feb 2023 08:11:24 -0800
Subject: [PATCH 94/98] Tweak
---
.../windows-autopatch-windows-quality-update-overview.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
index 107c863015..0ff47c507d 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
@@ -111,7 +111,9 @@ Windows Autopatch schedules and deploys required Out of Band (OOB) updates relea
> [!CAUTION]
> It's only recommended to use Windows Autopatch's end-user experience to pause and resume [Windows quality](windows-autopatch-windows-quality-update-overview.md#pausing-and-resuming-a-release) and [Windows feature updates](#pausing-and-resuming-a-release). If you need assistance with pausing and resuming updates, please [submit a support request](../operate/windows-autopatch-support-request.md).
-The service-level pause of updates is driven by the various software update deployment-related signals Windows Autopatch receive from Windows Update for Business several other product groups within Microsoft. If Windows Autopatch detects a [significant issue with a release](../operate/windows-autopatch-windows-quality-update-signals.md), we may decide to pause that release.
+The service-level pause of updates is driven by the various software update deployment-related signals Windows Autopatch receives from Windows Update for Business, and several other product groups within Microsoft.
+
+If Windows Autopatch detects a [significant issue with a release](../operate/windows-autopatch-windows-quality-update-signals.md), we may decide to pause that release.
> [!IMPORTANT]
> Pausing or resuming an update can take up to eight hours to be applied to devices. Windows Autopatch uses Microsoft Intune as its management solution and that's the average frequency devices take to communicate back to Microsoft Intune with new instructions to pause, resume or rollback updates.For more information, see [how long does it take for devices to get a policy, profile, or app after they are assigned from Microsoft Intune](/mem/intune/configuration/device-profile-troubleshoot#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
From 466e0ce1aa02b4111e4954c7dd7b1eaac265f4d5 Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Wed, 8 Feb 2023 08:22:05 -0800
Subject: [PATCH 95/98] Tweak.
---
.../operate/windows-autopatch-support-request.md | 2 --
.../windows-autopatch-windows-feature-update-overview.md | 2 +-
.../prepare/windows-autopatch-enrollment-support-request.md | 2 +-
3 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request.md
index 800f387276..79ff9e1b78 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-support-request.md
@@ -17,8 +17,6 @@ msreviewer: hathind
> [!IMPORTANT]
> Make sure you've [added and verified your admin contacts](../deploy/windows-autopatch-admin-contacts.md). The Windows Autopatch Service Engineering Team will contact these individuals for assistance with remediating issues.
-You can submit support tickets to Microsoft using the Windows Autopatch admin center. Email is the recommended approach to interact with the Windows Autopatch Service Engineering Team.
-
## Submit a new support request
Support requests are triaged and responded to as they're received.
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
index 7425935a04..4d8d128f89 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-feature-update-overview.md
@@ -105,4 +105,4 @@ Windows Autopatch doesn’t support the rollback of Windows feature updates.
## Contact support
-If you’re experiencing issues related to Windows feature updates, you can [submit a support request](../operate/windows-autopatch-support-request.md). Email is the recommended approach to interact with the Windows Autopatch Service Engineering Team.
+If you’re experiencing issues related to Windows feature updates, you can [submit a support request](../operate/windows-autopatch-support-request.md).
diff --git a/windows/deployment/windows-autopatch/prepare/windows-autopatch-enrollment-support-request.md b/windows/deployment/windows-autopatch/prepare/windows-autopatch-enrollment-support-request.md
index c36be7a98b..44447d5697 100644
--- a/windows/deployment/windows-autopatch/prepare/windows-autopatch-enrollment-support-request.md
+++ b/windows/deployment/windows-autopatch/prepare/windows-autopatch-enrollment-support-request.md
@@ -14,7 +14,7 @@ msreviewer: hathind
# Submit a tenant enrollment support request
-If you need more assistance with tenant enrollment, you can submit support requests to the Windows Autopatch Service Engineering Team in the Windows Autopatch enrollment tool. Email is the recommended approach to interact with the Windows Autopatch Service Engineering Team.
+If you need more assistance with tenant enrollment, you can submit support requests to the Windows Autopatch Service Engineering Team in the Windows Autopatch enrollment tool.
> [!NOTE]
> After you've successfully enrolled your tenant, this feature will no longer be accessible. You must [submit a support request through the Tenant administration menu](../operate/windows-autopatch-support-request.md).
From 2f809b5ce63b9100fbcc15e9d63bf5954945696f Mon Sep 17 00:00:00 2001
From: Jared Agee
Date: Wed, 8 Feb 2023 11:36:01 -0600
Subject: [PATCH 96/98] Update remote-credential-guard.md
Removed redundant portion of a sentence, "to turn on Windows Defender Remote Credential Guard".
---
.../security/identity-protection/remote-credential-guard.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/windows/security/identity-protection/remote-credential-guard.md b/windows/security/identity-protection/remote-credential-guard.md
index e094da893b..eb1922b3a8 100644
--- a/windows/security/identity-protection/remote-credential-guard.md
+++ b/windows/security/identity-protection/remote-credential-guard.md
@@ -128,7 +128,7 @@ You must enable Restricted Admin or Windows Defender Remote Credential Guard on
- Add a new DWORD value named **DisableRestrictedAdmin**.
- - To turn on Restricted Admin and Windows Defender Remote Credential Guard, set the value of this registry setting to 0 to turn on Windows Defender Remote Credential Guard.
+ - To turn on Restricted Admin and Windows Defender Remote Credential Guard, set the value of this registry setting to 0.
3. Close Registry Editor.
@@ -189,4 +189,4 @@ mstsc.exe /remoteGuard
- No credentials are sent to the target device, but the target device still acquires Kerberos Service Tickets on its own.
-- The server and client must authenticate using Kerberos.
\ No newline at end of file
+- The server and client must authenticate using Kerberos.
From bc4215046196969c65c42f6a46a68f68137dc75a Mon Sep 17 00:00:00 2001
From: tiaraquan
Date: Wed, 8 Feb 2023 14:01:26 -0800
Subject: [PATCH 97/98] Tweak.
---
.../windows-autopatch-windows-quality-update-overview.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
index 0ff47c507d..c2ad146ec6 100644
--- a/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
+++ b/windows/deployment/windows-autopatch/operate/windows-autopatch-windows-quality-update-overview.md
@@ -89,7 +89,7 @@ By default, the service expedites quality updates as needed. For those organizat
**To turn off service-driven expedited quality updates:**
1. Go to **[Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431)** > **Devices**.
-2. Under **Windows Autopatch** > **Release management**, go to the **Release settings** tab and turn off the **Expedited Quality Updates** setting.
+2. Under **Windows Autopatch** > **Release management**, go to the **Release settings** tab and turn off the **Expedited quality updates** setting.
> [!NOTE]
> Windows Autopatch doesn't allow customers to request expedited releases.
From 1a8346994b82d7db547a5ae0729f7ea3fafad082 Mon Sep 17 00:00:00 2001
From: Angela Fleischmann
Date: Wed, 8 Feb 2023 16:18:18 -0700
Subject: [PATCH 98/98] Update policy-csp-update.md
https://microsoft-ce-csi.acrolinx.cloud/api/v1/checking/scorecards/e399e338-279c-47c8-b5ad-b239d24218f0#CORRECTNESS
Line 2665 and 3061: is a integer. > is an integer.
Line 2736: on the every week. > every week.
Line 3120: allows to remove > allows removing
---
windows/client-management/mdm/policy-csp-update.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/windows/client-management/mdm/policy-csp-update.md b/windows/client-management/mdm/policy-csp-update.md
index 434acb5dde..e9921d6795 100644
--- a/windows/client-management/mdm/policy-csp-update.md
+++ b/windows/client-management/mdm/policy-csp-update.md
@@ -2662,7 +2662,7 @@ If you select "Apply only during active hours" in conjunction with Option 1 or 2
-Enables the IT admin to schedule the day of the update installation. The data type is a integer.
+Enables the IT admin to schedule the day of the update installation. The data type is an integer.
@@ -2733,7 +2733,7 @@ Enables the IT admin to schedule the day of the update installation. The data ty
-Enables the IT admin to schedule the update installation on the every week. Value type is integer.
+Enables the IT admin to schedule the update installation every week. Value type is integer.
@@ -3058,7 +3058,7 @@ Enables the IT admin to schedule the update installation on the third week of th
- the IT admin to schedule the time of the update installation. The data type is a integer. Supported values are 0-23, where 0 = 12 AM and 23 = 11 PM. The default value is 3.
+ the IT admin to schedule the time of the update installation. The data type is an integer. Supported values are 0-23, where 0 = 12 AM and 23 = 11 PM. The default value is 3.
@@ -3117,7 +3117,7 @@ Enables the IT admin to schedule the update installation on the third week of th
-This setting allows to remove access to "Pause updates" feature.
+This setting allows removing access to "Pause updates" feature.
Once enabled user access to pause updates is removed.