Merge pull request #273670 from MicrosoftDocs/main

ttorble · web-flow · commit d2a0af3696b7 · 2024-04-29T12:17:21.000+01:00
Publish to live, Monday 4 AM PST, 4/29
diff --git a/articles/api-management/TOC.yml b/articles/api-management/TOC.yml
@@ -643,7 +643,7 @@
       href: breaking-changes/metrics-retirement-aug-2023.md
     - name: Virtual network changes (September 2023)
       href: breaking-changes/rp-source-ip-address-change-sep-2023.md
-    - name: API version retirements (September 2023)
+    - name: API version retirements (June 2024)
       href: breaking-changes/api-version-retirement-sep-2023.md
     - name: Self-hosted gateway v0/v1 retirements (October 2023)
       href: breaking-changes/self-hosted-gateway-v0-v1-retirement-oct-2023.md
diff --git a/articles/api-management/breaking-changes/api-version-retirement-sep-2023.md b/articles/api-management/breaking-changes/api-version-retirement-sep-2023.md
@@ -1,33 +1,31 @@
 ---
-title: Azure API Management - API version retirements (September 2023) | Microsoft Docs
-description: The Azure API Management service is retiring all API versions prior to 2021-08-01. If you use one of these API versions, you must update your tools, scripts, or programs to use the latest versions.
+title: Azure API Management - API version retirements (June 2024) | Microsoft Docs
+description: Starting June 1, 2024, the Azure API Management service is retiring all API versions prior to 2021-08-01. If you use one of these API versions, you must update affected tools, scripts, or programs to use the latest versions.
 services: api-management
 author: dlepow
 ms.service: api-management
 ms.topic: reference
-ms.date: 11/06/2023
+ms.date: 04/26/2024
 ms.author: danlep
 ---
 
-# API version retirements (September 2023)
+# API version retirements (June 2024)
 
 [!INCLUDE [api-management-availability-premium-dev-standard-basic-consumption](../../../includes/api-management-availability-premium-dev-standard-basic-consumption.md)]
 
 Azure API Management uses Azure Resource Manager (ARM) to configure your API Management instances. The API version is embedded in your use of templates that describe your infrastructure, tools that are used to configure the service, and programs that you write to manage your Azure API Management services. 
 
-On 30 September 2023, all API versions for the Azure API Management service prior to **2021-08-01** will be retired and API calls using those API versions will fail. This means you'll no longer be able to create or manage your API Management services using your existing templates, tools, scripts, and programs until they've been updated. Data operations (such as accessing the APIs or Products configured on Azure API Management) will be unaffected by this update, including after 30 September 2023. 
-
-From now through 30 September 2023, you can continue to use the templates, tools, and programs without impact. You can transition to API version 2021-08-01 or later at any point prior to 30 September 2023. 
+Starting June 1, 2024, all API versions for the Azure API Management service prior to [**2021-08-01**](/rest/api/apimanagement/operation-groups?view=rest-apimanagement-2021-08-01) are being retired (disabled). The previously communicated retirement date was September 30, 2023. At any time after June 1, 2024, API calls using an API version prior to 2021-08-01 may fail without further notice. You'll no longer be able to create or manage your API Management services with existing templates, tools, scripts, and programs using a retired API version until they've been updated to use API version 2021-08-01 or later. Data plane operations (such as mediating API requests in the gateway) will be unaffected by this update, including after June 1, 2024.
 
 ## Is my service affected by this?
 
-While your service isn't affected by this change, any tool, script, or program that uses the Azure Resource Manager (such as the Azure CLI, Azure PowerShell, Azure API Management DevOps Resource Kit, or Terraform) to interact with the API Management service is affected by this change. You'll be unable to run those tools successfully unless you update the tools.
+While your service isn't affected by this change, any tool, script, or program that uses the Azure Resource Manager (such as the Azure CLI, Azure PowerShell, Azure API Management DevOps Resource Kit, or Terraform) to interact with the API Management service and calls an API Management API version prior to 2021-08-01 is affected by this change. After an API version is retired, you'll be unable to run any affected tools successfully unless you update the tools.
 
 ## What is the deadline for the change?
 
-The affected API versions will no longer be valid after 30 September 2023.
+The affected API versions will be retired gradually starting June 1, 2024.
 
