Access to Copilot Studio environments as Invited B2B user

(0) Share

Report

Posted on by JWILDES CTS

I have two tenants. Tenant A and Tenant B. I have configured power platform in both tenants. I have invited my account from Tenant A to Tenant B where it is a member in Tenant B and not a guest, and belongs to security groups which give me access to power platform environments in Tenant B. I want to be able to use Copilot Studio in Tenant B as invited user. However all I can access is the default environment. I can see all the environments in that tenant but I cannot access them even though my user account belongs to security groups in Tenant B that let me access them. I've also assigned power apps premium license to the invited user, and the copilot studio viral trial.

When I enter the url https://copilotstudio.microsoft.com/?tenant=<tenantID> I end up at the default environment for the tenant within Copilot studio and I'm able to create agents and do work, but that's not the environment I need to be in. I can see all of them when I go to change the environment but as soon as I do I get the pretty "This link is broken" power platform broken link page.

I don't have any issues when I have locally assigned accounts. I don't want to create locally assigned accounts here, this is our demo and dev environment but I want to setup access packages to allow users from our primary tenant (Tenant A) to request access to the Copilot Studio through group membership.

I'm at a loss as to what's going on here.

Thanks for the help.

Categories:

General topics

I have the same question (0)

All responses (9)

Answers (0)

Sort by

Bezanca 494 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hey @JWILDES CTS

I would start by trying to add them directly to the environment - Go to the target environment → Settings → Users + permissions → Users → Add user. Search for the cross-tenant member account and add them directly. Also assign them a security role directly, maybe Environment Maker and see if that makes any difference?

Thanks,

Adam

Was this reply helpful? Yes No
JWILDES CTS 8 on at

Like (0)

Report
Copy link

Link copied!

Thanks @Bezanca

I've already done that. Added them directly as environment maker, no difference. The user can see all the environments in that tenant when switched into it, but cannot access any of the environments except default. They are a direct member of each of these environments with the Environment Maker role. It was something that was suggested in earlier searches and troubleshooting.

Any other thoughts?

Was this reply helpful? Yes No
Bezanca 494 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hey @JWILDES CTS

Can they access the power apps portal within those environments? Is it just Copilot Studio that isn't loading?

What type of environments are they?

Thanks

Was this reply helpful? Yes No
JWILDES CTS 8 on at

Like (0)

Report
Copy link

Link copied!

@Bezanca when I visit make.powerapps.com as this user, I am in the correct tenant and environment and can create power apps.

When I go to the environment URL <customslug>.crm.dynamics.com , I see the apps loaded to the environment.

Every environment is a sandbox environment. PowerAutomate doesn't let me access the environments at all and defaults to Tenant A, at this point I don't care about that. CopilotStudio will allow me to go to the default environment but not any other.

Was this reply helpful? Yes No
JWILDES CTS 8 on at

Like (0)

Report
Copy link

Link copied!

@Bezanca I verified my roles in the environment. Added system customizer and system admin, definitely overkill but it's a dev environment.

Still same issue, when I bring up the copilotstudio site with the environment guid in the URL I get the broken link. When I visit make.powerapps.com and go to agents it comes up with a broken link as well, despite being in the correct tenant and environment.

Additionally any time I attempt to connect to copilotstudio with this environment the url goes from https://copilotstudio.microsoft.com to https://copilotstudio.preview.microsoft.com ...not sure if that's a hang up or causing issues but it could be.

Thanks for the assistance in troubleshooting this.

Was this reply helpful? Yes No
Bezanca 494 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hey @JWILDES CTS

Might be worth checking the settings in this article - https://learn.microsoft.com/en-us/power-platform/admin/security/guest-access

This is also worth a read although it’s around consuming agents across tenants and not making them in copilot studio, but it’s the closest info I can find you -

https://learn.microsoft.com/en-us/microsoft-copilot-studio/multi-tenant-overview

Was this reply helpful? Yes No
Bezanca 494 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Also the part about redirecting to the preview site - have you got the environment set to get new features early? I wonder if that’s what is causing the issue.

The default environment won’t be set to that. Have you got another environment which doesn’t get new features early that you can test with?

Was this reply helpful? Yes No
JWILDES CTS 8 on at

Like (0)

Report
Copy link

Link copied!

@Bezanca so I created an entirely new environment. Not managed, not early features, added the user as the system administrator. It works. When I start at make.powerapps.com and go to agents it launches and wants to build an agent in this environment. It doesn't use the preview URL. I can directly go to the environment via URL. I can switch to it when starting at the default environment.

So I guess that's it. Non managed, non early features. It is a sandbox environment, not production, not developer. I did add power apps premium licenses and bought 100 copilot studio user licenses, but those were assigned to this user as well before this new environment.

Was this reply helpful? Yes No
Suggested answer

Bezanca 494 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Awesome! I think we've managed to get to the answer together @JWILDES CTS!

There must be a limitation that B2B users can not use environments with early preview features turned on. I can't see any documentation about that, but that must be it!

Thanks,
Adam

Was this reply helpful? Yes No