Merge pull request #286621 from MicrosoftDocs/main

9/12/2024 AM Publish

Author: Taojunshen

.openpublishing.redirection.json

@@ -4365,6 +4365,11 @@
       "redirect_url": "/azure/virtual-wan/monitor-virtual-wan",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/virtual-wan/monitoring-best-practices.md",
+      "redirect_url": "/azure/virtual-wan/monitor-virtual-wan",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/virtual-wan/scenario-route-between-hubs-firewall.md",
       "redirect_url": "/azure/virtual-wan/scenario-route-between-vnets-firewall",

articles/app-service/environment/media/using/using-appcreate-skus.png

@@ -49,7 +49,7 @@ When you scale an App Service plan, the needed infrastructure is added automatic
 
 A scale operation on one size and operating system won't affect scaling of the other combinations of size and operating system. For example, if you are scaling a Windows I2v2 App Service plan, a scale operation to a Windows I3v2 App Service plan starts immediately. Scaling normally takes less than 15 minutes but can take up to 45 minutes.
 
-In a multi-tenant App Service, scaling is immediate, because a pool of shared resources is readily available to support it. App Service Environment is a single-tenant service, so there's no shared buffer, and resources are allocated based on need.
+In a multitenant App Service, scaling is immediate, because a pool of shared resources is readily available to support it. App Service Environment is a single-tenant service, so there's no shared buffer, and resources are allocated based on need.
 
 ## App access
 
@@ -177,7 +177,7 @@ If you have multiple App Service Environments, you might want some of them to be
 
 Select the value you want, and then select **Save**.
 
-![Screenshot that shows the App Service Environment configuration portal.][5]
+![Screenshot that shows the App Service Environment upgrade preference setting.][7]
 
 This feature makes the most sense when you have multiple App Service Environments, and you might benefit from sequencing the upgrades. For example, you might set your development and test App Service Environments to be early, and your production App Service Environments to be late.
 
@@ -199,6 +199,7 @@ To delete:
 [4]: ./media/using/using-logs.png
 [5]: ./media/using/using-configuration.png
 [6]: ./media/using/using-ip-addresses.png
+[7]: ./media/using/using-upgrade-preference.png
 
 <!--Links-->
 

articles/app-service/environment/media/using/using-configuration.png

@@ -8,9 +8,9 @@ ms.topic: include
 ms.date: 06/11/2024
 ---
 
-<!---
 At this time, a test or preview build is not available for the next release.
--->
+
+<!---
 
 Sept, 2024 preview release is now available.
 
@@ -43,3 +43,4 @@ Pre-release Notes:
 - Arc SQL Server | Allow the AG inventory feature for all license types | GA
   - Always On availability groups inventory feature is available for all license type
 - Arc SQL Server | Allow applying physical core license to physical machines | GA
+-->

articles/app-service/environment/media/using/using-ip-addresses.png

@@ -7,7 +7,7 @@ ms.reviewer: mikeray
 services: azure-arc
 ms.service: azure-arc
 ms.subservice: azure-arc-data
-ms.date: 08/22/2024
+ms.date: 09/09/2024
 ms.topic: conceptual
 ms.custom: references_regions, ignite-2023
 #Customer intent: As a data professional, I want to understand why my solutions would benefit from running with Azure Arc-enabled data services so that I can leverage the capability of the feature.
@@ -17,6 +17,12 @@ ms.custom: references_regions, ignite-2023
 
 This article highlights capabilities, features, and enhancements recently released or improved for Azure Arc-enabled data services.
 
+## September 9, 2024
+
+**Image tag**: `v1.33.0_2024-09-10`
+
+For complete release version information, review [Version log](version-log.md#september-9-2024). 
+
 ## August 13, 2024
 
 **Image tag**: `v1.32.0_2024-08-13`

articles/app-service/environment/media/using/using-upgrade-preference.png

@@ -18,6 +18,33 @@ ms.topic: conceptual
 
 This article identifies the component versions with each release of Azure Arc-enabled data services.
 
+## September 9, 2024
+
+|Component|Value|
+|-----------|-----------|
+|Container images tag |`v1.33.0_2024-09-10`|
+|**CRD names and version:**| |
+|`activedirectoryconnectors.arcdata.microsoft.com`| v1beta1, v1beta2, v1, v2|
+|`datacontrollers.arcdata.microsoft.com`| v1beta1, v1 through v5|
+|`exporttasks.tasks.arcdata.microsoft.com`| v1beta1, v1, v2|
+|`failovergroups.sql.arcdata.microsoft.com`| v1beta1, v1beta2, v1, v2|
+|`kafkas.arcdata.microsoft.com`| v1beta1 through v1beta4|
+|`monitors.arcdata.microsoft.com`| v1beta1, v1, v3|
+|`postgresqls.arcdata.microsoft.com`| v1beta1 through v1beta6|
+|`postgresqlrestoretasks.tasks.postgresql.arcdata.microsoft.com`| v1beta1|
+|`sqlmanagedinstances.sql.arcdata.microsoft.com`| v1beta1, v1 through v13|
+|`sqlmanagedinstancemonitoringprofiles.arcdata.microsoft.com`| v1beta1, v1beta2|
+|`sqlmanagedinstancereprovisionreplicatasks.tasks.sql.arcdata.microsoft.com`| v1beta1|
+|`sqlmanagedinstancerestoretasks.tasks.sql.arcdata.microsoft.com`| v1beta1, v1|
+|`telemetrycollectors.arcdata.microsoft.com`| v1beta1 through v1beta5|
+|`telemetryrouters.arcdata.microsoft.com`| v1beta1 through v1beta5|
+|Azure Resource Manager (ARM) API version|2023-11-01-preview|
+|`arcdata` Azure CLI extension version|1.5.18 ([Download](https://aka.ms/az-cli-arcdata-ext))|
+|Arc-enabled Kubernetes helm chart extension version|1.33.0|
+|Azure Arc Extension for Azure Data Studio<br/>`arc`<br/>`azcli`|<br/>1.8.0 ([Download](https://aka.ms/ads-arcdata-ext))</br>1.8.0 ([Download](https://aka.ms/ads-azcli-ext))|
+|SQL Database version | 972 |
+
+
 ## August 13, 2024
 
 |Component|Value|