Merge pull request #287866 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/load-testing/resource-supported-azure-resource-types.md

@@ -23,6 +23,7 @@ This section lists the Azure resource types that Azure Load Testing supports for
 * Azure API Management
 * Azure App Service
 * Azure App Service plan
+* Azure Application Gateway
 * Azure Application Insights
 * Azure Application Gateway
 * Azure Batch Service

articles/oracle/oracle-db/provision-manage-oracle-resources.md

@@ -37,28 +37,6 @@ The following management functions are available for all resources from the Micr
    1. Follow the steps to access the resource blade.
    1. You can remove a single or multiple resources from the blade by selecting the checkbox on the left side of the table. Once you have selected the resource(s) to remove, you can then select the **Delete** icon at the top of the blade.
    1. You can also remove a single resource by selecting the link to the resource from the **Name** field in the table. From the resource's detail page, select the **Delete** icon at the top of the blade.
-* **Move the resource to a new resource group.**
-   1. Follow the steps to access the resource blade.
-   1. Select the link to the resource from the **Name** field in the table.
-   1. From the resource's overview page, select the **Move** link on the Resource group field.
-   1. From the **Move resources** page, use the drop-down field for **Resource group** to select an existing resource group.
-   1. To create and use a new resource group, select the **Create new** link below the Resource group field. Enter a new resource group name in the **Name** field. Select the **OK** button to save your new resource group and use it. Select the **Cancel** button to return without creating a new resource group.
-* **Move the resource to a new subscription.**
-
-   > [!NOTE]
-   > You must have access to another Microsoft Azure subscription, and that subscription must have been setup for access to OracleDB@Azure. If both of these conditions are not met, you will not be able to successfully move the resource to another subscription.
-
-   1. Follow the steps to access the resource blade.
-   1. Select the link to the resource from the Name field in the table.
-   1. From the resource's overview page, select the **Move** link on the Subscription field.
-   1. From the **Move resources** page, use the drop-down field for **Subscription** to select an existing subscription.
-   1. You can also simultaneously move the resource group for the resource. To do this, note the steps in the **Move the resource to a new resource group** tasks. **Add, manage, or delete tags for the resource.**
-   1. Follow the steps to access the resource blade.
-   1. Select the link to the resource from the Name field in the table.
-   1. From the resource's overview page, select the **Edit** link on the **Tags** field.
-   1. To create a new tag, enter values in the **Name** and **Value** fields.
-   1. To edit an existing tag, change the value in the existing tag's **Value** field.
-   1. To delete an existing tag, select the **Trashcan** icon at the right-side of the tag.
 
 ## Manage resource allocation for Oracle Autonomous Database Serverless instances
 
@@ -81,4 +59,4 @@ Follow the following steps to access the Oracle Autonomous Database@Azure blade.
    1. Select the link to the resource from the **Name** field in the table.
    1. From the resource's detail page, select the **Go to OCI** link on the **OCI Database URL** field.
    1. Log in to OCI.
-   1. Manage the resource from within the OCI console.
+   1. Manage the resource from within the OCI console.

articles/reliability/migrate-cache-redis.md

@@ -18,6 +18,9 @@ Azure Cache for Redis supports zone redundancy in its Premium, Enterprise, and E
 
 Currently, the only way to convert a resource from non-availability zone support to availability zone support is to redeploy your current cache.
 
+ > [!NOTE]
+   > Zone redundancy isn't supported with geo-replication.
+
 ## Prerequisites
 
 To migrate to availability zone support, you must have an Azure Cache for Redis resource in either the Premium, Enterprise, or Enterprise Flash tiers.
@@ -54,4 +57,4 @@ Running multiple caches simultaneously as you convert your data to the new cache
 Learn more about:
 
 > [!div class="nextstepaction"]
-> [Azure services and regions that support availability zones](availability-zones-service-support.md)
+> [Azure services and regions that support availability zones](availability-zones-service-support.md)

articles/sap/automation/plan-deployment.md

@@ -57,7 +57,7 @@ The control plane provides the following services:
 
 The control plane is defined by using two configuration files, one for the deployer and one for the SAP Library.
 
-The deployment configuration file defines the region, environment name, and virtual network information. For example:
+The deployer configuration file defines the region, environment name, and virtual network information. For example:
 
 ```tfvars
 # Deployer Configuration File

articles/sentinel/data-transformation.md

@@ -101,7 +101,7 @@ Only the following tables are currently supported for custom log ingestion:
 - [**CommonSecurityLog**](/azure/azure-monitor/reference/tables/commonsecuritylog)
 - [**Syslog**](/azure/azure-monitor/reference/tables/syslog)
 - [**ASimAuditEventLogs**](/azure/azure-monitor/reference/tables/asimauditeventlogs)
-- **ASimAuthenticationEventLogs**
+- [**ASimAuthenticationEventLogs**](/azure/azure-monitor/reference/tables/asimauthenticationeventlogs)
 - [**ASimDnsActivityLogs**](/azure/azure-monitor/reference/tables/asimdnsactivitylogs)
 - [**ASimFileEventLogs**](/azure/azure-monitor/reference/tables/asimfileeventlogs)
 - [**ASimNetworkSessionLogs**](/azure/azure-monitor/reference/tables/asimnetworksessionlogs)

articles/site-recovery/site-recovery-vmware-deployment-planner-analyze-report.md

@@ -210,7 +210,7 @@ For example, if the workload characteristics of a disk put it in the P20 or P30
 
 **Boot Type**: Boot type of the virtual machine. It can be either BIOS or EFI.  Currently Azure Site Recovery supports Windows Server EFI virtual machines (Windows Server 2012, 2012 R2 and 2016) provided the number of partitions in the boot disk is less than 4 and boot sector size is 512 bytes. To protect EFI virtual machines, Azure Site Recovery mobility service version must be 9.13 or later. Only failover is supported for EFI virtual machines. Failback isn't supported.  
 
-**OS Type**: It's OS type of the virtual machine. It can be either Windows or Linux or other based on the chosen template from virtual machineware vSphere while creating the virtual machine.  
+**OS Type**: It's OS type of the virtual machine. It can be either Windows or Linux or other based on the chosen template from VMware vSphere while creating the virtual machine.  
 
 ## Incompatible virtual machines
 
@@ -282,4 +282,4 @@ Learn more about [cost estimation](site-recovery-vmware-deployment-planner-cost-
 
 
 ## Next steps
-Learn more about [cost estimation](site-recovery-vmware-deployment-planner-cost-estimation.md).
+Learn more about [cost estimation](site-recovery-vmware-deployment-planner-cost-estimation.md).