One folder, one group, six limits
Six Microsoft Entra group limits decide whether a sales team can open a shared forecast folder. Many revenue leaders share a forecast folder by adding a group instead of naming each person. When reps join or leave the sales team, the group changes and access follows it. The setup is tidy, but the identity platform sets ceilings on groups, and those ceilings are easy to forget until a rep cannot open the folder on the morning of a forecast call.
Key takeaways
- Dynamic groups share one 15,000 total across the whole organization (limit 1).
- Keep role-assignable groups to the few that need them, since the organization cap is 500 (limit 2).
- Keep owners few: the cap is 100 for one group (limit 3).
- Plan around 2,047 security groups for each user in SharePoint Online (limit 6).
This post walks through six published limits that matter when a forecast folder is shared through Microsoft Entra groups or other shared access groups. It follows one example case from start to finish. The revenue lead keeps a folder called North America Forecast. Access runs through a Microsoft Entra security group called NA Sales Forecast Readers. The group holds the North America sales team, and a single owner, the revenue operations lead, manages it. Each section comes back to that same group and asks what one limit means for it.
The numbers come from Microsoft's service limits and restrictions page for Microsoft Entra ID. Microsoft can change these numbers, so read the page yourself before you plan a rollout, and send the link to whoever administers your tenant. This post explains what each number means for a forecast folder. It does not replace the page.
Limit 1: dynamic groups share one ceiling
Start with groups whose membership comes from a rule instead of a list. Microsoft's page says an organization can have a maximum of 15,000 dynamic groups and dynamic administrative units combined. The count includes groups created automatically by entitlement management assignment policies. So the ceiling is not for each team or each group. It is one total for the whole organization.
In the example, suppose the revenue lead builds NA Sales Forecast Readers from a rule such as "department equals North America sales." That group is dynamic, so it draws from the same total as every other rule-based group and dynamic admin unit in the tenant. Other departments' rules, forgotten test groups, and automatic assignment policies all count against the same number. One forecast group barely moves that total, but the total belongs to everyone, so the useful question is who else is using it.
Rule-based membership has a real benefit. The cost is that a wrong rule adds the wrong people to the folder just as quickly. Before you point a forecast folder at a rule, test it against a handful of users you already know should and should not be in the group. Check the results by hand, and do it again after any change to the rule.
A static group, where the owner adds and removes members directly, is not a dynamic group. It does not draw from this shared total. For a team that the revenue lead can keep current in a few minutes a week, that trade is often worth making. The forecast folder stays simple, and the tenant-wide number stays free for the groups that need rules.
Limit 2: role-assignable groups cap at 500
Before going further, here are all six numbers side by side. Each one comes from the Microsoft page linked above, and the sections after this table explain each row in plain words.
| Limit | Published number | What the number applies to |
|---|---|---|
| Dynamic groups and dynamic administrative units | 15,000 combined | One total for the whole organization, including groups from entitlement management automatic assignment policies |
| Role-assignable groups | 500 | Groups created in a single Microsoft Entra organization (tenant) |
| Owners of a group | 100 | Users who can be owners of a single group |
| Groups for Entra Kerberos | 1010 | Groups carried when Entra Kerberos is used |
| Direct and nested group memberships | 2,048 | A user or a group that is a member of more than this many groups |
| Security groups for SharePoint Online | 2,047 | Security groups a user can belong to, direct and indirect, when SharePoint Online uses security groups |
Microsoft's page says a maximum of 500 role-assignable groups can be created in a single Microsoft Entra organization, which is one tenant.
In the example, the revenue lead might be tempted to mark NA Sales Forecast Readers as role-assignable so an admin role could be attached later. For folder sharing, that is usually unnecessary. Keeping role-assignable groups for the few that need them leaves the 500 allowance free for the rest. Settle the group type at the start, and write down the reason for each role-assignable group your tenant contains. A group that exists for no stated reason is the first place to look when the count gets close to 500.
Limit 3: 100 owners for one group
Microsoft's page says a maximum of 100 users can be owners of a single group. In the example, the group has one owner, the revenue operations lead.
The owner cap is a ceiling, not a goal. A long owner list tends to blur who approves a new rep, and it makes it unclear who should act when a group needs fixing. A small set of named owners, with one backup who knows the process, is easier to keep accurate than a long list copied from another group.
Owner changes also matter when people move. When someone leaves the revenue team, the first check is whether they are an owner of the forecast group or of any group that feeds it. If they are, reassign that role before their access ends, so the group is not left with no one who can manage it. Write the backup's name into the folder's notes so the next person knows whom to call. For the access side of a departure, see rep offboarding access controls.
Limit 4: 1010 groups for Entra Kerberos
Microsoft's page states a limit of 1010 groups for Entra Kerberos. This limit is about how many groups Entra Kerberos can carry. A single group can look harmless while the total for each rep grows.
This limit only matters when Entra Kerberos is part of how the folder is reached. Ask the administrator whether that path is in use before you treat the number as a risk. If it is not in use, this limit does not apply to that path, though the same habit of counting groups per person still helps.
In the example, a rep who belongs to NA Sales Forecast Readers may also belong to a regional group, a product group, a mailing list group, and a training group. Each of those counts toward the groups carried for that rep. The forecast group alone is not the number that matters. The sum across everything the rep belongs to is the number to check.
Ask the administrator for a count of groups for each rep in a sample of people who will open the folder. Flag anyone who is close to the limit, and ask which groups they could leave without losing access they need. Those reps are the ones most likely to see trouble first.
Limit 5: more than 2,048 direct and nested memberships
Microsoft's page says that if a user, or a group, is a member of more than 2,048 groups, counting direct and nested memberships, their access might be blocked. The word "might" is the page's own, and it matters. This is a risk to plan around, not a guaranteed outcome for every account.
Nested membership means one group is a member of another group. Each level of nesting adds to what a person effectively belongs to. In the example, suppose NA Sales Forecast Readers is nested inside a company-wide group called All Sales, and All Sales is nested inside a Revenue group. Every rep in the forecast group then also counts the chain above it. The rep may not see that chain at all.
Nesting is convenient for the administrator, because one parent group can grant many things at once. It also makes the true membership harder to see from the folder owner's chair. The practical steps are to avoid nesting the forecast group inside broad groups unless you need that link, to keep the forecast group sitting directly beside the folder rather than several levels deep, and to ask for the direct and nested count for the reps who open the folder.
When the count for a rep is high, the fix is usually removing a stale parent link, not adding more groups to balance it out. Stale links are easy to miss because nobody remembers why they exist.
Limit 6: 2,047 security groups in SharePoint Online
Microsoft's page says that when security groups are used with SharePoint Online, a user can be part of up to 2,047 security groups in total, including direct and indirect membership. That number sits one below the general figure of 2,048 in the previous section, and the two counts overlap. If your forecast folder lives in SharePoint Online and the access group is a security group, a rep who is near the limit reaches the SharePoint number first.
In the example, the North America Forecast folder sits in SharePoint Online and NA Sales Forecast Readers is a security group. The number to watch for each rep is 2,047, not 2,048. The count is the same kind of count as in limit 5, direct and indirect membership together, but the ceiling is lower.
This is the limit most likely to be missed, because the general number looks like the one that matters. Check the SharePoint line on the Microsoft page first, then confirm with the administrator whether the folder's access really runs through security groups. The figure applies to security groups, so if your sharing uses another kind of group, confirm that on the page before you rely on this number.
Illustrative example: one group with 3 owners
Suppose a team of 80 reps shares one folder through one group with 3 named owners. Three owners is far below the 100-owner cap. A rep who also belongs to 5 other groups stays well under the 2,047 SharePoint figure, so the nesting check is the one to make first.
What to check before you share the folder
Use this list as a planning sheet with the administrator. It follows the six limits above, in the order you would normally work through them.
- Confirm where the folder lives and how people reach it. If it is in SharePoint Online, limit 6 applies. If Entra Kerberos is part of the path, limit 4 applies.
- Create the access group as a plain security group unless you need it to be role-assignable. Only role-assignable groups count toward the 500 allowance (limit 2).
- Decide between a static group and a dynamic group. A dynamic group draws from the shared total of 15,000 (limit 1), so test any rule against known users first.
- Keep the owner list short and named, with one backup. Stay far below the 100-owner cap (limit 3).
- Avoid nesting the forecast group inside broad parent groups. Ask for direct and nested counts for the reps who open the folder (limit 5).
- Ask for the total group count for those same reps, and compare it with 2,047 for SharePoint Online and with 1010 for Entra Kerberos where those paths apply (limits 4 and 6).
- Reread the Microsoft page on the day you roll out, because the numbers can change.
Keep the list in the folder's notes or in the team's runbook, so the next revenue lead who inherits the folder can run it without reconstructing the reasoning.
Putting the example together
The North America Forecast folder and the NA Sales Forecast Readers group work well on their own. Nothing about the group itself is wrong. What can break access is the setup around it: a rule-based membership drawing from a shared total, an owner list that drifted, a parent group that nobody remembers adding, and a rep who belongs to more groups than anyone counted.
Each of the six limits points at one of those places. The 15,000 dynamic total and the 500 role-assignable allowance are tenant-wide budgets. The 100-owner cap is about who can change the group. The 1010 and 2,048 numbers are about how many groups a person or an Entra Kerberos path carries.
The useful habit is to run the check before the forecast call, not during it. For the call itself, see forecast call setup. Ask the administrator for the counts, compare them with the published numbers, and fix the stale links and owner gaps while there is still time. Review the membership and the limits on a schedule, not only when a rep reports a problem.
Next step today: open the Microsoft page linked above, compare its six numbers with your setup, and send the link to your tenant administrator.
Related guides: Excel forecast data limits: 30% missing points, 2 cycles · Forecast data refresh limits: 9 figures to read each week · Forecast pull published caps: 8 figures from vendor docs.
Frequently asked questions
Is there a limit on owners of one group?
A single group can have a maximum of 100 owners, according to Microsoft's service limits page. Keep the list short, with one named backup.
Which SharePoint limit matters most?
The 2,047 security-group figure matters most, because it is lower than the general 2,048 figure. It counts direct and indirect membership together.