Merge pull request #76802 from MicrosoftDocs/repo_sync_working_branch

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

Author: huypub

articles/iot-central/howto-create-custom-rules.md

@@ -348,4 +348,4 @@ In this how-to guide, you learned how to:
 * Create a Stream Analytics query that detects when a device has stopped sending data.
 * Send an email notification using the Azure Functions and SendGrid services.
 
-Now that you know how to create custom rules and notifications, the suggested next step is to learn how to[Visualize and analyze your Azure IoT Central data in a Power BI dashboard](howto-connect-powerbi.md).
+Now that you know how to create custom rules and notifications, the suggested next step is to learn how to [Visualize and analyze your Azure IoT Central data in a Power BI dashboard](howto-connect-powerbi.md).

articles/stream-analytics/stream-analytics-custom-path-patterns-blob-storage-output.md

@@ -21,7 +21,7 @@ Custom field or input attributes improve downstream data-processing and reportin
 
 ### Partition key options
 
-The partition key, or column name, used to partition input data may contain alphanumeric characters with hyphens, underscores, and spaces. It is not possible to use nested fields as a partition key unless used in conjunction with aliases.
+The partition key, or column name, used to partition input data may contain alphanumeric characters with hyphens, underscores, and spaces. It is not possible to use nested fields as a partition key unless used in conjunction with aliases. The partition key must be NVARCHAR(MAX).
 
 ### Example
 
@@ -53,11 +53,11 @@ Notice that each record in the blob has a **client_id** column matching the fold
    * cluster1/{date}/{aFieldInMyData}  
    * cluster1/{time}/{aFieldInMyData}  
    * cluster1/{aFieldInMyData}  
-   * cluster1/{date}/{time}/{aFieldInMyData}  
-
+   * cluster1/{date}/{time}/{aFieldInMyData} 
+   
 2. Partition keys are case insensitive, so partition keys like "John" and "john" are equivalent. Also, expressions cannot be used as partition keys. For example, **{columnA + columnB}** does not work.  
 
-3. When an input stream consists of records with a partition key cardinality under 8000, the records will be appended to existing blobs and only create new blobs when necessary. If the cardinality is over 8000 there is no guarantee existing blobs will be written to and new blobs won't be created for an arbitrary number of records with the same partition key.  
+3. When an input stream consists of records with a partition key cardinality under 8000, the records will be appended to existing blobs and only create new blobs when necessary. If the cardinality is over 8000 there is no guarantee existing blobs will be written to and new blobs won't be created for an arbitrary number of records with the same partition key.
 
 ## Custom DateTime path patterns
 

includes/monitoring-limits.md

@@ -14,6 +14,8 @@ ms.custom: "include file"
 | Autoscale settings |100 per region per subscription. | Same as default. |
 | Metric alerts (classic) |100 active alert rules per subscription. | Call support. |
 | Metric alerts |100 active alert rules per subscription. | Call support. |
+| Activity log alerts | 100 active alert rules per subscription. | Same as default. |
+| Log alerts | 512 | Call support. |
 | Action groups |2,000 action groups per subscription. | Call support. |
 
 **Action group-specific limits**

includes/storage-blob-scale-targets.md

@@ -17,4 +17,4 @@ ms.author: tamram
 | Maximum number of stored access policies per blob container | 5 |
 |Target throughput for single blob |Up to storage account ingress/egress limits<sup>1</sup> |
 
-<sup>1</sup> Single object throughput depends on several factors, including, but not limited to: concurrency, request size, performance tier, speed of source for uploads, and destination for downloads. To take advantage of [high-throughput block blob](https://azure.microsoft.com/blog/high-throughput-with-azure-blob-storage/) performance enhancements, use a Put Blob or Put Block request size of > 4 MiB (> 256 MiB for premium-performance block blob storage or for Data Lake Storage Gen2).
+<sup>1</sup> Single object throughput depends on several factors, including, but not limited to: concurrency, request size, performance tier, speed of source for uploads, and destination for downloads. To take advantage of [high-throughput block blob](https://azure.microsoft.com/blog/high-throughput-with-azure-blob-storage/) performance enhancements, use a Put Blob or Put Block request size of > 4 MiB (> 256 KiB for premium-performance block blob storage or for Data Lake Storage Gen2).

includes/virtual-machines-common-mitigate-se.md

@@ -119,7 +119,7 @@ If the output shows `MDS mitigation is enabled: False`, please [contact Azure Su
 <a name="linux"></a>Enabling the set of additional security features inside requires that the target operating system be fully up-to-date. Some mitigations will be enabled by default. The following section describes the features which are off by default and/or reliant on hardware support (microcode). Enabling these features may cause a performance impact. Reference your operating system provider’s documentation for further instructions
 
 
-**Step 1: Disable hyperthreading on the VM** - Customers running untrusted code on a hyperthreaded VM will need to disable hyperthreading or move to a non-hyperthreaded VM.  To check if you are running a hyperthreaded VM, run the `lspcu` command in the Linux VM. 
+**Step 1: Disable hyperthreading on the VM** - Customers running untrusted code on a hyperthreaded VM will need to disable hyperthreading or move to a non-hyperthreaded VM.  To check if you are running a hyperthreaded VM, run the `lscpu` command in the Linux VM. 
 
 If `Thread(s) per core = 2`, then hyperthreading has been enabled.