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
1. Updating guidance for running locally on PS 7.2 since PS 6 is already out of support and PS 7 is reaching EOL on Dec 3 2022.
2. Updating guidance for changing PowerShell version to 7.2 (both using Portal & PowerShell cmdlet)
-------
cc: @eamonoreilly
Copy file name to clipboardExpand all lines: articles/azure-functions/functions-reference-powershell.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -397,24 +397,24 @@ You can see the current version by printing `$PSVersionTable` from any function.
397
397
398
398
To learn more about Azure Functions runtime support policy, please refer to this [article](./language-support-policy.md)
399
399
400
-
### Running local on a specific version
400
+
### Running locally on PowerShell 7.2
401
401
402
-
When running locally the Azure Functions runtime defaults to using PowerShell Core 6. To instead use PowerShell 7 when running locally, you need to add the setting `"FUNCTIONS_WORKER_RUNTIME_VERSION" : "~7"` to the `Values` array in the local.setting.json file in the project root. When running locally on PowerShell 7, your local.settings.json file looks like the following example:
402
+
When running locally, the Azure Functions runtime defaults to using PowerShell 7.0. Support for PowerShell 7.0 in Azure Functions is ending on 3 December 2022. To use PowerShell 7.2 when running locally, you need to add the setting `"FUNCTIONS_WORKER_RUNTIME_VERSION" : "~7.2"` to the `Values` array in the local.setting.json file in the project root. When running locally on PowerShell 7.2, your local.settings.json file looks like the following example:
403
403
404
404
```json
405
405
{
406
406
"IsEncrypted": false,
407
407
"Values": {
408
408
"AzureWebJobsStorage": "",
409
409
"FUNCTIONS_WORKER_RUNTIME": "powershell",
410
-
"FUNCTIONS_WORKER_RUNTIME_VERSION" : "~7"
410
+
"FUNCTIONS_WORKER_RUNTIME_VERSION" : "~7.2"
411
411
}
412
412
}
413
413
```
414
414
415
415
### Changing the PowerShell version
416
416
417
-
Your function app must be running on version 3.x to be able to upgrade from PowerShell Core 6 to PowerShell 7. To learn how to do this, see [View and update the current runtime version](set-runtime-version.md#view-and-update-the-current-runtime-version).
417
+
Support for PowerShell 7.0 in Azure Functions is ending on 3 December 2022. Your function app must be running on version 4.x to be able to upgrade to PowerShell 7.2. To learn how to do this, see [View and update the current runtime version](set-runtime-version.md#view-and-update-the-current-runtime-version).
418
418
419
419
420
420
Use the following steps to change the PowerShell version used by your function app. You can do this either in the Azure portal or by using PowerShell.
@@ -424,9 +424,9 @@ Use the following steps to change the PowerShell version used by your function a
424
424
1. In the [Azure portal](https://portal.azure.com), browse to your function app.
425
425
426
426
1. Under **Settings**, choose **Configuration**. In the **General settings** tab, locate the **PowerShell version**.
427
-
428
-
:::image type="content" source="media/functions-reference-powershell/change-powershell-version-portal.png" alt-text="Choose the PowerShell version used by the function app":::
1. Choose your desired **PowerShell Core version** and select **Save**. When warned about the pending restart choose **Continue**. The function app restarts on the chosen PowerShell version.
Replace `<SUBSCRIPTION_ID>`, `<RESOURCE_GROUP>`, and `<FUNCTION_APP>` with the ID of your Azure subscription, the name of your resource group and function app, respectively. Also, replace `<VERSION>` with either `~6` or `~7`. You can verify the updated value of the `powerShellVersion` setting in `Properties` of the returned hash table.
441
+
Replace `<SUBSCRIPTION_ID>`, `<RESOURCE_GROUP>`, and `<FUNCTION_APP>` with the ID of your Azure subscription, the name of your resource group and function app, respectively. Also, replace `<VERSION>` with `~7.2`. You can verify the updated value of the `powerShellVersion` setting in `Properties` of the returned hash table.
0 commit comments