Answered

Issues when Publishing Custom Agents to Microsoft 365 Copilot

(5) Share

Report

Posted on by CopilotUserFr2025

Hello everyone,

In our company, we are currently deploying Microsoft Copilot Pro for all users. As part of this rollout, we’ve developed several custom advanced agents that we want to make available to our users.

Our Deployment Process

We manage our agents through Power Platform environments:

Development (Dev)
Testing (Test)
Production (Prod)

Here’s how we handle the lifecycle:

We create a solution in the Dev environment.
Agent Creation: We build the agent in the Dev environment in the previously created solution.
Testing: Once ready, we migrate the solution to Test environment and then via copilot studio we publish the agent though the channel: Teams and Microsoft 365 Copilot
Publishing:
- We add the channel and enable “Make agent available in Microsoft 365 Copilot”.
- Under Availability options, we select “Show to everyone in my org”.

The Issue

Sometimes, the agent appears in the Microsoft 365 Admin Center under the Agents tab, and the admin receives a request to approve it. After approval, the agent becomes visible to users in both Teams and Microsoft 365 Copilot under “Created by my organization”.

However, other times:

The agent only appears in the Teams Admin Center, not in Microsoft 365 Admin Center.
The admin can only approve it for Teams, and it doesn’t show up in Microsoft 365 Copilot.

What We Observed

If we create the agent directly in Microsoft Copilot Studio (without first creating a solution), it appears in Microsoft 365 Admin Center.
If we create a solution first, then build the agent inside it, it only appears in Teams Admin Center.

This behavior is inconsistent and not practical for our deployment goals.

Our Goal

We want a consistent and reliable process where:

Agents are developed in Dev, migrated to Test, tested in Test, migrated to Prod and deployed in Prod.
During testing, agents are available to selected users via Teams and Microsoft 365 Copilot.
Once validated, agents are deployed to everyone in the organization across Teams and Microsoft 365 Copilot.

Question

Are we missing something in the publishing process?

Is there a recommended way to ensure agents appear in both Teams and Microsoft 365 Copilot, and are manageable via the Microsoft 365 Admin Center?

Any insights or best practices would be greatly appreciated!

Also, if anyone needs help or has questions about this process, I’d be happy to share my experience and support where I can.

Thanks

Categories:

Publish & channel management

I have the same question (2)

All responses (3)

Answers (1)

Sort by

Romain The Low-Code... 2,562 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

hello,

thanks for the awesome description.

You said the only difference is solution first or no solution. BUT did you try on exactly the same agent or with an empty agent ? with default config ? (since MS support will ask you this question too if you open a ticket)

Because to my mind the reason could be feature inside the agent that are not supported in the central admin. I never had problem with agent inside solution. but what i doo in general is :

- create agent

- go to a solution

- add it to the solution with add existing agent

OR

Use default solution for agent in dedicated env.

Never add the problem :(

are you in production env every time ? Developper and sandbox have some time some strange restriction.

Sorry i m not helping but i hope my question could help some one else :)

1 people found this reply helpful.

Was this reply helpful? Yes No
CopilotUserFr2025 40 on at

Like (0)

Report
Copy link

Link copied!

Thanks for your answer.

I noticed the issue while testing different scenarios, including agents with specific topics and SharePoint knowledge bases.

Then I ran mock tests with basic agents (no extra topics, no knowledge base):
- When created inside a solution, the agent only appears in the Teams Admin Center.
- When created without a solution, it appears in the Microsoft 365 Admin Center as expected.

All environments we use (Dev, Test, Prod) are set up as Production environments, so it’s not related to environment type.

Based on this, I don’t think the problem is tied to agent configuration. It seems more like a platform behavior difference when agents are created within a solution. But, will do more testing

I think that Microsoft needs to provide clear documentation and consistent logic for this process. Our plan was to deploy Copilot Pro for all employees (+150), but this inconsistency is a blocker for us. So we might look for other providers.

I’ll continue testing and share updates if I find a workaround. If anyone from Microsoft or the community has official guidance or best practices, that would be very helpful.

1 people found this reply helpful.

Was this reply helpful? Yes No
Verified answer

CopilotUserFr2025 40 on at

Like (0)

Report
Copy link

Link copied!
Hey everyone,

I found a solution for this issue.

Here’s what I did and what worked:

I created my solution, then my agent.

I shared the agent in Microsoft 365 Copilot with my account by going to Channels → Teams and Microsoft 365 Copilot → See agent in Microsoft 365.

Then, I submitted a request for admin approval to deploy the agent or to target specific users.

By doing this, the agent appears and can be deployed in Teams and Microsoft 365 Copilot.

I wanted to share this with everyone.

It might help someone in the future

Thanks

2 people found this reply helpful.

Was this reply helpful? Yes No