Forum Discussion
Sensitivity labels
Hi all,
I have a question(s) related to sensitivity label(s) limitations:
1.) are there limitations on how many sensitivity labels can I create for 1 organization? If yes, what are they?
2.) "auto-labelling policies" - are there any limitations on that? If yes, what are they?
KR
DTLD
Dino_Vo as far as I know, there is not central documentation page that describes the service limitations. However, you can find the information accorss multiple pages. A general advice when looking for such information is using Google Dorks e.g. site:microsoft.com "Purview" "limit".
1) According to this documentation :
There is no limit to the number of sensitivity labels that you can create and publish, with one exception: If the label applies encryption that specifies the users and permissions, there is a maximum of 500 labels supported with this configuration. However, as a best practice to lower admin overheads and reduce complexity for your users, try to keep the number of labels to a minimum. Real-world deployments have proved effectiveness to be noticeably reduced when users have more than five main labels or more than five sublabels per main label.
2) Although it may not be comprehensive, you have some hints in this documentation :
Specific to auto-labeling for SharePoint and OneDrive:
- Maximum of 25,000 automatically labeled files in your tenant per day.
- Maximum of 100 auto-labeling policies per tenant, each targeting up to 100 sites (SharePoint or OneDrive) when they're specified individually. You can also specify all sites, and this configuration is exempt from the 100 sites maximum.
3) Additional information :For simulation mode the doc says : Simulation mode supports up to 1,000,000 matched files. If more than this number of files are matched from an auto-labeling policy, you can't turn on the policy to apply the labels. In this case, you must reconfigure the auto-labeling policy so that fewer files are matched, and rerun simulation. This maximum of 1,000,000 matched files applies to simulation mode only and not to an auto-labeling policy that's already turned on to apply sensitivity labels.For Sensitive information types (SIT) limits see here.
Limit Value maximum number of custom SITs created through the Compliance center 500 maximum length of regular expression 1024 characters maximum length for a given term in a keyword list 50 characters maximum number of terms in keyword list 2048 maximum number of distinct regexes per sensitive information type 20 maximum size of a keyword dictionary (post compression) 1MB (~1,000,000 characters) maximum number of keyword dictionary based SITs in a tenant 50 For eDiscovery limits : see here (I don't copy/paste the table, way too long)
For other various limits : see here.
Resource Default Limit Maximum Limit Microsoft Purview accounts per region, per tenant (all subscriptions combined) 3 Contact Support Data Map throughput^
There's no default limit on the data map metadata storage10 capacity units
250 operations per second100 capacity units
2,500 operations per secondvCores available for scanning, per account* 160 160 Concurrent scans per Purview account. The limit is based on the type of data sources scanned* 5 10 Maximum time that a scan can run for 7 days 7 days Size of assets per account 100M physical assets Contact Support Maximum size of an asset in a catalog 2 MB 2 MB Maximum length of an asset name and classification name 4 KB 4 KB 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
Dino_Vo as far as I know, there is not central documentation page that describes the service limitations. However, you can find the information accorss multiple pages. A general advice when looking for such information is using Google Dorks e.g. site:microsoft.com "Purview" "limit".
1) According to this documentation :
There is no limit to the number of sensitivity labels that you can create and publish, with one exception: If the label applies encryption that specifies the users and permissions, there is a maximum of 500 labels supported with this configuration. However, as a best practice to lower admin overheads and reduce complexity for your users, try to keep the number of labels to a minimum. Real-world deployments have proved effectiveness to be noticeably reduced when users have more than five main labels or more than five sublabels per main label.
2) Although it may not be comprehensive, you have some hints in this documentation :
Specific to auto-labeling for SharePoint and OneDrive:
- Maximum of 25,000 automatically labeled files in your tenant per day.
- Maximum of 100 auto-labeling policies per tenant, each targeting up to 100 sites (SharePoint or OneDrive) when they're specified individually. You can also specify all sites, and this configuration is exempt from the 100 sites maximum.
3) Additional information :For simulation mode the doc says : Simulation mode supports up to 1,000,000 matched files. If more than this number of files are matched from an auto-labeling policy, you can't turn on the policy to apply the labels. In this case, you must reconfigure the auto-labeling policy so that fewer files are matched, and rerun simulation. This maximum of 1,000,000 matched files applies to simulation mode only and not to an auto-labeling policy that's already turned on to apply sensitivity labels.For Sensitive information types (SIT) limits see here.
Limit Value maximum number of custom SITs created through the Compliance center 500 maximum length of regular expression 1024 characters maximum length for a given term in a keyword list 50 characters maximum number of terms in keyword list 2048 maximum number of distinct regexes per sensitive information type 20 maximum size of a keyword dictionary (post compression) 1MB (~1,000,000 characters) maximum number of keyword dictionary based SITs in a tenant 50 For eDiscovery limits : see here (I don't copy/paste the table, way too long)
For other various limits : see here.
Resource Default Limit Maximum Limit Microsoft Purview accounts per region, per tenant (all subscriptions combined) 3 Contact Support Data Map throughput^
There's no default limit on the data map metadata storage10 capacity units
250 operations per second100 capacity units
2,500 operations per secondvCores available for scanning, per account* 160 160 Concurrent scans per Purview account. The limit is based on the type of data sources scanned* 5 10 Maximum time that a scan can run for 7 days 7 days Size of assets per account 100M physical assets Contact Support Maximum size of an asset in a catalog 2 MB 2 MB Maximum length of an asset name and classification name 4 KB 4 KB 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 - Hi,
tnx for the definition 🙂
Really appreciate it.
KR
