Merge pull request #171863 from yossi-y/master

Changed storage partitioning

Author: PRMerger15

articles/azure-monitor/logs/logs-data-export.md

@@ -50,7 +50,9 @@ Currently, there are no additional charges for the data export feature. Pricing
 ### Storage account
 Data is sent to storage accounts as it reaches Azure Monitor and stored in hourly append blobs. The data export configuration creates a container for each table in the storage account with the name *am-* followed by the name of the table. For example, the table *SecurityEvent* would sent to a container named *am-SecurityEvent*.
 
-The storage account blob path is *WorkspaceResourceId=/subscriptions/subscription-id/resourcegroups/\<resource-group\>/providers/microsoft.operationalinsights/workspaces/\<workspace\>/y=\<four-digit numeric year\>/m=\<two-digit numeric month\>/d=\<two-digit numeric day\>/h=\<two-digit 24-hour clock hour\>/m=00/PT1H.json*. Since append blobs are limited to 50K writes in storage, the number of exported blobs may extend if the number of appends is high. The naming pattern for blobs in such a case would be PT1H_#.json, where # is the incremental blob count.
+Data is sent to storage accounts as it reaches Azure Monitor and stored in append blobs. The data export configuration creates a container for each table in the storage account a prefix *am-* followed by the name of the table. For example, *SecurityEvent* is exported to a container named *am-SecurityEvent*.
+
+The storage account blob path is in hourly blob path. Starting 15-October 2021, the blob path is in 5 minutes granularity: *WorkspaceResourceId=/subscriptions/subscription-id/resourcegroups/\<resource-group\>/providers/microsoft.operationalinsights/workspaces/\<workspace\>/y=\<four-digit numeric year\>/m=\<two-digit numeric month\>/d=\<two-digit numeric day\>/h=\<two-digit 24-hour clock hour\>/m=\<two-digit 60-minute clock minute\>/PT05M.json*. Since append blobs are limited to 50K writes in storage, the number of exported blobs may extend if the number of appends is high. The naming pattern for blobs in such a case would be PT05M_#.json*, where # is the incremental blob count.
 
 The storage account data format is [JSON lines](../essentials/resource-logs-blob-format.md). This means each record is delimited by a newline, with no outer records array and no commas between JSON records.