Merge pull request #212697 from bjspeaks/main

Updated the quotas for self-service policies

Author: prmerger-automator[bot]

articles/purview/concept-self-service-data-access-policy.md

@@ -49,8 +49,11 @@ Whenever a data consumer requests access to a dataset, the notification is sent
 Data consumer can access the requested dataset using tools such as PowerBI or Azure Synapse Analytics workspace.
 
 >[!NOTE]
-> Users will not be able to browse to the asset using the Azure Portal or Storage explorer if the only permission granted is read/modify access at the file or folder 
-> level of the storage account.
+> Users will not be able to browse to the asset using the Azure Portal or Storage explorer if the only permission granted is read/modify access at the file or folder level of the storage account.
+
+> [!CAUTION]
+> Folder level permission is required to access data in ADLS Gen 2 using PowerBI.
+> Additionally, resource sets are not supported by self-service policies. Hence, folder level permission needs to be granted to access resource set files such as CSV or parquet. 
 
 ## Next steps
 

articles/purview/how-to-manage-quotas.md

@@ -28,6 +28,7 @@ This article highlights the limits that currently exist in the Microsoft Purview
 |Maximum length of asset property name and value|32 KB|32 KB|
 |Maximum length of classification attribute  name and value|32 KB|32 KB|
 |Maximum number of glossary terms, per account|100K|100K|
+|Maximum number of self-service policies, per account|3K|3K|
 
 \* Self-hosted integration runtime scenarios aren't included in the limits defined in the above table.