Merge pull request #163081 from MicrosoftDocs/master

Merge master to live, Sunday 4 PM

Author: jborsecnik

articles/active-directory/fundamentals/active-directory-how-subscriptions-associated-directory.md

@@ -28,6 +28,8 @@ When a user signs up for a Microsoft cloud service, a new Azure AD tenant is
 
 All of your users have a single *home* directory for authentication. Your users can also be guests in other directories. You can see both the home and guest directories for each user in Azure AD.
 
+:::image type="content" source="media/active-directory-how-subscriptions-associated-directory/trust-relationship-azure-ad.png" alt-text="Screenshot that shows the trust relationship between Azure subscriptions and Azure active directories.":::
+
 > [!Important]
 > When you associate a subscription with a different directory, users that have roles assigned using [Azure role-based access control](../../role-based-access-control/role-assignments-portal.md) lose their access. Classic subscription administrators, including Service Administrator and Co-Administrators, also lose access.
 >

articles/azure-monitor/alerts/alerts-common-schema-definitions.md

@@ -174,7 +174,7 @@ Any alert instance describes the resource that was affected and the cause of the
 ### Log alerts
 
 > [!NOTE]
-> For log alerts that have a custom email subject and/or JSON payload defined, enabling the common schema reverts email subject and/or payload schema to the one described as follows. This means that if you want to have a custom JSON payload defined, the webhook cannot use the common alert schema. Alerts with the common schema enabled have an upper size limit of 256 KB per alert. Search results aren't embedded in the log alerts payload if they cause the alert size to cross this threshold. You can determine this by checking the flag `IncludeSearchResults`. When the search results aren't included, you should use the `LinkToFilteredSearchResultsAPI` or `LinkToSearchResultsAPI` to access query results with the [Log Analytics API](/rest/api/loganalytics/dataaccess/query/get).
+> For log alerts that have a custom email subject and/or JSON payload defined, enabling the common schema reverts email subject and/or payload schema to the one described as follows. This means that if you want to have a custom JSON payload defined, the webhook cannot use the common alert schema. Alerts with the common schema enabled have an upper size limit of 256 KB per alert. Search results aren't embedded in the log alerts payload if they cause the alert size to cross this threshold. You can determine this by checking the flag `IncludedSearchResults`. When the search results aren't included, you should use the `LinkToFilteredSearchResultsAPI` or `LinkToSearchResultsAPI` to access query results with the [Log Analytics API](/rest/api/loganalytics/dataaccess/query/get).
 
 #### `monitoringService` = `Log Analytics`
 
@@ -246,7 +246,7 @@ Any alert instance describes the resource that was affected and the cause of the
         ]
       }
     ],
-  "IncludeSearchResults": "True",
+  "IncludedSearchResults": "True",
   "AlertType": "Metric measurement"
   }
 }
@@ -318,7 +318,7 @@ Any alert instance describes the resource that was affected and the cause of the
         }
       ]
     },
-    "IncludeSearchResults": "True",
+    "IncludedSearchResults": "True",
     "AlertType": "Metric measurement"
   }
 }

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

@@ -49,7 +49,7 @@ Ingestion operations are issues that occurred during data ingestion including no
 
 
 #### Operation: Data collection stopped  
-Data collection stopped due to reaching the daily limit.
+"Data collection stopped due to daily limit of free data reached. Ingestion status = OverQuota"
 
 In the past 7 days, logs collection reached the daily set limit. The limit is set either as the workspace is set to "free tier", or daily collection limit was configured for this workspace.
 Note, after reaching the set limit, your data collection will automatically stop for the day and will resume only during the next collection day. 
