Skip to content

Commit b85fd69

Browse files
committed
Revised table and added support defs table
1 parent 8abdf9e commit b85fd69

File tree

1 file changed

+17
-16
lines changed

1 file changed

+17
-16
lines changed

articles/azure-functions/extension-bundles.md

Lines changed: 17 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -27,16 +27,18 @@ You define an extension bundle reference in the *host.json* project file by addi
2727

2828
## Supported extension bundles
2929

30-
This table lists the default `Microsoft.Azure.Functions.ExtensionBundle` bundles that are currently GA and any known end-of-support dates.
30+
This table lists all `Microsoft.Azure.Functions.ExtensionBundle` bundle versions and the current [support status](#support-policy).
3131

32-
| Bundle version | Version in host.json | Included extensions | End-of-support date |
32+
| Bundle version | Version in host.json | Support state | End-of-support date |
3333
| --- | --- | --- | --- |
34-
| 4.x | `[4.0.0, 5.0.0)` | See [extensions.json](https://github.com/Azure/azure-functions-extension-bundles/blob/main/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) used to generate the bundle. | Not yet determined |
35-
| 3.x | `[3.3.0, 4.0.0)` | See [extensions.json](https://github.com/Azure/azure-functions-extension-bundles/blob/main-v3/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) used to generate the bundle. | 05/30/2026 |
36-
| 2.x | `[2.*, 3.0.0)` | See [extensions.json](https://github.com/Azure/azure-functions-extension-bundles/blob/main-v2/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) used to generate the bundle. | 05/30/2026 |
37-
| 1.x | `[1.*, 2.0.0)` | See [extensions.json](https://github.com/Azure/azure-functions-extension-bundles/blob/v1.x/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) used to generate the bundle. | 05/30/2026 |
34+
| [4.x](https://github.com/Azure/azure-functions-extension-bundles/blob/main/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[4.0.0, 5.0.0)` | Active | Not yet determined |
35+
| [3.x](https://github.com/Azure/azure-functions-extension-bundles/blob/main-v3/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[3.3.0, 4.0.0)` | Deprecated | 05/30/2026 |
36+
| [2.x](https://github.com/Azure/azure-functions-extension-bundles/blob/main-v2/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[2.*, 3.0.0)` | Deprecated | 05/30/2026 |
37+
| [1.x](https://github.com/Azure/azure-functions-extension-bundles/blob/v1.x/src/Microsoft.Azure.Functions.ExtensionBundle/extensions.json) | `[1.*, 2.0.0)` | Deprecated | 05/30/2026 |
3838

39-
The default extension bundles are defined using version ranges, and this table links to the extension definitions for the bundle. For more information, see [Support policy](#support-policy).
39+
The default extension bundles are defined using version ranges. Select the **Bundle version** to see the _extensions.json_ definition file used to generate the current major extension bundle version.
40+
41+
For more information, see [Support policy](#support-policy).
4042

4143
## Extension bundles considerations
4244

@@ -69,19 +71,18 @@ Keep these considerations in mind when choosing to use a non-GA extension bundle
6971

7072
## Support policy 
7173

72-
Major version releases of extension bundles can occur when there are breaking changes or updates in the dependencies of the underlying binding extensions. These breaking changes, often introduced in Azure SDKs, require updates to the bundle to remain compatible.
73-
74-
Each major version of an extension bundle is supported for a minimum of 12 months after the next major version is released. This overlap period gives you time to plan, test, and upgrade your apps before the previous version is retired.
74+
Major version releases of extension bundles can occur when there are breaking changes or updates in the dependencies of the underlying binding extensions. These breaking changes, often introduced in Azure SDKs, require updates to the bundle to remain compatible.
7575

7676
You can view the extension bundle versions and their included extensions in the [Azure Functions Extension Bundles GitHub repo](https://github.com/Azure/azure-functions-extension-bundles/releases). Individual .NET packages are found on [https://nuget.org](https://nuget.org).
7777

78-
### Notification phase 
79-
80-
Microsoft provides advance notice before retiring an extension bundle or binding extension version. When you receive such a notification, you should begin planning to upgrade your function apps to a latest supported extension bundle version. This upgrade ensures that your apps continue to access new features, performance improvements, and support.
81-
82-
### Retirement phase 
78+
The removal of support for previously GA bundles follows these phases:
8379

84-
After the retirement of an extension bundle or binding extension version, function apps that use retired versions can still be created and deployed and continue to run on the platform. However, your function apps aren’t eligible for new features, security patches, and performance optimizations until you upgrade them to use a supported extension bundle version. You must upgrade your functions apps to a supported bundle version before you can receive support.
80+
| Phase | Description |
81+
| ----- | ----- |
82+
| Active | This is the latest GA extension bundle version, and it is the recommended version for your function apps. Bundle versions remain active for at least 12 months after being declared GA. |
83+
| Notification| Microsoft provides advanced notice before retiring an extension bundle or binding extension version. When you receive such a notification, you should begin planning to upgrade your function apps to a latest supported extension bundle version. This upgrade ensures that your apps continue to access new features, performance improvements, and support. |
84+
| Deprecation phase | Occurs 12 months after the next major version of an extension bundle moves into GA. This overlap period gives you time to plan, test, and upgrade your apps before the previous version is retired. |
85+
| Retirement phase | After the retirement of an extension bundle or binding extension version, function apps that use retired versions can still be created and deployed and continue to run on the platform. However, your function apps aren’t eligible for new features, security patches, and performance optimizations until you upgrade them to use a supported extension bundle version. You must upgrade your functions apps to a supported bundle version before you can receive support.|
8586

8687
## Related articles
8788

0 commit comments

Comments
 (0)