Merge pull request #308661 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/api-management/send-one-way-request-policy.md

@@ -28,6 +28,7 @@ The `send-one-way-request` policy sends the provided request to the specified UR
   <set-header>...</set-header>
   <set-body>...</set-body>
   <authentication-certificate thumbprint="thumbprint" />
+  <authentication-managed-identity resource="ResourceID"/>
 </send-one-way-request>
 ```
 
@@ -48,6 +49,7 @@ The `send-one-way-request` policy sends the provided request to the specified UR
 | [set-header](set-header-policy.md)                     | Sets a header in the request. Use multiple `set-header` elements for multiple request headers.                                  | No                              |
 | [set-body](set-body-policy.md)                       | Sets the body of the request.                   | No                              |
 | authentication-certificate | [Certificate to use for client authentication](authentication-certificate-policy.md), specified in a `thumbprint` attribute. | No                              |
+| authentication-managed-identity | [Authenticate with managed identity](authentication-managed-identity-policy.md) to resource specified in `resource` attribute. | No |
 | [proxy](proxy-policy.md) | Routes request via HTTP proxy. | No |
 
 

articles/api-management/send-request-policy.md

@@ -29,6 +29,7 @@ The `send-request` policy sends the provided request to the specified URL, waiti
   <set-header>...</set-header>
   <set-body>...</set-body>
   <authentication-certificate thumbprint="thumbprint" />
+  <authentication-managed-identity resource="ResourceID"/>
   <proxy>...</proxy>
 </send-request>
 ```
@@ -51,6 +52,7 @@ The `send-request` policy sends the provided request to the specified URL, waiti
 | [set-header](set-header-policy.md)                     | Sets a header in the request. Use multiple `set-header` elements for multiple request headers.                                  | No                              |
 | [set-body](set-body-policy.md)                       | Sets the body of the request.                   | No                              |
 | authentication-certificate | [Certificate to use for client authentication](authentication-certificate-policy.md), specified in a `thumbprint` attribute. | No                          |
+| authentication-managed-identity | [Authenticate with managed identity](authentication-managed-identity-policy.md) to resource specified in `resource` attribute. | No                          |
 | [proxy](proxy-policy.md) | Routes request via HTTP proxy. | No |
 
 ## Usage

articles/azure-vmware/azure-vmware-solution-nsx-scale-and-performance-recommendations-for-vmware-hcx.md

@@ -92,9 +92,11 @@ Mitigation options:
 
      * More details in the next section with an example of HCX migration use case.
 
-3. Edge Scale-OUT:  If customer has large number of Hosts in the SDDC and workloads, NSX Edge Scale-OUT (from two Edges to four Edges) could be an option to add additional NSX Edge data path resources.
+3. Edge Scale-OUT: If you have a large number of Hosts in the SDDC and workloads, NSX Edge Scale-OUT (from two Edges to four Edges) could be an option to add additional NSX Edge data path resources.
 
-     * However, NSX Edge Scale-OUT is effective only with a change in the NSX default Tier-1 Gateway topology to distribute the traffic optimally across all four Edge VMs. More details in the next section with an example of HCX migration use case.
+   * Edge Scale-OUT is currently not supported on Azure VMware Solution Stretched Cluster private cloud.
+
+   * NSX Edge Scale-OUT is effective only with a change in the NSX default Tier-1 Gateway topology to distribute the traffic optimally across all four Edge VMs. More details in the next section with an example of HCX migration use case.
 
 ### Default and configuration recommendations to the NSX Edge data path performance
 

articles/container-apps/plans.md

@@ -1,6 +1,6 @@
 ---
 title: Azure Container Apps plan types
-description: Compare different plains available in Azure Container Apps
+description: Compare different plans available in Azure Container Apps
 services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps

articles/oracle/oracle-db/oracle-database-regions.md

@@ -51,11 +51,11 @@ The list below mentions the Azure and corresponding OCI regions with the regiona
 | Germany West Central |Germany Central (Frankfurt) |  ✓  | ✓ | ✓ | ✓ | ✓ | ✓ | Dual |
 | Italy North | Italy North (Milan)   | ✓   | ✓   | ✓ |  ✓ | ✓ |  | Dual |
 | North Europe | Ireland (Dublin) | ✓  | ✓ |   | | | |   Dual   |
-| Spain Central | 	Spain Central (Madrid) | ✓  | ✓ | | | | |   Dual    |
+| Spain Central | 	Spain Central (Madrid) | ✓  | ✓ | ✓ | | | |   Dual    |
 | Sweden Central | 	Sweden Central (Stockholm) | ✓  | ✓ | | | | |   Dual    |
 | Switzerland North | Switzerland North (Zurich) | ✓  |  | | | | |   Single    |
 | UAE Central | UAE Central (Abu Dhabi) | ✓  | ✓ | | | | |   Single    |
-| UAE North | UAE North (Dubai) | ✓  | | ✓ | | | |   Dual    |
+| UAE North | UAE North (Dubai) | ✓  | ✓ | ✓ | | | |   Dual    |
 | UK South| UK South (London)   | ✓   | ✓   | ✓ | ✓ | ✓ | ✓ | Dual |
 | UK West | UK West (Newport)	   | ✓   | ✓  | | ✓ | ✓ |  | Single |
 
@@ -64,9 +64,9 @@ The list below mentions the Azure and corresponding OCI regions with the regiona
 
 | Azure region     | OCI region                 | Oracle Exadata Database@Azure | Oracle Autonomous Database@Azure | Oracle Database Autonomous Recovery Service@Azure | Exadata Database Service on Exascale Infrastructure@Azure | BaseDB     | Golden Gate  | Regional Availability |
 | ---------------- | -------------------------- | ----------------------------- | -------------------------------- | ------------------------------------------------- | --------------------------------------------------------- | ----------------- | --------------------- |---------|
-| Canada Central   | Canada Southeast (Toronto) | ✓      | ✓   |  ✓  | ✓   | ✓ |  |  Dual |
+| Canada Central   | Canada Southeast (Toronto) | ✓      | ✓   |  ✓  | ✓   | ✓ | ✓ |  Dual |
 | Canada East | Canada Southeast (Montreal) | ✓  | | | | | |   Single    |
-| Central US       | US Midwest (Chicago)       | ✓       | ✓      | ✓    |  ✓   |    |      | Dual    |
+| Central US       | US Midwest (Chicago)       | ✓       | ✓      | ✓    |  ✓   |  ✓  |      | Dual    |
 | East US          | US East (Ashburn)          | ✓     | ✓      | ✓      | ✓     | ✓ | ✓ | Dual|
 | East US 2        | US East (Ashburn)          | ✓    | ✓         | ✓       |  ✓   |   |  | Dual     |
 | North Central US | US Midwest (Chicago)   | ✓    |       |      |     |  |  | Single   |