Some updates based on PM input

Author: normesta

articles/storage/blobs/blob-inventory.md

@@ -5,10 +5,9 @@ services: storage
 author: normesta
 
 ms.service: storage
-ms.date: 11/02/2022
+ms.date: 12/02/2022
 ms.topic: conceptual
 ms.author: normesta
-ms.reviewer: klaasl
 ms.subservice: blobs
 ms.custom: references_regions
 ---
@@ -388,13 +387,23 @@ For more information about pricing for Azure Storage blob inventory, see [Azure
 
 This section describes limitations and known issues of the Azure Storage blob inventory feature.
 
-### Inventory job fails to complete for hierarchical namespace enabled accounts
+#### Inventory jobs take a longer time to complete in certain cases
 
-The inventory job might not complete within 2 days for an account with hundreds of millions of blobs and hierarchical namespace enabled. If this happens, no inventory file is created. If a job does not complete successfully, check subsequent jobs to see if they complete before contacting support. The performance of a job can vary, so if a job doesn't complete, it's possible that subsequent jobs will.
+An inventory job can take a longer amount of time in these cases:
 
-### Inventory job cannot write inventory reports
+- A large amount new data is added
 
-An object replication policy can prevent an inventory job from writing inventory reports to the destination container. Some other scenarios can archive the reports or make them immutable when they are partially completed. This can lead to inventory job failure.
+- A rule or set of rules is being run for the first time
+
+  The inventory run might take longer time to run as compared to the subsequent inventory runs.  
+
+- In inventory run is processing a large amount of data in hierarchical namespace enabled accounts
+
+  An inventory job might take more than one day to complete for hierarchal namespace enabled accounts that have hundreds of millions of blobs. Sometimes the inventory job fails and doesn't create an inventory file. If a job doesn't complete successfully, check subsequent jobs to see if they are complete before contacting support. 
+
+#### Inventory jobs can't write reports to containers that have an object replication policy
+
+An object replication policy can prevent an inventory job from writing inventory reports to the destination container. Some other scenarios can archive the reports or make the reports immutable when they are partially completed which can cause inventory jobs to fail.
 
 ## Next steps
 

articles/storage/blobs/calculate-blob-count-size.md

@@ -5,7 +5,7 @@ services: storage
 author: normesta
 
 ms.author: normesta
-ms.date: 08/16/2021
+ms.date: 12/02/2022
 ms.service: storage
 ms.subservice: blobs
 ms.topic: how-to
@@ -16,8 +16,6 @@ ms.custom: subject-rbac-steps
 
 This article uses the Azure Blob Storage inventory feature and Azure Synapse to calculate the blob count and total size of blobs per container. These values are useful when optimizing blob usage per container.
 
-Blob metadata is not included in this method. The Azure Blob Storage inventory feature uses the [List Blobs](/rest/api/storageservices/list-blobs) REST API with default parameters. So, the example doesn't support snapshots, '$' containers, and so on.
-
 ## Enable inventory reports
 
 The first step in this method is to [enable inventory reports](blob-inventory.md#enabling-inventory-reports) on your storage account. You may have to wait up to 24 hours after enabling inventory reports for your first report to be generated.