Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into diskBilling

Author: roygara

articles/backup/backup-azure-mysql-flexible-server-about.md

@@ -2,7 +2,7 @@
 title: Overview - retention of Azure Database for MySQL - Flexible Server for long term by using Azure Backup
 description: This article provides an overview of Azure Database for MySQL - Flexible Server retention for long term.
 ms.topic: overview
-ms.date: 02/16/2024
+ms.date: 03/08/2024
 ms.service: backup
 ms.custom: engagement-fy23
 author: AbhishekMallick-MS

articles/backup/backup-azure-mysql-flexible-server-restore.md

@@ -2,7 +2,7 @@
 title: Restore the Azure Database for MySQL - Flexible Server by using Azure Backup
 description: Learn how to restore the Azure Database for MySQL - Flexible Server.
 ms.topic: how-to
-ms.date: 02/16/2024
+ms.date: 03/08/2024
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ---

articles/backup/backup-azure-mysql-flexible-server-support-matrix.md

@@ -2,7 +2,7 @@
 title: Support matrix for Azure Database for MySQL - Flexible Server retention for long term by using Azure Backup
 description: Provides a summary of support settings and limitations when backing up Azure Database for MySQL - Flexible Server.
 ms.topic: conceptual
-ms.date: 02/16/2024
+ms.date: 03/08/2024
 ms.custom: references_regions
 ms.service: backup
 author: AbhishekMallick-MS

articles/backup/backup-azure-mysql-flexible-server.md

@@ -2,7 +2,7 @@
 title: Back up the Azure Database for MySQL - Flexible Server by using Azure Backup
 description: Learn how to back up the Azure Database for MySQL - Flexible Server.
 ms.topic: how-to
-ms.date: 02/16/2024
+ms.date: 03/08/2024
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ---

articles/backup/index.yml

@@ -12,7 +12,7 @@ metadata:
   ms.topic: landing-page
   author: AbhishekMallick-MS
   ms.author: v-abhmallick 
-  ms.date: 02/16/2024
+  ms.date: 03/08/2024
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 

articles/backup/whats-new.md

@@ -2,7 +2,7 @@
 title: What's new in Azure Backup
 description: Learn about the new features in the Azure Backup service.
 ms.topic: conceptual
-ms.date: 02/16/2024
+ms.date: 03/08/2024
 ms.service: backup
 ms.custom:
   - ignite-2023
@@ -19,7 +19,7 @@ You can learn more about the new releases by bookmarking this page or by [subscr
 ## Updates summary
 
 
-- February 2024
+- March 2024
   - [Support for long-term Retention for Azure Database for MySQL - Flexible Server (preview)](#support-for-long-term-retention-for-azure-database-for-mysql---flexible-server-preview)
 - January 2024
   - [Cross Region Restore support for PostgreSQL by using Azure Backup is now generally available](#cross-region-restore-support-for-postgresql-by-using-azure-backup-is-now-generally-available)

articles/key-vault/general/overview.md

@@ -41,7 +41,7 @@ Access to a key vault requires proper authentication and authorization before a
 
 Authentication is done via Microsoft Entra ID. Authorization may be done via Azure role-based access control (Azure RBAC) or Key Vault access policy. Azure RBAC can be used for both management of the vaults and to access data stored in a vault, while key vault access policy can only be used when attempting to access data stored in a vault.
 
-Azure Key Vaults may be either software-protected or, with the Azure Key Vault Premium tier, hardware-protected by hardware security modules (HSMs). Software-protected keys, secrets, and certificates are safeguarded by Azure, using industry-standard algorithms and key lengths.  For situations where you require added assurance, you can import or generate keys in HSMs that never leave the HSM boundary. Azure Key Vault uses nCipher HSMs, which are [Federal Information Processing Standards 140 validated](/azure/key-vault/keys/about-keys#compliance). You can use HSM vendor provided tools to move a key from your HSM to Azure Key Vault.
+Azure Key Vaults may be either software-protected or, with the Azure Key Vault Premium tier, hardware-protected by hardware security modules (HSMs). Software-protected keys, secrets, and certificates are safeguarded by Azure, using industry-standard algorithms and key lengths.  For situations where you require added assurance, you can import or generate keys in HSMs that never leave the HSM boundary. Azure Key Vault uses [Federal Information Processing Standard 140 validated HSMs](/azure/key-vault/keys/about-keys#compliance). You can use HSM vendor provided tools to move a key from your HSM to Azure Key Vault.
 
 Finally, Azure Key Vault is designed so that Microsoft doesn't see or extract your data.
 

articles/key-vault/keys/about-keys-details.md

@@ -109,8 +109,8 @@ For more information on JWK objects, see [JSON Web Key (JWK)](https://tools.ietf
 
 Key vault key auto-rotation can be set by configuring key auto-rotation policy. It is only available on Key Vault resource.
 
-- **Get Rotation Policy**: Retrieve rotation policy configuration
-- **Set Rotation Policy**: Set rotation policy configuration 
+- **Get Rotation Policy**: Retrieve rotation policy configuration.
+- **Set Rotation Policy**: Set rotation policy configuration.
 
 ## Key attributes
 
@@ -126,7 +126,7 @@ There are more read-only attributes that are included in any response that inclu
 - *updated*: IntDate, optional. The *updated* attribute indicates when this version of the key was updated. The value is null for keys that were last updated prior to the addition of this attribute. Its value MUST be a number containing an IntDate value.
 - *hsmPlatform*: string, optional. The underlying HSM Platform that is protecting a key.
     - A hsmPlatform value of 2 means the key is protected by our latest FIPS 140 Level 3 validated HSM platform.
-    - A hsmPlatform value of 1 means the key is protected by our previous FIPS 140 Level 2 HSM platform using nCipher HSMs.
+    - A hsmPlatform value of 1 means the key is protected by our previous FIPS 140 Level 2 validated HSM platform.
     - A hsmPlatform value of 0 means the key is protected by a FIPS 140 Level 1 HSM software cryptographic module.
     - if this is not set by a Managed HSM pool, it is protected by our latest FIPS 140 Level 3 validated HSM platform.