I can‘t use DCOE

(0) Share

Report

Posted on by LZ-10020948-0

You (v-lizhenghan@microsoft.com) need to be added to a security group to access this environment (cosmic)

Ask your admin to add you to this environment's security group and then retry accessing this environment. Learn about security groups

Troubleshoot user sign in issues

Error Code: notMemberOfOrg
Timestamp: 2/10/2026 9:46:28 AM UTC
Service Request Id: 438e696c-d40c-470e-967c-789a1b3d1804

Categories:

Dynamics 365 Customer Insights - Journeys

I have the same question (0)

All responses (1)

Answers (0)

Sreevalli 3,259 on at

Like (0)

Report
Copy link

Link copied!
Hi,

The error notMemberOfOrg usually indicates that your user isn’t part of the Azure AD security group required for the environment, but even if you are an admin, this can still happen when the environment belongs to a different tenant.
Here’s how to confirm and fix it:

1. Check which tenant the environment belongs to
Power Platform and DCOE environments are tied to one specific Azure AD tenant.
To verify which tenant owns the environment:

Open the Power Platform Admin Center.

Go to Environments → select the environment (e.g., “cosmic”).

In the Details panel, check the Tenant ID / Directory.

If the Tenant ID isn’t the one your account belongs to, the environment is in another organization’s tenant.

If the environment is in another tenant, being an admin in your tenant doesn’t grant access. you must exist as a member or guest in the owning tenant.
2. Check if a security group is assigned
In the environment settings:

Go to Access → Security group.

If a security group is listed, access is locked down and admins must also be explicitly added to that group.

3. Validate your user account type
If your account is:

A guest

A vendor account (v-xxx)

Not a member in the target tenant

…you may still be blocked even with admin privileges due to environment governance policies.
4. What to do next
If the tenant is different, you need to be:

Invited as a guest to the owning tenant

Added to the security group assigned to the environment

Once you're part of the correct tenant and group, the error should disappears.

Let me know if it helps!

Was this reply helpful? Yes No