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

Author: duongau

.openpublishing.redirection.json

@@ -2595,6 +2595,11 @@
       "redirect_url": "/azure/azure-maps/zoom-levels-and-tile-grid",
       "redirect_document_id": true
     },
+    {
+      "source_path": "articles/managed-grafana/how-to-sync-teams-with-azure-ad-groups.md",
+      "redirect_url": "managed-grafana/how-to-sync-teams-with-entra-groups",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/media-services/azure-media-player/azure-media-player-license.md",
       "redirect_url": "/legal/azure-media-player/azure-media-player-license",

articles/app-service/environment/overview.md

@@ -69,7 +69,7 @@ A benefit of using an App Service Environment instead of a multitenant service i
 App Service Environment v3 differs from earlier versions in the following ways:
 
 - There are no networking dependencies on the customer's virtual network. You can secure all inbound and outbound traffic and route outbound traffic as you want.
-- You can deploy an App Service Environment v3 that's enabled for zone redundancy. You set zone redundancy only during creation and only in regions where all App Service Environment v3 dependencies are zone redundant. In this case, each App Service Plan on the App Service Environment will need to have a minimum of three instances so that they can be spread across zones. For more information, see [Migrate App Service Environment to availability zone support](../../availability-zones/migrate-app-service-environment.md).
+- You can deploy an App Service Environment v3 that's enabled for zone redundancy. You set zone redundancy only during creation and only in regions where all App Service Environment v3 dependencies are zone redundant. This is a deployment time only decision. Changing zone redundancy is not possible after it has been deployed. With zone redundant App Service Environment, each App Service Plan on the App Service Environment will need to have a minimum of three instances so that they can be spread across zones. For more information, see [Migrate App Service Environment to availability zone support](../../availability-zones/migrate-app-service-environment.md).
 - You can deploy an App Service Environment v3 on a dedicated host group. Host group deployments aren't zone redundant.
 - Scaling is much faster than with an App Service Environment v2. Although scaling still isn't immediate, as in the multitenant service, it's a lot faster.
 - Front-end scaling adjustments are no longer required. App Service Environment v3 front ends automatically scale to meet your needs and are deployed on better hosts.
@@ -165,6 +165,7 @@ App Service Environment v3 is available in the following regions:
 | Southeast Asia       | ✅                           | ✅                          |
 | Spain Central        | ✅                           | ✅**                        |
 | Sweden Central       | ✅                           | ✅                          |
+| Sweden South         | ✅                           |                             |
 | Switzerland North    | ✅                           | ✅                          |
 | Switzerland West     | ✅                           |                             |
 | UAE Central          | ✅                           |                             |
@@ -188,23 +189,109 @@ App Service Environment v3 is available in the following regions:
 | US DoD Central       | ✅                           |                             |
 | US DoD East          | ✅                           |                             |
 | US Gov Arizona       | ✅                           |                             |
-| US Gov Iowa          |                              |                             |
 | US Gov Texas         | ✅                           |                             |
 | US Gov Virginia      | ✅                           |✅                          |
 
 ### Microsoft Azure operated by 21Vianet
 
 | Region               | Single zone support          | Availability zone support   |
 | -------------------- | :--------------------------: | :-------------------------: |
-| China East 2         |                              |                             |
+|                      | App Service Environment v3   | App Service Environment v3  |
 | China East 3         | ✅                          |                              |
-| China North 2        |                              |                             |
 | China North 3        | ✅                          | ✅                          |
 
 ### In-region data residency
 
 An App Service Environment will only store customer data including app content, settings and secrets within the region where it's deployed. All data is guaranteed to remain in the region. For more information, see [Data residency in Azure](https://azure.microsoft.com/explore/global-infrastructure/data-residency/#overview).
 
+## Pricing tiers
+
+The following sections list the regional pricing tiers (SKUs) availability for App Service Environment v3.
+
+> [!NOTE]
+> Windows Container plans currently do not support memory intensive SKUs.
+>
+ 
+### Azure Public:
+
+| Region               | Standard     | Large       | Memory intensive  |
+| -------------------- | :----------: | :---------: | :---------------: |
+|                      | I1v2-I3v2    | I4v2-I6v2   | I1mv2-I5mv2       |
+| Australia Central    | ✅          | ✅          | ✅               | 
+| Australia Central 2  | ✅          | ✅          | ✅               | 
+| Australia East       | ✅          | ✅          | ✅               | 
+| Australia Southeast  | ✅          | ✅          | ✅               | 
+| Brazil South         | ✅          | ✅          |                   | 
+| Brazil Southeast     | ✅          | ✅          | ✅               |
+| Canada Central       | ✅          | ✅          | ✅               |
+| Canada East          | ✅          | ✅          | ✅               | 
+| Central India        | ✅          | ✅          | ✅               | 
+| Central US           | ✅          | ✅ *        |                   | 
+| East Asia            | ✅          | ✅          | ✅               |
+| East US              | ✅          | ✅          |                   | 
+| East US 2            | ✅          | ✅          | ✅               |
+| France Central       | ✅          | ✅          | ✅               | 
+| France South         | ✅          | ✅          | ✅               | 
+| Germany North        | ✅          | ✅          | ✅               | 
+| Germany West Central | ✅          | ✅          | ✅               | 
+| Israel Central       | ✅          | ✅          |                   | 
+| Italy North          | ✅          | ✅          |                   | 
+| Japan East           | ✅          | ✅          | ✅               | 
+| Japan West           | ✅          | ✅          | ✅               | 
+| Jio India Central    | ✅          | ✅          |                   | 
+| Jio India West       | ✅          | ✅          |                   | 
+| Korea Central        | ✅          | ✅          |                   | 
+| Korea South          | ✅          | ✅          | ✅               |
+| Mexico Central       | ✅          | ✅          |                   | 
+| North Central US     | ✅          | ✅          | ✅               | 
+| North Europe         | ✅          | ✅          | ✅               |
+| Norway East          | ✅          | ✅          | ✅               | 
+| Norway West          | ✅          | ✅          | ✅               |
+| Poland Central       | ✅          | ✅          |                   |
+| Qatar Central        | ✅          | ✅          |                   |
+| South Africa North   | ✅          | ✅          | ✅               |
+| South Africa West    | ✅          | ✅          | ✅               | 
+| South Central US     | ✅          | ✅          | ✅               |
+| South India          | ✅          | ✅          |                   | 
+| Southeast Asia       | ✅          | ✅          | ✅               |
+| Spain Central        | ✅          | ✅          |                   | 
+| Sweden Central       | ✅          | ✅          | ✅               |
+| Sweden South         | ✅          | ✅          | ✅               |
+| Switzerland North    | ✅          | ✅          | ✅               |
+| Switzerland West     | ✅          | ✅          | ✅               | 
+| UAE Central          | ✅          | ✅          |                   | 
+| UAE North            | ✅          | ✅          | ✅               | 
+| UK South             | ✅          | ✅          | ✅               | 
+| UK West              | ✅          | ✅          | ✅               | 
+| West Central US      | ✅          | ✅ *        |                   | 
+| West Europe          | ✅          | ✅ *        |                   | 
+| West India           | ✅          | ✅          | ✅               | 
+| West US              | ✅          | ✅          |                   | 
+| West US 2            | ✅          | ✅          | ✅               | 
+| West US 3            | ✅          | ✅          | ✅               | 
+
+\* Windows Container does not support Large skus in this region.
+\** Linux does not support Memory intensive skus in this region.
+
+### Azure Government:
+
+| Region               | Standard     | Large       | Memory intensive  |
+| -------------------- | :----------: | :---------: | :---------------: |
+|                      | I1v2-I3v2    | I4v2-I6v2   | I1mv2-I5mv2       |
+| US DoD Central       | ✅          |✅ *         |                   |
+| US DoD East          | ✅          |✅ *         |                   |
+| US Gov Arizona       | ✅          |✅ *         |                   |
+| US Gov Texas         | ✅          |✅ *         |                   |
+| US Gov Virginia      | ✅          |✅ *         |                   |
+
+### Microsoft Azure operated by 21Vianet:
+
+| Region               | Standard     | Large       | Memory intensive  |
+| -------------------- | :----------: | :---------: | :---------------: |
+|                      | I1v2-I3v2    | I4v2-I6v2   | I1mv2-I5mv2       |
+| China East 3         | ✅          | ✅ *        |                   |
+| China North 3        | ✅          | ✅ *        |                   |
+
 ## Next steps
 
 > [!div class="nextstepaction"]

articles/automation/troubleshoot/change-tracking.md

@@ -136,7 +136,6 @@ Here are possible causes specific to this issue:
 Verify that the daemon for the Log Analytics agent for Linux (**omsagent**) is running on your machine. Run the following query in the Log Analytics workspace that's linked to your Automation account.
 
 ```loganalytics
-Copy
 Heartbeat
 | summarize by Computer, Solutions
 ```

articles/container-apps/media/observability/metrics-alert-split-by-dimension.png

@@ -5,7 +5,7 @@ services: container-apps
 author: v-jaswel
 ms.service: azure-container-apps
 ms.topic: how-to
-ms.date: 04/30/2024
+ms.date: 09/23/2024
 ms.author: v-wellsjason
 ---
 
@@ -19,23 +19,23 @@ The metrics explorer in the Azure portal allows you to visualize the data. You c
 
 Container Apps provides these basic metrics.
 
-| Category | Title | Description | Metric ID | Unit |
+| Title | Dimensions | Description | Metric ID | Unit |
 |--|--|--|--|--|
-| Basic | CPU Usage | CPU consumed by the container app, in nano cores (1,000,000,000 nanocores = 1 core) | UsageNanoCores | `nanocores` |
-| Basic | Memory Working Set Bytes | Container app working set memory used in bytes | `WorkingSetBytes` | bytes |
-| Basic | Network In Bytes | Network received bytes | `RxBytes` | bytes |
-| Basic | Network Out Bytes | Network transmitted bytes | `TxBytes` | bytes |
-| Basic | Replica count | Number of active replicas | `Replicas` | n/a |
-| Basic | Replica Restart Count | Restarts count of container app replicas | `RestartCount` | n/a |
-| Basic | Requests | Requests processed | `Requests` | n/a |
-| Basic | Reserved Cores | Number of reserved cores for container app revisions | `CoresQuotaUsed` | n/a |
-| Basic | Resiliency Connection Timeouts | Total connection timeouts | `ResiliencyConnectTimeouts` | n/a |
-| Basic | Resiliency Ejected Hosts | Number of currently ejected hosts | `ResiliencyEjectedHosts` | n/a |
-| Basic | Resiliency Ejections Aborted | Number of ejections aborted due to the max ejection % | `ResiliencyEjectionsAborted` | n/a |
-| Basic | Resiliency Request Retries | Total request retries | `ResiliencyRequestRetries` | n/a |
-| Basic | Resiliency Request Timeouts | Total requests that timed out waiting for a response | `ResiliencyRequestTimeouts` | n/a |
-| Basic | Resiliency Requests Pending Connection Pool | Total requests pending a connection pool connection | `ResiliencyRequestsPendingConnectionPool` | n/a |
-| Basic | Total Reserved Cores | Total cores reserved for the container app | `TotalCoresQuotaUsed` | n/a |
+| CPU Usage | Replica, Revision | CPU consumed by the container app, in nano cores (1,000,000,000 nanocores = 1 core) | `UsageNanoCores` | nanocores |
+| Memory Working Set Bytes | Replica, Revision | Container app working set memory used in bytes | `WorkingSetBytes` | bytes |
+| Network In Bytes | Replica, Revision | Network received bytes | `RxBytes` | bytes |
+| Network Out Bytes | Replica, Revision | Network transmitted bytes | `TxBytes` | bytes |
+| Replica count | Revision | Number of active replicas | `Replicas` | n/a |
+| Replica Restart Count | Replica, Revision | Restarts count of container app replicas | `RestartCount` | n/a |
+| Requests | Replica, Revision, Status Code, Status Code Category | Requests processed | `Requests` | n/a |
+| Reserved Cores | Revision | Number of reserved cores for container app revisions | `CoresQuotaUsed` | n/a |
+| Resiliency Connection Timeouts | Revision | Total connection timeouts | `ResiliencyConnectTimeouts` | n/a |
+| Resiliency Ejected Hosts | Revision | Number of currently ejected hosts | `ResiliencyEjectedHosts` | n/a |
+| Resiliency Ejections Aborted | Revision | Number of ejections aborted due to the max ejection % | `ResiliencyEjectionsAborted` | n/a |
+| Resiliency Request Retries | Revision | Total request retries | `ResiliencyRequestRetries` | n/a |
+| Resiliency Request Timeouts | Revision | Total requests that timed out waiting for a response | `ResiliencyRequestTimeouts` | n/a |
+| Resiliency Requests Pending Connection Pool | Replica | Total requests pending a connection pool connection | `ResiliencyRequestsPendingConnectionPool` | n/a |
+| Total Reserved Cores | None | Total cores reserved for the container app | `TotalCoresQuotaUsed` | n/a |
 
 The metrics namespace is `microsoft.app/containerapps`.
 

articles/container-apps/metrics.md

@@ -26,7 +26,7 @@ See the following quickstarts in the **azure-event-hubs-for-kafka** repo:
 | [Go](https://github.com/Azure/azure-event-hubs-for-kafka/tree/master/quickstart/go) | <p>This quickstart will show how to create and connect to an Event Hubs Kafka endpoint using an example producer and consumer written in Go.</p><p>This sample is based on [Confluent's Apache Kafka Golang client](https://github.com/confluentinc/confluent-kafka-go), modified for use with Event Hubs for Kafka.</p>| 
 | [Sarama kafka Go](https://github.com/Azure/azure-event-hubs-for-kafka/tree/master/quickstart/go-sarama-client) | This quickstart will show how to create and connect to an Event Hubs Kafka endpoint using an example producer and consumer written in Go using the [Sarama Kafka client](https://github.com/Shopify/sarama) library. |
 | [Kafka](https://github.com/Azure/azure-event-hubs-for-kafka/tree/master/quickstart/kafka-cli) | This quickstart will show how to create and connect to an Event Hubs Kafka endpoint using the CLI that comes bundled with the Apache Kafka distribution.| 
-| [Kafkacat](https://github.com/Azure/azure-event-hubs-for-kafka/tree/master/quickstart/kafkacat) | kafkacat is a non-JVM command-line consumer and producer based on librdkafka, popular due to its speed and small footprint. This quickstart contains a sample configuration and several simple sample kafkacat commands. | 
+| [kcat](https://github.com/Azure/azure-event-hubs-for-kafka/tree/master/quickstart/kafkacat) | kcat is a non-JVM command-line consumer and producer based on librdkafka, popular due to its speed and small footprint. This quickstart contains a sample configuration and several simple sample kafkacat commands. | 
 
 ### Quickstarts in DOCS
 See the quickstart: [Data streaming with Event Hubs using the Kafka protocol](event-hubs-quickstart-kafka-enabled-event-hubs.md) in this content set, which provides step-by-step instructions on how to stream into Event Hubs. You learn how to use your producers and consumers to talk to Event Hubs with just a configuration change in your applications.