-After 30 September 2023, if you prefer not to update your tools, scripts, and programs, your services will continue to run but you won't be able to add or remove APIs, change API policy, or otherwise configure your API Management service. 
+After an API version is retired, if you prefer not to update your affected tools, scripts, and programs, your services will continue to run. However, you won't be able to add or remove APIs, change API policy, or otherwise configure your API Management service with affected tools. 
 
 ## Required action
 
@@ -48,7 +46,7 @@ We also recommend setting the **Minimum API version** in your API Management ins
     * API Management DevOps Resource Kit: 1.0.0
     * Terraform azurerm provider: 3.0.0
     
-* **Azure SDKs** - Update the Azure API Management SDKs to the latest versions (or later): 
+* **Azure SDKs** - Update the Azure API Management SDKs to the latest versions or at least the following versions: 
     * .NET: 8.0.0 
     * Go: 1.0.0 
     * Python: 3.0.0 
@@ -57,18 +55,21 @@ We also recommend setting the **Minimum API version** in your API Management ins
 
 ### Update Minimum API version setting on your API Management instance
 
-We recommend setting the **Minimum API version** for your API Management instance using the Azure portal. This setting limits control plane API calls to your instance with an API version equal to or newer than this value. Currently you can set this to **2021-08-01**.
+We recommend setting the **Minimum API version** for your API Management instance using the Azure portal. This setting limits control plane API calls to your instance to an API version equal to or newer than this value. By setting this value to **2021-08-01**, you can assess the impact of the API version retirements on your tooling.
+
+
 
 To set the **Minimum API version** in the portal:
 
 1. In the [Azure portal](https://portal.azure.com), navigate to your API Management instance.
 1. In the left menu, under **Deployment + infrastructure**, select **Management API**.
 1. Select the **Management API settings** tab.
-1. Under **Prevent users with read-only permissions from accessing service secrets**, select **Yes**. The **Minimum API version** appears.
+1. Under **Enforce minimum API version**, select **Yes**. The **Minimum API version** appears.
 1. Select **Save**.
    
 ## More information
 
+* [Supported API Management API versions](/rest/api/apimanagement/operation-groups)
 * [Azure CLI](/cli/azure/update-azure-cli)
 * [Azure PowerShell](/powershell/azure/install-azure-powershell)
 * [Azure Resource Manager](../../azure-resource-manager/management/overview.md)
@@ -78,5 +79,4 @@ To set the **Minimum API version** in the portal:
 
 ## Related content
 
-See all [upcoming breaking changes and feature retirements](overview.md).
-
+See all [upcoming breaking changes and feature retirements](overview.md).
diff --git a/articles/api-management/breaking-changes/overview.md b/articles/api-management/breaking-changes/overview.md
@@ -21,7 +21,7 @@ The following table lists all the upcoming breaking changes and feature retireme
 | [Resource provider source IP address updates][bc1] | March 31, 2023 |
 | [Metrics retirements][metrics2023] | August 31, 2023 |
 | [Resource provider source IP address updates][rp2023] | September 30, 2023 |
-| [API version retirements][api2023] | September 30, 2023 |
+| [API version retirements][api2023] | June 1, 2024 |
 | [Deprecated (legacy) portal retirement][devportal2023] | October 31, 2023 |
 | [Self-hosted gateway v0/v1 retirement][shgwv0v1] | October 1, 2023 |
 | [Workspaces breaking changes][workspaces2024] | June 14, 2024 |
diff --git a/articles/azure-app-configuration/overview-managed-identity.md b/articles/azure-app-configuration/overview-managed-identity.md
@@ -85,7 +85,7 @@ The following steps will walk you through creating a user-assigned identity and
 1. Create a user-assigned identity called `myUserAssignedIdentity` using the CLI.
 
     ```azurecli-interactive
-    az identity create -resource-group myResourceGroup --name myUserAssignedIdentity
+    az identity create --resource-group myResourceGroup --name myUserAssignedIdentity
     ```
 
     In the output of this command, note the value of the `id` property.
diff --git a/articles/azure-app-configuration/quickstart-azure-kubernetes-service.md b/articles/azure-app-configuration/quickstart-azure-kubernetes-service.md
@@ -7,7 +7,7 @@ ms.service: azure-app-configuration
 ms.devlang: csharp
 ms.custom: devx-track-csharp, mode-other
 ms.topic: quickstart
-ms.date: 02/20/2024
+ms.date: 04/24/2024
 ms.author: junbchen
 #Customer intent: As an Azure Kubernetes Service user, I want to manage all my app settings in one place using Azure App Configuration.
 ---
@@ -20,6 +20,16 @@ A ConfigMap can be consumed as environment variables or a mounted file. In this
 
 > [!TIP]
 > See [options](./howto-best-practices.md#azure-kubernetes-service-access-to-app-configuration) for workloads hosted in Kubernetes to access Azure App Configuration.
+>
+
+> [!NOTE]
+> This quickstart will walk you through setting up the Azure App Configuration Kubernetes Provider. Optionally, you can use the following [Azure Developer CLI](/azure/developer/azure-developer-cli/install-azd) commands with the `azure-appconfig-aks` template to provision Azure resources and deploy the sample application used by this quickstart. For more information about this template, visit the [azure-appconfig-aks](https://github.com/Azure-Samples/azure-appconfig-aks) repo on GitHub.
+> 
+>  ``` azd
+>  azd init -t azure-appconfig-aks
+>  azd up
+>  ```
+>
 
 ## Prerequisites
 
@@ -32,10 +42,6 @@ A ConfigMap can be consumed as environment variables or a mounted file. In this
 * [helm](https://helm.sh/docs/intro/install/)
 * [kubectl](https://kubernetes.io/docs/tasks/tools/)
 
-> [!TIP]
-> The Azure Cloud Shell is a free, interactive shell that you can use to run the command line instructions in this article. It has common Azure tools preinstalled, including the .NET Core SDK. If you're logged in to your Azure subscription, launch your [Azure Cloud Shell](https://shell.azure.com) from shell.azure.com. You can learn more about Azure Cloud Shell by [reading our documentation](../cloud-shell/overview.md)
->
-
 ## Create an application running in AKS
 
 In this section, you will create a simple ASP.NET Core web application running in Azure Kubernetes Service (AKS). The application reads configuration from a local JSON file. In the next section, you will enable it to consume configuration from Azure App Configuration without changing the application code. If you already have an AKS application that reads configuration from a file, skip this section and go to [Use App Configuration Kubernetes Provider](#use-app-configuration-kubernetes-provider). You only need to ensure the configuration file generated by the provider matches the file path used by your application.
@@ -306,7 +312,7 @@ Add following key-values to the App Configuration store and leave **Label** and
 
     ![Screenshot showing Kubernetes Provider after using configMap.](./media/quickstarts/kubernetes-provider-app-launch-after.png)
 
-### Troubleshooting
+## Troubleshooting
 
 If you don't see your application picking up the data from your App Configuration store, run the following command to validate that the ConfigMap is created properly.
 
@@ -353,6 +359,10 @@ helm uninstall azureappconfiguration.kubernetesprovider --namespace azappconfig-
 
 [!INCLUDE[Azure App Configuration cleanup](../../includes/azure-app-configuration-cleanup.md)]
 
+> [!NOTE]
+> If you use the Azure Developer CLI to set up the resources, you can run the `azd down` command to delete all resources created by the `azure-appconfig-aks` template.
+> 
+
 ## Next steps
 
 In this quickstart, you:
diff --git a/articles/azure-monitor/app/availability-alerts.md b/articles/azure-monitor/app/availability-alerts.md
@@ -2,9 +2,8 @@
 title: Set up availability alerts with Application Insights
 description: Learn how to set up web tests in Application Insights. Get alerts if a website becomes unavailable or responds slowly.
 ms.topic: conceptual
-ms.date: 03/22/2023
-ms.reviewer: sdash
-
+ms.date: 04/28/2024
+ms.reviewer: cogoodson
 ---
 
 # Availability alerts
@@ -30,13 +29,13 @@ Alerts are now automatically enabled by default, but to fully configure an alert
 
 Automatically enabled availability alerts trigger an email when the endpoint you've defined is unavailable and when it's available again. Availability alerts that are created through this experience are state based. When the alert criteria are met, a single alert gets generated when the website is detected as unavailable. If the website is still down the next time the alert criteria is evaluated, it won't generate a new alert.
 
-For example, suppose that your website is down for an hour and you've set up an email alert with an evaluation frequency of 15 minutes. You'll only receive an email when the website goes down and another email when it's back up. You won't receive continuous alerts every 15 minutes to remind you that the website is still unavailable.
+For example, suppose that your website is down for an hour and you've set up an email alert with an evaluation frequency of 15 minutes. You'll only receive an email when the website goes down and another email when it's back online. You won't receive continuous alerts every 15 minutes to remind you that the website is still unavailable.
 
 You might not want to receive notifications when your website is down for only a short period of time, for example, during maintenance. You can change the evaluation frequency to a higher value than the expected downtime, up to 15 minutes. You can also increase the alert location threshold so that it only triggers an alert if the website is down for a specific number of regions. For longer scheduled downtimes, temporarily deactivate the alert rule or create a custom rule. It gives you more options to account for the downtime.
 
 #### Change the alert criteria
 
-To make changes to the location threshold, aggregation period, and test frequency, select the condition on the edit page of the alert rule to open the **Configure signal logic** window.
+To make changes to the location threshold, aggregation period, and test frequency, select the condition on the edit page of the alert rule to open the "**Configure signal logic**" window.
 
 ### Create a custom alert rule
 
diff --git a/articles/azure-monitor/app/availability-azure-functions.md b/articles/azure-monitor/app/availability-azure-functions.md
@@ -2,7 +2,8 @@
 title: Review TrackAvailability() test results
 description: This article explains how to review data logged by TrackAvailability() tests
 ms.topic: conceptual
-ms.date: 11/02/2023
+ms.date: 04/28/2024
+ms.reviewer: cogoodson
 ---
 
 # Review TrackAvailability() test results
diff --git a/articles/azure-monitor/app/availability-overview.md b/articles/azure-monitor/app/availability-overview.md
@@ -2,8 +2,8 @@
 title: Application Insights availability tests 
 description: Set up recurring web tests to monitor availability and responsiveness of your app or website.
 ms.topic: conceptual
-ms.date: 12/15/2023
-ms.reviewer: shyamala
+ms.date: 04/28/2024
+ms.reviewer: cogoodson
 ---
 
 # Application Insights availability tests
diff --git a/articles/azure-monitor/app/availability-private-test.md b/articles/azure-monitor/app/availability-private-test.md
@@ -2,8 +2,8 @@
 title: Private availability testing - Azure Monitor Application Insights
 description: Learn how to use availability tests on internal servers that run behind a firewall with private testing.
 ms.topic: conceptual
-ms.date: 03/22/2023
-ms.reviewer: shyamala
+ms.date: 04/28/2024
+ms.reviewer: cogoodson
 ---
 
 # Private testing
diff --git a/articles/azure-monitor/app/availability-standard-tests.md b/articles/azure-monitor/app/availability-standard-tests.md
@@ -3,6 +3,7 @@ title: Availability Standard test - Azure Monitor Application Insights
 description: Set up Standard tests in Application Insights to check for availability of a website with a single request test. 
 ms.topic: conceptual
 ms.date: 09/12/2023
+ms.reviewer: cogoodson
 ---
 
 # Standard test
@@ -33,7 +34,7 @@ To create a Standard test:
     | **SSL certificate validation test** | You can verify the SSL certificate on your website to make sure it's correctly installed, valid, trusted, and doesn't give any errors to any of your users. |
     | **Proactive lifetime check** | This setting enables you to define a set time period before your SSL certificate expires. After it expires, your test will fail. |
     |**Test frequency**| Sets how often the test is run from each test location. With a default frequency of five minutes and five test locations, your site is tested on average every minute.|
-    |**Test locations**|  The places from where our servers send web requests to your URL. *Our minimum number of recommended test locations is five* to ensure that you can distinguish problems in your website from network issues. You can select up to 16 locations.|
+    |**Test locations**|  Our servers send web requests to your URL from these locations. *Our minimum number of recommended test locations is five* to ensure that you can distinguish problems in your website from network issues. You can select up to 16 locations.|
     | **Custom headers** | Key value pairs that define the operating parameters. |
     | **HTTP request verb** | Indicate what action you want to take with your request. |
     | **Request body** | Custom data associated with your HTTP request. You can upload your own files, enter your content, or disable this feature. |
diff --git a/articles/azure-monitor/app/media/availability-alerts/create-test.png b/articles/azure-monitor/app/media/availability-alerts/create-test.png
diff --git a/articles/azure-monitor/app/sla-report.md b/articles/azure-monitor/app/sla-report.md
@@ -2,8 +2,8 @@
 title: Downtime, SLA, and outages workbook - Application Insights
 description: Calculate and report SLA for web test through a single pane of glass across your Application Insights resources and Azure subscriptions.
 ms.topic: conceptual
-ms.date: 03/22/2023
-ms.reviwer: casocha
+ms.date: 04/28/2024
+ms.reviewer: cogoodson
 ---
 
 # Downtime, SLA, and outages workbook
diff --git a/articles/hdinsight/hbase/apache-hbase-replication.md b/articles/hdinsight/hbase/apache-hbase-replication.md
@@ -4,7 +4,7 @@ description: Learn how to set up HBase replication from one HDInsight version to
 ms.service: hdinsight
 ms.custom: hdinsightactive
 ms.topic: how-to
-ms.date: 06/14/2023
+ms.date: 04/29/2024
 ---
 
 # Set up Apache HBase cluster replication in Azure virtual networks
@@ -374,7 +374,7 @@ Create keytab file for the user using `ktutil`.
 1. `wkt /etc/security/keytabs/admin.keytab`
 
 > [!NOTE] 
-> Make sure the keytab file is stored in `/etc/security.keytabs/` folder in the `<username>.keytab` format.
+> Make sure the keytab file is stored in `/etc/security/keytabs/` folder in the `<username>.keytab` format.
 
 **Step 2:** 
 Run script action with `-ku` option 
diff --git a/articles/machine-learning/how-to-manage-quotas.md b/articles/machine-learning/how-to-manage-quotas.md
@@ -149,7 +149,7 @@ To request an exception from the Azure Machine Learning product team, use the st
 
 <sup>4</sup> We reserve 20% extra compute resources for performing upgrades. For example, if you request 10 instances in a deployment, you must have a quota for 12. Otherwise, you receive an error. There are some VM SKUs that are exempt from extra quota. See [virtual machine quota allocation for deployment](how-to-deploy-online-endpoints.md#virtual-machine-quota-allocation-for-deployment) for more.
 
-<sup>5</sup> Requests per second, connections, bandwidth etc are related. If you request for increase for any of these limits, ensure estimating/calculating other related limites together.
+<sup>5</sup> Requests per second, connections, bandwidth etc. are related. If you request an increase for any of these limits, ensure estimating/calculating other related limits together.
 
 ### Azure Machine Learning pipelines
 [Azure Machine Learning pipelines](concept-ml-pipelines.md) have the following limits.
@@ -160,13 +160,6 @@ To request an exception from the Azure Machine Learning product team, use the st
 | Workspaces per resource group | 800 |
 
 
-### Azure Machine Learning job schedules
-[Azure Machine Learning job schedules](how-to-schedule-pipeline-job.md) have the following limits.
-
-| **Resource** | **Limit** |
-| --- | --- |
-| Schedules per region | 100 |
-
 ### Azure Machine Learning integration with Synapse
 
 Azure Machine Learning serverless Spark provides easy access to distributed computing capability for scaling Apache Spark jobs. Serverless Spark utilizes the same dedicated quota as Azure Machine Learning Compute. Quota limits can be increased by submitting a support ticket and [requesting for quota and limit increase](#request-quota-and-limit-increases) for ESv3 series under the "Machine Learning Service: Virtual Machine Quota" category.
diff --git a/articles/machine-learning/how-to-schedule-pipeline-job.md b/articles/machine-learning/how-to-schedule-pipeline-job.md
diff --git a/articles/sap/monitor/provider-ha-pacemaker-cluster.md b/articles/sap/monitor/provider-ha-pacemaker-cluster.md
diff --git a/articles/sap/monitor/set-up-network.md b/articles/sap/monitor/set-up-network.md
diff --git a/articles/virtual-machines/dedicated-hosts-how-to.md b/articles/virtual-machines/dedicated-hosts-how-to.md
