"Sharing is disabled in this environment": sharing limits explained

You try to add a co-owner to a cloud flow, and a red banner appears instead: "Sharing is disabled in this environment." The environment is a managed environment, and an admin has set rules that limit how widely people can share canvas apps, flows and agents there. Your share broke one of those rules, so it was stopped. This guide explains which rule does what, what you can still do as a maker, and where an admin changes it.

Why you see it

Sharing limits are a feature of Managed Environments. In a managed environment, admins can limit how broadly users share canvas apps, solution-aware cloud flows and agents. Microsoft's page on limiting sharing sets out how they behave:

• They're checked when someone shares. The rule applies at the moment you try to share with a person or a group.
• Existing access stays. People who had access before the rule was set keep it.
• Out-of-compliance items can only shrink. If an app, flow or agent breaks a rule set after it was shared, only unsharing is allowed until it complies.
• Changes take up to an hour to start being enforced after an admin saves them in the Power Platform admin center.
• Dataverse for Teams is a special case. Sharing to the team when you select Publish to Teams isn't affected, but sharing with people or groups in a different team is.

What the blocked share looks like on a flow, as of January 2025:

1. Co-owners: the page where you add owners to a flow. The page itself warns that an owner gets full control of the flow.
2. Add a system user or team as an owner, with its Enter names or email addresses box: where the share was attempted.
3. The red banner: the block itself, with here linking to your organisation's documentation and the administrator's address beside it.
4. Learn more, at the end of the banner.

"Organizations's" is how the banner reads on Learn's screenshot, typo included; our recreation keeps it as shown.

What each rule blocks

The rules sit in three groups, one per product. The names below are as the newest admin center screenshot on Learn (February 2026) shows them; Learn's own tables word some of them slightly differently, such as "Limit total individuals who can be shared to".

So a flow that can't be shared with anyone at all points to the cleared flow setting. An app that shares with a person but not with a group points to Exclude sharing with security groups. The admin center's own text adds one more rule for agents: sharing limits don't apply when an agent's authentication is set to No authentication.

If you're the maker

1. Read the banner's links. If your admins set governance error content, the banner links to your organisation's documentation and names a contact. Start there: your organisation's documentation is where it can say what to do instead.
2. Share within the rule, if it allows any sharing. If groups are excluded for apps, sharing with named people still works, up to any limit the admin set. For agents, check whether editors or viewers are still allowed.
3. Remove people first on an item that's out of compliance. Only unsharing works until it's back inside the rules.
4. Ask the admin if the work needs a share the rule forbids. Say what you're sharing, with whom and why. They can change the rule for the environment, or tell you which environment is meant for shared work.

Don't look for a way around the block, such as rebuilding the flow somewhere else and sharing from there. Sharing limits are part of how your organisation protects its data.

If you're the admin

Learn's steps to see or change the rules:

1. Sign in to the Power Platform admin center.
2. In the navigation pane, select Manage, then Environments, and choose the managed environment.
3. On the command bar, select Edit Managed Environments.
4. Find the Manage sharing section, choose the settings and select Save.

What the section shows, as of February 2026:

1. Power Apps, Canvas apps: the two radio buttons, and the greyed limit that turns on with Exclude sharing with security groups.
2. Power Automate, Solution-aware cloud flows: the single checkbox. It's shown cleared here to illustrate the blocked state (Learn's screenshot shows it ticked); cleared, it's the setting behind the flow banner above.
3. Copilot Studio: a short explanation, then the Editors and Viewers settings for agents.

After you save, allow up to an hour before testing the share again.

The same settings in PowerShell

Learn gives PowerShell scripts to set and remove the limits, using cmdlets from the Power Apps administration module (Microsoft.PowerApps.Administration.PowerShell). Each reads the environment's governance configuration, sets one or two values in its extended settings, and saves it back. For solution-aware cloud flows, the setting is solutionCloudFlows-limitSharingMode: disableSharing turns sharing off, and noLimit turns it back on. Learn's script to remove the flow limit:

# Retrieve the environment
$environment = Get-AdminPowerAppEnvironment -EnvironmentName <EnvironmentId>

# Update the managed environment settings
$governanceConfiguration = $environment.Internal.properties.governanceConfiguration
$governanceConfiguration.settings.extendedSettings | Add-Member -MemberType NoteProperty -Name 'solutionCloudFlows-limitSharingMode' -Value "noLimit" -Force

# Save the updated managed environment settings
Set-AdminPowerAppEnvironmentGovernanceConfiguration -EnvironmentName <EnvironmentId> -UpdatedGovernanceConfiguration $governanceConfiguration

For canvas apps the settings are limitSharingMode and maxLimitUserSharing; for agents, bot-limitSharingMode, bot-maxLimitUserSharing and bot-authoringSharingDisabled. One thing to watch if you copy Learn's agent script that excludes security groups: as published on 27 October 2026, it skips the line that reads $governanceConfiguration from the environment, which every other script on the page has. Add that line before running it.

Make the banner point somewhere useful

The banner's documentation link and contact address come from your tenant's governance error message content. Set it with New-PowerAppDlpErrorSettings (or update it with Set-PowerAppDlpErrorSettings), giving a URL for your guidance and an email address for questions; either can be shown on its own. Microsoft's Copilot Studio page warns that these settings apply to every Power Platform app in the tenant, so use a shared mailbox and a page that explains all your governance rules, not just this one.

The steps in this guide follow Microsoft's documentation as of 27 October 2026; we haven't run them in a tenant.

Sources

• Limit sharing — Microsoft Learn
• PowerShell support for Power Apps and Power Automate: governance error message content — Microsoft Learn
• Configure data policies for agents: Learn more and admin contact links — Microsoft Learn
• Set-AdminPowerAppEnvironmentGovernanceConfiguration — Microsoft Learn