Merge pull request #309188 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/connectors/connectors-azure-monitor-logs.md

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 04/15/2025
+ms.date: 12/09/2025
 # Customer intent: As a developer, I want to get log data from my Log Analytics workspace or telemetry from my Application Insights resource to use with my workflow in Azure Logic Apps.
 ---
 
@@ -41,7 +41,9 @@ Both of the following actions can run a log query against a Log Analytics worksp
 
 ## Limitations
 
-- The connector has the following limits, which your workflow might reach, based on the query that you use and the size of the results:
+- Visualizations on the Logs page and the connector use different charting libraries. So, the connector currently doesn't include some functionality.
+- Query data in Basic and Auxiliary plans isn't supported by Azure Monitor Logs connector.
+- The connector has the following query limits. To avoid limits, try aggregating data to reduce the results count or volume, or adjusting the workflow recurrence to run more frequently across a smaller time range.
 
   | Limit | Value | Notes | 
   |-------|-------|-------|
@@ -50,10 +52,6 @@ Both of the following actions can run a log query against a Log Analytics worksp
   | Max connector timeout | 110 seconds ||
   | Max query timeout | 100 seconds ||
 
-  To avoid reaching these limits, try aggregating data to reduce the results size, or adjusting the workflow recurrence to run more frequently across a smaller time range.
-
-- Visualizations on the Logs page and the connector use different charting libraries. So, the connector currently doesn't include some functionality.
-
 ## Prerequisites
 
 - An Azure account and subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).

articles/cost-management-billing/manage/mosp-ea-transfer.md

@@ -73,34 +73,9 @@ As described in the [prerequisites](#access-to-the-destination-ea) section, you
 After the EA account owner is created the subscription account Administrator, who is also now an EA account owner, receives an email. It notifies the user that they're now an EA Account Owner. If the user doesn't have access to an email mailbox associated with the account specified, there's no need to worry. The email is only a notification. Information in the email isn't required to proceed. However, an email mailbox is advised for future notifications about the subscription.
 
 ### Complete the subscription transfer
-
-Now that the subscription account administrator is also an EA account owner, they can create subscriptions under the EA.
-
-> [!IMPORTANT]
-> Before proceeding you need to understand what happens when a new EA account owner signs in to the Azure portal for the first time. Read and understand the following information before you sign in as the subscription account administrator.
-
-The first time a new EA account owner signs in to the Azure portal, they see the following warning:
-
-```
-WARNING
-
-You are about to associate your account (email address) to the following enrollment:
-
-Enrollment Name: <EnrollmentName>
-Enrollment Number: <EnrollmentNumber>
-
-All Enrollment Administrators can gain access to all of your subscriptions if you proceed.
-Additionally, all Azure subscriptions for which you are the account owner will be converted to your Enterprise Agreement.
-This includes subscriptions which include a monthly credit (e.g. Visual Studio, Microsoft Cloud Partner Program, BizSpart, etc.) meaning you will lose the monthly credit by proceeding.
-All subscriptions based on a Visual Studio subscriber offer (monthly credit for Visual Studio subscribers or Pay-As-You-Go Dev/Test) will be converted to use the Enterprise Dev/Test usage rates and be billed against this enrollment from today onwards.
-If you wish to retain the monthly credits currently associated with any of your subscriptions, please cancel.
-Please see additional details.
-
-Cancel  Continue
-```
+To complete the subscription transfer, a new EA Account owner needs to [activate account](direct-ea-administration.md#to-confirm-account-ownership-1) on the Azure portal.
 
 The warning states the following:
-
 ***When a user is added as an account owner, any Azure subscriptions associated with the account owner that are based on either the MOSP (PAYG) Dev/Test offer or the monthly credit offers for Visual Studio subscribers will be converted to the EA Dev/Test offer. Subscriptions based on other offer types, such as MOSP (PAYG), associated with the Account Owner will be converted to the standard EA subscription offer.***
 
 If the user understands the consequences of the warning, select **Continue** and the subscriptions associated with their account are transferred to the EA.

articles/service-bus-messaging/service-bus-async-messaging.md

@@ -11,6 +11,8 @@ Asynchronous messaging can be implemented in a variety of different ways. With q
 
 Applications typically use asynchronous messaging patterns to enable a number of communication scenarios. You can build applications in which clients can send messages to services, even when the service is not running. For applications that experience bursts of communications, a queue can help [level the load](/azure/architecture/patterns/queue-based-load-leveling) by providing a place to buffer communications. Finally, you can get a simple but effective load balancer to distribute messages across multiple machines.
 
+For a real-world analogy of asynchronous scalability and expected delays or retries, see Gregor Hohpe’s [Starbucks Does Not Use Two-Phase Commit](https://www.enterpriseintegrationpatterns.com/ramblings/18_starbucks.html) and the follow-up [What Starbucks Can Teach Us About Software Scalability](https://particular.net/blog/what-starbucks-can-teach-us-about-software-scalability). They offer a clear mental model for how Service Bus behaves under load.
+
 In order to maintain availability of any of these entities, consider a number of different ways in which these entities can appear unavailable for a durable messaging system. Generally speaking, we see the entity becomes unavailable to applications we write in the following different ways:
 
 * Unable to send messages.