Merge pull request #263702 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/configure-networking-how-to.md

@@ -62,8 +62,8 @@ To secure the storage for an existing function app:
     | Setting name | Value | Comment |
     |----|----|----|
     | `AzureWebJobsStorage`| Storage connection string | This is the connection string for a secured storage account. |
-    | `WEBSITE_CONTENTAZUREFILECONNECTIONSTRING` |  Storage connection string | This is the connection string for a secured storage account. This setting is required for Consumption and Premium plan apps on both Windows and Linux. It's not required for Dedicated plan apps, which aren't dynamically scaled by Functions. |
-    | `WEBSITE_CONTENTSHARE` | File share | The name of the file share created in the secured storage account where the project deployment files reside. This setting is required for Consumption and Premium plan apps on both Windows and Linux. It's not required for Dedicated plan apps, which aren't dynamically scaled by Functions. |
+    | `WEBSITE_CONTENTAZUREFILECONNECTIONSTRING` |  Storage connection string | This is the connection string for a secured storage account. This setting is required for Consumption and Elastic Premium plan apps on both Windows and Linux. It's not required for Dedicated plan apps, which aren't dynamically scaled by Functions. |
+    | `WEBSITE_CONTENTSHARE` | File share | The name of the file share created in the secured storage account where the project deployment files reside. This setting is required for Consumption and Elastic Premium plan apps on both Windows and Linux. It's not required for Dedicated plan apps, which aren't dynamically scaled by Functions. |
     | `WEBSITE_CONTENTOVERVNET` | 1 | A value of 1 enables your function app to scale when you have your storage account restricted to a virtual network. You should enable this setting when restricting your storage account to a virtual network. |
 
 1. Select **Save** to save the application settings. Changing app settings causes the app to restart.  

articles/azure-functions/functions-app-settings.md

@@ -614,7 +614,7 @@ Azure Files doesn't support using managed identity when accessing the file share
 
 ## WEBSITE\_CONTENTOVERVNET
 
-A value of `1` enables your function app to scale when you have your storage account restricted to a virtual network. You should enable this setting when restricting your storage account to a virtual network. To learn more, see [Restrict your storage account to a virtual network](configure-networking-how-to.md#restrict-your-storage-account-to-a-virtual-network).
+A value of `1` enables your function app to scale when you have your storage account restricted to a virtual network. You should enable this setting when restricting your storage account to a virtual network. Only required when using `WEBSITE_CONTENTAZUREFILECONNECTIONSTRING`. To learn more, see [Restrict your storage account to a virtual network](configure-networking-how-to.md#restrict-your-storage-account-to-a-virtual-network).
 
 |Key|Sample value|
 |---|------------|

articles/azure-functions/functions-recover-storage-account.md

@@ -31,7 +31,7 @@ In the preceding step, if you can't find a storage account connection string, it
 
 * Required:
   * [`AzureWebJobsStorage`](./functions-app-settings.md#azurewebjobsstorage)
-* Required for Premium plan functions:
+* Required for Elastic Premium and Consumption plan functions:
   * [`WEBSITE_CONTENTAZUREFILECONNECTIONSTRING`](./functions-app-settings.md)
   * [`WEBSITE_CONTENTSHARE`](./functions-app-settings.md)
 

includes/service-bus-quotas-table.md

@@ -25,7 +25,7 @@ The following table lists quota information specific to Azure Service Bus messag
 | Maximum size of any messaging entity name: namespace, subscription, or subscription rule |Entity | 50 characters. |   |
 | Maximum size of a message ID | Entity | 128 |   |
 | Maximum size of a message session ID | Entity | 128 |   |
-| Message size for a queue, topic, or subscription entity | Entity | 256 KB for [Standard tier](../articles/service-bus-messaging/service-bus-premium-messaging.md)<br/> 100 MB for [Premium tier](../articles/service-bus-messaging/service-bus-premium-messaging.md). <br /><br />The message size includes the size of properties (system and user) and the size of payload. The size of system properties varies depending on your scenario.  |Incoming messages that exceed these quotas are rejected, and an exception is received by the calling code. | 
+| Message size for a queue, topic, or subscription entity | Entity | 256 KB for [Standard tier](../articles/service-bus-messaging/service-bus-premium-messaging.md)<br/> 100 MB for [Premium tier](../articles/service-bus-messaging/service-bus-premium-messaging.md). <br /><br />The maximum size for batches is 256 KB for the Standard tier, and 1MB for the Premium tier. <br /><br />The message size includes the size of properties (system and user) and the size of payload. The size of system properties varies depending on your scenario.  |Incoming messages that exceed these quotas are rejected, and an exception is received by the calling code. | 
 | Message property size for a queue, topic, or subscription entity |Entity | <p>Maximum message property size for each property is 32 KB.</p><p>Cumulative size of all properties can't exceed 64 KB. This limit applies to the entire header of the brokered message, which has both user properties and system properties, such as sequence number, label, and message ID.</p><p>Maximum number of header properties in property bag: **byte/int.MaxValue**.</p> | The exception `SerializationException` is generated.| 
 | Number of subscriptions per topic |Entity |2,000 per-topic for the Standard tier and Premium tier. |Subsequent requests for creating additional subscriptions for the topic are rejected. As a result, if configured through the portal, an error message is shown. If called from the management API, an exception is received by the calling code. |
 | Number of SQL filters per topic |Entity |2,000 |Subsequent requests for creation of additional filters on the topic are rejected, and an exception is received by the calling code. |