Skip to content

Commit bb7d8db

Browse files
committed
update
Signed-off-by: Hannah Hunter <[email protected]>
1 parent 588559e commit bb7d8db

3 files changed

Lines changed: 6 additions & 6 deletions

File tree

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -286,10 +286,10 @@ If you are not seeing the throughput numbers you expect and your CPU and memory
286286
> [!TIP]
287287
> In some cases you can significantly increase the throughput of external events, activity fan-in, and entity operations by increasing the value of the `controlQueueBufferThreshold` setting in **host.json**. Increasing this value beyond its default causes the Durable Task Framework storage provider to use more memory to prefetch these events more aggressively, reducing delays associated with dequeueing messages from the Azure Storage control queues. For more information, see the [host.json](durable-functions-bindings.md#host-json) reference documentation.
288288
289-
### Flex Consumption Plan
290-
The [Flex Consumption plan](../flex-consumption-plan.md) is an Azure Functions hosting plan that provides many of the benefits of the Consumption plan, including a serverless billing model, while also adding useful features, such as private networking, instance memory size selection, and full support for managed identity authentication.
289+
### Flex Consumption Plan (supported by Durable Task Scheduler)
290+
The [Flex Consumption plan](../flex-consumption-plan.md), which is supported by Durable Task Scheduler, is an Azure Functions hosting plan that provides many of the benefits of the Consumption plan, including a serverless billing model, while also adding useful features, such as private networking, instance memory size selection, and full support for managed identity authentication.
291291

292-
You should follow these performance recommendations when hosting Durable Functions in the Flex Consumption plan:
292+
You should follow these performance recommendations when hosting Durable Functions in the Flex Consumption plan (supported by Durable Task Scheduler):
293293

294294
* Set the [always ready instance count](../flex-consumption-how-to.md#set-always-ready-instance-counts) for the `durable` group to `1`. This ensures that there is always one instance ready to handle Durable Functions related requests, thus reducing the application's cold start.
295295
* Reduce the [queue polling interval](durable-functions-azure-storage-provider.md#queue-polling) to 10 seconds or less. Since this plan type is more sensitive to queue polling delays, lowering the polling interval will help increase the frequency of polling operations, thus ensuring requests are handled faster. However, more frequent polling operations will lead to a higher Azure Storage account cost.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -179,7 +179,7 @@ There are many significant tradeoffs between the various supported storage provi
179179
| Price-performance configurable? | ❌ No | ✅ Yes (Event Hubs TUs and CUs) | ✅ Yes (SQL vCPUs) | Coming soon! |
180180
| Disconnected environment support | ❌ Azure connectivity required | ❌ Azure connectivity required | ✅ Fully supported | ❌ Azure connectivity required |
181181
| Identity-based connections | ✅ Fully supported |❌ Not supported | ⚠️ Requires runtime-driven scaling | ✅ Fully supported |
182-
| [Flex Consumption plan](../flex-consumption-plan.md) | ✅ Fully supported ([see notes](./durable-functions-azure-storage-provider.md#flex-consumption-plan)) |❌ Not supported | ✅ Fully supported | ❌ Not supported |
182+
| [Flex Consumption plan](../flex-consumption-plan.md) | ✅ Fully supported ([see notes](./durable-functions-azure-storage-provider.md#flex-consumption-plan)) |❌ Not supported | ✅ Fully supported | ✅ Fully supported |
183183

184184
## Next steps
185185

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -299,7 +299,7 @@ az role assignment create --assignee "$clientId" --role "Storage Blob Data Owner
299299

300300
#### Azure SQL Database
301301
>[!NOTE]
302-
> 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.
302+
> 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. The Flex Consumption plan is supported by Durable Task Scheduler.
303303
304304
1. Start by setting your developer identity as the database's admin.
305305

@@ -347,7 +347,7 @@ If you're using user-assigned managed identity to authenticate to the SQL databa
347347
sqlconnstr="Server=tcp:$dbserver.database.windows.net,1433;Initial Catalog=$sqlDB;Persist Security Info=False;User ID=$clientId;MultipleActiveResultSets=False;Encrypt=True;TrustServerCertificate=False;Authentication='Active Directory Managed Identity';"
348348
```
349349

350-
For Flex Consumption apps, use a connection string to authenticate for now. You can find it by going to the SQL database resource on Azure portal, navigating to the **Settings** tab, then clicking on **Connection strings**:
350+
For Flex Consumption apps (supported by Durable Task Scheduler), use a connection string to authenticate for now. You can find it by going to the SQL database resource on Azure portal, navigating to the **Settings** tab, then clicking on **Connection strings**:
351351

352352
:::image type="content" source="./media/quickstart-mssql/mssql-azure-db-connection-string.png" alt-text="Screenshot showing database connection string.":::
353353

0 commit comments

Comments
 (0)