Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Learn Build Service GitHub App

articles/aks/load-balancer-standard.md

@@ -5,7 +5,7 @@ description: Learn how to use a public load balancer with a Standard SKU to expo
 ms.subservice: aks-networking
 ms.custom: devx-track-azurecli
 ms.topic: how-to
-ms.date: 02/22/2023
+ms.date: 06/17/2023
 ms.author: allensu
 author: asudbring
 #Customer intent: As a cluster operator or developer, I want to learn how to create a service in AKS that uses an Azure Load Balancer with a Standard SKU.
@@ -211,7 +211,7 @@ An outbound rule configures outbound NAT for all virtual machines identified by
 
 While you can use an outbound rule with a single public IP address, outbound rules are great for scaling outbound NAT because they ease the configuration burden. You can use multiple IP addresses to plan for large-scale scenarios and outbound rules to mitigate SNAT exhaustion prone patterns. Each IP address provided by a frontend provides 64k ephemeral ports for the load balancer to use as SNAT ports.
 
-When using a *Standard* SKU load balancer with managed outbound public IPs (which are created by default), you can scale the number of managed outbound public IPs using the **`load-balancer-managed-ip-count`** parameter.
+When using a *Standard* SKU load balancer with managed outbound public IPs (which are created by default), you can scale the number of managed outbound public IPs using the **`--load-balancer-managed-outbound-ip-count`** parameter.
 
 Use the following command to update an existing cluster. You can also set this parameter to have multiple managed outbound public IPs.
 
@@ -233,7 +233,7 @@ az aks update \
 
 The above example sets the number of managed outbound public IPs to *2* for the *myAKSCluster* cluster in *myResourceGroup*.
 
-At cluster creation time, you can also use the **`load-balancer-managed-ip-count`** parameter to set the initial number of managed outbound public IPs by appending the **`--load-balancer-managed-outbound-ip-count`** parameter and setting it to your desired value. The default number of managed outbound public IPs is *1*.
+At cluster creation time, you can also set the initial number of managed outbound public IPs by appending the **`--load-balancer-managed-outbound-ip-count`** parameter and setting it to your desired value. The default number of managed outbound public IPs is *1*.
 
 ### Provide your own outbound public IPs or prefixes
 

articles/automation/automation-update-azure-modules.md

@@ -3,17 +3,13 @@ title: Update Azure PowerShell modules in Azure Automation
 description: This article tells how to update common Azure PowerShell modules provided by default in Azure Automation.
 services: automation
 ms.subservice: process-automation
-ms.date: 05/03/2023
+ms.date: 07/03/2023
 ms.topic: conceptual 
 ms.custom: devx-track-azurepowershell
 ---
 
 # Update Azure PowerShell modules in Automation
 
