LowCodeStacks™
Sign in

Fix "You aren't a member of the environment's security group"

Power Apps says you can't open apps in this environment. Why sharing the app isn't enough, how an admin adds you to the right group and syncs it, and what's next.

Governance & adminFix a problem7 min read

Checked against Microsoft Learn · 5 sourcesPosted by the Maker DeskHow we write guides

Someone shared a canvas app with you, you open the link, and instead of the app you get: "You can't open apps in this environment. You aren't a member of the environment's security group." Nothing is wrong with the app or the way it was shared. The environment the app lives in only lets in members of one Microsoft Entra group, and you aren't in it yet. Only an admin can fix that, and this guide is the short list of what they need to check.

The four checks a person passes before a canvas app opens in an environment that has a security group. Check 1: are they a member of the environment's security group? If not, they see the message You can't open apps in this environment. You aren't a member of the environment's security group. The fix is to add them to the group and then have an admin re-add the user or run diagnostics so the environment syncs. Check 2: is their account enabled in Microsoft Entra ID? Check 3: do they have a licence with a Power Platform or Dynamics 365 service plan, or does the environment have per-app plans? If not, assign one and sync. Check 4: do they have at least one security role, directly or through a group team? If not, they get a data access denied error, and the fix is to assign a role. When all four pass, the app opens. A side note lists the exceptions: Power Platform administrators and application users get in without being members, but Dynamics 365 administrators must be members.
Group membership is only the first check: an enabled account, a licence and a security role come next.
  • A shared canvas app shows You can't open apps in this environment. You aren't a member of the environment's security group.
  • The message may name a contact to ask for access, if your admins have set governance details.
  • It started for many people at once, often right after an admin attached a group to the environment.

Why sharing the app isn't enough

An admin can associate a Microsoft Entra security group (or a Microsoft 365 group) with an environment to control who can be a user there. Microsoft's rules for it:

  • Adding someone to the group adds them to the environment, and removing someone from the group disables them there.
  • Only licensed members of the group are created as users in the environment.
  • Attaching a group to an environment that already has users disables everyone who isn't in the group. That's why the message often appears for a whole team on the same morning.
  • A canvas app can still be shared with people outside the group, but they must be members to run it. That's exactly the gap this message reports.

Some accounts are treated differently, which explains "it works for me but not for them":

WhoNeeds to be in the group?
Someone with the Power Platform Administrator roleNo: they show as an active user and can sign in
Someone with the Dynamics 365 administrator roleYes: they can't use the environment until they're added and enabled
Application users (the identities that services and integrations sign in as)No
A member of a group nested inside the environment's groupThey aren't added in advance: they're added the first time they open the environment, or through a Dataverse group team

Find the environment's security group

The app's owner can tell you which environment it's in. Then an admin with the Power Platform Administrator or Dynamics 365 administrator role checks which group that environment uses:

  1. Sign in to the Power Platform admin center.
  2. In the navigation pane, select Manage, then Environments, and choose the environment.
  3. Select Edit. The Edit details pane has a Security group area that shows the group; select its Edit icon only if you mean to change it.

Check it's the group you expected. Two settings Microsoft rules out: on-premises Windows Active Directory groups aren't supported, only Microsoft Entra groups; and the default and developer environments can't have a security group at all.

Add the person and sync them to the environment

From blocked to opening the app
  1. Step 1Add them to the environment's group
  2. Step 2Re-add the user or run diagnostics
  3. Step 3Assign a security role
  1. Add them to the group. In the Microsoft 365 admin center, go to Teams & groups > Active teams & groups, select the group, select Edit next to Members, then + Add members. This needs the Groups Administrator or User Administrator role: Microsoft notes that the Power Platform Administrator role alone can't manage Entra groups. You can do the same in the Microsoft Entra admin center.
  2. Sync the change to the environment. A membership change has to reach the environment before it counts. To push it now, an admin can re-add the user: in the Power Platform admin center, open the environment, select Settings, expand Users + permissions, select Users, then Add user, find the person and select Add.
  3. Or run diagnostics. On the same Users page, select the person and then Run diagnostics. It syncs their details from Microsoft Entra ID into the environment and says why they can or can't get in, with what to fix. If you open a support case, include its results.
  4. Open the app again.

After the group, a licence and a role

Being in the group only gets someone through the door. For an environment with a Dataverse database, Microsoft lists four things a person needs:

RequirementIf it's missing
Their account is enabled for sign-in in Microsoft Entra IDThey can't sign in at all
A licence with a Power Platform or Dynamics 365 service plan, or per-app plans allocated to the environmentThey aren't created as a user; assign a licence, then re-add them so it syncs
Membership of the environment's group, if it has oneThe message this guide is about
At least one security role, assigned directly or through a group teamA data access denied error when they run an app

With a per-app plan allocated to the environment, Microsoft treats every user as licensed when they open it. For which role grants what, see our Dataverse access cheat sheet; for which licence a person needs, see Power Apps licensing explained.

Do

  • Give each important environment its own group, and add people to the group rather than to the environment one by one.
  • Grant security roles to a Dataverse group team linked to the same Entra group, so access follows membership.
  • Set governance details, so the message tells people whom to ask.

Don't

  • Don't remove the group from the environment to make the message go away: it's the control that keeps everyone else out.
  • Don't attach a group to a busy environment without first checking who's missing from it; everyone outside it is disabled at once.

Sources

Add LowCodeStacks as a preferred source on Google

Did this fix it?

Comments

No comments yet. Share what worked for you.

Sign in to comment. Comments show under a display name you choose, never your email.