From bd70d1cbc56f32ac94de050468bd0e1d51e0eaf6 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Wed, 14 Aug 2024 12:28:49 -0400 Subject: [PATCH 1/7] Metadata updates + docfx --- windows/security/docfx.json | 12 +++++++++--- .../certification/fips-140-validation.md | 4 ---- .../certification/validations/cc-windows-previous.md | 4 ---- .../validations/cc-windows-server-2022-2019-2016.md | 4 ---- .../validations/cc-windows-server-previous.md | 4 ---- .../validations/cc-windows-server-semi-annual.md | 4 ---- .../certification/validations/cc-windows10.md | 4 ---- .../certification/validations/cc-windows11.md | 4 ---- .../validations/fips-140-other-products.md | 5 +---- .../validations/fips-140-windows-previous.md | 5 +---- .../validations/fips-140-windows-server-2016.md | 4 ---- .../validations/fips-140-windows-server-2019.md | 5 +---- .../validations/fips-140-windows-server-previous.md | 4 ---- .../fips-140-windows-server-semi-annual.md | 4 ---- .../certification/validations/fips-140-windows10.md | 4 ---- .../certification/validations/fips-140-windows11.md | 4 ---- .../windows-platform-common-criteria.md | 4 ---- 17 files changed, 12 insertions(+), 67 deletions(-) diff --git a/windows/security/docfx.json b/windows/security/docfx.json index c921606652..3f047d42c7 100644 --- a/windows/security/docfx.json +++ b/windows/security/docfx.json @@ -99,7 +99,9 @@ "operating-system-security/data-protection/**/*.md": "paolomatarazzo", "operating-system-security/data-protection/**/*.yml": "paolomatarazzo", "operating-system-security/network-security/**/*.md": "paolomatarazzo", - "operating-system-security/network-security/**/*.yml": "paolomatarazzo" + "operating-system-security/network-security/**/*.yml": "paolomatarazzo", + "security-foundations/certification/*.md": "paolomatarazzo", + "security-foundations/certification/*.yml": "paolomatarazzo" }, "ms.author": { "application-security//**/*.md": "vinpa", @@ -119,7 +121,9 @@ "operating-system-security/data-protection/**/*.md": "paoloma", "operating-system-security/data-protection/**/*.yml": "paoloma", "operating-system-security/network-security/**/*.md": "paoloma", - "operating-system-security/network-security/**/*.yml": "paoloma" + "operating-system-security/network-security/**/*.yml": "paoloma", + "security-foundations/certification/*.md": "paoloma", + "security-foundations/certification/*.yml": "paoloma" }, "appliesto": { "application-security//**/*.md": [ @@ -233,7 +237,8 @@ "operating-system-security/data-protection/personal-data-encryption/*.md": "rhonnegowda", "operating-system-security/device-management/windows-security-configuration-framework/*.md": "jmunck", "operating-system-security/network-security/vpn/*.md": "pesmith", - "operating-system-security/network-security/windows-firewall/*.md": "nganguly" + "operating-system-security/network-security/windows-firewall/*.md": "nganguly", + "security-foundations/certification/*.md": "paoloma" }, "ms.collection": { "book/*.md": "tier3", @@ -242,6 +247,7 @@ "information-protection/tpm/*.md": "tier1", "operating-system-security/data-protection/bitlocker/*.md": "tier1", "operating-system-security/data-protection/personal-data-encryption/*.md": "tier1", + "security-foundations/certification/*.md": "tier3", "threat-protection/auditing/*.md": "tier3" }, "ROBOTS": { diff --git a/windows/security/security-foundations/certification/fips-140-validation.md b/windows/security/security-foundations/certification/fips-140-validation.md index 7e2163afdc..739b778e25 100644 --- a/windows/security/security-foundations/certification/fips-140-validation.md +++ b/windows/security/security-foundations/certification/fips-140-validation.md @@ -3,10 +3,6 @@ title: Windows FIPS 140 validation description: Learn how Microsoft products and cryptographic modules follow the U.S. Federal government standard FIPS 140. ms.date: 2/1/2024 ms.topic: reference -ms.author: v-rodurff -author: msrobertd -ms.reviewer: paoloma -ms.collection: tier3 --- # Windows FIPS 140 validation diff --git a/windows/security/security-foundations/certification/validations/cc-windows-previous.md b/windows/security/security-foundations/certification/validations/cc-windows-previous.md index 58209a1bc7..8d5cd8c275 100644 --- a/windows/security/security-foundations/certification/validations/cc-windows-previous.md +++ b/windows/security/security-foundations/certification/validations/cc-windows-previous.md @@ -3,10 +3,6 @@ title: Common Criteria certifications for previous Windows releases description: Learn about the completed Common Criteria certifications for previous Windows releases. ms.date: 2/1/2024 ms.topic: reference -ms.author: v-rodurff -author: msrobertd -ms.reviewer: paoloma -ms.collection: tier3 --- # Common Criteria certifications for previous Windows releases diff --git a/windows/security/security-foundations/certification/validations/cc-windows-server-2022-2019-2016.md b/windows/security/security-foundations/certification/validations/cc-windows-server-2022-2019-2016.md index 5e7d75c602..75df55214c 100644 --- a/windows/security/security-foundations/certification/validations/cc-windows-server-2022-2019-2016.md +++ b/windows/security/security-foundations/certification/validations/cc-windows-server-2022-2019-2016.md @@ -3,10 +3,6 @@ title: Common Criteria certifications for Windows Server 2022, 2019, and 2016 description: Learn about the completed Common Criteria certifications for Windows Server 2022, 2019, and 2016. ms.date: 2/1/2024 ms.topic: reference -ms.author: v-rodurff -author: msrobertd -ms.reviewer: paoloma -ms.collection: tier3 --- # Windows Server 2022, 2019, and 2016 Common Criteria certifications diff --git a/windows/security/security-foundations/certification/validations/cc-windows-server-previous.md b/windows/security/security-foundations/certification/validations/cc-windows-server-previous.md index d8b655246d..392c293fd2 100644 --- a/windows/security/security-foundations/certification/validations/cc-windows-server-previous.md +++ b/windows/security/security-foundations/certification/validations/cc-windows-server-previous.md @@ -3,10 +3,6 @@ title: Common Criteria certifications for previous Windows Server releases description: Learn about the completed Common Criteria certifications for previous Windows Server releases. ms.date: 2/1/2024 ms.topic: reference -ms.author: v-rodurff -author: msrobertd -ms.reviewer: paoloma -ms.collection: tier3 --- # Common Criteria certifications for previous Windows Server releases diff --git a/windows/security/security-foundations/certification/validations/cc-windows-server-semi-annual.md b/windows/security/security-foundations/certification/validations/cc-windows-server-semi-annual.md index d65c3f9442..979a3196ee 100644 --- a/windows/security/security-foundations/certification/validations/cc-windows-server-semi-annual.md +++ b/windows/security/security-foundations/certification/validations/cc-windows-server-semi-annual.md @@ -3,10 +3,6 @@ title: Common Criteria certifications for Windows Server semi-annual releases description: Learn about the completed Common Criteria certifications for Windows Server semi-annual releases. ms.date: 2/1/2024 ms.topic: reference -ms.author: v-rodurff -author: msrobertd -ms.reviewer: paoloma -ms.collection: tier3 --- # Windows Server semi-annual Common Criteria certifications diff --git a/windows/security/security-foundations/certification/validations/cc-windows10.md b/windows/security/security-foundations/certification/validations/cc-windows10.md index 916d28b4cd..36bd9cc400 100644 --- a/windows/security/security-foundations/certification/validations/cc-windows10.md +++ b/windows/security/security-foundations/certification/validations/cc-windows10.md @@ -3,10 +3,6 @@ title: Common Criteria certifications for Windows 10 description: Learn about the completed Common Criteria certifications for Windows 10. ms.date: 2/1/2024 ms.topic: reference -ms.author: v-rodurff -author: msrobertd -ms.reviewer: paoloma -ms.collection: tier3 --- # Windows 10 Common Criteria certifications diff --git a/windows/security/security-foundations/certification/validations/cc-windows11.md b/windows/security/security-foundations/certification/validations/cc-windows11.md index 1f653104a1..52e683c0c2 100644 --- a/windows/security/security-foundations/certification/validations/cc-windows11.md +++ b/windows/security/security-foundations/certification/validations/cc-windows11.md @@ -3,10 +3,6 @@ title: Common Criteria certifications for Windows 11 description: Learn about the completed Common Criteria certifications for Windows 11. ms.date: 2/1/2024 ms.topic: reference -ms.author: v-rodurff -author: msrobertd -ms.reviewer: paoloma -ms.collection: tier3 --- # Windows 11 Common Criteria certifications diff --git a/windows/security/security-foundations/certification/validations/fips-140-other-products.md b/windows/security/security-foundations/certification/validations/fips-140-other-products.md index 1d93f90168..009d8e3b18 100644 --- a/windows/security/security-foundations/certification/validations/fips-140-other-products.md +++ b/windows/security/security-foundations/certification/validations/fips-140-other-products.md @@ -3,11 +3,8 @@ title: FIPS 140 validated modules for other products description: This topic lists the completed FIPS 140 cryptographic module validations for products other than Windows and Windows Server that leverage the Windows cryptographic modules. ms.date: 2/1/2024 ms.topic: reference -ms.author: v-rodurff -author: msrobertd -ms.reviewer: paoloma -ms.collection: tier3 --- + # FIPS 140 validated modules in other products The following tables list the completed FIPS 140 validations in products other than Windows and Windows Server that leverage the Windows cryptographic modules. The linked Security Policy document for each module provides details on the module capabilities and the policies the operator must follow to use the module in its FIPS approved mode of operation. For details on the FIPS approved algorithms used by each module, including CAVP algorithm certificates, see the module's linked Security Policy document or CMVP module certificate. diff --git a/windows/security/security-foundations/certification/validations/fips-140-windows-previous.md b/windows/security/security-foundations/certification/validations/fips-140-windows-previous.md index eca7af6d57..25731d7f15 100644 --- a/windows/security/security-foundations/certification/validations/fips-140-windows-previous.md +++ b/windows/security/security-foundations/certification/validations/fips-140-windows-previous.md @@ -3,11 +3,8 @@ title: FIPS 140 validated modules for previous Windows versions description: This topic lists the completed FIPS 140 cryptographic module validations for versions of Windows prior to Windows 10. ms.date: 2/1/2024 ms.topic: reference -ms.author: v-rodurff -author: msrobertd -ms.reviewer: paoloma -ms.collection: tier3 --- + # FIPS 140 validated modules in previous Windows versions The following tables list the completed FIPS 140 validations of cryptographic modules used in versions of Windows prior to Windows 10, organized by major release of the operating system. The linked Security Policy document for each module provides details on the module capabilities and the policies the operator must follow to use the module in its FIPS approved mode of operation. For information on using the overall operating system in its FIPS approved mode, see [Use Windows in a FIPS approved mode of operation](../fips-140-validation.md#use-windows-in-a-fips-approved-mode-of-operation). For details on the FIPS approved algorithms used by each module, including CAVP algorithm certificates, see the module's linked Security Policy document or CMVP module certificate. diff --git a/windows/security/security-foundations/certification/validations/fips-140-windows-server-2016.md b/windows/security/security-foundations/certification/validations/fips-140-windows-server-2016.md index e745be28d9..7105cd5459 100644 --- a/windows/security/security-foundations/certification/validations/fips-140-windows-server-2016.md +++ b/windows/security/security-foundations/certification/validations/fips-140-windows-server-2016.md @@ -3,10 +3,6 @@ title: FIPS 140 validated modules for Windows Server 2016 description: This topic lists the completed FIPS 140 cryptographic module validations for Windows Server 2016. ms.date: 2/1/2024 ms.topic: reference -ms.author: v-rodurff -author: msrobertd -ms.reviewer: paoloma -ms.collection: tier3 --- # FIPS 140 validated modules in Windows Server 2016 diff --git a/windows/security/security-foundations/certification/validations/fips-140-windows-server-2019.md b/windows/security/security-foundations/certification/validations/fips-140-windows-server-2019.md index caebf60f2a..c5ef45bb70 100644 --- a/windows/security/security-foundations/certification/validations/fips-140-windows-server-2019.md +++ b/windows/security/security-foundations/certification/validations/fips-140-windows-server-2019.md @@ -3,11 +3,8 @@ title: FIPS 140 validated modules for Windows Server 2019 description: This topic lists the completed FIPS 140 cryptographic module validations for Windows Server 2019. ms.date: 4/5/2024 ms.topic: reference -ms.author: v-rodurff -author: msrobertd -ms.reviewer: paoloma -ms.collection: tier3 --- + # FIPS 140 validated modules in Windows Server 2019 The following tables list the completed FIPS 140 validations of cryptographic modules used in Windows Server 2019, organized by major release of the operating system. The linked Security Policy document for each module provides details on the module capabilities and the policies the operator must follow to use the module in its FIPS approved mode of operation. For information on using the overall operating system in its FIPS approved mode, see [Use Windows in a FIPS approved mode of operation](../fips-140-validation.md#use-windows-in-a-fips-approved-mode-of-operation). For details on the FIPS approved algorithms used by each module, see its linked Security Policy document or module certificate. diff --git a/windows/security/security-foundations/certification/validations/fips-140-windows-server-previous.md b/windows/security/security-foundations/certification/validations/fips-140-windows-server-previous.md index 7e5d018a04..659435689f 100644 --- a/windows/security/security-foundations/certification/validations/fips-140-windows-server-previous.md +++ b/windows/security/security-foundations/certification/validations/fips-140-windows-server-previous.md @@ -3,10 +3,6 @@ title: FIPS 140 validated modules for previous Windows Server versions description: This topic lists the completed FIPS 140 cryptographic module validations for versions of Windows Server prior to Windows Server 2016. ms.date: 2/1/2024 ms.topic: reference -ms.author: v-rodurff -author: msrobertd -ms.reviewer: paoloma -ms.collection: tier3 --- # FIPS 140 validated modules in previous Windows Server versions diff --git a/windows/security/security-foundations/certification/validations/fips-140-windows-server-semi-annual.md b/windows/security/security-foundations/certification/validations/fips-140-windows-server-semi-annual.md index 773a622fe4..d1d1724b36 100644 --- a/windows/security/security-foundations/certification/validations/fips-140-windows-server-semi-annual.md +++ b/windows/security/security-foundations/certification/validations/fips-140-windows-server-semi-annual.md @@ -3,10 +3,6 @@ title: FIPS 140 validated modules for Windows Server Semi-Annual Releases description: This topic lists the completed FIPS 140 cryptographic module validations for Windows Server semi-annual releases. ms.date: 2/1/2024 ms.topic: reference -ms.author: v-rodurff -author: msrobertd -ms.reviewer: paoloma -ms.collection: tier3 --- # FIPS 140 validated modules in Windows Server semi-annual releases diff --git a/windows/security/security-foundations/certification/validations/fips-140-windows10.md b/windows/security/security-foundations/certification/validations/fips-140-windows10.md index d2d5b384b6..e555337cb5 100644 --- a/windows/security/security-foundations/certification/validations/fips-140-windows10.md +++ b/windows/security/security-foundations/certification/validations/fips-140-windows10.md @@ -3,10 +3,6 @@ title: FIPS 140 validated modules for Windows 10 description: This topic lists the completed FIPS 140 cryptographic module validations for Windows 10. ms.date: 2/1/2024 ms.topic: reference -ms.author: v-rodurff -author: msrobertd -ms.reviewer: paoloma -ms.collection: tier3 --- # FIPS 140 validated modules for Windows 10 diff --git a/windows/security/security-foundations/certification/validations/fips-140-windows11.md b/windows/security/security-foundations/certification/validations/fips-140-windows11.md index 0eb4fa7733..bf551c22b5 100644 --- a/windows/security/security-foundations/certification/validations/fips-140-windows11.md +++ b/windows/security/security-foundations/certification/validations/fips-140-windows11.md @@ -3,10 +3,6 @@ title: FIPS 140 validated modules for Windows 11 description: This topic lists the completed FIPS 140 cryptographic module validations for Windows 11. ms.date: 2/1/2024 ms.topic: reference -ms.author: v-rodurff -author: msrobertd -ms.reviewer: paoloma -ms.collection: tier3 --- # FIPS 140 validated modules for Windows 11 diff --git a/windows/security/security-foundations/certification/windows-platform-common-criteria.md b/windows/security/security-foundations/certification/windows-platform-common-criteria.md index d012841b09..e59b0403b4 100644 --- a/windows/security/security-foundations/certification/windows-platform-common-criteria.md +++ b/windows/security/security-foundations/certification/windows-platform-common-criteria.md @@ -3,10 +3,6 @@ title: Windows Common Criteria certifications description: Learn how Microsoft products are certified under the Common Criteria for Information Technology Security Evaluation program. ms.date: 2/1/2024 ms.topic: reference -ms.author: v-rodurff -author: msrobertd -ms.reviewer: paoloma -ms.collection: tier3 --- # Common Criteria certifications From dcf2a3de64ddafc0fc4d727054f8d8c884c50432 Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Wed, 14 Aug 2024 14:47:59 -0400 Subject: [PATCH 2/7] update --- windows/security/docfx.json | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/windows/security/docfx.json b/windows/security/docfx.json index 3f047d42c7..097ae0c094 100644 --- a/windows/security/docfx.json +++ b/windows/security/docfx.json @@ -100,8 +100,8 @@ "operating-system-security/data-protection/**/*.yml": "paolomatarazzo", "operating-system-security/network-security/**/*.md": "paolomatarazzo", "operating-system-security/network-security/**/*.yml": "paolomatarazzo", - "security-foundations/certification/*.md": "paolomatarazzo", - "security-foundations/certification/*.yml": "paolomatarazzo" + "security-foundations/certification/**/*.md": "paolomatarazzo", + "security-foundations/certification/**/*.yml": "paolomatarazzo" }, "ms.author": { "application-security//**/*.md": "vinpa", @@ -122,8 +122,8 @@ "operating-system-security/data-protection/**/*.yml": "paoloma", "operating-system-security/network-security/**/*.md": "paoloma", "operating-system-security/network-security/**/*.yml": "paoloma", - "security-foundations/certification/*.md": "paoloma", - "security-foundations/certification/*.yml": "paoloma" + "security-foundations/certification/**/*.md": "paoloma", + "security-foundations/certification/**/*.yml": "paoloma" }, "appliesto": { "application-security//**/*.md": [ @@ -238,7 +238,7 @@ "operating-system-security/device-management/windows-security-configuration-framework/*.md": "jmunck", "operating-system-security/network-security/vpn/*.md": "pesmith", "operating-system-security/network-security/windows-firewall/*.md": "nganguly", - "security-foundations/certification/*.md": "paoloma" + "security-foundations/certification/**/*.md": "paoloma" }, "ms.collection": { "book/*.md": "tier3", @@ -247,7 +247,7 @@ "information-protection/tpm/*.md": "tier1", "operating-system-security/data-protection/bitlocker/*.md": "tier1", "operating-system-security/data-protection/personal-data-encryption/*.md": "tier1", - "security-foundations/certification/*.md": "tier3", + "security-foundations/certification/**/*.md": "tier3", "threat-protection/auditing/*.md": "tier3" }, "ROBOTS": { From f387ab21fc5e3f729d204c4bd177a47660991f5a Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Wed, 14 Aug 2024 15:25:03 -0400 Subject: [PATCH 3/7] author update --- windows/security/docfx.json | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/security/docfx.json b/windows/security/docfx.json index 097ae0c094..d7c7571c0e 100644 --- a/windows/security/docfx.json +++ b/windows/security/docfx.json @@ -100,8 +100,8 @@ "operating-system-security/data-protection/**/*.yml": "paolomatarazzo", "operating-system-security/network-security/**/*.md": "paolomatarazzo", "operating-system-security/network-security/**/*.yml": "paolomatarazzo", - "security-foundations/certification/**/*.md": "paolomatarazzo", - "security-foundations/certification/**/*.yml": "paolomatarazzo" + "security-foundations/certification/**/*.md": "mike-grimm", + "security-foundations/certification/**/*.yml": "mike-grimm" }, "ms.author": { "application-security//**/*.md": "vinpa", @@ -122,8 +122,8 @@ "operating-system-security/data-protection/**/*.yml": "paoloma", "operating-system-security/network-security/**/*.md": "paoloma", "operating-system-security/network-security/**/*.yml": "paoloma", - "security-foundations/certification/**/*.md": "paoloma", - "security-foundations/certification/**/*.yml": "paoloma" + "security-foundations/certification/**/*.md": "mgrimm", + "security-foundations/certification/**/*.yml": "mgrimm" }, "appliesto": { "application-security//**/*.md": [ From ff98685151b481697666dfd9b882e6031695f3a6 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Wed, 14 Aug 2024 13:18:02 -0700 Subject: [PATCH 4/7] Edit-dep-syncset --- windows/whats-new/deprecated-features.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/whats-new/deprecated-features.md b/windows/whats-new/deprecated-features.md index a23ff9f3aa..fa2925d159 100644 --- a/windows/whats-new/deprecated-features.md +++ b/windows/whats-new/deprecated-features.md @@ -105,7 +105,7 @@ The features in this article are no longer being actively developed, and might b |IIS Digest Authentication | We recommend that users use alternative authentication methods.| 1709 | |RSA/AES Encryption for IIS | We recommend that users use CNG encryption provider. | 1709 | |Screen saver functionality in Themes | Disabled in Themes. Screen saver functionality in Group Policies, Control Panel, and Sysprep continues to be functional. Lock screen features and policies are preferred. | 1709 | -|Sync your settings (updated: July, 30, 2024) | Back-end changes: In future releases, the back-end storage for the current sync process will change. A single cloud storage system will be used for Enterprise State Roaming and all other users. As part of this change, we will stop supporting the Device Syncing Settings and App Data report. All other **Sync your settings** options and the Enterprise State Roaming feature will continue to work provided your clients are running an up-to-date version of:
- Windows 11
- Windows 10, version 21H2, or later | 1709 | +|Sync your settings (updated: July, 30, 2024) | Back-end changes: In future releases, the back-end storage for the current sync process will change. A single cloud storage system will be used for Enterprise State Roaming and all other users. As part of this change, we will stop supporting the Device Syncing Settings and App Data report. All other **Sync your settings** options will continue to work provided your clients are running an up-to-date version of:
- Windows 11
- Windows 10, version 21H2, or later | 1709 | |System Image Backup (SIB) Solution|This feature is also known as the **Backup and Restore (Windows 7)** legacy control panel. For full-disk backup solutions, look for a third-party product from another software publisher. You can also use [OneDrive](/onedrive/) to sync data files with Microsoft 365.| 1709 | |TLS RC4 Ciphers |To be disabled by default. For more information, see [TLS (Schannel SSP) changes in Windows 10 and Windows Server 2016](/windows-server/security/tls/tls-schannel-ssp-changes-in-windows-10-and-windows-server)| 1709 | |Trusted Platform Module (TPM) Owner Password Management |This functionality within TPM.msc will be migrated to a new user interface.| 1709 | From 4071baaa482a3a82fa07862a6e7929dad7bdf025 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Wed, 14 Aug 2024 15:34:47 -0700 Subject: [PATCH 5/7] wu-sec-fresh-9257294 --- windows/deployment/update/windows-update-security.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/windows-update-security.md b/windows/deployment/update/windows-update-security.md index 1d7ec557b6..013dcffe27 100644 --- a/windows/deployment/update/windows-update-security.md +++ b/windows/deployment/update/windows-update-security.md @@ -10,7 +10,7 @@ ms.author: mstewart appliesto: - ✅ Windows 11 - ✅ Windows 10 -ms.date: 08/28/2023 +ms.date: 08/15/2024 --- # Windows Update security From badb401fe62f93362a48132b42d343050eb7013c Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Thu, 15 Aug 2024 11:25:42 -0700 Subject: [PATCH 6/7] Reorganizing prep --- .openpublishing.redirection.windows-deployment.json | 5 +++++ windows/deployment/windows-autopatch/TOC.yml | 5 ++--- .../windows-autopatch-groups-manage-autopatch-groups.md | 0 3 files changed, 7 insertions(+), 3 deletions(-) rename windows/deployment/windows-autopatch/{deploy => manage}/windows-autopatch-groups-manage-autopatch-groups.md (100%) diff --git a/.openpublishing.redirection.windows-deployment.json b/.openpublishing.redirection.windows-deployment.json index 76f5946caf..d8157714f0 100644 --- a/.openpublishing.redirection.windows-deployment.json +++ b/.openpublishing.redirection.windows-deployment.json @@ -1369,6 +1369,11 @@ "source_path": "windows/deployment/windows-autopatch/manage/windows-autopatch-windows-quality-update-signals.md", "redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-quality-update-overview", "redirect_document_id": true + }, + { + "source_path": "windows/deployment/windows-autopatch/deploy/windows-autopatch-manage-autopatch-groups.md", + "redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-manage-autopatch-groups", + "redirect_document_id": true } ] } diff --git a/windows/deployment/windows-autopatch/TOC.yml b/windows/deployment/windows-autopatch/TOC.yml index f4de9aac02..bc3107c229 100644 --- a/windows/deployment/windows-autopatch/TOC.yml +++ b/windows/deployment/windows-autopatch/TOC.yml @@ -42,14 +42,13 @@ href: deploy/windows-autopatch-register-devices.md - name: Windows Autopatch groups overview href: deploy/windows-autopatch-groups-overview.md - items: - - name: Manage Windows Autopatch groups - href: deploy/windows-autopatch-groups-manage-autopatch-groups.md - name: Post-device registration readiness checks href: deploy/windows-autopatch-post-reg-readiness-checks.md - name: Manage href: items: + - name: Manage Windows Autopatch groups + href: manage/windows-autopatch-groups-manage-autopatch-groups.md - name: Customize Windows Update settings href: manage/windows-autopatch-customize-windows-update-settings.md - name: Windows feature updates diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-manage-autopatch-groups.md b/windows/deployment/windows-autopatch/manage/windows-autopatch-groups-manage-autopatch-groups.md similarity index 100% rename from windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-manage-autopatch-groups.md rename to windows/deployment/windows-autopatch/manage/windows-autopatch-groups-manage-autopatch-groups.md From c40112ae7c29fcde9c2ee1e0338d53dffb8bb501 Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Thu, 15 Aug 2024 11:39:52 -0700 Subject: [PATCH 7/7] fixed broken links --- .openpublishing.redirection.windows-deployment.json | 2 +- windows/deployment/windows-autopatch/TOC.yml | 2 +- .../windows-autopatch-device-registration-overview.md | 2 +- .../deploy/windows-autopatch-groups-overview.md | 2 +- .../deploy/windows-autopatch-register-devices.md | 2 +- ...oups.md => windows-autopatch-manage-autopatch-groups.md} | 2 +- .../windows-autopatch-windows-feature-update-overview.md | 6 +++--- .../windows-autopatch/overview/windows-autopatch-faq.yml | 2 +- .../overview/windows-autopatch-overview.md | 2 +- .../overview/windows-autopatch-roles-responsibilities.md | 6 +++--- .../whats-new/windows-autopatch-whats-new-2023.md | 2 +- 11 files changed, 15 insertions(+), 15 deletions(-) rename windows/deployment/windows-autopatch/manage/{windows-autopatch-groups-manage-autopatch-groups.md => windows-autopatch-manage-autopatch-groups.md} (98%) diff --git a/.openpublishing.redirection.windows-deployment.json b/.openpublishing.redirection.windows-deployment.json index d8157714f0..51aa5dc28d 100644 --- a/.openpublishing.redirection.windows-deployment.json +++ b/.openpublishing.redirection.windows-deployment.json @@ -1371,7 +1371,7 @@ "redirect_document_id": true }, { - "source_path": "windows/deployment/windows-autopatch/deploy/windows-autopatch-manage-autopatch-groups.md", + "source_path": "windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-manage-autopatch-groups.md", "redirect_url": "/windows/deployment/windows-autopatch/manage/windows-autopatch-manage-autopatch-groups", "redirect_document_id": true } diff --git a/windows/deployment/windows-autopatch/TOC.yml b/windows/deployment/windows-autopatch/TOC.yml index bc3107c229..a678f8d182 100644 --- a/windows/deployment/windows-autopatch/TOC.yml +++ b/windows/deployment/windows-autopatch/TOC.yml @@ -48,7 +48,7 @@ href: items: - name: Manage Windows Autopatch groups - href: manage/windows-autopatch-groups-manage-autopatch-groups.md + href: manage/windows-autopatch-manage-autopatch-groups.md - name: Customize Windows Update settings href: manage/windows-autopatch-customize-windows-update-settings.md - name: Windows feature updates diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-device-registration-overview.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-device-registration-overview.md index 3b2702240b..705c158639 100644 --- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-device-registration-overview.md +++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-device-registration-overview.md @@ -46,7 +46,7 @@ See the following detailed workflow diagram. The diagram covers the Windows Auto | Step | Description | | ----- | ----- | | **Step 1: Identify devices** | IT admin identifies devices to be managed by the Windows Autopatch service. | -| **Step 2: Add devices** | IT admin adds devices through Direct membership or nests other Microsoft Entra ID assigned or dynamic groups into the **Windows Autopatch Device Registration** Microsoft Entra ID assigned group when using adding existing device-based Microsoft Entra groups while [creating](../deploy/windows-autopatch-groups-manage-autopatch-groups.md#create-a-custom-autopatch-group)/[editing](../deploy/windows-autopatch-groups-manage-autopatch-groups.md#edit-the-default-or-a-custom-autopatch-group) Custom Autopatch groups, or [editing](../deploy/windows-autopatch-groups-manage-autopatch-groups.md#edit-the-default-or-a-custom-autopatch-group) the Default Autopatch group | +| **Step 2: Add devices** | IT admin adds devices through Direct membership or nests other Microsoft Entra ID assigned or dynamic groups into the **Windows Autopatch Device Registration** Microsoft Entra ID assigned group when using adding existing device-based Microsoft Entra groups while [creating](../manage/windows-autopatch-manage-autopatch-groups.md#create-a-custom-autopatch-group)/[editing](../manage/windows-autopatch-manage-autopatch-groups.md#edit-the-default-or-a-custom-autopatch-group) Custom Autopatch groups, or [editing](../manage/windows-autopatch-manage-autopatch-groups.md#edit-the-default-or-a-custom-autopatch-group) the Default Autopatch group | | **Step 3: Discover devices** | The Windows Autopatch Discover Devices function discovers devices (hourly) that were previously added by the IT admin into the **Windows Autopatch Device Registration** Microsoft Entra ID assigned group or from Microsoft Entra groups used with Autopatch groups in **step #2**. The Microsoft Entra device ID is used by Windows Autopatch to query device attributes in both Microsoft Intune and Microsoft Entra ID when registering devices into its service.
  1. Once devices are discovered from the Microsoft Entra group, the same function gathers additional device attributes and saves it into its memory during the discovery operation. The following device attributes are gathered from Microsoft Entra ID in this step:
    1. **AzureADDeviceID**
    2. **OperatingSystem**
    3. **DisplayName (Device name)**
    4. **AccountEnabled**
    5. **RegistrationDateTime**
    6. **ApproximateLastSignInDateTime**
  2. In this same step, the Windows Autopatch discover devices function calls another function, the device prerequisite check function. The device prerequisite check function evaluates software-based device-level prerequisites to comply with Windows Autopatch device readiness requirements before registration.
| | **Step 4: Check prerequisites** | The Windows Autopatch prerequisite function makes an Intune Graph API call to sequentially validate device readiness attributes required for the registration process. For detailed information, see the [Detailed prerequisite check workflow diagram](#detailed-prerequisite-check-workflow-diagram) section. The service checks the following device readiness attributes, and/or prerequisites:
  1. **If the device is Intune-managed or not.**
    1. Windows Autopatch looks to see **if the Microsoft Entra device ID has an Intune device ID associated with it**.
      1. If **yes**, it means this device is enrolled into Intune.
      2. If **not**, it means the device isn't enrolled into Intune, hence it can't be managed by the Windows Autopatch service.
    2. **If the device is not managed by Intune**, the Windows Autopatch service can't gather device attributes such as operating system version, Intune enrollment date, device name and other attributes. When this happens, the Windows Autopatch service uses the Microsoft Entra device attributes gathered and saved to its memory in **step 3a**.
      1. Once it has the device attributes gathered from Microsoft Entra ID in **step 3a**, the device is flagged with the **Prerequisite failed** status, then added to the **Not registered** tab so the IT admin can review the reason(s) the device wasn't registered into Windows Autopatch. The IT admin will remediate these devices. In this case, the IT admin should check why the device wasn't enrolled into Intune.
      2. A common reason is when the Microsoft Entra device ID is stale, it doesn't have an Intune device ID associated with it anymore. To remediate, [clean up any stale Microsoft Entra device records from your tenant](windows-autopatch-register-devices.md#clean-up-dual-state-of-hybrid-azure-ad-joined-and-azure-registered-devices-in-your-azure-ad-tenant).
    3. **If the device is managed by Intune**, the Windows Autopatch prerequisite check function continues to the next prerequisite check, which evaluates whether the device has checked into Intune in the last 28 days.
  2. **If the device is a Windows device or not.**
    1. Windows Autopatch looks to see if the device is a Windows and corporate-owned device.
      1. **If yes**, it means this device can be registered with the service because it's a Windows corporate-owned device.
      2. **If not**, it means the device is a non-Windows device, or it's a Windows device but it's a personal device.
  3. **Windows Autopatch checks the Windows SKU family**. The SKU must be either:
    1. **Enterprise**
    2. **Pro**
    3. **Pro Workstation**
  4. **If the device meets the operating system requirements**, Windows Autopatch checks whether the device is either:
    1. **Only managed by Intune.**
      1. If the device is only managed by Intune, the device is marked as Passed all prerequisites.
    2. **Co-managed by both Configuration Manager and Intune.**
      1. If the device is co-managed by both Configuration Manager and Intune, an additional prerequisite check is evaluated to determine if the device satisfies the co-management-enabled workloads required by Windows Autopatch to manage devices in a co-managed state. The required co-management workloads evaluated in this step are:
        1. **Windows Updates Policies**
        2. **Device Configuration**
        3. **Office Click to Run**
      2. If Windows Autopatch determines that one of these workloads isn't enabled on the device, the service marks the device as **Prerequisite failed** and moves the device to the **Not registered** tab.
| | **Step 5: Calculate deployment ring assignment** | Once the device passes all prerequisites described in **step #4**, Windows Autopatch starts its deployment ring assignment calculation. The following logic is used to calculate the Windows Autopatch deployment ring assignment:
  1. If the Windows Autopatch tenant's existing managed device size is **≤ 200**, the deployment ring assignment is **First (5%)**, **Fast (15%)**, remaining devices go to the **Broad ring (80%)**.
  2. If the Windows Autopatch tenant's existing managed device size is **>200**, the deployment ring assignment will be **First (1%)**, **Fast (9%)**, remaining devices go to the **Broad ring (90%)**.
| diff --git a/windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-overview.md b/windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-overview.md index acdf9129ce..1ab150d7a1 100644 --- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-overview.md +++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-groups-overview.md @@ -190,7 +190,7 @@ The following are the Microsoft Entra ID assigned groups that represent the soft ### About device registration -Autopatch groups register devices with the Windows Autopatch service when you either [create](../deploy/windows-autopatch-groups-manage-autopatch-groups.md#create-a-custom-autopatch-group) or [edit a Custom Autopatch group](../deploy/windows-autopatch-groups-manage-autopatch-groups.md#edit-the-default-or-a-custom-autopatch-group), and/or when you [edit the Default Autopatch group](../deploy/windows-autopatch-groups-manage-autopatch-groups.md#edit-the-default-or-a-custom-autopatch-group) to use your existing Microsoft Entra groups instead of the Windows Autopatch Device Registration group provided by the service. +Autopatch groups register devices with the Windows Autopatch service when you either [create](../manage/windows-autopatch-manage-autopatch-groups.md#create-a-custom-autopatch-group) or [edit a Custom Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md#edit-the-default-or-a-custom-autopatch-group), and/or when you [edit the Default Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md#edit-the-default-or-a-custom-autopatch-group) to use your existing Microsoft Entra groups instead of the Windows Autopatch Device Registration group provided by the service. ## Common ways to use Autopatch groups 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 5836f3979a..d3e5f4afa6 100644 --- a/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md +++ b/windows/deployment/windows-autopatch/deploy/windows-autopatch-register-devices.md @@ -35,7 +35,7 @@ When you either create/edit a [Custom Autopatch group](../deploy/windows-autopat If devices aren't registered, Autopatch groups starts the device registration process by using your existing device-based Microsoft Entra groups instead of the Windows Autopatch Device Registration group. -For more information, see [create Custom Autopatch groups](../deploy/windows-autopatch-groups-manage-autopatch-groups.md#create-a-custom-autopatch-group) and [edit Autopatch group](../deploy/windows-autopatch-groups-manage-autopatch-groups.md#edit-the-default-or-a-custom-autopatch-group) to register devices using the Autopatch groups device registration method. +For more information, see [create Custom Autopatch groups](../manage/windows-autopatch-manage-autopatch-groups.md#create-a-custom-autopatch-group) and [edit Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md#edit-the-default-or-a-custom-autopatch-group) to register devices using the Autopatch groups device registration method. diff --git a/windows/deployment/windows-autopatch/manage/windows-autopatch-groups-manage-autopatch-groups.md b/windows/deployment/windows-autopatch/manage/windows-autopatch-manage-autopatch-groups.md similarity index 98% rename from windows/deployment/windows-autopatch/manage/windows-autopatch-groups-manage-autopatch-groups.md rename to windows/deployment/windows-autopatch/manage/windows-autopatch-manage-autopatch-groups.md index cd9cd8132d..30d237f9ca 100644 --- a/windows/deployment/windows-autopatch/manage/windows-autopatch-groups-manage-autopatch-groups.md +++ b/windows/deployment/windows-autopatch/manage/windows-autopatch-manage-autopatch-groups.md @@ -180,4 +180,4 @@ When you create or edit the Custom or Default Autopatch group, Windows Autopatch #### Device conflict post device registration -Autopatch groups will keep monitoring for all device conflict scenarios listed in the [Manage device conflict scenarios when using Autopatch groups](../deploy/windows-autopatch-groups-manage-autopatch-groups.md#manage-device-conflict-scenarios-when-using-autopatch-groups) section even after devices were successfully registered with the service. +Autopatch groups will keep monitoring for all device conflict scenarios listed in the [Manage device conflict scenarios when using Autopatch groups](../manage/windows-autopatch-manage-autopatch-groups.md#manage-device-conflict-scenarios-when-using-autopatch-groups) section even after devices were successfully registered with the service. diff --git a/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-feature-update-overview.md b/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-feature-update-overview.md index 24c4fc7e02..3f370a7509 100644 --- a/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-feature-update-overview.md +++ b/windows/deployment/windows-autopatch/manage/windows-autopatch-windows-feature-update-overview.md @@ -98,8 +98,8 @@ There are two scenarios that the Global release is used: | Scenario | Description | | ----- | ----- | -| Scenario #1 | You assign Microsoft Entra groups to be used with the deployment ring (Last) or you add additional deployment rings when you customize the [Default Autopatch group](../deploy/windows-autopatch-groups-manage-autopatch-groups.md#edit-the-default-or-a-custom-autopatch-group).

A global Windows feature update policy is automatically assigned behind the scenes to the newly added deployment rings or when you assigned Microsoft Entra groups to the deployment ring (Last) in the Default Autopatch group.

| -| Scenario #2 | You create new [Custom Autopatch groups](../deploy/windows-autopatch-groups-manage-autopatch-groups.md#create-a-custom-autopatch-group).

The global Windows feature policy is automatically assigned behind the scenes to all deployment rings as part of the Custom Autopatch groups you create.

| +| Scenario #1 | You assign Microsoft Entra groups to be used with the deployment ring (Last) or you add additional deployment rings when you customize the [Default Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md#edit-the-default-or-a-custom-autopatch-group).

A global Windows feature update policy is automatically assigned behind the scenes to the newly added deployment rings or when you assigned Microsoft Entra groups to the deployment ring (Last) in the Default Autopatch group.

| +| Scenario #2 | You create new [Custom Autopatch groups](../manage/windows-autopatch-manage-autopatch-groups.md#create-a-custom-autopatch-group).

The global Windows feature policy is automatically assigned behind the scenes to all deployment rings as part of the Custom Autopatch groups you create.

| > [!NOTE] > Global releases don't show up in the Windows feature updates release management blade. @@ -124,7 +124,7 @@ The differences in between the global and the default Windows feature update pol | Default Windows feature update policy | Global Windows feature update policy | | ----- | ----- | -| | +| | | ### Custom release diff --git a/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml b/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml index 2aea84859d..205e52e37a 100644 --- a/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml +++ b/windows/deployment/windows-autopatch/overview/windows-autopatch-faq.yml @@ -79,7 +79,7 @@ sections: No. Don't change, edit, add to, or remove any of the configurations. Doing so might cause unintended configuration conflicts and impact the Windows Autopatch service. For more information about policies and configurations, see [Changes made at tenant enrollment](/windows/deployment/windows-autopatch/references/windows-autopatch-changes-to-tenant). - question: How can I represent our organizational structure with our own deployment cadence? answer: | - [Windows Autopatch groups](../deploy/windows-autopatch-groups-overview.md) helps you manage updates in a way that makes sense for your businesses. For more information, see [Windows Autopatch groups overview](../deploy/windows-autopatch-groups-overview.md) and [Manage Windows Autopatch groups](../deploy/windows-autopatch-groups-manage-autopatch-groups.md). + [Windows Autopatch groups](../deploy/windows-autopatch-groups-overview.md) helps you manage updates in a way that makes sense for your businesses. For more information, see [Windows Autopatch groups overview](../deploy/windows-autopatch-groups-overview.md) and [Manage Windows Autopatch groups](../manage/windows-autopatch-manage-autopatch-groups.md). - name: Update management questions: - question: What systems does Windows Autopatch update? diff --git a/windows/deployment/windows-autopatch/overview/windows-autopatch-overview.md b/windows/deployment/windows-autopatch/overview/windows-autopatch-overview.md index f8f71f9db2..dc12d303ad 100644 --- a/windows/deployment/windows-autopatch/overview/windows-autopatch-overview.md +++ b/windows/deployment/windows-autopatch/overview/windows-autopatch-overview.md @@ -63,7 +63,7 @@ Microsoft remains committed to the security of your data and the [accessibility] | Area | Description | | ----- | ----- | | Prepare | The following articles describe the mandatory steps to prepare and enroll your tenant into Windows Autopatch: | -| Deploy | Once you've enrolled your tenant, this section instructs you to: | +| Deploy | Once you've enrolled your tenant, this section instructs you to: | | Operate | This section includes the following information about your day-to-day life with the service: | References | This section includes the following articles: | 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 215fef87ca..68e12d9680 100644 --- a/windows/deployment/windows-autopatch/overview/windows-autopatch-roles-responsibilities.md +++ b/windows/deployment/windows-autopatch/overview/windows-autopatch-roles-responsibilities.md @@ -58,7 +58,7 @@ For more information and assistance with preparing for your Windows Autopatch de | Remediate registration issues | :heavy_check_mark: | :x: | | Populate the Test and Last deployment ring membership | :heavy_check_mark: | :x: | | [Manually override device assignments to deployment rings](../operate/windows-autopatch-update-management.md#moving-devices-in-between-deployment-rings) | :heavy_check_mark: | :x: | -| Review device conflict scenarios | :heavy_check_mark: | :x: | +| Review device conflict scenarios | :heavy_check_mark: | :x: | | Communicate to end-users, help desk and stakeholders | :heavy_check_mark: | :x: | ## Manage @@ -68,8 +68,8 @@ For more information and assistance with preparing for your Windows Autopatch de | [Maintain contacts in the Microsoft Intune admin center](../deploy/windows-autopatch-admin-contacts.md) | :heavy_check_mark: | :x: | | [Maintain and manage the Windows Autopatch service configuration](../monitor/windows-autopatch-maintain-environment.md) | :x: | :heavy_check_mark: | | [Maintain customer configuration to align with the Windows Autopatch service configuration](../monitor/windows-autopatch-maintain-environment.md) | :heavy_check_mark: | :x: | -| Resolve service remediated device conflict scenarios | :x: | :heavy_check_mark: | -| Resolve remediated device conflict scenarios | :heavy_check_mark: | :x: | +| Resolve service remediated device conflict scenarios | :x: | :heavy_check_mark: | +| Resolve remediated device conflict scenarios | :heavy_check_mark: | :x: | | Maintain the Test and Last deployment ring membership | :heavy_check_mark: | :x: | | Monitor [Windows update signals](../manage/windows-autopatch-windows-quality-update-signals.md) for safe update release | :x: | :heavy_check_mark: | | Test specific [business update scenarios](../manage/windows-autopatch-windows-quality-update-signals.md) | :heavy_check_mark: | :x: | 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 3774758175..a3fda24453 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 @@ -100,7 +100,7 @@ Minor corrections such as typos, style, or formatting issues aren't listed. | ----- | ----- | | [Roles and responsibilities](../overview/windows-autopatch-roles-responsibilities.md) | Updated article to include Windows Autopatch groups | | [Windows Autopatch groups overview](../deploy/windows-autopatch-groups-overview.md) | General Availability | -| [Manage Windows Autopatch groups](../deploy/windows-autopatch-groups-manage-autopatch-groups.md) | General Availability | +| [Manage Windows Autopatch groups](../manage/windows-autopatch-manage-autopatch-groups.md) | General Availability | | [Customize Windows Update settings](../operate/windows-autopatch-groups-windows-update.md) | General Availability | | [Windows quality updates](../operate/windows-autopatch-groups-windows-quality-update-overview.md) | General Availability | | [Windows feature updates](../operate/windows-autopatch-groups-windows-feature-update-overview.md) | General Availability |