Merge pull request #235647 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: huypub

articles/active-directory/hybrid/migrate-from-federation-to-cloud-authentication.md

@@ -94,7 +94,7 @@ Modern authentication clients (Office 2016 and Office 2013, iOS, and Android app
 
 To plan for rollback, use the [documented current federation settings](#document-current-federation-settings) and check the [federation design and deployment documentation](/windows-server/identity/ad-fs/deployment/windows-server-2012-r2-ad-fs-deployment-guide). 
 
-The rollback process should include converting managed domains to federated domains by using the [Convert-MSOLDomainToFederated](/powershell/module/microsoft.graph.identity.directorymanagement/new-mgdomainfederationconfiguration?view=graph-powershell-1.0&preserve-view=true) cmdlet. If necessary, configuring extra claims rules.
+The rollback process should include converting managed domains to federated domains by using the [New-MgDomainFederationConfiguration](/powershell/module/microsoft.graph.identity.directorymanagement/new-mgdomainfederationconfiguration?view=graph-powershell-1.0&preserve-view=true) cmdlet. If necessary, configuring extra claims rules.
 
 ## Migration considerations 
 

articles/advisor/advisor-reference-cost-recommendations.md

@@ -316,6 +316,18 @@ Apache Spark for Azure Synapse Analytics pool's Autoscale feature automatically
 
 Learn more about [Synapse workspace - EnableSynapseSparkComputeAutoScaleGuidance (Consider enabling autoscale feature on spark compute.)](https://aka.ms/EnableSynapseSparkComputeAutoScaleGuidance).
 
+## Web
+
+### Right-size underutilized App Service plans
+
+We've analyzed the usage patterns of your app service plan over the past 7 days and identified low CPU usage. While certain scenarios can result in low utilization by design, you can often save money by choosing a less expensive SKU while retaining the same features.
+
+> [!NOTE]
+> - Currently, this recommendation only works for App Service plans running on Windows on a SKU that allows you to downscale to less expensive tiers without losing any features, like from P3v2 to P2v2 or from P2v2 to P1v2. 
+> - CPU bursts that last only a few minutes might not be correctly detected. Please perform a careful analysis in your App Service plan metrics blade before downscaling your SKU.
+
+Learn more about [App Service plans](../app-service/overview-hosting-plans.md).
+
 ## Azure Monitor
 
 For Azure Monitor cost optimization suggestions, please see [Optimize costs in Azure Monitor](../azure-monitor/best-practices-cost.md).

articles/azure-functions/functions-run-local.md

@@ -492,6 +492,8 @@ curl --request POST -H "Content-Type:application/json" --data "{'input':'sample
 ```
 ---
 
+The administrator endpoint also provides a list of all (HTTP triggered and non-HTTP triggered) functions on `http://localhost:{port}/admin/functions/`.
+
 When you call an administrator endpoint on your function app in Azure, you must provide an access key. To learn more, see [Function access keys](functions-bindings-http-webhook-trigger.md#authorization-keys).
 
 ## <a name="publish"></a>Publish to Azure

articles/azure-maps/how-to-use-indoor-module-ios.md

@@ -13,14 +13,11 @@ services: azure-maps
 
 The Azure Maps iOS SDK allows you to render indoor maps created in Azure Maps Creator services.
 
-> [!NOTE]
-> The iOS SDK will support *dynamic styling* in a future release, coming soon!
-
 ## Prerequisites
 
-1. Be sure to complete the steps in the [Quickstart: Create an iOS app](quick-ios-app.md). Code blocks in this article can be inserted into the  `viewDidLoad` function of `ViewController`.
-1. [Create a Creator resource](how-to-manage-creator.md)
-1. Get a `tilesetId` by completing the [tutorial for creating Indoor maps](tutorial-creator-indoor-maps.md). You'll use this identifier to render indoor maps with the Azure Maps iOS SDK.
+1. Complete the steps in the [Quickstart: Create an iOS app]. Code blocks in this article can be inserted into the `viewDidLoad` function of `ViewController`.
+1. A [Creator resource]
+1. Get a `tilesetId` by completing the [Tutorial: Use Creator to create indoor maps]. The tileset ID is used to render indoor maps with the Azure Maps iOS SDK.
 
 ## Instantiate the indoor manager
 
@@ -74,11 +71,17 @@ func indoorManager(
 
 ## Example
 
-The screenshot below shows the above code displaying an indoor map.
+The following screenshot shows the above code displaying an indoor map.
 
 ![A screenshot that displays an indoor map created using the above sample code.](./media/ios-sdk/indoor-maps/indoor.png)
 
 ## Additional information
 
-- [Creator for indoor maps](creator-indoor-maps.md)
-- [Drawing package requirements](drawing-requirements.md)
+- [Creator for indoor maps]
+- [Drawing package requirements]
+
+[Quickstart: Create an iOS app]: quick-ios-app.md
+[Creator resource]: how-to-manage-creator.md
+[Tutorial: Use Creator to create indoor maps]: tutorial-creator-indoor-maps.md
+[Creator for indoor maps]: creator-indoor-maps.md
+[Drawing package requirements]: drawing-requirements.md

articles/azure-monitor/app/app-insights-overview.md

@@ -34,7 +34,7 @@ To understand the number of Application Insights resources required to cover you
 
 ## How do I use Application Insights?
 
-Application Insights is enabled through either [autoinstrumentation](codeless-overview.md) (agent) or by adding the [Application Insights SDK](sdk-support-guidance.md) to your application code. [Many languages](platforms.md) are supported. The applications could be on Azure, on-premises, or hosted by another cloud. To figure out which type of instrumentation is best for you, see [How do I instrument an application?](#how-do-i-instrument-an-application).
+Application Insights is enabled through either [autoinstrumentation](codeless-overview.md) (agent) or by adding the [Application Insights SDK](sdk-support-guidance.md) to your application code. [Many languages](#supported-languages) are supported. The applications could be on Azure, on-premises, or hosted by another cloud. To figure out which type of instrumentation is best for you, see [How do I instrument an application?](#how-do-i-instrument-an-application).
 
 The Application Insights agent or SDK preprocesses telemetry and metrics before sending the data to Azure. Then it's ingested and processed further before it's stored in Azure Monitor Logs (Log Analytics). For this reason, an Azure account is required to use Application Insights.
 
@@ -192,4 +192,4 @@ Leave product feedback for the engineering team in the [Feedback Community](http
 - [Autoinstrumentation overview](codeless-overview.md)
 - [Overview dashboard](overview-dashboard.md)
 - [Availability overview](availability-overview.md)
-- [Application Map](app-map.md)
+- [Application Map](app-map.md)

articles/azure-resource-manager/bicep/user-defined-data-types.md

@@ -218,4 +218,4 @@ resource storageAccount 'Microsoft.Storage/storageAccounts@2022-09-01' = {
 
 ## Next steps
 
-- For a list of the Bicep date types, see [Data types](./data-types.md).
+- For a list of the Bicep data types, see [Data types](./data-types.md).

articles/backup/azure-kubernetes-service-cluster-manage-backups.md

@@ -3,7 +3,7 @@ title: Manage Azure Kubernetes Service (AKS) backups using Azure Backup
 description: This article explains how to manage Azure Kubernetes Service (AKS) backups using Azure Backup.
 ms.topic: how-to
 ms.service: backup
-ms.date: 03/27/2023
+ms.date: 04/21/2023
 author: jyothisuri
 ms.author: jsuri
 ---
@@ -82,23 +82,23 @@ This section provides the set of Azure CLI commands to perform create, update, o
 To install the Backup Extension, run the following command:
 
    ```azurecli-interactive
-   az k8s-extension create --name azure-aks-backup --extension-type Microsoft.DataProtection.Kubernetes --scope cluster --cluster-type managedClusters --cluster-name aksclustername --resource-group aksclusterrg --release-train stable --configuration-settings blobContainer=containername storageAccount=storageaccountname storageAccountResourceGroup=storageaccountrg storageAccountSubscriptionId=subscriptionid
+   az k8s-extension create --name azure-aks-backup --extension-type Microsoft.DataProtection.Kubernetes --scope cluster --cluster-type managedClusters --cluster-name <aksclustername> --resource-group <aksclusterrg> --release-train stable --configuration-settings blobContainer=<containername> storageAccount=<storageaccountname> storageAccountResourceGroup=<storageaccountrg> storageAccountSubscriptionId=<subscriptionid>
    ```
 
 ### View Backup Extension installation status
 
 To view the progress of Backup Extension installation, use the following command:
 
    ```azurecli-interactive
-   az k8s-extension show --name azure-aks-backup --cluster-type managedClusters --cluster-name aksclustername --resource-group aksclusterrg
+   az k8s-extension show --name azure-aks-backup --cluster-type managedClusters --cluster-name <aksclustername> --resource-group <aksclusterrg>
    ```
 
 ### Update resources in Backup Extension
 
 To update blob container, CPU, and memory in the Backup Extension, use the following command:
 
    ```azurecli-interactive
-   az k8s-extension update --name azure-aks-backup --cluster-type managedClusters --cluster-name aksclustername --resource-group aksclusterrg --release-train stable --configuration-settings [blobContainer=containername storageAccount=storageaccountname storageAccountResourceGroup=storageaccountrg storageAccountSubscriptionId=subscriptionid] [cpuLimit=1] [memoryLimit=1Gi]
+   az k8s-extension update --name azure-aks-backup --cluster-type managedClusters --cluster-name <aksclustername> --resource-group <aksclusterrg> --release-train stable --configuration-settings [blobContainer=<containername> storageAccount=<storageaccountname> storageAccountResourceGroup=<storageaccountrg> storageAccountSubscriptionId=<subscriptionid>] [cpuLimit=1] [memoryLimit=1Gi]
    
    []: denotes the 3 different sub-groups of updates possible (discard the brackets while using the command)
 
@@ -109,15 +109,15 @@ To update blob container, CPU, and memory in the Backup Extension, use the follo
 To stop the Backup Extension install operation, use the following command:
 
    ```azurecli-interactive
-   az k8s-extension delete --name azure-aks-backup --cluster-type managedClusters --cluster-name aksclustername --resource-group aksclusterrg
+   az k8s-extension delete --name azure-aks-backup --cluster-type managedClusters --cluster-name <aksclustername> --resource-group <aksclusterrg>
    ```
 
 ### Grant permission on storage account
 
 To provide *Storage Account Contributor Permission* to the Extension Identity on storage account, run the following command:
 
    ```azurecli-interactive
-   az role assignment create --assignee-object-id $(az k8s-extension show --name azure-aks-backup --cluster-name aksclustername --resource-group aksclusterresourcegroup --cluster-type managedClusters --query aksAssignedIdentity.principalId --output tsv) --role 'Storage Account Contributor' --scope /subscriptions/subscriptionid/resourceGroups/storageaccountresourcegroup/providers/Microsoft.Storage/storageAccounts/storageaccountname 
+   az role assignment create --assignee-object-id $(az k8s-extension show --name azure-aks-backup --cluster-name <aksclustername> --resource-group <aksclusterrg> --cluster-type managedClusters --query identity.principalId --output tsv) --role 'Storage Account Contributor' --scope /subscriptions/<subscriptionid>/resourceGroups/<storageaccountrg>/providers/Microsoft.Storage/storageAccounts/<storageaccountname> 
    ```
 
 
@@ -127,12 +127,11 @@ To enable Trusted Access between Backup vault and AKS cluster, use the following
 
    ```azurecli-interactive
    az aks trustedaccess rolebinding create \
-   -g $myResourceGroup \ 
-   --cluster-name $myAKSCluster 
-   –n <randomRoleBindingName> \ 
-   -s <vaultID> \ 
+   --resource-group <backupvaultrg> \ 
+   --cluster-name <aksclustername> \
+   --name <randomRoleBindingName> \ 
+   --source-resource-id /subscriptions/<subscriptionid>/resourcegroups/<backupvaultrg>/providers/Microsoft.DataProtection/BackupVaults/<backupvaultname> \ 
    --roles Microsoft.DataProtection/backupVaults/backup-operator
-
    ```
 
 Learn more about [other commands related to Trusted Access](../aks/trusted-access-feature.md#trusted-access-feature-overview).
@@ -141,4 +140,4 @@ Learn more about [other commands related to Trusted Access](../aks/trusted-acces
 
 - [Back up Azure Kubernetes Service cluster (preview)](azure-kubernetes-service-cluster-backup.md)
 - [Restore Azure Kubernetes Service cluster (preview)](azure-kubernetes-service-cluster-restore.md)
-- [Supported scenarios for backing up Azure Kubernetes Service cluster (preview)](azure-kubernetes-service-cluster-backup-support-matrix.md)
+- [Supported scenarios for backing up Azure Kubernetes Service cluster (preview)](azure-kubernetes-service-cluster-backup-support-matrix.md)

articles/devtest-labs/devtest-lab-integrate-ci-cd.md

@@ -70,12 +70,10 @@ $labVmRgName = (Get-AzResource -Id $labVmComputeId).ResourceGroupName
 $labVmName = (Get-AzResource -Id $labVmId).Name
 
 # Get lab VM public IP address
-$labVMIpAddress = (Get-AzPublicIpAddress -ResourceGroupName $labVmRgName
-                -Name $labVmName).IpAddress
+$labVMIpAddress = (Get-AzPublicIpAddress -ResourceGroupName $labVmRgName -Name $labVmName).IpAddress
 
 # Get lab VM FQDN
-$labVMFqdn = (Get-AzPublicIpAddress -ResourceGroupName $labVmRgName
-           -Name $labVmName).DnsSettings.Fqdn
+$labVMFqdn = (Get-AzPublicIpAddress -ResourceGroupName $labVmRgName -Name $labVmName).DnsSettings.Fqdn
 
 # Set a variable labVmRgName to store the lab VM resource group name
 Write-Host "##vso[task.setvariable variable=labVmRgName;]$labVmRgName"
@@ -127,10 +125,10 @@ The next step creates a golden image VM to use for future deployments. This step
    - **Virtual Machine Name**: the variable you specified for your virtual machine name: *$vmName*.
    - **Template**: Browse to and select the template file you checked in to your project repository.
    - **Parameters File**: If you checked a parameters file into your repository, browse to and select it.
-   - **Parameter Overrides**: Enter `-newVMName '$(vmName)' -userName '$(userName)' -password (ConvertTo-SecureString -String '$(password)' -AsPlainText -Force)`.
-   - Drop down **Output Variables**, and under **Reference name**, enter the variable for the created lab VM ID. If you use the default *labVmId*, you can refer to the variable in subsequent tasks as **$(labVmId)**.
+   - **Parameter Overrides**: Enter `-newVMName '$(vmName)' -userName '$(userName)' -password '$(password)'`.
+   - Drop down **Output Variables**, and under **Reference name**, enter the variable for the created lab VM ID. Let's enter *vm* for **Reference name** for simplicity. **labVmId** will be an attribute of this variable and will be referred to later as *$vm.labVmId*. If you use any other name, then remember to use it accordingly in the subsequent tasks.
 
-     You can create a name other than the default, but remember to use the correct name in subsequent tasks. You can write the Lab VM ID in the following form: `/subscriptions/{subscription Id}/resourceGroups/{resource group Name}/providers/Microsoft.DevTestLab/labs/{lab name}/virtualMachines/{vmName}`.
+     Lab VM ID will be in the following form: `/subscriptions/{subscription Id}/resourceGroups/{resource group Name}/providers/Microsoft.DevTestLab/labs/{lab name}/virtualMachines/{vmName}`.
 
 ### Collect the details of the DevTest Labs VM
 
@@ -143,7 +141,7 @@ Next, the pipeline runs the script you created to collect the details of the Dev
    - **Azure Subscription**: Select your service connection or subscription.
    - **Script Type**: Select **Script File Path**.
    - **Script Path**: Browse to and select the PowerShell script that you checked in to your source code repository. You can use built-in properties to simplify the path, for example: `$(System.DefaultWorkingDirectory/Scripts/GetLabVMParams.ps1`.
-   - **Script Arguments**: Enter the name of the **labVmId** variable you populated in the previous task, for example *-labVmId '$(labVmId)'*.
+   - **Script Arguments**: Enter the value as **-labVmId $(vm.labVmId)**.
 
 The script collects the required values and stores them in environment variables within the release pipeline, so you can refer to them in later steps.
 
@@ -159,7 +157,7 @@ The next task creates an image of the newly deployed VM in your lab. You can use
    - **Lab**: Select your lab.
    - **Custom Image Name**: Enter a name for the custom image.
    - **Description**: Enter an optional description to make it easy to select the correct image.
-   - **Source Lab VM**: The source **labVmId**. If you changed the default name of the **labVmId** variable, enter it here. The default value is **$(labVmId)**.
+   - **Source Lab VM**: The source **labVmId**. Enter the value as **$(vm.labVmId)**.
    - **Output Variables**: You can edit the name of the default Custom Image ID variable if necessary.
 
 ### Deploy your app to the DevTest Labs VM (optional)
@@ -177,7 +175,7 @@ The final task is to delete the VM that you deployed in your lab. You'd ordinari
 1. Configure the task as follows:
    - **Azure RM Subscription**: Select your service connection or subscription.
    - **Lab**: Select your lab.
-   - **Virtual Machine**: Select the VM you want to delete.
+   - **Virtual Machine**: Enter the value as **$(vm.labVmId)**.
    - **Output Variables**: Under **Reference name**, if you changed the default name of the **labVmId** variable, enter it here. The default value is **$(labVmId)**.
 
 ### Save the release pipeline