@@ -63,9 +63,7 @@ Or, you can decide to ([Manage your maximum daily data volume](./manage-cost-sto
 * Data collection rate is calculated per day, and will reset at the start of the next day, you can also monitor collection resume event by [Create an alert](./manage-cost-storage.md#alert-when-daily-cap-reached) on "Data collection resumed" Operation event.
 
 #### Operation: Ingestion rate
-Ingestion rate limit approaching\passed the limit.
-
- Your ingestion rate has passed the 80%; at this point there is not issue. Note, data collected exceeding the threshold will be dropped. </br>
+"The data ingestion volume rate crossed the threshold in your workspace: {0:0.00} MB per one minute and data has been dropped." 
 
 Recommended Actions:
 *	Check _LogOperation table for ingestion rate event 
@@ -81,15 +79,15 @@ For further information: </br>
 
 
 #### Operation: Maximum table column count
-Custom fields count have reached the limit.
+"Data of type \<**table name**\> was dropped because number of fields \<**new fields count**\> is above the limit of \<**current field count limit**\> custom fields per data type." 
 
 Recommended Actions: 
 For custom tables, you can move to [Parsing the data](./parse-text.md) in queries.
 
 #### Operation: Field content validation
-One of the fields of the data being ingested had more than 32 Kb in size, so it got truncated.
+"The following fields' values \<**field name**\> of type \<**table name**\> have been trimmed to the max allowed size, \<**field size limit**\> bytes. Please adjust your input accordingly." 
 
-Log Analytics limits ingested fields size to 32 Kb, larger size fields will be trimmed to 32 Kb. We don’t recommend sending fields larger than 32 Kb as the trim process might remove important information. 
+Field larger then the limit size was proccessed by Azure logs, the field was trimed to the allowed field limit. We don’t recommend sending fields larger than the allowed limit as this will resualt in data loss. 
 
 Recommended Actions:
 Check the source of the affected data type:
@@ -100,6 +98,8 @@ Check the source of the affected data type:
 
 ### Data collection
 #### Operation: Azure Activity Log collection
+"Access to the subscription was lost. Ensure that the \<**subscription id**\> subscription is in the \<**tenant id**\> Azure Active Directory tenant. If the subscription is transferred to another tenant, there is no impact to the services, but information for the tenant could take up to an hour to propagate. '"
+
 Description: In some situations, like moving a subscription to a different tenant, the Azure Activity logs might stop flowing in into the workspace. In those situations, we need to reconnect the subscription following the process described in this article.
 
 Recommended Actions: 
@@ -111,6 +111,8 @@ Recommended Actions:
 
 ### Agent
 #### Operation: Linux Agent
+"Two successive configuration applications from OMS Settings failed"
+
 Config settings on the portal have changed.
 
 Recommended Action

articles/key-vault/managed-hsm/private-link.md

@@ -11,7 +11,10 @@ ms.custom: devx-track-azurecli
 
 ---
 
-# Integrate Managed HSM with Azure Private Link
+# Integrate Managed HSM with Azure Private Link (preview)
+
+>[!NOTE]
+> Azure private endpoints feature for Managed HSM is currently available as **a preview** in following regions: **UK South, Europe West, Canada Central, Australia Central**, and **Asia East**. It will be available in all the [other regions](https://azure.microsoft.com/global-infrastructure/services/?products=key-vault&regions=all) in next few days.
 
 Azure Private Link Service enables you to access Azure Services (for example, Managed HSM, Azure Storage, and Azure Cosmos DB etc.) and Azure hosted customer/partner services over a Private Endpoint in your virtual network.
 

articles/synapse-analytics/sql/develop-tables-statistics.md

@@ -199,7 +199,7 @@ Another option you have is to specify the sample size as a percent:
 ```sql
 CREATE STATISTICS col1_stats
     ON dbo.table1 (col1)
-    WITH SAMPLE = 50 PERCENT;
+    WITH SAMPLE 50 PERCENT;
 ```
 
 #### Create single-column statistics on only some of the rows
@@ -227,7 +227,7 @@ You can also combine the options together. The following example creates a filte
 CREATE STATISTICS stats_col1
     ON table1 (col1)
     WHERE col1 > '2000101' AND col1 < '20001231'
-    WITH SAMPLE = 50 PERCENT;
+    WITH SAMPLE 50 PERCENT;
 ```
 
 For the full reference, see [CREATE STATISTICS](/sql/t-sql/statements/create-statistics-transact-sql?view=azure-sqldw-latest&preserve-view=true).
@@ -245,7 +245,7 @@ In this example, the histogram is on *product\_category*. Cross-column statistic
 CREATE STATISTICS stats_2cols
     ON table1 (product_category, product_sub_category)
     WHERE product_category > '2000101' AND product_category < '20001231'
-    WITH SAMPLE = 50 PERCENT;
+    WITH SAMPLE 50 PERCENT;
 ```
 
 Because a correlation exists between *product\_category* and *product\_sub\_category*, a multi-column statistics object can be useful if these columns are accessed at the same time.