From aff975f29c48ac3d2d681d1258c176fcc8f235a8 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Wed, 3 Apr 2024 11:37:43 -0700 Subject: [PATCH 1/6] winreleasehealth-8884260 --- windows/deployment/update/check-release-health.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/windows/deployment/update/check-release-health.md b/windows/deployment/update/check-release-health.md index 164a2970b3..435d21c5be 100644 --- a/windows/deployment/update/check-release-health.md +++ b/windows/deployment/update/check-release-health.md @@ -13,7 +13,7 @@ ms.localizationpriority: medium appliesto: - ✅ Windows 11 - ✅ Windows 10 -ms.date: 09/08/2023 +ms.date: 04/04/2024 --- # How to check Windows release health @@ -85,6 +85,18 @@ You can sign up for email notifications about Windows known issues and informati > [!Note] > When a single known issue affects multiple versions of Windows, you'll receive only one email notification, even if you've selected notifications for multiple versions. Duplicate emails won't be sent. +## Working with the Windows updates API in Microsoft Graph + +If you'd like to develop an alternative way to get information on known issues documented within the Windows release health section in the admin center, you can use the Windows updates API in Microsoft Graph. + +The Windows updates API has current and historical known issues data for any supported Windows product. You can check if an issue is confirmed, and if a resolution is available before calling support or spending time troubleshooting. + +The Windows updates API also has product lifecycle information. For instance, you can search for end of servicing dates for all supported Windows versions and editions you manage in your organization. For more information on how to access these known issue and lifecycle data, see [Microsoft Graph product resource type](/graph/api/resources/windowsupdates-product). + +> [!Note] +> These Windows data sets are currently under the [Microsoft Graph REST API beta endpoint reference](/graph/api/overview?view=graph-rest-beta&preserve-view=true). + + ## Status definitions In the **Windows release health** experience, every known issue is assigned as status. Those statuses are defined as follows: From 10c46fab0b2eb0c82046a06ea74fcc499898835e Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Wed, 3 Apr 2024 11:46:04 -0700 Subject: [PATCH 2/6] winreleasehealth-8884260 --- windows/deployment/update/check-release-health.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/update/check-release-health.md b/windows/deployment/update/check-release-health.md index 435d21c5be..0dcd458dd0 100644 --- a/windows/deployment/update/check-release-health.md +++ b/windows/deployment/update/check-release-health.md @@ -87,9 +87,9 @@ You can sign up for email notifications about Windows known issues and informati ## Working with the Windows updates API in Microsoft Graph -If you'd like to develop an alternative way to get information on known issues documented within the Windows release health section in the admin center, you can use the Windows updates API in Microsoft Graph. +If you'd like to develop an alternative way to get information on known issues documented within the Windows release health section in the admin center, you can use the [Windows updates API in Microsoft Graph](/graph/windowsupdates-concept-overview). -The Windows updates API has current and historical known issues data for any supported Windows product. You can check if an issue is confirmed, and if a resolution is available before calling support or spending time troubleshooting. +The [Windows updates API has current and historical known issues data for any supported Windows product. You can check if an issue is confirmed, and if a resolution is available before calling support or spending time troubleshooting. The Windows updates API also has product lifecycle information. For instance, you can search for end of servicing dates for all supported Windows versions and editions you manage in your organization. For more information on how to access these known issue and lifecycle data, see [Microsoft Graph product resource type](/graph/api/resources/windowsupdates-product). From 0b536ceafb44bae97f2ae64f94dc19e6a72ce4f8 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Wed, 3 Apr 2024 11:58:24 -0700 Subject: [PATCH 3/6] winreleasehealth-8884260 --- windows/deployment/update/check-release-health.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/check-release-health.md b/windows/deployment/update/check-release-health.md index 0dcd458dd0..14ce77948a 100644 --- a/windows/deployment/update/check-release-health.md +++ b/windows/deployment/update/check-release-health.md @@ -89,7 +89,7 @@ You can sign up for email notifications about Windows known issues and informati If you'd like to develop an alternative way to get information on known issues documented within the Windows release health section in the admin center, you can use the [Windows updates API in Microsoft Graph](/graph/windowsupdates-concept-overview). -The [Windows updates API has current and historical known issues data for any supported Windows product. You can check if an issue is confirmed, and if a resolution is available before calling support or spending time troubleshooting. +The Windows updates API has current and historical known issues data for any supported Windows product. You can check if an issue is confirmed, and if a resolution is available before calling support or spending time troubleshooting. The Windows updates API also has product lifecycle information. For instance, you can search for end of servicing dates for all supported Windows versions and editions you manage in your organization. For more information on how to access these known issue and lifecycle data, see [Microsoft Graph product resource type](/graph/api/resources/windowsupdates-product). From fe2be7c6f8d50e8f825e2dbb7dda16865599a310 Mon Sep 17 00:00:00 2001 From: Phil Urban <29461692+PhillyUrbs@users.noreply.github.com> Date: Thu, 4 Apr 2024 11:44:53 -0400 Subject: [PATCH 4/6] Corrected Windows 1 to Windows 11 --- .../start/supported-csp-start-menu-layout-windows.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/configuration/start/supported-csp-start-menu-layout-windows.md b/windows/configuration/start/supported-csp-start-menu-layout-windows.md index 995c92acfa..a42bb23a00 100644 --- a/windows/configuration/start/supported-csp-start-menu-layout-windows.md +++ b/windows/configuration/start/supported-csp-start-menu-layout-windows.md @@ -39,7 +39,7 @@ For information on customizing the Start menu layout using policy, see [Customiz - [Start/HideUserTile](/windows/client-management/mdm/policy-csp-start#start-hideusertile) - [Start/HideRecentJumplists](/windows/client-management/mdm/policy-csp-start#start-hiderecentjumplists) - [Start/NoPinningToTaskbar](/windows/client-management/mdm/policy-csp-start#start-nopinningtotaskbar) -- **Start/ShowOrHideMostUsedApps**: New policy starting with Windows 1. This policy enforces always showing Most Used Apps, or always hiding Most Used Apps in the Start menu. If you use this policy, the [Start/HideFrequentlyUsedApps](/windows/client-management/mdm/policy-csp-start#start-hidefrequentlyusedapps) policy is ignored. +- **Start/ShowOrHideMostUsedApps**: New policy starting with Windows 11. This policy enforces always showing Most Used Apps, or always hiding Most Used Apps in the Start menu. If you use this policy, the [Start/HideFrequentlyUsedApps](/windows/client-management/mdm/policy-csp-start#start-hidefrequentlyusedapps) policy is ignored. The [Start/HideFrequentlyUsedApps](/windows/client-management/mdm/policy-csp-start#start-hidefrequentlyusedapps) policy enforces hiding Most Used Apps on the Start menu. You can't use this policy to enforce always showing Most Used Apps on the Start menu. From 90af5038e4848d25f1677593156ea0352e60fb51 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 4 Apr 2024 09:43:07 -0700 Subject: [PATCH 5/6] winreleasehealth-8884260 --- windows/deployment/update/check-release-health.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/update/check-release-health.md b/windows/deployment/update/check-release-health.md index 14ce77948a..fb83ad99f7 100644 --- a/windows/deployment/update/check-release-health.md +++ b/windows/deployment/update/check-release-health.md @@ -87,7 +87,7 @@ You can sign up for email notifications about Windows known issues and informati ## Working with the Windows updates API in Microsoft Graph -If you'd like to develop an alternative way to get information on known issues documented within the Windows release health section in the admin center, you can use the [Windows updates API in Microsoft Graph](/graph/windowsupdates-concept-overview). +If you'd like to develop an alternative way to get information on known issues documented within the Windows release health section in the admin center, you can use the Windows updates API in [Microsoft Graph](/graph/api/overview). The Windows updates API has current and historical known issues data for any supported Windows product. You can check if an issue is confirmed, and if a resolution is available before calling support or spending time troubleshooting. From 343fc06d43a599b00babf6510366d3a022b62d18 Mon Sep 17 00:00:00 2001 From: MSRobertD <43757104+MSRobertD@users.noreply.github.com> Date: Thu, 4 Apr 2024 10:16:08 -0700 Subject: [PATCH 6/6] Merge branch 'main' of https://github.com/MicrosoftDocs/windows-docs-pr into AzureStackPortal-January2024 --- .../fips-140-windows-server-2019.md | 31 ++++++++++++++++++- 1 file changed, 30 insertions(+), 1 deletion(-) 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 bff75555af..9d713369eb 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 @@ -1,7 +1,7 @@ --- 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: 2/1/2024 +ms.date: 4/4/2024 ms.topic: reference ms.author: v-rodurff author: msrobertd @@ -27,6 +27,19 @@ Build: 10.0.17763.107. Validated Editions: Standard Core, Datacenter Core |[Virtual TPM][sp-3690]|10.0.17763|[#3690][certificate-3690]|FIPS Approved: AES, CKG, CVL, DRBG, ECDSA, HMAC, KAS, KBKDF, KTS, RSA, and SHS; Other Allowed: NDRNG| |[Windows OS Loader][sp-3615]|10.0.17763|[#3615][certificate-3615]|FIPS Approved: AES, CKG, DRBG, RSA, and SHS; Other Allowed: NDRNG| +Builds: 10.0.17763.10021 and 10.0.17763.10127. Validated Edition: Datacenter Core + +|Cryptographic Module (linked to Security Policy document)|CMVP Certificate #|Validated Algorithms| +|--- |--- |--- | +|[BitLocker Dump Filter][sp-4688]|[#4688][certificate-4688]|FIPS Approved: AES, RSA, and SHS| +|[Boot Manager][sp-4484]|[#4484][certificate-4484]|FIPS Approved: AES, CKG, HMAC, PBKDF, RSA, and SHS| +|[Code Integrity][sp-4602]|[#4602][certificate-4602]|FIPS Approved: RSA and SHS| +|[Cryptographic Primitives Library][sp-4687]|[#4687][certificate-4687]|FIPS Approved: AES, CKG, CVL, DRBG, DSA, ECDSA, HMAC, KAS, KBKDF, KTS, PBKDF, RSA, SHS, and Triple-DES; Other Allowed: ECDH and NDRNG| +|[Kernel Mode Cryptographic Primitives Library][sp-4670]|[#4670][certificate-4670]|AES, CKG, CVL, DRBG, DSA, ECDSA, HMAC, KAS, KBKDF, KTS, PBKDF, RSA, SHS, and Triple-DES; Other Allowed: ECDH| +|[Secure Kernel Code Integrity][sp-4640]|[#4640][certificate-4640]|FIPS Approved: RSA and SHS| +|[Virtual TPM][sp-4686]|[#4686][certificate-4686]|FIPS Approved: AES, CKG, CVL, DRBG, ECDSA, HMAC, KAS, KBKDF, KTS, RSA, and SHS; Other Allowed: NDRNG| +|[Windows OS Loader][sp-4545]|[#4545][certificate-4545]|FIPS Approved: AES, RSA, and SHS; Other Allowed: NDRNG| + --- @@ -41,6 +54,14 @@ Build: 10.0.17763.107. Validated Editions: Standard Core, Datacenter Core [certificate-3644]: https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/3644 [certificate-3651]: https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/3651 [certificate-3690]: https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/3690 +[certificate-4484]: https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4484 +[certificate-4545]: https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4545 +[certificate-4602]: https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4602 +[certificate-4640]: https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4640 +[certificate-4670]: https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4670 +[certificate-4686]: https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4686 +[certificate-4687]: https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4687 +[certificate-4688]: https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4688 @@ -52,3 +73,11 @@ Build: 10.0.17763.107. Validated Editions: Standard Core, Datacenter Core [sp-3644]: https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp3644.pdf [sp-3651]: https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp3651.pdf [sp-3690]: https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp3690.pdf +[sp-4484]: https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp4484.pdf +[sp-4545]: https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp4545.pdf +[sp-4602]: https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp4602.pdf +[sp-4640]: https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp4640.pdf +[sp-4670]: https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp4670.pdf +[sp-4686]: https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp4686.pdf +[sp-4687]: https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp4687.pdf +[sp-4688]: https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp4688.pdf \ No newline at end of file