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

roygara · roygara · commit 22dfaaf532f0 · 2023-03-16T11:27:44.000-07:00
diff --git a/articles/active-directory/app-provisioning/use-scim-to-provision-users-and-groups.md b/articles/active-directory/app-provisioning/use-scim-to-provision-users-and-groups.md
@@ -8,7 +8,7 @@ ms.service: active-directory
 ms.subservice: app-provisioning
 ms.workload: identity
 ms.topic: tutorial
-ms.date: 03/15/2023
+ms.date: 03/16/2023
 ms.author: kenwith
 ms.reviewer: arvinh
 ---
diff --git a/articles/aks/includes/keda/current-version-callout.md b/articles/aks/includes/keda/current-version-callout.md
@@ -8,4 +8,6 @@ ms.author: tomkerkhove
 ---
 
 > [!IMPORTANT]
-> The KEDA add-on installs version *2.7.0* of KEDA on your cluster.
+> The KEDA add-on installs version *2.7.0* of KEDA on your cluster.
+> 
+> Due to [KEDA's Kubernetes Compatibility policy](https://keda.sh/docs/latest/operate/cluster/#kubernetes-compatibility), the managed KEDA addon is will only be supported in Kubernetes versions <= 1.25 when generally available. Please follow the [release notes](https://github.com/Azure/AKS/releases) to be notified for additional Kubernetes version support.
diff --git a/articles/aks/keda-about.md b/articles/aks/keda-about.md
@@ -30,15 +30,12 @@ Learn more about how KEDA works in the [official KEDA documentation][keda-archit
 
 ## Installation and version
 
->[!WARNING]
-> The managed KEDA addon will not be supported in K8s version 1.26 at GA. Please follow the [release notes](https://github.com/Azure/AKS/releases) to be notified when it will be supported.
+[!INCLUDE [Current version callout](./includes/keda/current-version-callout.md)]
 
 KEDA can be added to your Azure Kubernetes Service (AKS) cluster by enabling the KEDA add-on using an [ARM template][keda-arm] or [Azure CLI][keda-cli].
 
 The KEDA add-on provides a fully supported installation of KEDA that is integrated with AKS.
 
-[!INCLUDE [Current version callout](./includes/keda/current-version-callout.md)]
-
 ## Capabilities and features
 
 KEDA provides the following capabilities and features:
diff --git a/articles/aks/keda-deploy-add-on-arm.md b/articles/aks/keda-deploy-add-on-arm.md
@@ -16,9 +16,6 @@ This article shows you how to deploy the Kubernetes Event-driven Autoscaling (KE
 
 ## Prerequisites
 
->[!WARNING]
-> The managed KEDA addon will not be supported in K8s version 1.26 at GA. Please follow the [release notes](https://github.com/Azure/AKS/releases) to be notified when it will be supported.
-
 - An Azure subscription. If you don't have an Azure subscription, you can create a [free account](https://azure.microsoft.com/free).
 - [Azure CLI installed](/cli/azure/install-azure-cli).
 - Firewall rules are configured to allow access to the Kubernetes API server. ([learn more][aks-firewall-requirements])
diff --git a/articles/aks/keda-deploy-add-on-cli.md b/articles/aks/keda-deploy-add-on-cli.md
@@ -16,9 +16,6 @@ This article shows you how to install the Kubernetes Event-driven Autoscaling (K
 
 ## Prerequisites
 
->[!WARNING]
-> The managed KEDA addon will not be supported in K8s version 1.26 at GA. Please follow the [release notes](https://github.com/Azure/AKS/releases) to be notified when it will be supported.
-
 - An Azure subscription. If you don't have an Azure subscription, you can create a [free account](https://azure.microsoft.com/free).
 - [Azure CLI installed](/cli/azure/install-azure-cli).
 - Firewall rules are configured to allow access to the Kubernetes API server. ([learn more][aks-firewall-requirements])
diff --git a/articles/aks/keda-integrations.md b/articles/aks/keda-integrations.md
@@ -11,8 +11,7 @@ ms.author: tomkerkhove
 
 The Kubernetes Event-driven Autoscaling (KEDA) add-on integrates with features provided by Azure and open source projects.
 
->[!WARNING]
-> The managed KEDA addon will not be supported in K8s version 1.26 at GA. Please follow the [release notes](https://github.com/Azure/AKS/releases) to be notified when it will be supported.
+[!INCLUDE [Current version callout](./includes/keda/current-version-callout.md)]
 
 [!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
 
diff --git a/articles/automation/automation-solution-vm-management-config.md b/articles/automation/automation-solution-vm-management-config.md
@@ -3,7 +3,7 @@ title: Configure Azure Automation Start/Stop VMs during off-hours
 description: This article tells how to configure the Start/Stop VMs during off-hours feature to support different use cases or scenarios.
 services: automation
 ms.subservice: process-automation
-ms.date: 03/07/2023
+ms.date: 03/16/2023
 ms.topic: conceptual
 ms.custom: engagement-fy23
 ---
@@ -12,7 +12,7 @@ ms.custom: engagement-fy23
 
 > [!NOTE]
 > Start/Stop VM during off-hours version 1 is unavailable in the marketplace now as it will retire by 30 September 2023. We recommend you start using [version 2](../azure-functions/start-stop-vms/overview.md),
-which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until 30 September 2023. The details of the announcement will be shared on March 31st 2023. 
+which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until 30 September 2023. The details of the announcement will be shared soon. 
 
 This article describes how to configure the [Start/Stop VMs during off-hours](automation-solution-vm-management.md) feature to support the described scenarios. You can also learn how to:
 
diff --git a/articles/automation/automation-solution-vm-management-logs.md b/articles/automation/automation-solution-vm-management-logs.md
@@ -3,15 +3,15 @@ title: Query logs from Azure Automation Start/Stop VMs during off-hours
 description: This article tells how to use Azure Monitor to query log data generated by Start/Stop VMs during off-hours.
 services: automation
 ms.subservice: process-automation
-ms.date: 02/28/2023
+ms.date: 03/16/2023
 ms.topic: conceptual
 ms.custom: engagement-fy23
 ---
 
 # Query logs from Start/Stop VMs during off-hours
 
 > [!NOTE]
-> Start/Stop VM during off-hours version 1 is unavailable in the marketplace now as it will retire by 30 September 2023. We recommend you start using [version 2](../azure-functions/start-stop-vms/overview.md), which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until 30 September 2023. The details of the announcement will be shared on March 31st 2023.  
+> Start/Stop VM during off-hours version 1 is unavailable in the marketplace now as it will retire by 30 September 2023. We recommend you start using [version 2](../azure-functions/start-stop-vms/overview.md), which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until 30 September 2023. The details of the announcement will be shared soon.  
 
 Azure Automation forwards two types of records to the linked Log Analytics workspace: job logs and job streams. This article reviews the  data available for [query](../azure-monitor/logs/log-query-overview.md) in Azure Monitor.
 
diff --git a/articles/automation/automation-solution-vm-management-remove.md b/articles/automation/automation-solution-vm-management-remove.md
@@ -3,15 +3,15 @@ title: Remove Azure Automation Start/Stop VMs during off-hours overview
 description: This article describes how to remove the Start/Stop VMs during off-hours feature and unlink an Automation account from the Log Analytics workspace.
 services: automation
 ms.subservice: process-automation
-ms.date: 02/28/2023
+ms.date: 03/16/2023
 ms.topic: conceptual
 ms.custom: engagement-fy23
 ---
 
 # Remove Start/Stop VMs during off-hours from Automation account
 
 > [!NOTE]
-> Start/Stop VM during off-hours version 1 is unavailable in the marketplace now as it will retire by 30 September 2023. We recommend you start using [version 2](../azure-functions/start-stop-vms/overview.md), which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until 30 September 2023. The details of the announcement will be shared on March 31st 2023. 
+> Start/Stop VM during off-hours version 1 is unavailable in the marketplace now as it will retire by 30 September 2023. We recommend you start using [version 2](../azure-functions/start-stop-vms/overview.md), which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until 30 September 2023. The details of the announcement will be shared soon. 
 
 After you enable the Start/Stop VMs during off-hours feature to manage the running state of your Azure VMs, you may decide to stop using it. Removing this feature can be done using one of the following methods based on the supported deployment models:
 
diff --git a/articles/automation/automation-solution-vm-management.md b/articles/automation/automation-solution-vm-management.md
@@ -3,15 +3,15 @@ title: Azure Automation Start/Stop VMs during off-hours overview
 description: This article describes the Start/Stop VMs during off-hours feature, which starts or stops VMs on a schedule and proactively monitor them from Azure Monitor Logs.
 services: automation
 ms.subservice: process-automation
-ms.date: 02/28/2023
+ms.date: 03/16/2023
 ms.topic: conceptual 
 ms.custom: devx-track-azurepowershell, engagement-fy23
 ---
 
 # Start/Stop VMs during off-hours overview
 
 > [!NOTE]
-> Start/Stop VM during off-hours version 1 is unavailable in the marketplace now as it will retire by 30 September 2023. We recommend you start using [version 2](../azure-functions/start-stop-vms/overview.md), which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until 30 September 2023. The details of the announcement will be shared on March 31st 2023. 
+> Start/Stop VM during off-hours version 1 is unavailable in the marketplace now as it will retire by 30 September 2023. We recommend you start using [version 2](../azure-functions/start-stop-vms/overview.md), which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until 30 September 2023. The details of the announcement will be shared soon. 
 
 The Start/Stop VMs during off-hours feature start or stops enabled Azure VMs. It starts or stops machines on user-defined schedules, provides insights through Azure Monitor logs, and sends optional emails by using [action groups](../azure-monitor/alerts/action-groups.md). The feature can be enabled on both Azure Resource Manager and classic VMs for most scenarios.
 
diff --git a/articles/automation/how-to/region-mappings.md b/articles/automation/how-to/region-mappings.md
@@ -1,7 +1,7 @@
 ---
 title: Supported regions for linked Log Analytics workspace
 description: This article describes the supported region mappings between an Automation account and a Log Analytics workspace as it relates to certain features of Azure Automation.
-ms.date: 02/27/2023
+ms.date: 03/16/2023
 services: automation
 ms.topic: conceptual
 ms.custom: references_regions
@@ -10,7 +10,7 @@ ms.custom: references_regions
 # Supported regions for linked Log Analytics workspace
 
 > [!NOTE]
-> Start/Stop VM during off-hours version 1 is unavailable in the marketplace now as it will retire by 30 September 2023. We recommend you start using [version 2](../../azure-functions/start-stop-vms/overview.md), which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until 30 September 2023. The details of the announcement will be shared on March 31st 2023. 
+> Start/Stop VM during off-hours version 1 is unavailable in the marketplace now as it will retire by 30 September 2023. We recommend you start using [version 2](../../azure-functions/start-stop-vms/overview.md), which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until 30 September 2023. The details of the announcement will be shared soon. 
 
 In Azure Automation, you can enable the Update Management, Change Tracking and Inventory, and Start/Stop VMs during off-hours features for your servers and virtual machines. These features have a dependency on a Log Analytics workspace, and therefore require linking the workspace with an Automation account. However, only certain regions are supported to link them together. In general, the mapping is *not* applicable if you plan to link an Automation account to a workspace that won't have these features enabled.
 
diff --git a/articles/automation/media/migrate-run-as-account-managed-identity/user-assigned-expanded.png b/articles/automation/media/migrate-run-as-account-managed-identity/user-assigned-expanded.png
diff --git a/articles/automation/media/migrate-run-as-account-managed-identity/user-assigned-inline.png b/articles/automation/media/migrate-run-as-account-managed-identity/user-assigned-inline.png
diff --git a/articles/automation/media/migrate-run-as-account-managed-identity/view-client-id-expanded.png b/articles/automation/media/migrate-run-as-account-managed-identity/view-client-id-expanded.png
diff --git a/articles/automation/media/migrate-run-as-account-managed-identity/view-client-id-inline.png b/articles/automation/media/migrate-run-as-account-managed-identity/view-client-id-inline.png
diff --git a/articles/automation/migrate-run-as-accounts-managed-identity.md b/articles/automation/migrate-run-as-accounts-managed-identity.md
@@ -3,7 +3,7 @@ title: Migrate from a Run As account to Managed identities
 description: This article describes how to migrate from a Run As account to managed identities in Azure Automation.
 services: automation
 ms.subservice: process-automation
-ms.date: 03/03/2023
+ms.date: 03/14/2023
 ms.topic: conceptual 
 ms.custom: devx-track-azurepowershell
 ---
@@ -99,9 +99,7 @@ try
 { 
 
     "Logging in to Azure..." 
-
-$identity = Get-AzUserAssignedIdentity -ResourceGroupName <myResourceGroup> -Name <myUserAssignedIdentity> 
-Connect-AzAccount -Identity -AccountId $identity.ClientId 
+    Connect-AzAccount -Identity -AccountId <Client Id of myUserAssignedIdentity>
 } 
 catch { 
     Write-Error -Message $_.Exception 
@@ -164,6 +162,18 @@ foreach ($ResourceGroup in $ResourceGroups)
 
 ---
 
+### View client ID of user assigned identity
+
+1. In your Automation account, under **Account Settings**, select **Identity**. 
+1. In **User assigned** tab, select user assigned identity.
+
+    :::image type="content" source="./media/migrate-run-as-account-managed-identity/user-assigned-inline.png" alt-text="Screenshot that shows the navigation path to view client ID." lightbox="./media/migrate-run-as-account-managed-identity/user-assigned-expanded.png":::
+
+1. Go to **Overview**> **Essentials**, to view the **Client ID**.
+
+    :::image type="content" source="./media/migrate-run-as-account-managed-identity/view-client-id-inline.png" alt-text="Screenshot that shows how to view a client ID." lightbox="./media/migrate-run-as-account-managed-identity/view-client-id-expanded.png":::
+
+
 ## Graphical runbooks
 
 ### Check if a Run As account is used in graphical runbooks
diff --git a/articles/automation/troubleshoot/start-stop-vm.md b/articles/automation/troubleshoot/start-stop-vm.md
@@ -3,15 +3,15 @@ title: Troubleshoot Azure Automation Start/Stop VMs during off-hours issues
 description: This article tells how to troubleshoot and resolve issues arising during the use of the Start/Stop VMs during off-hours feature.
 services: automation
 ms.subservice: process-automation
-ms.date: 02/28/2023
+ms.date: 03/16/2023
 ms.topic: troubleshooting
 ms.custom: devx-track-azurepowershell, engagement-fy23
 ---
 
 # Troubleshoot Start/Stop VMs during off-hours issues
 
 > [!NOTE]
-> Start/Stop VM during off-hours version 1 is unavailable in the marketplace now as it will retire by 30 September 2023. We recommend you start using [version 2](../../azure-functions/start-stop-vms/overview.md), which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until 30 September 2023. The details of the announcement will be shared on March 31st 2023. 
+> Start/Stop VM during off-hours version 1 is unavailable in the marketplace now as it will retire by 30 September 2023. We recommend you start using [version 2](../../azure-functions/start-stop-vms/overview.md), which is now generally available. The new version offers all existing capabilities and provides new features, such as multi-subscription support from a single Start/Stop instance. If you have the version 1 solution already deployed, you can still use the feature, and we will provide support until 30 September 2023. The details of the announcement will be shared soon. 
 
 This article provides information on troubleshooting and resolving issues that arise when you deploy the Azure Automation Start/Stop VMs during off-hours feature on your VMs. 
 
diff --git a/articles/cost-management-billing/savings-plan/reservation-trade-in.md b/articles/cost-management-billing/savings-plan/reservation-trade-in.md
