Title: [Azure Functions] Simplify large-payload configuration by reusing an existing storage connection · Issue #271 · microsoft/durabletask-python · GitHub
Open Graph Title: [Azure Functions] Simplify large-payload configuration by reusing an existing storage connection · Issue #271 · microsoft/durabletask-python
X Title: [Azure Functions] Simplify large-payload configuration by reusing an existing storage connection · Issue #271 · microsoft/durabletask-python
Description: Community feedback wanted Would you use a simpler way to configure large-payload storage in the azure-functions-durable v2 SDK using a storage connection your Function App already has? Please add a thumbs-up reaction to this issue if thi...
Open Graph Description: Community feedback wanted Would you use a simpler way to configure large-payload storage in the azure-functions-durable v2 SDK using a storage connection your Function App already has? Please add a...
X Description: Community feedback wanted Would you use a simpler way to configure large-payload storage in the azure-functions-durable v2 SDK using a storage connection your Function App already has? Please add a...
Opengraph URL: https://github.com/microsoft/durabletask-python/issues/271
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Azure Functions] Simplify large-payload configuration by reusing an existing storage connection","articleBody":"## Community feedback wanted\n\nWould you use a simpler way to configure large-payload storage in the `azure-functions-durable` v2 SDK using a storage connection your Function App already has?\n\n**Please add a thumbs-up reaction to this issue if this would help, and comment with your use case.** In particular:\n\n- Would you use the Function App's host storage (`AzureWebJobsStorage`), a separate Azure Storage backend account, or another named connection?\n- Do you use a connection string, system-assigned managed identity, or user-assigned managed identity? Is local development with Azurite important?\n- Would explicitly choosing a connection name be sufficient, or is automatic discovery of the Durable backend's account important?\n- Is constructing a `BlobPayloadStore` explicitly a meaningful obstacle today?\n\nThis issue is gathering demand and requirements, not committing to an API or delivery timeline.\n\n## Context\n\nPR #270 adds explicit configuration through `DFApp.configure_large_payloads(payload_store=...)`. We are keeping that implementation simple: applications supply their own payload store.\n\nA potential follow-up would reuse existing Functions storage configuration so users do not need to construct a blob store or repeat connection-resolution code. Host storage and the Azure Storage Durable backend often use the same account, but can be configured separately.\n\n## Possible direction\n\nIllustrative API only; these convenience forms are not implemented:\n\n```python\napp.configure_large_payloads() # Opt in, using AzureWebJobsStorage\n\napp.configure_large_payloads(connection_name=\"DurableStorage\")\n```\n\nCalling the API would remain an explicit opt-in to SDK payload externalization. The existing `payload_store=...` form would remain available for full control, mutually exclusive with connection-based configuration.\n\nAutomatic discovery of the Azure Storage backend's account is a separate option to evaluate based on feedback, rather than a prerequisite for a named-connection helper.\n\n## Design considerations\n\n- Resolve both connection strings and identity-based connection settings, including identity selection and local development behavior.\n- Backend discovery would need to honor effective host configuration, environment overrides, and supported aliases. The Python SDK does not currently receive a resolved backend storage configuration.\n- Account selection must be stable across workers and deployments so existing payload references remain readable. Client bindings targeting other connections also need consideration because payload configuration is currently process-wide.\n- Use a dedicated SDK payload container, not the backend's large-message container. Sharing an account does not make backend purge clean up SDK payload blobs; permissions and retention remain important.\n- Azure Storage backend large-message handling and SDK payload externalization are separate mechanisms. This proposal only simplifies configuration of the latter.\n\nReferences: [Functions host storage settings](https://learn.microsoft.com/en-us/azure/azure-functions/functions-app-settings#azurewebjobsstorage) and [Durable Azure Storage connection configuration](https://learn.microsoft.com/en-us/azure/durable-task/durable-functions/durable-functions-azure-storage-provider#connections).","author":{"url":"https://github.com/andystaples","@type":"Person","name":"andystaples"},"datePublished":"2026-09-24T00:50:13Z","url":"https://github.com/microsoft/durabletask-python/issues/271"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:e1cc605d-4e9f-d923-b96e-36d587bcdd1a |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | AA8E:1F42:6E964:9967F:6AFE1E88 |
| html-safe-nonce | 422217606fced2d29941368081336795d5dfe6fd1922e3ed568cd34baa3feaf7 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBQThFOjFGNDI6NkU5NjQ6OTk2N0Y6NkFGRTFFODgiLCJ2aXNpdG9yX2lkIjoiNzU1OTc2MTg2NzIzMzQzNTI3MiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 472d10d9f8e842f4c4ffb974c98ed811bde3f5e5a3fc077ff8aa837e329fe561 |
| hovercard-subject-tag | issue:5561407756 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/microsoft/durabletask-python/271/issue_layout |
| twitter:image | https://opengraph.githubassets.com/2f526428e4462d2093c9a9dc375c9a178ba51d1fe4da2f503b6bc19a662f44b9/microsoft/durabletask-python/issues/271 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/2f526428e4462d2093c9a9dc375c9a178ba51d1fe4da2f503b6bc19a662f44b9/microsoft/durabletask-python/issues/271 |
| og:image:alt | Community feedback wanted Would you use a simpler way to configure large-payload storage in the azure-functions-durable v2 SDK using a storage connection your Function App already has? Please add a... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | andystaples |
| hostname | github.com |
| expected-hostname | github.com |
| None | d0525ab1464526bf4532a5551aa348cf100dff75ef808a96fc67a08b1d946aa9 |
| turbo-cache-control | no-preview |
| go-import | github.com/microsoft/durabletask-python git https://github.com/microsoft/durabletask-python.git |
| octolytics-dimension-user_id | 6154722 |
| octolytics-dimension-user_login | microsoft |
| octolytics-dimension-repository_id | 627664515 |
| octolytics-dimension-repository_nwo | microsoft/durabletask-python |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 627664515 |
| octolytics-dimension-repository_network_root_nwo | microsoft/durabletask-python |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | fef3993a71fa20f7be8e167132fbf9619bc66e12 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width