Learn about important Azure product updates, roadmap, and announcements. Subscribe to notifications to stay informed.
The TypeScript developer experience in Azure Functions has improved. New tools include the Azure Functions Core Tools and the Azure Functions Extension for Visual Studio Code, as well as a npm package that contains type definitions for using TypeScript with Azure Functions and some npm scripts to abstract some func commands.
Azure Functions now has GA support for Java development on the Functions 2.0 runtime.
The Serverless Community Library is an open-source set of prebuilt components based on common use cases using Functions and Logic Apps.
Azure Functions now supports Python development on the Functions 2.0 runtime.
Use managed identities with Linux apps and use user-assigned identities on the App Service platform, including Azure Functions hosted under an App Service plan.
Azure Key Vault integration with Azure Functions lets you build more secure serverless applications out of the box, taking advantage of secrets management to get the benefits of rotation policies and centralized access control.
Azure Functions runtime 2.0 is now available on IoT Edge.
The cross platform and improved Azure Functions runtime is now generally available, allowing you to use your cross-platform .NET Core assets within your Functions apps.
Azure Functions will now support consumption plan for deploying to Linux.
Azure Functions now supports Python development using Python 3.6 on the Functions v2 (cross-platform) runtime.
The upcoming release of the Azure Functions Runtime 2.0 introduces some major improvements, but some of these changes will cause breaks to existing apps deployed with the v2 runtime.
The .NET Framework 4.7.2 update is scheduled to deploy to Azure App Service apps gradually during September 2018.
A new version of the Azure Functions Runtime will be deployed soon. It uses the latest version of Azure Java Functions Library v1.0.0-beta-5, which has breaking changes that affect HttpTrigger Java functions.
App Service and Azure Functions support of Managed Service Identity (MSI) is now generally available.
Starting June 30, all new apps in Azure App Service will be created with TLS 1.2 by default.
We recently announced that all Azure App Service and Azure Functions apps could update TLS configuration. Reporting tools should now correctly indicate that lower versions of TLS are blocked.
HTTP/2 configuration is available in the Azure portal, to make the selection of HTTP/2 a seamless process with just a few clicks of the mouse.
Sites that have SNI-SSL selected will not be able to work with TLS 1.0 selected, if receiving traffic from older browser versions.