Merge pull request #274681 from MicrosoftDocs/repo_sync_working_branch

Taojunshen · web-flow · commit a18cbefe689b · 2024-05-09T00:32:05.000+08:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/azure-monitor/alerts/action-groups.md b/articles/azure-monitor/alerts/action-groups.md
@@ -23,6 +23,7 @@ Global requests from clients can be processed by action group services in any re
 - You can add up to five action groups to an alert rule.
 - Action groups are executed concurrently, in no specific order.
 - Multiple alert rules can use the same action group.
+- Action Groups are defined by the unique set of actions and the users to be notified. For example, if you want to notify User1, User2 and User3 by email for two different alert rules, you only need to create one action group which you can apply to both alert rules.
 
 ## Create an action group in the Azure portal
 1. Go to the [Azure portal](https://portal.azure.com/).
diff --git a/articles/azure-signalr/signalr-concept-internals.md b/articles/azure-signalr/signalr-concept-internals.md
@@ -28,18 +28,18 @@ A self-hosted ASP.NET Core SignalR application server listens to and connects cl
 With SignalR Service, the application server no longer accepts persistent client connections, instead:
 
 1. A `negotiate` endpoint is exposed by Azure SignalR Service SDK for each hub.
-1. The endpoint responds to client negotiation requests and redirect clients to SignalR Service.
+1. The endpoint responds to client negotiation requests and redirects clients to SignalR Service.
 1. The clients connect to SignalR Service.
 
 For more information, see [Client connections](#client-connections).
 
 Once the application server is started:
 
 - For ASP.NET Core SignalR: Azure SignalR Service SDK opens five WebSocket connections per hub to SignalR Service. 
-- For ASP.NET SignalR: Azure SignalR Service SDK opens five WebSocket connections per hub to SignalR Service, and one per application WebSocket connection.
+- For ASP.NET SignalR: Azure SignalR Service SDK opens five WebSocket connections per hub to SignalR Service and one per application WebSocket connection.
 
 
-The initial number of connections defaults to 5 and is configurable using the `InitialHubServerConnectionCount` option in the SignalR Service SDK.  For more information, see  [configuration](https://github.com/Azure/azure-signalr/blob/dev/docs/run-asp-net-core.md#maxhubserverconnectioncount). 
+The initial number of connections defaults to 5 and is configurable using the `InitialHubServerConnectionCount` option in the SignalR Service SDK.  For more information, see  [configuration](signalr-howto-use.md#configure-options). 
 
 While the application server is connected to the SignalR service, the Azure SignalR service may send load-balancing messages to the server.  Then, the SDK starts new server connections to the service for better performance. Messages to and from clients are multiplexed into these connections.
 
diff --git a/articles/azure-signalr/signalr-howto-scale-multi-instances.md b/articles/azure-signalr/signalr-howto-scale-multi-instances.md
@@ -31,7 +31,7 @@ dotnet user-secrets set Azure:SignalR:ConnectionString:backup:secondary <Connect
 
 ### Add multiple endpoints from code
 
-A `ServicEndpoint` class describes the properties of an Azure SignalR Service endpoint.
+A `ServiceEndpoint` class describes the properties of an Azure SignalR Service endpoint.
 You can configure multiple instance endpoints when using Azure SignalR Service SDK through:
 ```cs
 services.AddSignalR()
@@ -274,4 +274,4 @@ When no `primary` endpoint is available, the client's `/negotiate` picks from th
 You can use multiple endpoints in high availability and disaster recovery scenarios.
 
 > [!div class="nextstepaction"]
-> [Setup SignalR Service for disaster recovery and high availability](./signalr-concept-disaster-recovery.md)
+> [Setup SignalR Service for disaster recovery and high availability](./signalr-concept-disaster-recovery.md)
diff --git a/articles/connectors/connectors-create-api-crmonline.md b/articles/connectors/connectors-create-api-crmonline.md
@@ -14,7 +14,7 @@ ms.date: 01/04/2024
 > The Dynamics 365 connector is officially deprecated and is no longer available. Instead, use the 
 > [Microsoft Dataverse connector](/connectors/commondataserviceforapps/) to access Microsoft Dataverse 
 > used for Microsoft Dynamics 365 Sales, Microsoft Dynamics 365 Customer Service, Microsoft Dynamics 365 
-> Field Service, Microsoft Dynamics 365 Marketing, and Microsoft Dynamics 365 Project Service Automation.
+> Field Service, Microsoft Dynamics 365 Customer Insights - Journeys, and Microsoft Dynamics 365 Project Service Automation.
 >
 > The Dataverse connector replaces the Microsoft Dataverse (Legacy) connector, previously named as the 
 > Common Data Service 2.0 connector, which replaced the Dynamics 365 connector.
diff --git a/articles/container-apps/scale-app.md b/articles/container-apps/scale-app.md
@@ -214,6 +214,9 @@ az containerapp create \
   --image <CONTAINER_IMAGE_LOCATION>
   --min-replicas 0 \
   --max-replicas 5 \
+  --transport tcp \
+  --ingress <external/internal> \
+  --target-port <CONTAINER_TARGET_PORT> \
   --scale-rule-name azure-tcp-rule \
   --scale-rule-type tcp \
   --scale-rule-tcp-concurrency 100
diff --git a/articles/container-registry/container-registry-artifact-streaming.md b/articles/container-registry/container-registry-artifact-streaming.md
@@ -95,7 +95,7 @@ Start artifact streaming, by following these general steps:
 
     ```azurecli-interactive
     az configure --defaults acr="mystreamingtest"
-    az acr import -source docker.io/jupyter/all-spark-notebook:latest -t jupyter/all-spark-notebook:latest
+    az acr import --source docker.io/jupyter/all-spark-notebook:latest -t jupyter/all-spark-notebook:latest
     ```
 
 3. Create an artifact streaming from the Image
diff --git a/articles/cosmos-db/try-free.md b/articles/cosmos-db/try-free.md
@@ -42,7 +42,7 @@ The following table lists the limits for the [Try Azure Cosmos DB](https://aka.m
 ² After expiration, the information stored in your account is deleted. You can upgrade your account prior to expiration and migrate the information stored.
 
 > [!NOTE]
-> Try Azure Cosmos DB supports global distribution in only the **East US**, **North Europe**, **Southeast Asia**, and **North Central US** regions. Azure support tickets can't be created for Try Azure Cosmos DB accounts. However, support is provided for subscribers with existing support plans.
+> Try Azure Cosmos DB supports global distribution in only the **East US**, **North Europe**, **Southeast Asia**, and **North Central US** regions. Azure support tickets can't be created for Try Azure Cosmos DB accounts. However, support is provided for subscribers with existing support plans. If the account exceeds the maximum resource limits, it's automatically deleted.
 
 ### [MongoDB](#tab/mongodb)
 
@@ -75,7 +75,7 @@ The following table lists the limits for the [Try Azure Cosmos DB](https://aka.m
 | Maximum storage size (GiB) | 128 |
 
 ¹ A new trial can be requested after expiration.
-² After expiration, the information stored in your account is deleted. You can upgrade your account prior to expiration and migrate the information stored.
+² After expiration, the information stored in your account is deleted. You can upgrade your account prior to expiration and migrate the information stored. If the account exceeds the maximum resource limits, it's automatically deleted.
 
 ---
 
diff --git a/articles/event-grid/includes/limits.md b/articles/event-grid/includes/limits.md
@@ -44,10 +44,14 @@ The following limits apply to MQTT in Azure Event Grid namespace resource.
 | Inbound MQTT bandwidth per Event Grid namespace         | 1 MB per second per TU                                                            |
 | Inbound MQTT publishing requests per session | 100 messages per second                                                           |
 | Inbound MQTT bandwidth per session        | 1 MB per second                                                                   |
+| Inbound in-flight MQTT messages*        | 100 messages                                                                   |
+| Inbound in-flight MQTT bandwidth*         | 64 KB                                                             |
 | Outbound MQTT publishing requests per Event Grid namespace | 1,000 messages per second per TU                                                         |
 | Outbound MQTT bandwidth per Event Grid namespace        | 1 MB per second per TU                                                            |
 | Outbound MQTT publishing requests per session| 100 messages per second                                                           |
 | Outbound MQTT bandwidth per session       | 1 MB per second                                                                   |
+| Outbound in-flight MQTT messages*        | 100 messages                                                                   |
+| Outbound in-flight MQTT bandwidth*         | 64 KB                                                             |
 | Max message size                             | 512 KB                                                                            |
 | Segments per topic/ topic filter             | 8                                                                                 |
 | Topic size                                   | 256 B                                                                             |
@@ -72,6 +76,8 @@ The following limits apply to MQTT in Azure Event Grid namespace resource.
 | Topic templates                              | 10 per topic space                                                                |
 | Permission bindings                          | 100                                                                               |
 
+\* For MQTTv5, learn more about [flow control support](../mqtt-support.md#flow-control).
+
 ## Events limits in Event Grid namespace
 
 The following limits apply to events in Azure Event Grid namespace resource.
diff --git a/articles/expressroute/expressroute-howto-coexist-resource-manager.md b/articles/expressroute/expressroute-howto-coexist-resource-manager.md
@@ -34,7 +34,6 @@ The steps to configure both scenarios are covered in this article. This article
 * ExpressRoute-VPN Gateway coexist configurations are **not supported on the Basic SKU**.
 * If you want to use transit routing between ExpressRoute and VPN, **the ASN of Azure VPN Gateway must be set to 65515, and Azure Route Server should be used.** Azure VPN Gateway supports the BGP routing protocol. For ExpressRoute and Azure VPN to work together, you must keep the Autonomous System Number of your Azure VPN gateway at its default value, 65515. If you previously selected an ASN other than 65515 and you change the setting to 65515, you must reset the VPN gateway for the setting to take effect.
 * **The gateway subnet must be /27 or a shorter prefix**, such as /26, /25, or you receive an error message when you add the ExpressRoute virtual network gateway.
-* **Coexistence in a dual-stack virtual network is not supported.** If you're using ExpressRoute IPv6 support and a dual-stack ExpressRoute gateway, coexistence with VPN Gateway isn't possible.
 
 ## Configuration designs
 
diff --git a/articles/operator-insights/operator-insights-faq.yml b/articles/operator-insights/operator-insights-faq.yml
@@ -44,6 +44,7 @@ sections:
           - UK South
           - North Europe 
           - West Europe
-          - Australia East 
+          - Australia East
+          - UAE North
 
           We'll be enabling other regions. If your region isn't in the list, contact your local Microsoft representative.
diff --git a/articles/virtual-machines/linux/endorsed-distros.md b/articles/virtual-machines/linux/endorsed-distros.md
@@ -47,20 +47,20 @@ Images published and maintained by either Microsoft or partners. There are a lar
 Platform Images are a type of Marketplace images for which Microsoft has partnered with several mainstream publishers (see table below about Partners) to create a set of “platform images” that undergo additional testing and receive predictable updates (see section below on Image Update Cadence). These platform images can be used for building your own custom images and solution stacks. These images are published by the endorsed Linux distribution partners such as Canonical (Ubuntu), Red Hat (RHEL), and Credativ (Debian). 
 
 
-Microsoft CSS provides commercially reasonable support for these images. Additionally, Red Hat, Canonical, and SUSE offer integrated vendor support capabilities for their platform images.  
+Microsoft provides commercially reasonable customer support for these images. Additionally, Red Hat, Canonical, and SUSE offer integrated vendor support capabilities for their platform images.
 
 
 ### Custom Images 
 These images are created and maintained by the customer, often based on platform images. These images can also be created from scratch and uploaded to Azure - [learn how to create custom images](tutorial-custom-images.md). Customers can host these images in [Azure Compute Gallery](../azure-compute-gallery.md) and they can share these images with others in their organization.  
 
  
-Microsoft CSS provides commercially reasonable support for custom images. 
+Microsoft provides commercially reasonable customer support for custom images. 
 
 ### Community Gallery Images
 These images are created and provided by open source projects, communities and teams. These images are provided using licensing terms set out by the publisher, often under an open source license. They do not appear as traditional marketplace listings, however, they do appear in the portal and via command line tools. More information on community galleries can be found here: [Azure Compute Gallery](../azure-compute-gallery.md#community-gallery).
 
 
-Microsoft CSS provides support for Community Gallery images. 
+Microsoft provides commercially reasonable support for Community Gallery images. 
 
 
 

Original file line number	Diff line number	Diff line change
`@@ -14,7 +14,7 @@ ms.date: 01/04/2024`
`14`	`14`	`> The Dynamics 365 connector is officially deprecated and is no longer available. Instead, use the`
`15`	`15`	`> [Microsoft Dataverse connector](/connectors/commondataserviceforapps/) to access Microsoft Dataverse`
`16`	`16`	`> used for Microsoft Dynamics 365 Sales, Microsoft Dynamics 365 Customer Service, Microsoft Dynamics 365`
`17`		`-> Field Service, Microsoft Dynamics 365 Marketing, and Microsoft Dynamics 365 Project Service Automation.`
	`17`	`+> Field Service, Microsoft Dynamics 365 Customer Insights - Journeys, and Microsoft Dynamics 365 Project Service Automation.`
`18`	`18`	`>`
`19`	`19`	`> The Dataverse connector replaces the Microsoft Dataverse (Legacy) connector, previously named as the`
`20`	`20`	`> Common Data Service 2.0 connector, which replaced the Dynamics 365 connector.`