Merge pull request #268495 from MicrosoftDocs/main

3/08 OOB Publish at 8AM

Author: huypub

articles/ai-services/cognitive-services-virtual-networks.md

@@ -59,6 +59,7 @@ Virtual networks are supported in [regions where Azure AI services are available
 > - `AzureResourceManager`
 > - `CognitiveServicesManagement`
 > - `CognitiveServicesFrontEnd`
+> - `Storage` (Speech Studio only)
 
 ## Change the default network access rule
 

articles/aks/howto-deploy-java-liberty-app.md

@@ -59,23 +59,23 @@ The following steps guide you to create a Liberty runtime on AKS. After completi
    1. Create a new resource group. Because resource groups must be unique within a subscription, pick a unique name. An easy way to have unique names is to use a combination of your initials, today's date, and some identifier. For example, `ejb0913-java-liberty-project-rg`.
    1. Select *East US* as **Region**.
 
-   Create environment variables in your shell for the resource group names for the cluster and the database.
-
-   ### [Bash](#tab/in-bash)
-
-   ```bash
-   export RESOURCE_GROUP_NAME=<your-resource-group-name>
-   export DB_RESOURCE_GROUP_NAME=<your-resource-group-name>
-   ```
-
-   ### [PowerShell](#tab/in-powershell)
-
-   ```powershell
-   $Env:RESOURCE_GROUP_NAME="<your-resource-group-name>"
-   $Env:DB_RESOURCE_GROUP_NAME="<your-resource-group-name>"
-   ```
-
-   ---
+    Create environment variables in your shell for the resource group names for the cluster and the database.
+ 
+    ### [Bash](#tab/in-bash)
+ 
+    ```bash
+    export RESOURCE_GROUP_NAME=<your-resource-group-name>
+    export DB_RESOURCE_GROUP_NAME=<your-resource-group-name>
+    ```
+ 
+    ### [PowerShell](#tab/in-powershell)
+ 
+    ```powershell
+    $Env:RESOURCE_GROUP_NAME="<your-resource-group-name>"
+    $Env:DB_RESOURCE_GROUP_NAME="<your-resource-group-name>"
+    ```
+ 
+    ---
 
 1. Select **Next**, enter the **AKS** pane. This pane allows you to select an existing AKS cluster and Azure Container Registry (ACR), instead of causing the deployment to create a new one, if desired. This capability enables you to use the sidecar pattern, as shown in the [Azure architecture center](/azure/architecture/patterns/sidecar). You can also adjust the settings for the size and number of the virtual machines in the AKS node pool. The remaining values do not need to be changed from their default values.
 

articles/azure-monitor/app/distributed-trace-data.md

@@ -188,7 +188,7 @@ This feature is enabled by default for JavaScript and the headers are automatica
       distributedTracingMode: 2 // DistributedTracingModes.W3C
   ```
 
-If the XMLHttpRequest or Fetch Ajax requests are sent to a different domain host, including subdomains, the correlation headers aren't included by default. To enable this feature, set the [`enableCorsCorrelation` configuration field](./javascript-sdk-configuration.md#sdk-configuration) to `true`. If you set `enableCorsCorrelation` to `true`, all XMLHttpRequest and Fetch Ajax requests include the correlation headers. As a result, if the application on the server that is being called doesn't support the `traceparent` header, the request might fail, depending on whether the browser / version can validate the request based on which headers the server accepts.
+If the XMLHttpRequest or Fetch Ajax requests are sent to a different domain host, including subdomains, the correlation headers aren't included by default. To enable this feature, set the [`enableCorsCorrelation` configuration field](./javascript-sdk-configuration.md#sdk-configuration) to `true`. If you set `enableCorsCorrelation` to `true`, all XMLHttpRequest and Fetch Ajax requests include the correlation headers. As a result, if the application on the server that is being called doesn't support the `traceparent` header, the request might fail, depending on whether the browser / version can validate the request based on which headers the server accepts. You can use the [`correlationHeaderExcludedDomains` configuration field](./javascript-sdk-configuration.md#sdk-configuration) to exclude the server's domain from cross-component correlation header injection. For example, you can use `correlationHeaderExcludedDomains: ['*.auth0.com']` to exclude correlation headers from requests sent to the Auth0 identity provider.
 
 > [!IMPORTANT]
 > To see all configurations required to enable correlation, see the [JavaScript correlation documentation](./javascript.md#enable-distributed-tracing).

articles/azure-monitor/essentials/data-collection-endpoint-overview.md

@@ -84,9 +84,9 @@ Create associations between endpoints to your target machines or resources by us
 ## Sample data collection endpoint
 For a sample DCE, see [Sample data collection endpoint](data-collection-endpoint-sample.md).
 
-
 ## Limitations
-- Data collection endpoints only support Log Analytics workspaces as a destination for collected data. [Custom metrics (preview)](../essentials/metrics-custom-overview.md) collected and uploaded via Azure Monitor Agent aren't currently controlled by DCEs. Data collection endpoints also can't be configured over private links.
+
+- Data collection endpoints only support Log Analytics workspaces as a destination for collected data. [Custom metrics (preview)](../essentials/metrics-custom-overview.md) collected and uploaded via Azure Monitor Agent aren't currently controlled by DCEs.
 
 - Data collection endpoints are where [Logs ingestion API ingestion limits](../service-limits.md#logs-ingestion-api) are applied.
 

articles/azure-resource-manager/management/lock-resources.md

@@ -2,7 +2,7 @@
 title: Protect your Azure resources with a lock
 description: You can safeguard Azure resources from updates or deletions by locking all users and roles.
 ms.topic: conceptual
-ms.date: 01/02/2024
+ms.date: 03/08/2024
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
 content_well_notification: 
   - AI-contribution
@@ -90,19 +90,19 @@ Applying locks can lead to unexpected results. Some operations, which don't seem
 
 - A read-only lock on a **Log Analytics workspace** prevents **User and Entity Behavior Analytics (UEBA)** from being enabled.
 
-- A cannot-delete lock on a **Log Analytics workspace** doesn't prevent [data purge operations](../../azure-monitor/logs/personal-data-mgmt.md#delete), remove the [data purge](../../role-based-access-control/built-in-roles.md#data-purger) role from the user instead. 
+- A cannot-delete lock on a **Log Analytics workspace** doesn't prevent [data purge operations](../../azure-monitor/logs/personal-data-mgmt.md#delete). Instead, remove the [data purge](../../role-based-access-control/built-in-roles.md#data-purger) role from the user.
 
 - A read-only lock on a **subscription** prevents **Azure Advisor** from working correctly. Advisor is unable to store the results of its queries.
 
 - A read-only lock on an **Application Gateway** prevents you from getting the backend health of the application gateway. That [operation uses a POST method](/rest/api/application-gateway/application-gateways/backend-health), which a read-only lock blocks.
 
 - A read-only lock on an Azure Kubernetes Service (AKS) cluster limits how you can access cluster resources through the portal. A read-only lock prevents you from using the AKS cluster's Kubernetes resources section in the Azure portal to choose a cluster resource. These operations require a POST method request for authentication.
 
-- A cannot-delete lock on a **Virtual Machine** that is protected by **Site Recovery** prevents certain resource links related to Site Recovery from being removed properly when you remove the protection or disable replication. If you plan to protect the VM again later, you need to remove the lock prior to disabling protection. If you don't remove the lock, you need to follow certain steps to clean up the stale links before you can protect the VM. For more information, see [Troubleshoot Azure VM replication](../../site-recovery/azure-to-azure-troubleshoot-errors.md#replication-not-enabled-on-vm-with-stale-resources-error-code-150226).
+- A cannot-delete lock on a **Virtual Machine** that is protected by **Site Recovery** prevents certain resource links related to Site Recovery from being removed properly when you remove the protection or disable replication. If you plan to protect the VM again later, you need to remove the lock before disabling protection. If you don't remove the lock, you need to follow certain steps to clean up the stale links before you can protect the VM. For more information, see [Troubleshoot Azure VM replication](../../site-recovery/azure-to-azure-troubleshoot-errors.md#replication-not-enabled-on-vm-with-stale-resources-error-code-150226).
 
 ## Who can create or delete locks
 
-To create or delete management locks, you need access to `Microsoft.Authorization/*` or `Microsoft.Authorization/locks/*` actions. Only the **Owner** and the **User Access Administrator** built-in roles can create and delete management locks. You can create a custom role with the required permissions.
+To create or delete management locks, you need access to `Microsoft.Authorization/*` or `Microsoft.Authorization/locks/*` actions. Users assigned to the **Owner** and the **User Access Administrator** roles have the required access. Some specialized built-in roles also grant this access. You can create a custom role with the required permissions.
 
 ## Managed applications and locks
 
@@ -136,7 +136,7 @@ In the left navigation panel, the subscription lock feature's name is **Resource
 
 When using an ARM template or Bicep file to deploy a lock, it's good to understand how the deployment scope and the lock scope work together. To apply a lock at the deployment scope, such as locking a resource group or a subscription, leave the scope property unset. When locking a resource, within the deployment scope, set the scope property on the lock.
 
-The following template applies a lock to the resource group it's deployed to. Notice there isn't a scope property on the lock resource because the lock scope matches the deployment scope. Deploy this template at the resource group level.
+The following template applies a lock to the resource group. Notice there isn't a scope property on the lock resource because the lock scope matches the deployment scope. Deploy this template at the resource group level.
 
 # [JSON](#tab/json)
 

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

@@ -0,0 +1,55 @@
+---
+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.service: backup
+ms.custom: engagement-fy23
+author: AbhishekMallick-MS
+ms.author: v-abhmallick
+---
+
+# Long-term retention for Azure Database for MySQL - Flexible Server by using Azure Backup (preview)
+
+Azure Backup and Azure Database Services together allow you to build an enterprise-class backup solution for Azure Database for MySQL - Flexible servers that retain backups for **up to 10 years**. If you have an Azure Database for MySQL - Flexible server, then you can extend  the retention of backups beyond 35 days with built-in operational tier backup capability of MySQL - Flexible database.
+
+This feature allows you to extend the current limitation of *35 days* backup retention to *10 years*, meeting your compliance and regulatory requirements.
+
+Also, the backups are copied to an isolated storage environment outside of your tenant and subscription provide protection against ransomware attacks. In addition to long-term retention (LTR), this feature enhances the backup resiliency by protecting the source data from different levels of data loss, such as accidental deletions and ransomware protection. It's a zero-infrastructure solution with Azure Backup managing the backups with automated retention and backup scheduling. You can create a backup policy to define the backup schedule and retention. Based on the policy definition, Azure Backup transfers backups to the vault as blobs and manages their lifecycle. You can manage the backups centrally beside other protected workloads via the Azure Backup Center. 
+
+You can recover this backup in your specified storage containers, which can be used to rebuild the MySQL - Flexible server. You can also use native tools to restore this data as a new MySQL - Flexible server with database native tools. 
+
+## Azure Database for MySQL - Flexible Server backup flow
+
+To back up an Azure Database for MySQL - Flexible Server:
+
+1. Grant permissions to the Backup vault MSI on the target ARM resource (MySQL-Flexible  server), establishing access and control.
+2. Configure backup policies, and specify the scheduling, retention, and other parameters.
+
+Once the configuration is complete:
+
+- Azure Backup invokes the backup based on the policy schedules on the ARM API of MySQL Flex server, writing data to a secure blob container with a SAS for enhanced security.
+- Backup job runs independently, preventing disruptions during long-running tasks.
+- The retention and recovery point lifecycles align with the backup policies for effective management.
+- During the restore, Azure Backup invokes restore on the ARM API of the MySQL - Flexible Server using the Statistical Analysis System (SAS) for asynchronous, nondisruptive recovery.
+
+:::image type="content" source="./media/backup-azure-mysql-flexible-server-about/mysql-flexible-server-backup-architecture.png" alt-text="Diagram shows the backup flow for Azure Database for MySQL Flexible Server." lightbox="./media/backup-azure-mysql-flexible-server-about/mysql-flexible-server-backup-architecture.png":::
+
+## Azure Backup authentication with MySQL - Flexible server
+
+Azure Backup needs to connect to Azure MySQL - Flexible server while taking each backup. 
+
+## Permissions for an Azure Database for MySQL - Flexible Server backup
+
+The following table lists permissions that the vault MSI requires for successful backup operations:
+
+| Operation | Permission |
+| --- | --- |
+| **Backup** | - MySQL Flexible Server Long-term Retention Backup Role <br><br> - Reader Role on the server's resource group. |
+| **Restore** | Storage Blob Data Contributor Role on the target storage account. |
+
+## Next steps
+
+- [Support matrix for Azure Database for MySQL - Flexible Server retention for long term (preview)](backup-azure-mysql-flexible-server-support-matrix.md).
+- [Back up an Azure Database for MySQL - Flexible Server (preview)](backup-azure-mysql-flexible-server.md).
+- [Restore an Azure Database for MySQL - Flexible Server (preview)](backup-azure-mysql-flexible-server-restore.md).

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

@@ -0,0 +1,47 @@
+---
+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
+author: AbhishekMallick-MS
+ms.author: v-abhmallick
+---
+
+# Restore the Azure Database for MySQL - Flexible Server by using Azure Backup (preview)
+
+This article describes how to restore the Azure Database for MySQL - Flexible Server by using Azure Backup.
+
+Learn more about the [supported scenarios. considerations, and limitations](backup-azure-mysql-flexible-server-support-matrix.md).
+
+## Restore MySQL - Flexible Server database
+
+To restore the database, follow these steps:
+
+1. Go to the *Backup vault* > **Backup instances**.
+
+2. Select the **Azure Database for MySQL - Flexible Server** > **Restore**.
+
+   :::image type="content" source="./media/backup-azure-mysql-flexible-server-restore/restore-parameters.png" alt-text="Screenshot shows how to go to the backup instance." lightbox="./media/backup-azure-mysql-flexible-server-restore/restore-parameters.png":::
+
+3. Click **Select restore point** > **Point-in-time** you want to restore.
+
+   To change the date range, select **Time period**.
+
+   :::image type="content" source="./media/backup-azure-mysql-flexible-server-restore/restore-point.png" alt-text="Screenshot shows the selection of point-in-time recovery point." lightbox="./media/backup-azure-mysql-flexible-server-restore/restore-point.png":::
+
+4. On the **Restore parameters** tab, choose the **Target Storage account**, and then select **Validate**.
+
+   The validation process checks if the restore parameters and permissions are assigned for the restore operation.
+
+
+   :::image type="content" source="./media/backup-azure-mysql-flexible-server-restore/restore.png" alt-text="Screenshot shows the selection of restore parameters." lightbox="./media/backup-azure-mysql-flexible-server-restore/restore.png":::
+
+5. When the validation is successful, select **Restore**.
+
+   It restores the selected database backups in the target storage account.
+
+   :::image type="content" source="./media/backup-azure-mysql-flexible-server-restore/review-restore.png" alt-text="Screenshot shows how to trigger restore operation." lightbox="./media/backup-azure-mysql-flexible-server-restore/review-restore.png":::
+
+## Next steps
+
+- [Back up the Azure Database for MySQL - Flexible Server (preview)](backup-azure-mysql-flexible-server.md)

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

@@ -0,0 +1,33 @@
+---
+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.custom: references_regions
+ms.service: backup
+author: AbhishekMallick-MS
+ms.author: v-abhmallick
+---
+
+# Support matrix for Azure Database for MySQL - Flexible Server protection by using Azure Backup (preview)
+
+This article summarizes  the supported scenarios, considerations, and limitations for Azure Database for MySQL - Flexible Server backup and retention for long term by using [Azure Backup](./backup-overview.md).
+
+## Supported regions
+
+Long-term retention for Azure Database for MySQL - Flexible Server (preview) is available in all Azure public cloud regions.
+
+## Supported scenarios
+
+- This feature backs up the entire MySQL - Flexible Server to the Backup vault.
+- You can recover the MySQL - Flexible Server long-term retention (LTR) data in the specified storage containers that allow to rebuild the MySQL - Flexible Server. You can also restore this data as a new MySQL - Flexible Server with database native tools. 
+
+## Limitations
+- Individual database-level granular selection is currently not supported.
+- End-to-end creation and restoration of MySQL - Flexible Server by using Azure Backup is currently not supported. 
+
+## Next steps
+
+- [About Azure Database for MySQL - Flexible Server retention for long term (preview)](backup-azure-mysql-flexible-server-about.md).
+- [Back up an Azure Database for MySQL - Flexible Server (preview)](backup-azure-mysql-flexible-server.md).
+- [Restore an Azure Database for MySQL - Flexible Server (preview)](backup-azure-mysql-flexible-server-restore.md).