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
We have identified that a subset of customers have incorrectly configured V1 Function Apps. User action is required to configure these applications correctly to avoid potential impact. In the coming days this will start redirecting to ~2 which will break the large majority of apps with this setting.
Function Apps use the FUNCTIONS_EXTENSION_VERSION app setting to control which version of functions the app runs on. A V1 Function App should have this setting set to ~1. It should look like this:
and this:
Take Action
If you have a V1 app and you don't have this setting, fix it. Make sure it is set to ~1. Don't use values such as "latest" or "" (i.e. empty string).
If you have an automated deployment of any kind, make sure that your automated deployment is setting this correctly. We've seen cases where ARM templates are being executed that are missing this setting.
Also if you have a V2 app, you should set it to ~2 instead of "beta". That will prevent your V2 app from running into similar issues in the future.
We have identified that a subset of customers have incorrectly configured V1 Function Apps. User action is required to configure these applications correctly to avoid potential impact. In the coming days this will start redirecting to ~2 which will break the large majority of apps with this setting.
Function Apps use the FUNCTIONS_EXTENSION_VERSION app setting to control which version of functions the app runs on. A V1 Function App should have this setting set to ~1. It should look like this:
and this:
Take Action
If you have a V1 app and you don't have this setting, fix it. Make sure it is set to ~1. Don't use values such as "latest" or "" (i.e. empty string).
If you have an automated deployment of any kind, make sure that your automated deployment is setting this correctly. We've seen cases where ARM templates are being executed that are missing this setting.
Also if you have a V2 app, you should set it to ~2 instead of "beta". That will prevent your V2 app from running into similar issues in the future.
Questions?
Please use Azure/app-service-announcements-discussions#69 for discussion of this announcement.
The text was updated successfully, but these errors were encountered: