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

This error can occur even when you are the agent owner, because ownership and runtime access are separate checks.

I would suggest checking these points:

1. Authentication settings: In Copilot Studio, open Settings > Security > Authentication and verify the configured authentication method. Make sure it matches how the agent is embedded in your code app.

2. Publish the latest configuration: If you recently changed authentication or access settings, save and publish the agent again, then retest it.

3. Verify the signed-in identity: Confirm that the Microsoft account used in the embedded app belongs to the same tenant as the agent. If the app uses a different tenant, cross-tenant access restrictions may cause this error.

4. Check the embedding method: If you are embedding the agent using the Direct Line API or a custom web client, verify that the authentication and channel configuration are appropriate for that integration. Being signed in to the website does not automatically authenticate the user to the agent.

5. Review agent sharing and tenant policies: Ask your administrator to confirm that the agent is published, available through the intended channel, and permitted by your organization's authentication and data policies.

Official Microsoft documentation:

Configure user authentication in Copilot Studio:

https://learn.microsoft.com/en-us/microsoft-copilot-studio/configuration-end-user-authentication

Configure authentication for agents:

https://learn.microsoft.com/en-us/microsoft-copilot-studio/agents-experience/settings-overview

One question: How are you embedding the agent in your code app: using the Copilot Studio embed code, the Direct Line API, or a custom web client? The exact integration method will help narrow down the fix.

If this helps, please like the response.

wow so easy, just do the settings, and publish the agent, even though that isnt required to get the demo website. Or even if you don't want to publish yet. Then make sure you have the correct embedded user, even though there is no way to find that out who that is. And that even if you are a owner, you might not be able to use it if you have the wrong version, and version number is where? Genius, i will do those things.

Actually, I was trying through the web app based embed code we have in newer preview version of the copilot agent. But it seems like for these we have to toggle the authentication as no authentication instead of Microsoft Entra Authenticated. 
But is there a way to handle this with Microsoft authentication allowed? And if let's say I go with no authentication approach also will the user not have to authenticate the connected flows and connections separately? As this this web app is embed inside code app

Hi, this usually means the embedded app user is not matching the Copilot Studio access settings.
Check that the bot is published, the security settings allow your user or group, and you are signing in with the same Entra ID tenant used by the copilot. Also confirm the embedded app is using the correct bot/environment endpoint.
Even as owner, the embedded channel can still block access if the auth token, tenant, or published bot version does not match.