Adding permissions info for subpartitioning

Author: deborahc

articles/cosmos-db/hierarchical-partition-keys.md

@@ -585,6 +585,7 @@ while (queryIterator.hasMoreResults()) {
 - You can specify hierarchical partition keys only up to three layers in depth.
 - Hierarchical partition keys can currently be enabled only on new containers. You must set partition key paths at the time of container creation, and you can't change them later. To use hierarchical partitions on existing containers, create a new container with the hierarchical partition keys set and move the data by using [container copy jobs](container-copy.md).
 - Hierarchical partition keys are currently supported only for the API for NoSQL accounts. The APIs for MongoDB and Cassandra aren't currently supported.
+- Hierarchical partition keys aren't currently supported with the [Permissions feature<a id="permissions"></a>](secure-access-to-data.md#permissionsa-idpermissionsa). You can't assign a permission to a partial prefix of the hierarchical partition key path. Permissions can only be assigned to the entire logical partition key path. For example, if you have partitioned by ``TenantId`` - > ``UserId``, you can't assign a permission that is for a specific value of ``TenantId``. However, you can assign a permission for a partition key if you specify both the value for ``TenantId`` and ``UserId```.
 
 ## Next steps
 

articles/cosmos-db/scaling-provisioned-throughput-best-practices.md

@@ -57,7 +57,6 @@ Azure Cosmos DB distributes your data across logical and physical partitions bas
 ### Step 2: Calculate the default maximum throughput
 The highest RU/s you can scale to without triggering Azure Cosmos DB to split partitions is equal to `Current number of physical partitions * 10,000 RU/s`. You can get this value from the Azure Cosmos DB Resource Provider. Perform a GET request on your [database](/rest/api/cosmos-db-resource-provider/2023-04-15/sql-resources/get-sql-database-throughput) or [container](/rest/api/cosmos-db-resource-provider/2023-04-15/sql-resources/get-sql-container-throughput) throughput setting objects and retrieve the `instantMaximumThroughput` property. This value is also available in the Scale and Settings page of your database or container in the portal.
 
-
 #### Example
 Suppose we have an existing container with five physical partitions and 30,000 RU/s of manual provisioned throughput. We can increase the RU/s to 5 * 10,000 RU/s = 50,000 RU/s instantly. Similarly if we had a container with autoscale max RU/s of 30,000 RU/s (scales between 3000 - 30,000 RU/s), we could increase our max RU/s to 50,000 RU/s instantly (scales between 5000 - 50,000 RU/s). 
 > [!TIP]