Support for native Azure Functions deployment in .NET Aspire (serverless model, not only ACA)
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 991
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 196
Description
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Is your feature request related to a problem? Please describe the problem.
I am trying to use Azure Functions together with .NET Aspire for orchestration and deployment.
Currently, Azure Functions integration in Aspire is only available as preview and only supports deployment as containers into Azure Container Apps (ACA).
There is no way to deploy an Azure Functions project directly to Azure Functions in the serverless model.
This limitation makes it difficult to adopt Aspire in scenarios where teams already rely on native Azure Functions and don’t want to containerize them just for orchestration.
Reference: [Issue #920](https://github.com/dotnet/aspire/issues/920?utm_source=chatgpt.com)
– this was not targeted for 9.0 GA.
Documentation: [Azure Functions integration with .NET Aspire](https://learn.microsoft.com/en-us/azure/azure-functions/dotnet-aspire-integration?utm_source=chatgpt.com)
– clearly states ACA-only deployment.
### Describe the solution you'd like
Add support in .NET Aspire to deploy Azure Functions projects directly to Azure Functions (serverless runtime), in addition to the existing ACA container option.
Support deployment to native Azure Functions as first-class target.
Provide parity with existing triggers (HTTP, Timer, Blob, Queue, Cosmos DB, Service Bus, Event Hub).
Offer tooling and guidance for production scenarios where Aspire orchestrates both serverless and container-based workloads.
### Additional context
Benefits of adding this support:
Makes Aspire attractive for hybrid apps that mix Functions and containerized services.
Aligns Aspire with the core Azure Functions use case (serverless, event-driven applications).
Reduces friction for developers who already rely on Azure Functions and don’t want to containerize them unnecessarily.
Contributor guide
Assessment
This issue has not been assessed yet.