Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems. Azure Functions allows developers to take action by connecting to data sources or messaging solutions, thus making it easy to process and react to events. Azure Functions scale based on demand and you pay only for the resources you consume.
This repository acts as a directory for folks looking for the various resources we have for Azure Functions.
To get started with Azure Functions, you can visit functions.azure.com and click on the green Get Started button. If you need a trial Azure subscription, there is also a link on that page.
Visit azure.com for the primary Azure Functions documentation page.
If you would like documentation on the Functions runtime oriented towards contributors, those are hosted in the Azure WebJobs SDK script GitHub wiki.
If you have questions about Azure Functions, we encourage you to reach out to the community and Azure Functions dev team for help.
While we do our best to help out in a timely basis, we don't have any promise around the above resources. If you need an SLA on support from us, it's recommended you invest in an Azure Support plan.
We track functional issues in a variety of places for Azure Functions. If you have found an issue or have a feature request, please submit an issue to the below repositories.
[!IMPORTANT] Have a platform-level issue? GitHub issues are for clear, reproducible bugs and feature requests in the code owned by the repositories below. They are not the right place for Azure Functions platform-level concerns, such as:
- Deployments (including remote build, OneDeploy,
RuntimeFailed/ExpectationFailedcontroller errors)- Scaling, cold start, or instance/availability behavior
- ARM / control plane operations, provisioning, or configuration
- Portal, billing, quotas, networking, or storage infrastructure
For these concerns, please open a formal Azure support case so the appropriate team can investigate with access to your resources and telemetry. Support cases are the fastest path to resolution and let us handle resource-specific data privately. Platform issues opened on GitHub will typically be redirected to support.
| Item | Description | Link |
|---|---|---|
| Documentation | Docs for Azure Functions features + getting started | File an Issue |
| Runtime | Script Host, Triggers & Bindings, Language Support | File an Issue |
| Core Tools | Command line interface for local development | File an Issue |
| Dev Tools | Visual Studio and VS Code | File an Issue |
| Portal | User Interface or Experience Issue | File an Issue |
| Templates | Code Issues with Creation Template | File an Issue |
| Azure CLI | Create and manage function apps in Azure (az functionapp) | File and Issue |
[!NOTE] The table above lists the most common areas. If your issue is with a binding/trigger extension (for example Storage, Event Grid, Event Hubs, Service Bus, Cosmos DB, Timer, or Durable Functions) or another part of the product not listed here, find the owning repository in the GitHub repositories list below and file your issue there.
Before filing an issue, please check that it doesn't already exist. If you're not sure if you should file an issue, you can open up an MSDN forum question. We also have a uservoice feedback site which we can track your feature requests through.
azure-functions Stack Overflow tag94 followers · starred Aug 2017
357 followers · starred May 2016
96 followers · starred Sep 2019
62 followers · starred Apr 2024
Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems. Azure Functions allows developers to take action by connecting to data sources or messaging solutions, thus making it easy to process and react to events. Azure Functions scale based on demand and you pay only for the resources you consume.
This repository acts as a directory for folks looking for the various resources we have for Azure Functions.
To get started with Azure Functions, you can visit functions.azure.com and click on the green Get Started button. If you need a trial Azure subscription, there is also a link on that page.
Visit azure.com for the primary Azure Functions documentation page.
If you would like documentation on the Functions runtime oriented towards contributors, those are hosted in the Azure WebJobs SDK script GitHub wiki.
If you have questions about Azure Functions, we encourage you to reach out to the community and Azure Functions dev team for help.
While we do our best to help out in a timely basis, we don't have any promise around the above resources. If you need an SLA on support from us, it's recommended you invest in an Azure Support plan.
We track functional issues in a variety of places for Azure Functions. If you have found an issue or have a feature request, please submit an issue to the below repositories.
[!IMPORTANT] Have a platform-level issue? GitHub issues are for clear, reproducible bugs and feature requests in the code owned by the repositories below. They are not the right place for Azure Functions platform-level concerns, such as:
- Deployments (including remote build, OneDeploy,
RuntimeFailed/ExpectationFailedcontroller errors)- Scaling, cold start, or instance/availability behavior
- ARM / control plane operations, provisioning, or configuration
- Portal, billing, quotas, networking, or storage infrastructure
For these concerns, please open a formal Azure support case so the appropriate team can investigate with access to your resources and telemetry. Support cases are the fastest path to resolution and let us handle resource-specific data privately. Platform issues opened on GitHub will typically be redirected to support.
| Item | Description | Link |
|---|---|---|
| Documentation | Docs for Azure Functions features + getting started | File an Issue |
| Runtime | Script Host, Triggers & Bindings, Language Support | File an Issue |
| Core Tools | Command line interface for local development | File an Issue |
| Dev Tools | Visual Studio and VS Code | File an Issue |
| Portal | User Interface or Experience Issue | File an Issue |
| Templates | Code Issues with Creation Template | File an Issue |
| Azure CLI | Create and manage function apps in Azure (az functionapp) | File and Issue |
[!NOTE] The table above lists the most common areas. If your issue is with a binding/trigger extension (for example Storage, Event Grid, Event Hubs, Service Bus, Cosmos DB, Timer, or Durable Functions) or another part of the product not listed here, find the owning repository in the GitHub repositories list below and file your issue there.
Before filing an issue, please check that it doesn't already exist. If you're not sure if you should file an issue, you can open up an MSDN forum question. We also have a uservoice feedback site which we can track your feature requests through.
azure-functions Stack Overflow tag94 followers · starred Aug 2017
357 followers · starred May 2016
96 followers · starred Sep 2019
62 followers · starred Apr 2024