You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/extension-bundles.md
+18-3Lines changed: 18 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Azure Functions Extension Bundles
3
3
description: Learn how to use extension bundles to make the correct set of Azure Functions trigger and binding extensions available in your non-.NET function code.
4
4
ms.topic: concept-article
5
-
ms.date: 05/30/2025
5
+
ms.date: 07/25/2025
6
6
7
7
#Customer intent: I want to understand how to correctly install extension bundles so that the functionality implemented in the extensions is available to my functions in my preferred development language.
8
8
---
@@ -19,7 +19,7 @@ Extension bundles add a predefined set of compatible binding extensions to your
19
19
20
20
When you create an Azure Functions project from a non-.NET template, extension bundles are already enabled in the app's `host.json` file.
21
21
22
-
## Defining an extension bundle reference
22
+
## Define an extension bundle reference
23
23
24
24
You define an extension bundle reference in the `host.json` project file by adding an `extensionBundle` section, as in this example:
25
25
@@ -46,7 +46,22 @@ Keep these considerations in mind when you work with extension bundles:
46
46
- Use the latest version range to obtain optimal app performance and access to the latest features.
47
47
- In the unlikely event that you can't use an extension bundle, you must instead [explicitly install extensions](./functions-bindings-register.md#explicitly-install-extensions).
48
48
49
-
## Previewing extension bundles
49
+
## Upgrade extension bundles
50
+
51
+
It's important to keep your bundle version up-to-date so that your apps can continue to be eligible for new features, security patches, and performance optimizations.
52
+
53
+
To upgrade your app to the most recent bundle, edit the host.json file in the root of your app project. Replace the value of `extensionBundle.version` with the most recent [supported extension bundles version](#supported-extension-bundles).
54
+
55
+
Keep these considerations in mind when upgrading the extension bundle version used by your app:
56
+
57
+
+ The contents of the latest 4.x bundle can always be found at [this release page in the repo](https://github.com/Azure/azure-functions-extension-bundles/releases/latest).
58
+
+ Review the reference documentation for any extensions used by your app to look for any breaking changes between versions. For the list of extension versions included in the default bundle, see the `extension.json` project file linked [from this table](#supported-extension-bundles). You can also review the [bundle releases page](https://github.com/Azure/azure-functions-extension-bundles/releases) in the bundles repo for a specific bundle version tags.
59
+
+ Always verify your app locally after upgrading the bundle version to ensure compatibility with the updated extensions. You can use the [func start](functions-core-tools-reference.md#func-start) command in Azure Functions Core Tools or F5 in Visual Studio or Visual Studio Code to run your function app locally.
60
+
+ The way that you trigger extensions to be updated based on changes to the bundle version in the host.json file depends on your app environment:
61
+
+ Local project: extensions are updated locally when Core Tools starts, either from the `func start` command or when debugging in your development tools.
62
+
+ Function app: extensions are updated when you deploy the updated host.json file to your function app in Azure.
63
+
64
+
## Preview extension bundles
50
65
51
66
Prerelease versions of specific binding extensions are maintained in a preview extension bundle: `Microsoft.Azure.Functions.ExtensionBundle.Preview`. You can use this preview extension bundle to take advantage of preview extensions and new behaviors in existing extensions before they reach general availability (GA).
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-bindings-register.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ To manually install binding extensions:
60
60
61
61
1. Validate your app functionality locally and then redeploy your project, including `extensions.csproj`, to your function app in Azure.
62
62
63
-
As soon as possible, you should [switch your app back to using the latest supported extension bundle](./extension-bundles.md#defining-an-extension-bundle-reference).
63
+
As soon as possible, you should [switch your app back to using the latest supported extension bundle](./extension-bundles.md#define-an-extension-bundle-reference).
0 commit comments