Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into tamram22-0505a

Author: tamram

articles/app-service/app-service-key-vault-references.md

@@ -32,11 +32,21 @@ If your vault is configured with [network restrictions](../key-vault/general/ove
 
 1. Make sure the application has outbound networking capabilities configured, as described in [App Service networking features](./networking-features.md) and [Azure Functions networking options](../azure-functions/functions-networking-options.md).
 
-    Linux applications attempting to use private endpoints additionally require that the app be explicitly configured to have all traffic route through the virtual network. This requirement will be removed in a forthcoming update. To set this, use the following CLI command:
+    Linux applications attempting to use private endpoints additionally require that the app be explicitly configured to have all traffic route through the virtual network. This requirement will be removed in a forthcoming update. To set this, use the following Azure CLI or Azure PowerShell command:
+
+    # [Azure CLI](#tab/azure-cli)
 
     ```azurecli
-    az webapp config set --subscription <sub> -g <rg> -n <appname> --generic-configurations '{"vnetRouteAllEnabled": true}'
+    az webapp config set --subscription <sub> -g MyResourceGroupName -n MyAppName --generic-configurations '{"vnetRouteAllEnabled": true}'
+    ```
+    
+    # [Azure PowerShell](#tab/azure-powershell) 
+
+    ```azurepowershell
+    Update-AzFunctionAppSetting -Name MyAppName -ResourceGroupName MyResourceGroupName -AppSetting @{vnetRouteAllEnabled = $true}
     ```
+    
+    ---
 
 2. Make sure that the vault's configuration accounts for the network or subnet through which your app will access it.
 
@@ -53,11 +63,24 @@ Once you have granted permissions to the user-assigned identity, follow these st
 
 1. Configure the app to use this identity for Key Vault reference operations by setting the `keyVaultReferenceIdentity` property to the resource ID of the user-assigned identity.
 
+    # [Azure CLI](#tab/azure-cli)
+    
     ```azurecli-interactive
     userAssignedIdentityResourceId=$(az identity show -g MyResourceGroupName -n MyUserAssignedIdentityName --query id -o tsv)
     appResourceId=$(az webapp show -g MyResourceGroupName -n MyAppName --query id -o tsv)
     az rest --method PATCH --uri "${appResourceId}?api-version=2021-01-01" --body "{'properties':{'keyVaultReferenceIdentity':'${userAssignedIdentityResourceId}'}}"
     ```
+    # [Azure PowerShell](#tab/azure-powershell) 
+    
+    ```azurepowershell-interactive   
+    $userAssignedIdentityResourceId = Get-AzUserAssignedIdentity -ResourceGroupName MyResourceGroupName -Name MyUserAssignedIdentityName | Select-Object -ExpandProperty Id
+    $appResourceId = Get-AzFunctionApp -ResourceGroupName MyResourceGroupName -Name MyAppName | Select-Object -ExpandProperty Id
+    
+    $Path = "{0}?api-version=2021-01-01" -f $appResourceId
+    Invoke-AzRestMethod -Method PATCH -Path $Path -Payload "{'properties':{'keyVaultReferenceIdentity':'$userAssignedIdentityResourceId'}}"
+    ```
+    
+    ---
 
 This configuration will apply to all references for the app.
 

articles/azure-arc/data/release-notes.md

@@ -56,6 +56,8 @@ Add support for specifying labels and annotations on the secondary service endpo
 - If three replicas, then `REQUIRED_SECONDARIES_TO_COMMIT = 1`.  
 - If one or two replicas, then `REQUIRED_SECONDARIES_TO_COMMIT = 0`.
 
+In this release, the default value of the readable secondary service is `Cluster IP`.  The secondary service type can be set in the Kubernetes yaml/json at `spec.services.readableSecondaries.type`. In the next release, the default value will be the same as the primary service type.
+
 ### User experience improvements
 
 Notifications added in Azure Portal if billing data has not been uploaded to Azure recently.

articles/azure-arc/kubernetes/quickstart-connect-cluster.md

@@ -255,24 +255,6 @@ eastus   AzureArcTest1 microsoft.kubernetes/connectedclusters
 
 ---
 
-## Connect a cluster with custom certificate
-
-If you need the outbound communication from Arc agents to authenticate via a certificate, pass the certificate during onboarding. In case you need to pass multiple certificates, combine them into a single certificate chain and pass it through.
-
-### [Azure CLI](#tab/azure-cli)
-
-Run the connect command with parameters specified:
-
-```azurecli
-az connectedk8s connect --name <cluster-name> --resource-group <resource-group> --proxy-cert <path-to-cert-file>
-```
-
-### [Azure PowerShell](#tab/azure-powershell)
-
-This scenario is not supported via the powershell cmdlet. 
-
----
-
 ## Connect using an outbound proxy server
 
 If your cluster is behind an outbound proxy server, requests must be routed via the outbound proxy server.
@@ -317,6 +299,22 @@ If your cluster is behind an outbound proxy server, requests must be routed via
 
 ---
 
+For outbound proxy servers where only a trusted certificate needs to be provided without the proxy server endpoint inputs, `az connectedk8s connect` can be run with just the `--proxy-cert` input specified. In case multiple trusted certificates are expected, the combined certificate chain can be provided in a single file using the `--proxy-cert` parameter.
+
+### [Azure CLI](#tab/azure-cli)
+
+Run the connect command with the `--proxy-cert` parameter specified:
+
+```azurecli
+az connectedk8s connect --name <cluster-name> --resource-group <resource-group> --proxy-cert <path-to-cert-file>
+```
+
+### [Azure PowerShell](#tab/azure-powershell)
+
+The ability to pass in the proxy certificate only without the proxy server endpoint details is not yet supported via PowerShell. 
+
+---
+
 ## Verify cluster connection
 
 Run the following command:

articles/azure-functions/functions-networking-options.md

@@ -211,12 +211,26 @@ When you run a Premium plan, you can connect non-HTTP trigger functions to servi
 
 :::image type="content" source="media/functions-networking-options/virtual-network-trigger-toggle.png" alt-text="VNETToggle":::
 
+### [Azure CLI](#tab/azure-cli)
+
 You can also enable virtual network triggers by using the following Azure CLI command:
 
 ```azurecli-interactive
 az resource update -g <resource_group> -n <function_app_name>/config/web --set properties.functionsRuntimeScaleMonitoringEnabled=1 --resource-type Microsoft.Web/sites
 ```
 
+### [Azure PowerShell](#tab/azure-powershell)
+
+You can also enable virtual network triggers by using the following Azure PowerShell command:
+
+```azurepowershell-interactive
+$Resource = Get-AzResource -ResourceGroupName <resource_group> -ResourceName <function_app_name>/config/web -ResourceType Microsoft.Web/sites
+$Resource.Properties.functionsRuntimeScaleMonitoringEnabled = $true
+$Resource | Set-AzResource -Force
+```
+
+---
+
 > [!TIP]
 > Enabling virtual network triggers may have an impact on the performance of your application since your App Service plan instances will need to monitor your triggers to determine when to scale. This impact is likely to be very small.
 

articles/azure-functions/functions-premium-plan.md

@@ -57,7 +57,7 @@ In the Premium plan, you can have your app always ready on a specified number of
 
 You can configure the number of always ready instances in the Azure portal by selected your **Function App**, going to the **Platform Features** tab, and selecting the **Scale Out** options. In the function app edit window, always ready instances are specific to that app.
 
-![Elastic Scale Settings](./media/functions-premium-plan/scale-out.png)
+![Elastic scale settings in the portal](./media/functions-premium-plan/scale-out.png)
 
 # [Azure CLI](#tab/azurecli)
 
@@ -66,6 +66,17 @@ You can also configure always ready instances for an app with the Azure CLI.
 ```azurecli-interactive
 az resource update -g <resource_group> -n <function_app_name>/config/web --set properties.minimumElasticInstanceCount=<desired_always_ready_count> --resource-type Microsoft.Web/sites
 ```
+
+# [Azure PowerShell](#tab/azure-powershell) 
+
+You can also configure always ready instances for an app with the Azure PowerShell.
+
+```azurepowershell-interactive
+$Resource = Get-AzResource -ResourceGroupName <resource_group> -ResourceName <function_app_name>/config/web -ResourceType Microsoft.Web/sites
+$Resource.Properties.minimumElasticInstanceCount = <desired_always_ready_count>
+$Resource | Set-AzResource -Force
+```
+
 ---
 
 ### Pre-warmed instances
@@ -80,12 +91,32 @@ Consider this example of how always-ready instances and pre-warmed instances wor
 
 As soon as the first trigger comes in, the five always-ready instances become active, and a pre-warmed instance is allocated. The app is now running with six provisioned instances: the five now-active always ready instances, and the sixth pre-warmed and inactive buffer. If the rate of executions continues to increase, the five active instances are eventually used. When the platform decides to scale beyond five instances, it scales into the pre-warmed instance. When that happens, there are now six active instances, and a seventh instance is instantly provisioned and fill the pre-warmed buffer. This sequence of scaling and pre-warming continues until the maximum instance count for the app is reached. No instances are pre-warmed or activated beyond the maximum.
 
+# [Portal](#tab/portal)
+
+You can configure the number of pre-warmed instances in the Azure portal by selecting the **Scale Out** options under **Settings** of a function app deployed to that plan and then adjusting the **Always Ready Instances** count.
+
+![Pre-warmed instance Settings in the portal](./media/functions-premium-plan/scale-out.png)
+
+# [Azure CLI](#tab/azurecli)
+
 You can modify the number of pre-warmed instances for an app using the Azure CLI.
 
 ```azurecli-interactive
 az resource update -g <resource_group> -n <function_app_name>/config/web --set properties.preWarmedInstanceCount=<desired_prewarmed_count> --resource-type Microsoft.Web/sites
 ```
 
+# [Azure PowerShell](#tab/azure-powershell)
+
+You can modify the number of pre-warmed instances for an app using the Azure PowerShell.
+
+```azurepowershell-interactive
+$Resource = Get-AzResource -ResourceGroupName <resource_group> -ResourceName <function_app_name>/config/web -ResourceType Microsoft.Web/sites
+$Resource.Properties.preWarmedInstanceCount = <desired_prewarmed_count>
+$Resource | Set-AzResource -Force
+```
+
+---
+
 ### Maximum function app instances
 
 In addition to the [plan maximum instance count](#plan-and-sku-settings), you can configure a per-app maximum. The app maximum can be configured using the [app scale limit](./event-driven-scaling.md#limit-scale-out).
@@ -120,27 +151,61 @@ When you create the plan, there are two plan size settings: the minimum number o
 
 If your app requires instances beyond the always-ready instances, it can continue to scale out until the number of instances hits the maximum burst limit. You're billed for instances beyond your plan size only while they are running and allocated to you, on a per-second basis. The platform makes it's best effort at scaling your app out to the defined maximum limit.
 
-You can configure the plan size and maximums in the Azure portal by selecting the **Scale Out** options in the plan or a function app deployed to that plan (under **Platform Features**).
+# [Portal](#tab/portal)
+
+You can configure the plan size and maximums in the Azure portal by selecting the **Scale Out** options under **Settings** of a function app deployed to that plan.
+
+![Elastic plan size settings in the portal](./media/functions-premium-plan/scale-out.png)
+
+# [Azure CLI](#tab/azurecli)
 
 You can also increase the maximum burst limit from the Azure CLI:
 
 ```azurecli-interactive
 az functionapp plan update -g <resource_group> -n <premium_plan_name> --max-burst <desired_max_burst>
 ```
 
+# [Azure PowerShell](#tab/azure-powershell)
+
+You can also increase the maximum burst limit from the Azure PowerShell:
+
+```azurepowershell-interactive
+Update-AzFunctionAppPlan -ResourceGroupName <resource_group> -Name <premium_plan_name> -MaximumWorkerCount <desired_max_burst> -Force
+```
+
+---
+
 The minimum for every plan will be at least one instance. The actual minimum number of instances will be autoconfigured for you based on the always ready instances requested by apps in the plan. For example, if app A requests five always ready instances, and app B requests two always ready instances in the same plan, the minimum plan size will be calculated as five. App A will be running on all 5, and app B will only be running on 2.
 
 > [!IMPORTANT]
 > You are charged for each instance allocated in the minimum instance count regardless if functions are executing or not.
 
 In most circumstances, this autocalculated minimum is sufficient. However, scaling beyond the minimum occurs at a best effort. It's possible, though unlikely, that at a specific time scale-out could be delayed if additional instances are unavailable. By setting a minimum higher than the autocalculated minimum, you reserve instances in advance of scale-out.
 
+# [Portal](#tab/portal)
+
+You can configure the minimum instances in the Azure portal by selecting the **Scale Out** options under **Settings** of a function app deployed to that plan.
+
+![Minimum instance settings in the portal](./media/functions-premium-plan/scale-out.png)
+
+# [Azure CLI](#tab/azurecli)
+
 Increasing the calculated minimum for a plan can be done using the Azure CLI.
 
 ```azurecli-interactive
 az functionapp plan update -g <resource_group> -n <premium_plan_name> --min-instances <desired_min_instances>
 ```
 
+# [Azure PowerShell](#tab/azure-powershell)
+
+Increasing the calculated minimum for a plan can be done using the Azure PowerShell.
+
+```azurepowershell-interactive
+Update-AzFunctionAppPlan -ResourceGroupName <resource_group> -Name <premium_plan_name> -MinimumWorkerCount <desired_min_instances> -Force
+```
+
+---
+
 ### Available instance SKUs
 
 When creating or scaling your plan, you can choose between three instance sizes. You will be billed for the total number of cores and memory provisioned, per second that each instance is allocated to you. Your app can automatically scale out to multiple instances as needed.

articles/azure-monitor/agents/agent-linux.md

@@ -7,16 +7,15 @@ ms.date: 03/31/2022
 ---
 
 # Install Log Analytics agent on Linux computers
-The Log Analytics agents are on a **deprecation path** and will no longer be supported after **August 31, 2024**. If you use the Log Analytics agents to ingest data to Azure Monitor, make sure to [migrate to the new Azure Monitor agent](./azure-monitor-agent-migration.md) prior to that date.  
-
-
 This article provides details on installing the Log Analytics agent on Linux computers using the following methods:
 
 * [Install the agent for Linux using a wrapper-script](#install-the-agent-using-wrapper-script) hosted on GitHub. This is the recommended method to install and upgrade the agent when the computer has connectivity with the Internet, directly or through a proxy server.
 * [Manually download and install](#install-the-agent-manually) the agent. This is required when the Linux computer does not have access to the Internet and will be communicating with Azure Monitor or Azure Automation through the [Log Analytics gateway](./gateway.md). 
 
+The installation methods described in this article are typically used for virtual machines on-premises or in other clouds. See [Installation options](./log-analytics-agent.md#installation-options) for more efficient options you can use for Azure virtual machines.
+
 >[!IMPORTANT]
-> The installation methods described in this article are typically used for virtual machines on-premises or in other clouds. See [Installation options](./log-analytics-agent.md#installation-options) for more efficient options you can use for Azure virtual machines.
+> The Log Analytics agents are on a **deprecation path** and will no longer be supported after **August 31, 2024**. If you use the Log Analytics agents to ingest data to Azure Monitor, make sure to [migrate to the new Azure Monitor agent](./azure-monitor-agent-migration.md) prior to that date.  
 
 
 

articles/index.yml

@@ -400,13 +400,6 @@ productDirectory:
         - analytics
       url: /power-bi/developer/azure-pbie-what-is-power-bi-embedded
     # Card
-    - title: R Server for HDInsight
-      summary: Predictive analytics, machine learning, and statistical modeling for big data
-      imageSrc: https://static.docs.com/ui/media/product/azure/hdinsight.svg
-      azureCategories:
-        - analytics
-      url: hdinsight/r-server/r-server-overview.md
-    # Card
     - title: Azure Cosmos DB
       summary: Fast NoSQL database with open APIs for any scale
       imageSrc: https://static.docs.com/ui/media/product/azure/cosmos-db.svg