Merge pull request #301779 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/azure-functions/functions-how-to-azure-devops.md

@@ -240,7 +240,7 @@ variables:
   # Container registry service connection established during pipeline creation
   dockerRegistryServiceConnection: <Docker registry service connection>
   imageRepository: <Name of your image repository>
-  containerRegistry: <Name of the Azure container registry>
+  containerRegistry: <Name of the Azure Container Registry>
   dockerfilePath: '$(Build.SourcesDirectory)/Dockerfile'
   tag: '$(Build.BuildId)'
   

articles/oracle/oracle-db/oracle-database-network-plan.md

@@ -22,7 +22,8 @@ Default network features enable basic network connectivity for both new and exis
 Advanced network features enhance the virtual networking experience, offering improved security, performance, and control—similar to standard Azure VMs. These features are generally available for new deployments in the following regions:
 
 * Australia East
-* Australia Southeast 
+* Australia Southeast
+* Canada Central
 * Central US 
 * East US 
 * East US2 

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

@@ -57,6 +57,7 @@ The list below mentions the Azure and corresponding OCI regions with the regiona
 | West US | US West (San Jose)  | ✓  | ✓  | ✓| | Preview available | Single |
 | Central US | US Midwest (Chicago)  | ✓  |   ✓  | ✓ | | | Dual |
 | East US 2 | US East (Ashburn) | ✓  |   | | | | Dual |
+| South Central US | ✓  |   | | | | Dual |
 
 > [!NOTE]
 > To provision Oracle Database@Azure resources in a supported region, your tenancy must be subscribed to the target region. Learn how to [manage regions](https://docs.oracle.com/iaas/Content/Identity/regions/managingregions.htm#Managing_Regions) and [subscribe to an infrastructure region](https://docs.oracle.com/iaas/Content/Identity/regions/To_subscribe_to_an_infrastructure_region.htm#subscribe).

articles/reliability/reliability-fabric.md

@@ -195,10 +195,12 @@ OneLake data remains accessible through multiple channels:
     * Azure Storage Explorer: See [Integrate OneLake with Azure Storage Explorer](/fabric/onelake/onelake-azure-storage-explorer)
 
     * OneLake File Explorer: See [Use OneLake file explorer to access Fabric data](/fabric/onelake/onelake-file-explorer)
- 
-The OneLake catalog remains available during disaster failover in read-only mode:
+
+* In a disaster scenario, the OneLake catalog is in read-only mode:
+    
     * Explore tab: You can access the Explore tab to view all items and workspaces, including their metadata and related details.
-    * Govern tab: You can access the Govern tab to view insights, recommended actions, and governance tools - based on the most recent successful model refresh prior to failover.
+
+    * Govern tab: You can access the Govern tab to view insights, recommended actions, and governance tools - based on the most recent successful model refresh prior to failover. 
 
 #### Phase 3: Recovery plan
 

articles/reliability/reliability-functions.md

@@ -49,7 +49,7 @@ When you configure Elastic Premium function app plans as zone redundant, the pla
 
 Instance spreading with a zone-redundant deployment is determined inside the following rules, even as the app scales in and out:
 
-- The minimum function app instance count is three. 
+- The minimum function app instance count is two. 
 - When you specify a capacity larger than the number of zones, the instances are spread evenly only when the capacity is a multiple of the number of zones. 
 - For a capacity value more than Number of Zones * Number of instances, extra instances are spread across the remaining zones.
 
@@ -107,8 +107,8 @@ Availability zone support is a property of the Premium plan. Here are current co
 - You can only enable availability zones in the plan when you create your app. You can't convert an existing Premium plan to use availability zones.
 - You must use a [zone redundant storage account (ZRS)](../storage/common/storage-redundancy.md#zone-redundant-storage) for your function app's [default host storage account](../azure-functions/storage-considerations.md#storage-account-requirements). If you use a different type of storage account, your app might behave unexpectedly during a zonal outage.
 - Both Windows and Linux are supported.
-- Function apps hosted on a Premium plan must have a minimum of three [always ready instances](../azure-functions/functions-premium-plan.md#always-ready-instances).
-- The platform enforces this minimum count behind the scenes if you specify an instance count fewer than three.
+- Function apps hosted on a Premium plan must have a minimum of two [always ready instances](../azure-functions/functions-premium-plan.md#always-ready-instances).
+- The platform enforces this minimum count behind the scenes if you specify an instance count fewer than two.
 - If you aren't using Premium plan or a scale unit that supports availability zones, are in an unsupported region, or are unsure, see the [migration guidance](../reliability/migrate-functions.md).
 ::: zone-end 
 ### Pricing 
@@ -118,7 +118,7 @@ There's no separate meter associated with enabling availability zones. Pricing f
 When you enable availability zones in an app with always-ready instance configuration of fewer than two instances for each [per-function scaling function or group](../azure-functions/flex-consumption-plan.md#per-function-scaling), the platform automatically creates two instances of the [always-ready](../azure-functions/flex-consumption-plan.md#always-ready-instances) type for each per-function scaling function or group. These new instances are also billed as always-ready instances.
 ::: zone-end 
 ::: zone pivot="premium-plan" 
-There's no extra cost associated with enabling availability zones. Pricing for a zone-redundant Premium App Service plan is the same as a single zone Premium plan. For each App Service plan you use, you're charged based on the SKU you choose, the capacity you specify, and any instances you scale to based on your autoscale criteria. If you enable availability zones on a plan with fewer than three instances, the platform enforces a minimum instance count of three for that App Service plan, and you're charged for all three instances.
+There's no extra cost associated with enabling availability zones. Pricing for a zone-redundant Premium App Service plan is the same as a single zone Premium plan. For each App Service plan you use, you're charged based on the SKU you choose, the capacity you specify, and any instances you scale to based on your autoscale criteria. If you enable availability zones on a plan with fewer than two instances, the platform enforces a minimum instance count of two for that App Service plan, and you're charged for both instances.
 ::: zone-end 
 ### Create a function app in a zone-redundant plan 
 ::: zone pivot="flex-consumption-plan"