You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -27,22 +27,22 @@ Inherited permissions are set as the default at the root site collection level a
27
27
Each time you break inheritance by granting access to a new user account or group at any level in a site, even on a single item, you are creating a new unique security “scope” ID. That scope is counted as a unique permission towards the total limit. A library (or list) cannot have greater than 50,000 unique security scopes.
28
28
29
29
30
-
31
-
When the number of unique security scopes exceeds the value of the list view threshold, added SQL server round trips take place that can affect performance.
32
-
When migrating, we recommend that you have less than 5,000 unique scopes per library.
30
+
31
+
When the number of unique security scopes exceeds the value of the list view threshold, added SQL server round trips take place that can affect performance.
32
+
When migrating, we recommend that you have less than 5,000 unique scopes per library.
33
33
34
34
## Role assignments
35
-
35
+
36
36
A role assignment is a mapping between a user, a SharePoint object (Web, list, file) and a role (Design, Full Control, Contribute, etc.). The role assignment ties together the role definition (permission level) with the specific user or group, and the scope that that permission level will be applied to (such as list, folder, item).
37
37
38
38
There is a role assignment limit of 5,000 per security scope.
39
39
40
-
## Item limits
40
+
## Item limits
41
41
42
-
When a library (or list) contains more than 100,000 items (files and folders or list items), you cannot break permissions inheritance on the list itself. There is a limit of 100,000 items that can be updated or removed as a part of creating a new SharePoint security scope.
42
+
When a library (or list) contains more than 100,000 items (files and folders or list items), you cannot break permissions inheritance on the list itself. There is a limit of 100,000 items that can be updated or removed as a part of creating a new SharePoint security scope.
43
43
44
44
If you are migrating a structure that has more than 100,000 children (such as files, folders, lists, or other object types), you need to restructure the migration by importing security in multiple phases to avoid exceeding this limit. Any VROOM invite, REST share link, or any other permission-modifying function call will trigger an HTTP 429 throttle if the threshold is reached. Permissions will not be updated. Unlike other throttles, waiting and trying again will not resolve the situation as you have reached a hard limit of 100,000.
45
-
To learn more about the service limits in SharePoint for Microsoft 365, see [SharePoint Limits](https://docs.microsoft.com/en-us/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-limits#items-in-lists-and-libraries).
45
+
To learn more about the service limits in SharePoint for Microsoft 365, see [SharePoint Limits](https://docs.microsoft.com/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-limits#items-in-lists-and-libraries).
46
46
47
47
## Folders containing fewer than 100,000 items
48
48
@@ -53,32 +53,33 @@ If your library (or list) has fewer than 100,000 items, and you have less than 5
53
53
If you have a folder with more than 100,000 items, we recommend one of the following approaches. Determine how many items are in your source or root folder, including lists or other object types. Scan and determine which folder structures have greater than 100,000 items.
54
54
55
55
### Method 1: Restructure the source layout
56
+
56
57
The first option is to restructure your *source* layout.
57
58
58
59
For example, divide a single folder of 250,000 items into four folders at the root so each folder has less than 100,000 items. There is still “room to grow”, presuming users will continue to add content and make changes here.
59
60
60
-
Make sure that there are no more than 50,000 unique scopes in the structure: ideally less than 5,000.
61
+
Make sure that there are no more than 50,000 unique scopes in the structure: ideally less than 5,000.
61
62
62
63
In this example, at the source, break up the structure into four folders, A, B, C, and D, each having less than 100,000 items. Then perform the migration. See the illustration below.
63
64
64
-
65
-
65
+
66
+
66
67
>[!NOTE]
67
-
>There are other limits that must be considered during migration. See [SharePoint Limits](https://docs.microsoft.com/en-us/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-limits#items-in-lists-and-libraries) for details.
68
+
>There are other limits that must be considered during migration. See [SharePoint Limits](https://docs.microsoft.com/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-limits#items-in-lists-and-libraries) for details.
68
69
69
70
### Method 2: Create your destination layout to avoid exceeding limits
71
+
70
72
The alternate approach is to keep your source layout, applying unique scopes at the destination before migration.
71
73
72
-
**Example:** Your source folder has 250,000 items within it. At your target ___location, create folders A, B, C, and D and apply the unique scopes and scope ID. This will break inheritance. Then proceed with your content migration.
73
-
If you do not want your end users to share items until migration is completed, use the Migration API to migrate the content & scopes, but set the scope to NULL to prevent any use.
74
+
**Example:** Your source folder has 250,000 items within it. At your target ___location, create folders A, B, C, and D and apply the unique scopes and scope ID. This will break inheritance. Then proceed with your content migration.
75
+
If you do not want your end users to share items until migration is completed, use the Migration API to migrate the content & scopes, but set the scope to NULL to prevent any use.
74
76
After all the content and incremental migrations are completed, apply the proper scope.
75
77
76
-
After the incremental migration has completed, and only if you previously set the scope to NULL, you can reapply the unique scope for folders A, B, C, D separately. When you reapply the scope, evaluate your folder size starting at the lowest level of hierarchy.
78
+
After the incremental migration has completed, and only if you previously set the scope to NULL, you can reapply the unique scope for folders A, B, C, D separately. When you reapply the scope, evaluate your folder size starting at the lowest level of hierarchy.
77
79
78
80
## Other Sharing/Permission related considerations
79
-
81
+
80
82
The REST share link or any other permission-modifying function will not take effect if you attempt to update the permission on a file that is checked out by a user.
81
83
Finally, if a SharePoint site or OneDrive ___location is being actively used during migration, the existing permissions applied on that site, user or document will be enforced.
82
-
83
-
**Example:** If you attempt to modify the permission on a site that only allows access to existing users already defined on the site, and the user you are trying to add to a file or folder does not already have permissions on the site itself, the permission call (e.g. VROOM Invite) will not be able to make the modification.
84
84
85
+
**Example:** If you attempt to modify the permission on a site that only allows access to existing users already defined on the site, and the user you are trying to add to a file or folder does not already have permissions on the site itself, the permission call (e.g. VROOM Invite) will not be able to make the modification.
0 commit comments