-> [!Important]
-> If you are facing issues while upgrading to **Az.Accounts version 2.12.2** or upgrading to a newer version with dependencies on **Az.Accounts version 2.12.2**, we recommend you use **Az.Accounts version 2.12.1 or lower** to avoid issues with Az modules that are dependent on Az.Accounts. For more information, see [steps to import module with specific versions](shared-resources/modules.md#import-modules-by-using-powershell).
- 
-
 The most common PowerShell modules are provided by default in each Automation account. See [Default modules](shared-resources/modules.md#default-modules). As the Azure team updates the Azure modules regularly, changes can occur with the included cmdlets. These changes, for example, renaming a parameter or deprecating a cmdlet entirely, can negatively affect your runbooks. 
 
 > [!NOTE]

articles/azure-monitor/essentials/integrate-keda.md

@@ -33,7 +33,7 @@ This article walks you through the steps to integrate KEDA into your AKS cluster
 
 ## Set up a workload identity
 
-1. Start by setting up some environment variables. Change the values to suit your AKS cluster. 
+1. Start by setting up some environment variables. Change the values to suit your AKS cluster.
 
     ```bash
     export RESOURCE_GROUP="rg-keda-integration"
@@ -43,9 +43,11 @@ This article walks you through the steps to integrate KEDA into your AKS cluster
     export FEDERATED_IDENTITY_CREDENTIAL_NAME="kedaFedIdentity" 
     export SERVICE_ACCOUNT_NAMESPACE="keda"
     export SERVICE_ACCOUNT_NAME="keda-operator"
+    export AKS_CLUSTER_NAME="aks-cluster-name"
     ```
 
-    + `SERVICE_ACCOUNT_NAME` - KEDA must use the service account that was used to create federated credentials.
+    + `SERVICE_ACCOUNT_NAME` - KEDA must use the service account that was used to create federated credentials. This can be any user defined name.
+    + `AKS_CLUSTER_NAME`- The name of the AKS cluster where you want to deploy KEDA.
     + `SERVICE_ACCOUNT_NAMESPACE` Both KEDA and service account must be in same namespace.
     + `USER_ASSIGNED_IDENTITY_NAME` is the name of the Azure Active directory identity that's created for KEDA. 
     + `FEDERATED_IDENTITY_CREDENTIAL_NAME` is the name of the credential that's created for KEDA to use to authenticate with Azure.
@@ -66,13 +68,13 @@ This article walks you through the steps to integrate KEDA into your AKS cluster
 1. Store the OIDC issuer url in an environment variable to be used later.
 
     ```bash
-    export AKS_OIDC_ISSUER="$(az aks show -n $CLUSTER_NAME -g $RESOURCE_GROUP --query "oidcIssuerProfile.issuerUrl" -otsv)"
+    export AKS_OIDC_ISSUER="$(az aks show -n $AKS_CLUSTER_NAME -g $RESOURCE_GROUP --query "oidcIssuerProfile.issuerUrl" -otsv)"
     ```
 
 1. Create a user assigned identity for KEDA. This identity is used by KEDA to authenticate with Azure Monitor. 
 
     ```azurecli
-     az identity create --name $USER_ASSIGNED_IDENTITY_NAME --resource-group $RESOURCE_GROUP --location $LOCATION --subscription     $SUBSCRIPTION
+     az identity create --name $USER_ASSIGNED_IDENTITY_NAME --resource-group $RESOURCE_GROUP --location $LOCATION --subscription $SUBSCRIPTION
     ```
 
     The output will be similar to the following:
@@ -94,25 +96,25 @@ This article walks you through the steps to integrate KEDA into your AKS cluster
 
 1. Store the `clientId` and `tenantId` in environment variables to use later.  
     ```bash
-    export USER_ASSIGNED_CLIENT_ID="$(az identity show --resource-group $RESOURCE_GROUP --name $USER_ASSIGNED_IDENTITY_NAME --query     'clientId' -otsv)"
-    export TENANT_ID="$(az identity show --resource-group $RESOURCE_GROUP --name $USER_ASSIGNED_IDENTITY_NAME --query 'tenantId'     -otsv)"
+    export USER_ASSIGNED_CLIENT_ID="$(az identity show --resource-group $RESOURCE_GROUP --name $USER_ASSIGNED_IDENTITY_NAME --query 'clientId' -otsv)"
+    export TENANT_ID="$(az identity show --resource-group $RESOURCE_GROUP --name $USER_ASSIGNED_IDENTITY_NAME --query 'tenantId' -otsv)"
     ```
 
-1. Assign the *Monitoring Data Reader* role to the identity for your Azure Monitor workspace. This role allows the identity to read metrics from your workspace. 
+1. Assign the *Monitoring Data Reader* role to the identity for your Azure Monitor workspace. This role allows the identity to read metrics from your workspace. Replace the *Azure Monitor Workspace resource group* and *Azure Monitor Workspace name* with the resource group and name of the Azure Monitor workspace which is configured to collect metrics from the AKS cluster.
 
     ```azurecli
     az role assignment create \
     --assignee $USER_ASSIGNED_CLIENT_ID \
     --role "Monitoring Data Reader" \
-    --scope /subscriptions/$SUBSCRIPTION/resourceGroups/<Azure Monitor Workspace resource group>/providers/microsoft.monitor/accounts/    <Azure monitor workspace name>
+    --scope /subscriptions/$SUBSCRIPTION/resourceGroups/<Azure Monitor Workspace resource group>/providers/microsoft.monitor/accounts/<Azure monitor workspace name>
     ```
 
 
-1. Create the KEDA namespace, then create Kubernetes service account. This service account is used by KEDA to authenticate with Azure. 
+1. Create the KEDA namespace, then create Kubernetes service account. This service account is used by KEDA to authenticate with Azure.
 
     ```azurecli
     
-    az aks get-credentials -n $CLUSTER_NAME -g $RESOURCE_GROUP
+    az aks get-credentials -n $AKS_CLUSTER_NAME -g $RESOURCE_GROUP
     
     kubectl create namespace keda
     
@@ -129,13 +131,13 @@ This article walks you through the steps to integrate KEDA into your AKS cluster
 
 1. Check your service account by running
     ```bash
-    kubectl describe serviceaccount workload-identity-sa -n keda
+    kubectl describe serviceaccount $SERVICE_ACCOUNT_NAME -n keda
     ```
 
 1. Establish a federated credential between the service account and the user assigned identity. The federated credential allows the service account to use the user assigned identity to authenticate with Azure.
 
     ```azurecli
-    az identity federated-credential create --name $FEDERATED_IDENTITY_CREDENTIAL_NAME --identity-name $USER_ASSIGNED_IDENTITY_NAME     --resource-group $RESOURCE_GROUP --issuer $AKS_OIDC_ISSUER --subject     system:serviceaccount:$SERVICE_ACCOUNT_NAMESPACE:$SERVICE_ACCOUNT_NAME --audience api://AzureADTokenExchange
+    az identity federated-credential create --name $FEDERATED_IDENTITY_CREDENTIAL_NAME --identity-name $USER_ASSIGNED_IDENTITY_NAME --resource-group $RESOURCE_GROUP --issuer $AKS_OIDC_ISSUER --subject     system:serviceaccount:$SERVICE_ACCOUNT_NAMESPACE:$SERVICE_ACCOUNT_NAME --audience api://AzureADTokenExchange
     ```
 
     > [!Note]
@@ -145,7 +147,14 @@ This article walks you through the steps to integrate KEDA into your AKS cluster
 
 KEDA can be deployed using YAML manifests, Helm charts, or Operator Hub. This article uses Helm charts. For more information on deploying KEDA, see [Deploying KEDA](https://keda.sh/docs/2.10/deploy/)
 
-Deploy KEDA using the following command. 
+Add helm repository:
+
+```bash 
+helm repo add kedacore https://kedacore.github.io/charts
+helm repo update
+```
+
+Deploy KEDA using the following command:
 
 ```bash 
 helm install keda kedacore/keda --namespace keda \