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/language-support-policy.md
+3-11Lines changed: 3 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,21 +11,19 @@ This article explains Azure functions language runtime support policy.
11
11
12
12
## Retirement process
13
13
14
-
Azure Functions runtime is built around various components, including operating systems, the Azure Functions host, and language-specific workers. To maintain full support coverages for function apps, Azure Functions uses a phased reduction in support as programming language versions reach their end-of-life dates. For most language versions, the retirement date coincides with the community end-of-life date.
14
+
Azure Functions runtime is built around various components, including operating systems, the Azure Functions host, and language-specific workers. To maintain full support coverages for function apps, Azure Functions support aligns with end-of-life support for a given language. To acheive this, Functions implements a phased reduction in support as programming language versions reach their end-of-life dates. For most language versions, the retirement date coincides with the community end-of-life date.
15
15
16
16
### Notification phase
17
17
18
18
We'll send notification emails to function app users about upcoming language version retirements. The notifications will be at least one year before the date of retirement. Upon the notification, you should prepare to upgrade the language version that your functions apps use to a supported version.
19
19
20
20
### Retirement phase
21
21
22
-
Starting on the end-of-life date for a language version, you can no longer create new function apps targeting that language version.
23
-
24
-
After the language end-of-life date, function apps that use retired language versions won't be eligible for new features, security patches, and performance optimizations. However, these function apps will continue to run on the platform.
22
+
After the language end-of-life date, function apps that use retired language versions can still be created and continue to run on the platform, however they won't be eligible for new features, security patches, and performance optimizations.
25
23
26
24
> [!IMPORTANT]
27
25
>You're highly encouraged to upgrade the language version of your affected function apps to a supported version.
28
-
>If you're running functions apps using an unsupported language version, you'll be required to upgrade before receiving support for the function apps.
26
+
>If you're running functions apps using an unsupported language version, you'll be required to upgrade before receiving support for your function app.
29
27
30
28
31
29
## Retirement policy exceptions
@@ -34,15 +32,9 @@ There are few exceptions to the retirement policy outlined above. Here is a list
0 commit comments