You don't have access to talk to this bot, contact the owner

(2) Share

Report

Posted on by Bjon

I have been deploying Copilot Studio chatbot to all local internal users.

Now I tried to deploy the bot to other region, but it is still for internal staff used only, but I am getting error "You don't have access to talk to this bot, contact the owner"

Anyone knows how to troubleshoot here?
Which part of the bot I need to configure to allow access?

Categories:

Bot administration

I have the same question (0)

All responses (7)

Answers (0)

Sort by

Suggested answer

11manish 2,430 on at

Like (0)

Report
Copy link

Link copied!
The most likely fix is:

Share the bot with the target users/groups

Ensure users have environment access

Verify Teams app permission policies

Republish the bot after permission changes

Confirm authentication mode supports cross-region users

In enterprise deployments, this usually resolves it:

Add users/security groups to bot sharing

Give users Basic User role in environment

Republish Teams channel

Reinstall Teams app

That fixes the issue in most cases.

Was this reply helpful? Yes No
MS.Ragavendar 7,169 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
@Bjon,

If users are in a different Azure AD tenant Or accessing through B2B / external accounts they will get exactly this error.

Copilot Studio → Bot → Settings → Security

how the access is defined, Users in my organization or Anyone with the link (external)

If you want only internal staff, this setting is correct, But users must be in the same Entra ID tenant.

Quick Check

Are users in the “other region” still in the same tenant, or a different tenant?

✅If this helped, please Accept as Solution to help others ❤️ A Like is appreciated 🏷️ Tag @MS.Ragavendar for follow-ups.

Was this reply helpful? Yes No
Suggested answer

chiaraalina 2,059 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi @Bjon

I get that error if I share Agent with users that only have Basic User permissions. The users need a security role with bot (Read, Write - User level) and botcomponent (Read, Write - User level).

Assign an existing security role with these permissions or create a custom security role and assign it to all the users.

Was this reply helpful? Yes No
Suggested answer

AP-26031104-0 Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hi Bjon

This is a sharing/permissions issue, not a regional one. Work through these checks:

1. Bot Sharing Settings (most likely cause)
In Copilot Studio → Share — check if the bot is shared with specific users/groups. If so, the other region's users aren't included. Set it to "Everyone in your organization" or add the relevant group.

2. Authentication Settings
Settings → Security → Authentication — if set to "Authenticate with Microsoft", ensure those users are in the same tenant and not blocked by Conditional Access policies (e.g. location-based restrictions).

3. Teams App Permission Policies (if deployed via Teams)
In Teams Admin Center → Apps → Permission policies — verify the policy applies to all users, not just a specific region/group.

The error message itself points straight to the sharing layer, so Step 1 resolves this in most cases. Hope this helps!

Was this reply helpful? Yes No
Suggested answer

Haque 3,249 on at

Like (1)

Report
Copy link

Link copied!

Hi @Bjon,

This clearly indicates an issue with the bot's access permissions or tenant/region-specific configuration.

Apart from the answers everyone given, can you please check Bot Channel Registration: If the bot uses channels (Teams, Web Chat, etc.), ensure channel registrations and permissions are correctly set for the new region.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Bjon 71 on at

Like (0)

Report
Copy link

Link copied!

I added user in this page to share to the user.

Added them to the AD group to allow permission to the bot.

In the bot setting, I has also set Multi-Tenant Support.

Where else shall I set?

Was this reply helpful? Yes No
Suggested answer

AP-26031104-0 Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!
Bjon next places to check are usually these:

Environment Security Role
The users also need access to the Power Platform environment itself, not just the bot share.
In Power Platform Admin Center → Environment → Settings → Users + permissions → Security roles

Assign a role that includes:

bot → Read (User)

botcomponent → Read (User)

Even “Basic User” alone is often not enough.

Environment Access
Make sure the external/other-region users are actually added as users inside the environment.
Sometimes B2B users exist in Entra ID but are not provisioned into the Dataverse environment.

Tenant Type Check
Are these users:

Same tenant users in another region?

Or guest/B2B users from another tenant?

If they are guest users, Copilot Studio sharing can still fail depending on authentication/channel configuration.

Teams Deployment
If using Teams:

Re-publish the bot

Reinstall/update the Teams app

Verify Teams App Permission Policies allow the app for those users

Authentication Mode
In:
Copilot Studio → Settings → Security → Authentication

Try confirming whether:

“Users in my organization”
or

“Anyone with the link”

matches your intended access model.

Usually the missing piece is environment-level security roles or Dataverse user provisioning.

Was this reply helpful? Yes No