Skip to content

Clarify Makers group type requirements and environment request approval troubleshooting #10908

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
Copilot wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Clarify Makers group type requirements and environment request approval troubleshooting #10908

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4688b08
Initial plan
Copilot Feb 27, 2026
75bf8b7
docs: clarify makers group type and env request approval troubleshooting
Copilot Feb 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions CenterofExcellenceResources/FAQ-EnvironmentAccessControl.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -580,12 +580,25 @@ Get-AzureADGroup -Filter "DisplayName eq 'Your Group Name'" | Select-Object Obje
3. **Group type**: Must be a Microsoft 365 group, not a security group
4. **Service principals**: Flow filters out service principals - this is expected

**Important clarification on "mail-enabled" guidance**:
- The `Admin | Add Maker to Group` flow uses the Office 365 Groups connector actions `ListGroupMembers` and `AddMemberToGroup`.
- Those actions expect a **Microsoft 365 Group** (Unified group).
- A **mail-enabled security group** can be valid for email scenarios, but it is **not** the group type this flow is designed to manage.

**Resolution**:
1. Check flow run history for specific error messages
2. Verify environment variable `Power Platform Maker Group ID` has correct group ID
3. Ensure the connection owner has permission to manage the M365 group membership
4. If you don't need automatic additions, turn off the flow

### Issue: Environment request is approved but creation flow does not run

If the approval date is not updating and no environment gets created, verify these first:
1. Flow **EnvRequestCreateApprovedEnvironment** is turned on and connections are healthy.
2. The request status is actually updated to **Approved** (`coe_requeststatus = 597910003`) and the record is saved.
3. Connection reference `admin_CoECorePowerPlatformforAdminsEnvRequest` is authenticated with a Power Platform admin account.
4. No unmanaged layer has overwritten trigger/configuration in environment request flows.

### Issue: Can't find the Admin | Add Maker to Group flow

**Resolution**:
Expand Down