Merge pull request #312727 from hhunter-ms/flex-consumption-typo

[Durable] Fix some typos around hosting plans

Author: prmerger-automator[bot]

articles/azure-functions/durable/durable-functions-azure-storage-provider.md

@@ -201,7 +201,7 @@ Durable Functions creates the queues, tables, and blobs it uses in a configured
 - The `durableTask/storageProvider/connectionStringName` setting (Durable Functions 2.x)
 - The `durableTask/azureStorageConnectionStringName` setting (in Durable Functions 1.x)
 
-# [Durable Functions 2.x](#tab/durable-2x)
+### [Durable Functions 2.x](#tab/durable-2x)
 
 ```json
 {
@@ -215,7 +215,7 @@ Durable Functions creates the queues, tables, and blobs it uses in a configured
 }
 ```
 
-# [Durable Functions 1.x](#tab/durable-1x)
+### [Durable Functions 1.x](#tab/durable-1x)
 
 ```json
 {
@@ -243,7 +243,7 @@ While you can scale out activity functions infinitely by adding more virtual mac
 
 You define the number of control queues in your `host.json` file. The following example `host.json` snippet sets the `durableTask/storageProvider/partitionCount` property (`durableTask/partitionCount` in Durable Functions 1.x) to `3`. You have as many control queues as you have partitions.
 
-# [Durable Functions 2.x](#tab/durable-2x)
+### [Durable Functions 2.x](#tab/durable-2x)
 
 ```json
 {
@@ -257,7 +257,7 @@ You define the number of control queues in your `host.json` file. The following
 }
 ```
 
-# [Durable Functions 1.x](#tab/durable-1x)
+### [Durable Functions 1.x](#tab/durable-1x)
 
 ```json
 {
@@ -310,7 +310,7 @@ Orchestration instances and entities are distributed across all control queue in
 
 You can enable extended sessions by setting `durableTask/extendedSessionsEnabled` to `true` in your `host.json` file. You can use the `durableTask/extendedSessionIdleTimeoutInSeconds` setting to control how long an idle session stays in memory:
 
-# [Durable Functions 2.x](#tab/durable-2x)
+### [Durable Functions 2.x](#tab/durable-2x)
 ```json
 {
   "extensions": {
@@ -322,7 +322,7 @@ You can enable extended sessions by setting `durableTask/extendedSessionsEnabled
 }
 ```
 
-# [Durable Functions 1.x](#tab/durable-1x)
+### [Durable Functions 1.x](#tab/durable-1x)
 ```json
 {
   "extensions": {

articles/azure-functions/durable/durable-functions-storage-providers.md

@@ -121,7 +121,7 @@ You can use the following table to understand the significant tradeoffs between
 | Price-performance configurable? | Coming soon! | ❌ No | ✅ Yes (SQL vCPUs) | ✅ Yes (Event Hubs TUs and CUs) | 
 | Disconnected environment support | ❌ Azure connectivity required | ❌ Azure connectivity required | ✅ Fully supported | ❌ Azure connectivity required |
 | Identity-based connections | ✅ Fully supported | ✅ Fully supported | ⚠️ Requires runtime-driven scaling | ❌ Not supported |
-| [Flex Consumption plan](../flex-consumption-plan.md) | ❌ Not supported | ✅ Fully supported ([see notes](./durable-functions-azure-storage-provider.md#flex-consumption-plan)) | ✅ Fully supported | ❌ Not supported |
+| [Flex Consumption plan](../flex-consumption-plan.md) | ✅ Fully supported | ✅ Fully supported ([see notes](./durable-functions-azure-storage-provider.md#flex-consumption-plan)) | ✅ Fully supported | ❌ Not supported |
 
 ::: zone-end
 

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

@@ -132,9 +132,6 @@ The Durable Task Scheduler emulator is only available as a Docker image today.
 
    #### [Consumption SKU](#tab/consumption)
 
-   > [!NOTE]
-   > The Consumption SKU is currently in preview. [Learn more about the SKU and orchestration framework combinations recommended for production use.](./durable-task-scheduler-billing.md)
-
     ```azurecli
     az durabletask scheduler create --name "YOUR_SCHEDULER" --resource-group "YOUR_RESOURCE_GROUP" --location "LOCATION" --ip-allowlist "[0.0.0.0/0]" --sku-name "consumption"
     ```

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

@@ -19,7 +19,7 @@ The Durable Task Scheduler is a managed backend service that persists orchestrat
 The [Durable Task Scheduler](./durable-task-scheduler.md) is a purpose-built backend as a service that persists orchestration state for your Durable Task SDK applications. The Durable Task Scheduler offers two pricing models to accommodate different service requirements, usage patterns, and preferred billing models:
 
 - [Dedicated](#dedicated-sku)
-- [Consumption (preview)](#consumption-sku)
+- [Consumption](#consumption-sku)
 
 ## What is an action?
 
@@ -106,9 +106,6 @@ A software as a service (SaaS) platform supports 800 million orchestrations mont
 
 ## Consumption SKU
 
-> [!NOTE]
-> The Consumption SKU is currently in preview. [Learn more about the SKU and orchestration framework recommended for production use.](../choose-orchestration-framework.md)
-
 The Consumption SKU offers a pay-as-you-use model, ideal for variable workloads and development scenarios. 
 
 Currently, you're limited to 10 schedulers and five task hubs per region per subscription when using the Consumption SKU. For more quota, [contact support](https://github.com/Azure/azure-functions-durable-extension/issues).

articles/azure-functions/durable/quickstart-mssql.md

@@ -299,7 +299,7 @@ az role assignment create --assignee "$clientId" --role "Storage Blob Data Owner
 
 #### Azure SQL Database
 >[!NOTE]
-> Authenticating to Azure SQL database using managed identity is _not_ supported when hosting a Durable Functions app in the Flex Consumption plan. If your app is hosted in the Flex Consumption plan, skip to the [set app settings](#set-required-app-settings) section. 
+> Authenticating to Azure SQL database using managed identity is _not_ supported when hosting a Durable Functions app in the Flex Consumption plan. If your app is hosted in the Flex Consumption plan, skip to the [set app settings](#set-required-app-settings) section. If you'd like to use it, the Flex Consumption plan is supported by Durable Task Scheduler.
 
 1. Start by setting your developer identity as the database's admin.