Answered

Agents now stating - You don't have access to talk to this bot, contact the owner

(3) Share

Report

Posted on by BadgerBen

For the last few months, my Agents have been working fine, with 'Share' permission for colleagues with the role of 'Editor' and 'Everyone in organization' set to 'No permissions, unless specified'. The agents are available via SharePoint Channel as either approved, default or neither for the sites in question. All have been working fine. For the last couple of days we've been seeing: 'You don't have access to talk to this bot, contact the owner' for anyone that hasn't been added to the agent via the Share button.

I'm aware there have been some changes to the Copilot studio platform, but can't find anything that calls this out specifically.

Has something changed, and what does '...can manage connections and configure the to either chat with it or allow it to operate autonomously on their behalf' actually do?

Thanks!

Categories:

Bot administration

General topics

Publish & channel management

I have the same question (0)

All responses (5)

Answers (1)

Sort by

Suggested answer

Valantis 6,735 on at

Like
a
(2)

Report
Copy link

Link copied!

Hi @BadgerBen,

This matches a pattern several users are hitting around mid-June 2026. A few things changed simultaneously that could explain it:

1. Copilot Credits enforcement started June 16, 2026. If your environment doesn't have Copilot Credits allocated or PAYG configured, agents may block access with the "You don't have access" message rather than a billing error. Check PPAC > Billing > your environment and verify credits are allocated or PAYG is enabled.

2. Check your agent's authentication settings. Go to Copilot Studio > Settings > Security > Authentication. If it recently changed from "No authentication" to requiring Microsoft authentication, users who aren't explicitly shared will get the access denied message. Microsoft has been tightening default authentication settings on existing agents during platform updates.

3. The SharePoint channel specifically: the SharePoint channel may have been refreshed during a platform update which can reset channel-level authentication settings. Open the SharePoint channel configuration and verify the authentication mode is still what you set originally.

4. For the "...can manage connections and configure..." permission you asked about: this is the new connection permission model Microsoft introduced. It controls whether shared users can manage the agent's connector connections on their behalf. Set it to "Can use" rather than "Can manage" for end users who just need to chat.

Raise a Microsoft support ticket referencing June 14-16 as the regression date with your agent IDs.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
BadgerBen 7 on at

Like
a
(1)

Report
Copy link

Link copied!

Thank you for your reply. If you have any links to describe changes mid June, that would be great.

1. The Agent is in an environment backed by a PAYG billing policy

2. The Agent has always been configured with entra auth.

3. I can't see a way to check auth settings on the SharePoint channel?

4. The agent doesn't use any tools (it's literally just public website and SP knowledge with some topics.

I can 'Share' the agent with everyone in my org, or do so via Entra groups, but I'd like to understand the implication of doing that, as it's a change to how things were working previously.

Thanks again.

Was this reply helpful? Yes No
Verified answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!
If your intention is for all users in the organization to use the agent:

Change Everyone in organization to Can chat (if your governance policies allow it), or

Share the agent with an Entra ID security group instead of individual users.

If your intention is to restrict access:

Keep Everyone in organization = No permissions, unless specified.

Explicitly share the agent (or share with a security group).

Nothing appears to be wrong with your agents or SharePoint channel configuration. The platform is increasingly enforcing explicit agent sharing permissions,

and publishing an agent to SharePoint no longer implicitly grants chat access.

The new permission wording around "chat" and "operate autonomously on their behalf" is related to Microsoft's move toward autonomous agents and delegated

actions, where an agent can do more than simply answer questions and may execute actions using a user's permissions.

Was this reply helpful? Yes No
VirginiaH 9 on at

Like
a
(0)

Report
Copy link

Link copied!

This hit us today as well.

Previously, anyone with a "Read" role in SharePoint could use the chatbot (we have PAYG setup).

Now, we seem to have to explicitly share the chatbot with a user group. That's fine if it's everyone, it's an additional administrative headache if not. Our site owners won't understand and will be coming to us for assistance.

Do I understand this new requirement correctly?

Was this reply helpful? Yes No
BadgerBen 7 on at

Like
a
(0)

Report
Copy link

Link copied!

Sharing the agent a couple of Entra groups resolved the issue. I wanted to be sure 60,000 users didn't receive a message telling them I'd shared an agent with them before doing this - I can confirm they didn't.

Was this reply helpful? Yes No