add limitations and scenarios

Author: PallabPaul

articles/confidential-ledger/data-organization.md

@@ -85,7 +85,7 @@ Adding Tags to a collection is a preview feature available with the latest previ
 
 Additionally, this feature is limited to Confidential Ledgers that are of the **Public** Ledger Type. **Private** Ledger Type is not supported.
 
-They allow for improved management of data within a collection by acting as secondary keys to a collection of data. Tags are limited to 64 character strings. Each transaction can support upto five tags. If an error is seen related to the number of tags supported and a higher limit is required, reach out to Support.  
+They allow for improved management of data within a collection by acting as secondary keys to acollection IDs vercus sus Tags. collection of data. Tags are limited to 64 character strings. Each transaction can support upto five tags. If an error is seen related to the number of tags supported and a higher limit is required, reach out to Support.  
 
 In order to use tags inside a collection, tags parameter needs to be specified. 
 
@@ -103,6 +103,18 @@ for entry in list_result:
     print(f"Contents: {entry['contents']}")
 ```
 
+## Sample Scenarios
+
+The following scenarios can help you decide when to use collection IDs versus Tags.
+
+| Scenario | Recommended approach | Why |
+|--|--|--|
+| You write general records and mostly read by transaction ID or latest entry. | Use the default collection ID (`subledger-0`). | This approach keeps data organization simple and avoids managing many collection IDs. |
+| You need strict logical separation of data sets, such as tenant-specific or workload-specific isolation. | Use dedicated collection IDs for each logical group. | Group-level collection IDs make it easier to isolate and list records by boundary. |
+| You need query-oriented lookups at a finer granularity, including per-entry categorization. | Prefer tags within a shared collection before creating a unique collection ID per entry. | You can achieve similar query outcomes without creating and managing a unique collection ID for every entry. |
+
+If your main goal is query flexibility, start with tags and add more collection IDs only when clear isolation boundaries are required.
+
 
 ## Next steps
 

articles/confidential-ledger/overview.md

@@ -82,6 +82,22 @@ Confidential ledger nodes are deployed across Azure availability zones to provid
 
 Data is automatically replicated to Azure regional pairs for disaster recovery. For information about data residency considerations, see [Data residency for Azure confidential ledger](data-residency.md).
 
+### Limitations
+
+| Resource | Limit |
+|--|--|
+| Number of ledgers per subscription | 2 standard SKU ledgers |
+| Number of collection IDs per ledger | 50,000 |
+| Storage limit per ledger | 1 TB |
+| Create entry | 1900 requests per second, 1900 transactions per second |
+| Get current entry | 3600 requests per second |
+| Get entry | 3200 requests per second |
+| Get receipt | 2400 requests per second |
+| List entries | 3300 requests per second |
+
+> [!NOTE]
+> To request higher limits or discuss limitations, reach out to the Azure Confidential Ledger team.
+
 ## Constraints
 
 - After a confidential ledger instance is created, you can't change the ledger type (private or public).