Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into esanrefreshp3

Author: roygara

articles/active-directory-b2c/service-limits.md

@@ -8,7 +8,7 @@ manager: CelesteDG
 ms.service: azure-active-directory
 
 ms.topic: reference
-ms.date: 08/19/2025
+ms.date: 01/08/2026
 ms.subservice: b2c
 zone_pivot_groups: b2c-policy-type
 
@@ -186,7 +186,7 @@ The following table lists the administrative configuration limits in the Azure A
 
 ## Region specific service limits 
 
-As a protection for our customers, Microsoft places some restrictions on telephony verification for certain region codes. The following table lists the region codes and their corresponding limits.
+As a protection for our customers, Microsoft places some restrictions on telephony verification for certain region codes. The following table lists the region codes and their corresponding limits. These limits apply to both SMS and Voice verification.
 
 | Region Code | Region Name                                    | Limit per tenant per 60 minutes | Limit per tenant per 24 hours            |                         
 |:----------- |:---------------------------------------------- |:------------------------------- | :----------------------------------------|

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-dedicated-sku.md

@@ -57,7 +57,7 @@ Durable Task Scheduler offers two SKU options: Dedicated and Consumption (previe
 
 The Dedicated SKU provides  performance and pricing through preallocated Capacity Units (CUs). You can purchase up to three CUs. 
 
-Currently, you're limited to 15 task hubs when using the Dedicated SKU. For more quota, [contact support](https://github.com/Azure/azure-functions-durable-extension/issues).
+Currently, you're limited to 25 task hubs when using the Dedicated SKU. For more quota, [contact support](https://github.com/Azure/azure-functions-durable-extension/issues).
 
 #### Key features
 

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler.md

@@ -107,7 +107,7 @@ Creating multiple task hubs isolates different workloads that can be managed ind
 - Create task hubs for different teams within your organization. 
 - Share the same scheduler instance across multiple apps. 
 
-Scheduler sharing is a great way to optimize cost when multiple teams have scenarios requiring orchestrations. Although you can create unlimited task hubs in one scheduler instance, they share the same resources; if one task hub is heavily loaded, it might affect the performance of the other task hubs.
+Scheduler sharing is a great way to optimize cost when multiple teams have scenarios requiring orchestrations. Although you can create multiple task hubs in one scheduler instance, they share the same resources; if one task hub is heavily loaded, it might affect the performance of the other task hubs.
 
 ### Emulator for local development
 
@@ -160,7 +160,7 @@ Stale orchestration data should be purged periodically to ensure efficient stora
 
     You're limited in how many task hubs you can use depending on your billing SKU. 
 
-     - [When using the Dedicated SKU,](./durable-task-scheduler-dedicated-sku.md#dedicated-sku) task hubs are limited to 15. 
+     - [When using the Dedicated SKU,](./durable-task-scheduler-dedicated-sku.md#dedicated-sku) task hubs are limited to 25. 
      - [When using the Consumption SKU,](./durable-task-scheduler-dedicated-sku.md#consumption-sku-preview) task hubs are limited to 5. 
 
     For more quota, [contact support](https://github.com/Azure/azure-functions-durable-extension/issues).