Clarified Azure PowerShell prerequisites

Author: mikefrobbins

articles/azure-functions/create-first-function-cli-csharp-ieux.md

@@ -35,7 +35,7 @@ There is also a [Visual Studio Code-based version](create-first-function-vs-code
 
     + [Azure CLI](/cli/azure/install-azure-cli) version 2.4 or later.
 
-    + [Azure PowerShell](/powershell/azure/install-az-ps) version 5.0 or later.
+    + The Azure [Az PowerShell module](/powershell/azure/install-az-ps) version 5.9.0 or later.
 
 ---
 
@@ -57,7 +57,7 @@ Verify your prerequisites, which depend on whether you are using the Azure CLI o
 
 +**Run** `func --version` to check that the Azure Functions Core Tools are version 3.x.
 
-+ **Run** `(Get-Module -ListAvailable Az).Version` and verify version 5.0 or later. 
++ **Run** `(Get-Module -ListAvailable Az).Version` and verify version 5.0 or later.
 
 + **Run** `Connect-AzAccount` to sign in to Azure and verify an active subscription.
 
@@ -69,7 +69,7 @@ Verify your prerequisites, which depend on whether you are using the Azure CLI o
 
 In this section, you create a local <abbr title="A logical container for one or more individual functions that can be deployed and managed together.">Azure Functions project</abbr> in C#. Each function in the project responds to a specific <abbr title="An event that invokes the function’s code, such as an HTTP request, a queue message, or a specific time.">trigger</abbr>.
 
-1. Run the `func init` command to create a functions project in a folder named *LocalFunctionProj* with the specified runtime:  
+1. Run the `func init` command to create a functions project in a folder named *LocalFunctionProj* with the specified runtime:
 
     ```csharp
     func init LocalFunctionProj --dotnet
@@ -83,24 +83,24 @@ In this section, you create a local <abbr title="A logical container for one or
     <br/>
 
 1. Add a function to your project by using the following command:
-    
+
     ```console
     func new --name HttpExample --template "HTTP trigger" --authlevel "anonymous"
-    ``` 
+    ```
     The `--name` argument is the unique name of your function (HttpExample).
 
     The `--template` argument specifies the function's trigger (HTTP).
 
-    
-    <br/>   
-    <details>  
-    <summary><strong>Optional: Code for HttpExample.cs</strong></summary>  
-    
+
+    <br/>
+    <details>
+    <summary><strong>Optional: Code for HttpExample.cs</strong></summary>
+
     *HttpExample.cs* contains a `Run` method that receives request data in the `req` variable is an [HttpRequest](/dotnet/api/microsoft.aspnetcore.http.httprequest) that's decorated with the **HttpTriggerAttribute**, which defines the trigger behavior.
 
     :::code language="csharp" source="~/functions-docs-csharp/http-trigger-template/HttpExample.cs":::
-        
-    The return object is an [ActionResult](/dotnet/api/microsoft.aspnetcore.mvc.actionresult) that returns a response message as either an [OkObjectResult](/dotnet/api/microsoft.aspnetcore.mvc.okobjectresult) (200) or a [BadRequestObjectResult](/dotnet/api/microsoft.aspnetcore.mvc.badrequestobjectresult) (400). To learn more, see [Azure Functions HTTP triggers and bindings](./functions-bindings-http-webhook.md?tabs=csharp).  
+
+    The return object is an [ActionResult](/dotnet/api/microsoft.aspnetcore.mvc.actionresult) that returns a response message as either an [OkObjectResult](/dotnet/api/microsoft.aspnetcore.mvc.okobjectresult) (200) or a [BadRequestObjectResult](/dotnet/api/microsoft.aspnetcore.mvc.badrequestobjectresult) (400). To learn more, see [Azure Functions HTTP triggers and bindings](./functions-bindings-http-webhook.md?tabs=csharp).
     </details>
 
 <br/>
@@ -115,7 +115,7 @@ In this section, you create a local <abbr title="A logical container for one or
     func start
     ```
 
-    Toward the end of the output, the following lines should appear: 
+    Toward the end of the output, the following lines should appear:
 
     <pre class="is-monospace is-size-small has-padding-medium has-background-tertiary has-text-tertiary-invert">
     ...
@@ -147,7 +147,7 @@ In this section, you create a local <abbr title="A logical container for one or
 <br/>
 
 ---
-    
+
 ## 5. Create supporting Azure resources for your function
 
 Before you can deploy your function code to Azure, you need to create a <abbr title="A logical container for related Azure resources that you can manage as a unit.">resource group</abbr>, a <abbr title="An account that contains all your Azure storage data objects. The storage account provides a unique namespace for your storage data.">storage account</abbr>, and a <abbr title="The cloud resource that hosts serverless functions in Azure, which provides the underlying compute environment in which functions run.">function app</abbr> by using the following commands:
@@ -160,15 +160,15 @@ Before you can deploy your function code to Azure, you need to create a <abbr ti
     ```
 
 
-    # [Azure PowerShell](#tab/azure-powershell) 
+    # [Azure PowerShell](#tab/azure-powershell)
     ```azurepowershell
     Connect-AzAccount
     ```
 
 
     ---
 
-1. Create a resource group named `AzureFunctionsQuickstart-rg` in the `westeurope` region. 
+1. Create a resource group named `AzureFunctionsQuickstart-rg` in the `westeurope` region.
 
     # [Azure CLI](#tab/azure-cli)
 
@@ -188,7 +188,7 @@ Before you can deploy your function code to Azure, you need to create a <abbr ti
     ---
 
     You can't host Linux and Windows apps in the same resource group. If you have an existing resource group named `AzureFunctionsQuickstart-rg` with a Windows function app or web app, you must use a different resource group.
-    
+
 1. Create a general-purpose Azure Storage account in your resource group and region:
 
     # [Azure CLI](#tab/azure-cli)
@@ -215,24 +215,24 @@ Before you can deploy your function code to Azure, you need to create a <abbr ti
 **Replace** '<APP_NAME>' with a globally unique name.
 
     # [Azure CLI](#tab/azure-cli)
-        
+
     ```azurecli
     az functionapp create --resource-group AzureFunctionsQuickstart-rg --consumption-plan-location westeurope --runtime dotnet --functions-version 3 --name <APP_NAME> --storage-account <STORAGE_NAME>
     ```
-    
-    
+
+
     # [Azure PowerShell](#tab/azure-powershell)
-    
+
     ```azurepowershell
     New-AzFunctionApp -Name <APP_NAME> -ResourceGroupName AzureFunctionsQuickstart-rg -StorageAccount <STORAGE_NAME> -Runtime dotnet -FunctionsVersion 3 -Location 'West Europe'
     ```
-    
-    
+
+
     ---
-    
+
     Replace `<STORAGE_NAME>` with the name of the account you used in the previous step.
 
-    Replace `<APP_NAME>` with a <abbr title="A name that must be unique across all Azure customers globally. For example, you can use a combination of your personal or organization name, application name, and a numeric identifier, as in contoso-bizapp-func-20.">unique name</abbr>. The `<APP_NAME>` is also the default DNS domain for the function app. 
+    Replace `<APP_NAME>` with a <abbr title="A name that must be unique across all Azure customers globally. For example, you can use a combination of your personal or organization name, application name, and a numeric identifier, as in contoso-bizapp-func-20.">unique name</abbr>. The `<APP_NAME>` is also the default DNS domain for the function app.
 
     <br/>
     <details>
@@ -281,7 +281,7 @@ Functions in msdocs-azurefunctions-qs:
 
 ## 7. Invoke the function on Azure
 
-Copy the complete **Invoke URL** shown in the output of the `publish` command into a browser address bar. **Append** the query parameter **&name=Functions**. 
+Copy the complete **Invoke URL** shown in the output of the `publish` command into a browser address bar. **Append** the query parameter **&name=Functions**.
 
 ![The output of the function run on Azure in a browser](../../includes/media/functions-run-remote-azure-cli/function-test-cloud-browser.png)
 

articles/azure-functions/create-first-function-cli-csharp.md

@@ -31,7 +31,7 @@ Before you begin, you must have the following:
 [!INCLUDE [functions-cli-dotnet-prerequisites](../../includes/functions-cli-dotnet-prerequisites.md)]
 ::: zone-end
 ::: zone pivot="programming-runtime-functions-v4"
-# [In-process](#tab/in-process)    
+# [In-process](#tab/in-process)
 
 + [.NET 6.0 SDK](https://dotnet.microsoft.com/download)
 
@@ -41,7 +41,7 @@ Before you begin, you must have the following:
 
     + [Azure CLI](/cli/azure/install-azure-cli) version 2.4 or later.
 
-    + [Azure PowerShell](/powershell/azure/install-az-ps) version 5.0 or later.
+    + The Azure [Az PowerShell module](/powershell/azure/install-az-ps) version 5.9.0 or later.
 
 # [Isolated process](#tab/isolated-process)
 
@@ -55,7 +55,7 @@ Before you begin, you must have the following:
 
     + [Azure CLI](/cli/azure/install-azure-cli) version 2.4 or later.
 
-    + [Azure PowerShell](/powershell/azure/install-az-ps) version 5.0 or later.
+    + The Azure [Az PowerShell module](/powershell/azure/install-az-ps) version 5.9.0 or later.
 ---
 ::: zone-end
 
@@ -81,7 +81,7 @@ Verify your prerequisites, which depend on whether you are using Azure CLI or Az
 
 + Run `dotnet --list-sdks` to check that the required versions are installed.
 
-+ Run `(Get-Module -ListAvailable Az).Version` and verify version 5.0 or later. 
++ Run `(Get-Module -ListAvailable Az).Version` and verify version 5.0 or later.
 
 + Run `Connect-AzAccount` to sign in to Azure and verify an active subscription.
 
@@ -91,9 +91,9 @@ Verify your prerequisites, which depend on whether you are using Azure CLI or Az
 
 In Azure Functions, a function project is a container for one or more individual functions that each responds to a specific trigger. All functions in a project share the same local and hosting configurations. In this section, you create a function project that contains a single function.
 
-1. Run the `func init` command, as follows, to create a functions project in a folder named *LocalFunctionProj* with the specified runtime:  
+1. Run the `func init` command, as follows, to create a functions project in a folder named *LocalFunctionProj* with the specified runtime:
 
-    # [In-process](#tab/in-process) 
+    # [In-process](#tab/in-process)
 
     ```csharp
     func init LocalFunctionProj --dotnet
@@ -118,7 +118,7 @@ In Azure Functions, a function project is a container for one or more individual
 
     ```console
     func new --name HttpExample --template "HTTP trigger" --authlevel "anonymous"
-    ``` 
+    ```
 
     `func new` creates a HttpExample.cs code file.
 
@@ -128,23 +128,23 @@ If desired, you can skip to [Run the function locally](#run-the-function-locally
 
 #### HttpExample.cs
 
-The function code generated from the template depends on the type of compiled C# project.  
+The function code generated from the template depends on the type of compiled C# project.
 
-# [In-process](#tab/in-process) 
+# [In-process](#tab/in-process)
 
 *HttpExample.cs* contains a `Run` method that receives request data in the `req` variable is an [HttpRequest](/dotnet/api/microsoft.aspnetcore.http.httprequest) that's decorated with the **HttpTriggerAttribute**, which defines the trigger behavior.
 
 :::code language="csharp" source="~/functions-docs-csharp/http-trigger-template/HttpExample.cs":::
 
-The return object is an [ActionResult](/dotnet/api/microsoft.aspnetcore.mvc.actionresult) that returns a response message as either an [OkObjectResult](/dotnet/api/microsoft.aspnetcore.mvc.okobjectresult) (200) or a [BadRequestObjectResult](/dotnet/api/microsoft.aspnetcore.mvc.badrequestobjectresult) (400). 
+The return object is an [ActionResult](/dotnet/api/microsoft.aspnetcore.mvc.actionresult) that returns a response message as either an [OkObjectResult](/dotnet/api/microsoft.aspnetcore.mvc.okobjectresult) (200) or a [BadRequestObjectResult](/dotnet/api/microsoft.aspnetcore.mvc.badrequestobjectresult) (400).
 
 # [Isolated process](#tab/isolated-process)
 
-*HttpExample.cs* contains a `Run` method that receives request data in the `req` variable is an [HttpRequestData](/dotnet/api/microsoft.azure.functions.worker.http.httprequestdata) object that's decorated with the **HttpTriggerAttribute**, which defines the trigger behavior. Because of the isolated process model,    `HttpRequestData` is a representation of the actual `HttpRequest`, and not the request object itself. 
+*HttpExample.cs* contains a `Run` method that receives request data in the `req` variable is an [HttpRequestData](/dotnet/api/microsoft.azure.functions.worker.http.httprequestdata) object that's decorated with the **HttpTriggerAttribute**, which defines the trigger behavior. Because of the isolated process model,    `HttpRequestData` is a representation of the actual `HttpRequest`, and not the request object itself.
 
 :::code language="csharp" source="~/functions-docs-csharp/http-trigger-isolated/HttpExample.cs":::
 
-The return object is an [HttpResponseData](/dotnet/api/microsoft.azure.functions.worker.http.httpresponsedata) object that contains the data that's handed back to the HTTP response. 
+The return object is an [HttpResponseData](/dotnet/api/microsoft.azure.functions.worker.http.httpresponsedata) object that contains the data that's handed back to the HTTP response.
 
 ---
 
@@ -158,28 +158,28 @@ To learn more, see [Azure Functions HTTP triggers and bindings](./functions-bind
     func start
     ```
 
-    Toward the end of the output, the following lines should appear: 
-    
+    Toward the end of the output, the following lines should appear:
+
     <pre>
     ...
-    
+
     Now listening on: http://0.0.0.0:7071
     Application started. Press Ctrl+C to shut down.
-    
+
     Http Functions:
-    
+
             HttpExample: [GET,POST] http://localhost:7071/api/HttpExample
     ...
-    
+
     </pre>
-    
-    >[!NOTE]  
+
+    >[!NOTE]
     > If HttpExample doesn't appear as shown above, you likely started the host from outside the root folder of the project. In that case, use **Ctrl**+**C** to stop the host, navigate to the project's root folder, and run the previous command again.
 
 1. Copy the URL of your `HttpExample` function from this output to a browser:
 
     # [In-process](#tab/in-process)
-    
+
      To the function URL, append the query string `?name=<YOUR_NAME>`, making the full URL like `http://localhost:7071/api/HttpExample?name=Functions`. The browser should display a response message that echoes back your query string value. The terminal in which you started your project also shows log output as you make requests.
 
     # [Isolated process](#tab/isolated-process)
@@ -199,50 +199,50 @@ To learn more, see [Azure Functions HTTP triggers and bindings](./functions-bind
     ```azurecli
     az functionapp create --resource-group AzureFunctionsQuickstart-rg --consumption-plan-location <REGION> --runtime dotnet --functions-version 3 --name <APP_NAME> --storage-account <STORAGE_NAME>
     ```
-    The [az functionapp create](/cli/azure/functionapp#az_functionapp_create) command creates the function app in Azure. 
+    The [az functionapp create](/cli/azure/functionapp#az_functionapp_create) command creates the function app in Azure.
 
     # [Azure CLI](#tab/azure-cli/isolated-process)
 
     ```azurecli
     az functionapp create --resource-group AzureFunctionsQuickstart-rg --consumption-plan-location <REGION> --runtime dotnet-isolated --functions-version 3 --name <APP_NAME> --storage-account <STORAGE_NAME>
-    ``` 
-    
-    The [az functionapp create](/cli/azure/functionapp#az_functionapp_create) command creates the function app in Azure. 
+    ```
+
+    The [az functionapp create](/cli/azure/functionapp#az_functionapp_create) command creates the function app in Azure.
 
     # [Azure PowerShell](#tab/azure-powershell/in-process)
-    
+
     ```azurepowershell
     New-AzFunctionApp -Name <APP_NAME> -ResourceGroupName AzureFunctionsQuickstart-rg -StorageAccount <STORAGE_NAME> -Runtime dotnet -FunctionsVersion 3 -Location '<REGION>'
     ```
 
-    The [New-AzFunctionApp](/powershell/module/az.functions/new-azfunctionapp) cmdlet creates the function app in Azure. 
+    The [New-AzFunctionApp](/powershell/module/az.functions/new-azfunctionapp) cmdlet creates the function app in Azure.
 
     # [Azure PowerShell](#tab/azure-powershell/isolated-process)
 
     ```azurepowershell
     New-AzFunctionApp -Name <APP_NAME> -ResourceGroupName AzureFunctionsQuickstart-rg -StorageAccount <STORAGE_NAME> -Runtime dotnet-isolated -FunctionsVersion 3 -Location '<REGION>'
     ```
 
-    The [New-AzFunctionApp](/powershell/module/az.functions/new-azfunctionapp) cmdlet creates the function app in Azure. 
+    The [New-AzFunctionApp](/powershell/module/az.functions/new-azfunctionapp) cmdlet creates the function app in Azure.
 
     ---
 
     ::: zone pivot="programming-runtime-functions-v4"
     > [!NOTE]
     > This command creates a function app using the 3.x version of the Azure Functions runtime. The `func azure functionapp publish` command that you'll run later updates the app to version 4.x.
     ::: zone-end
-    
-    In the previous example, replace `<STORAGE_NAME>` with the name of the account you used in the previous step, and replace `<APP_NAME>` with a globally unique name appropriate to you. The `<APP_NAME>` is also the default DNS domain for the function app. 
-    
+
+    In the previous example, replace `<STORAGE_NAME>` with the name of the account you used in the previous step, and replace `<APP_NAME>` with a globally unique name appropriate to you. The `<APP_NAME>` is also the default DNS domain for the function app.
+
     This command creates a function app running in your specified language runtime under the [Azure Functions Consumption Plan](consumption-plan.md), which is free for the amount of usage you incur here. The command also provisions an associated Azure Application Insights instance in the same resource group, with which you can monitor your function app and view logs. For more information, see [Monitor Azure Functions](functions-monitoring.md). The instance incurs no costs until you activate it.
 
 [!INCLUDE [functions-publish-project-cli](../../includes/functions-publish-project-cli.md)]
 
 ## Invoke the function on Azure
 
-Because your function uses an HTTP trigger and supports GET requests, you invoke it by making an HTTP request to its URL. It's easiest to do this in a browser.  
+Because your function uses an HTTP trigger and supports GET requests, you invoke it by making an HTTP request to its URL. It's easiest to do this in a browser.
 
-# [In-process](#tab/in-process) 
+# [In-process](#tab/in-process)
 
 Copy the complete **Invoke URL** shown in the output of the publish command into a browser address bar, appending the query parameter `?name=Functions`. When you navigate to this URL, the browser should display similar output as when you ran the function locally.
 
@@ -258,7 +258,7 @@ Copy the complete **Invoke URL** shown in the output of the publish command into
 
 ## Next steps
 
-# [In-process](#tab/in-process) 
+# [In-process](#tab/in-process)
 
 > [!div class="nextstepaction"]
 > [Connect to Azure Queue Storage](functions-add-output-binding-storage-queue-cli.md?pivots=programming-language-csharp&tabs=in-process)