Merge pull request #301867 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

@@ -445,7 +445,7 @@ You'll deploy with the [Azure Function App Deploy v2](/azure/devops/pipelines/ta
 
 The v2 version of the task includes support for newer applications stacks for .NET, Python, and Node. The task includes networking predeployment checks. When there are predeployment issues, deployment stops. 
 
-To deploy to Azure Functions, add the following snippet at the end of your `azure-pipelines.yml` file. The default `appType` is Windows. You can specify Linux by setting the `appType` to `functionAppLinux`. Deploying to a Flex Consumption app requires you to set both `appType: functionAppLinux` and `isFlexConsumption: true`.
+To deploy to Azure Functions, add the following snippet at the end of your `azure-pipelines.yml` file. The default `appType` is Windows. You can specify Linux by setting the `appType` to `functionAppLinux`. Deploying to a Flex Consumption app requires you to set both `appType: functionAppLinux` and `isFlexConsumption: true`. The reason must be set to `functionAppLinux` when you use Flex Consumption because [Flex Consumption](/azure/azure-functions/flex-consumption-plan) is a Linux-based Azure Function.
 
 ### [Windows App](#tab/windows)
 ```yaml

articles/confidential-computing/guest-attestation-confidential-virtual-machines-design.md

@@ -95,7 +95,6 @@ Refer to [Azure Confidential VMs attestation guidance & FAQ](https://github.com/
 | Report Payload | 32   | 1184 | The hardware report. |
 | Runtime Data   | 1216 | variable length | The runtime data includes claims endorsed by the hardware report. |
 
-
 #### Header
 
 | Name | Offset (bytes) | Size (bytes) | Description |
@@ -115,11 +114,12 @@ The report generated by the hardware (AMD SEV-SNP or Intel TDX). The report_data
 
 | Name | Offset (bytes) | Size (bytes) | Description | Measured |
 | :--- | :--- | :--- | :--- | :--- |
-| Data Size      | 0  | 4 | The size of Runtime Claims. | No |
+| Data Size      | 0  | 4 | The size of Runtime Data. | No |
 | Version        | 4  | 4 | Format version. Expected: 1. | No |
 | Report Type    | 8  | 4 | The type of hardware report. Expected: 2 (AMD SEV-SNP), 4 (Intel TDX) | No |
 | Hash Type      | 12 | 4 | The algorithm used to hash the runtime data. The hash value is captured in the report_data field of the hardware report. Expected: 1 (SHA-256), 2 (SHA-384), 3 (SHA-512) | No |
-| Runtime Claims | 16 | variable length | The runtime claims in JSON format. | Yes |
+| Claim Size     | 16 | 4 | The size of Runtime Claims. | No |
+| Runtime Claims | 20 | variable length | The runtime claims in JSON format. | Yes |
 
 #### Runtime Claims
 

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

@@ -57,7 +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 |
+| 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/private-link/private-endpoint-dns.md

@@ -123,7 +123,7 @@ For Azure services, use the recommended zone names as described in the following
 >| Azure Database for MySQL - Flexible Server (Microsoft.DBforMySQL/flexibleServers) | mysqlServer | privatelink.mysql.database.azure.com | mysql.database.azure.com |
 >| Azure Database for MariaDB (Microsoft.DBforMariaDB/servers) | mariadbServer | privatelink.mariadb.database.azure.com | mariadb.database.azure.com |
 >| Azure Cache for Redis (Microsoft.Cache/Redis) | redisCache | privatelink.redis.cache.windows.net | redis.cache.windows.net |
->| Azure Cache for Redis Enterprise (Microsoft.Cache/RedisEnterprise) | redisEnterprise | privatelink.redisenterprise.cache.azure.net | redisenterprise.cache.azure.net |
+>| Azure Cache for Redis Enterprise (Microsoft.Cache/RedisEnterprise) | redisEnterprise | privatelink.redisenterprise.cache.azure.net | {cachename}.{region}.redisenterprise.cache.azure.net |
 >| Azure Managed Redis (Microsoft.Cache/RedisEnterprise) | redisEnterprise | privatelink.redis.azure.net | {instanceName}.{region}.redis.azure.net |
 
 ### Hybrid + multicloud

articles/virtual-network/ip-services/default-outbound-access.md

@@ -160,7 +160,15 @@ az network vnet subnet update --resource-group rgname --name subnetname --vnet-n
 
 * To activate or update virtual machine operating systems, such as Windows, an explicit outbound connectivity method is required.
 
-* In configurations using a User Defined Route (UDR) with a default route (0.0.0.0/0) that sends traffic to an upstream firewall/network virtual appliance, any traffic that bypasses this route (for example, to Service Tagged destinations) breaks in a Private subnet.
+* In configurations using User Defined Routes (UDRs), any configured routes with [next hop type `Internet`](../virtual-networks-udr-overview.md#next-hop-types-across-azure-tools) will break in a Private subnet.
+
+  * A common example is the use of a UDR to steer traffic to an upstream network virtual appliance/firewall, with exceptions for certain Azure Service Tags to bypass inspection.
+
+    * A default route for the destination 0.0.0.0/0, with a next hop type of Virtual Appliance applies in the general case.
+
+    * One or more routes are configured to [Service Tag destinations](../virtual-networks-udr-overview.md#service-tags-for-user-defined-routes) with next hop type `Internet`, to bypass the NVA/firewall. Unless an [explicit outbound connectivity method](#add-an-explicit-outbound-connectivity-method) is also configured for the source of the connection to these destinations, attempts to connection to these destinations will fail, because default outbound access isn't available.
+
+  * This limitation doesn't apply to the use of Service Endpoints, which use a different next hop type `VirtualNetworkServiceEndpoint`. See [Virtual Network service endpoints](../virtual-network-service-endpoints-overview.md).
 
 * Private Subnets aren't applicable to delegated or managed subnets used for hosting PaaS services. In these scenarios, outbound connectivity is managed by the individual service.