Cannot publish a "new experience" agent after deploying via Pipelines to a managed environment

(1) Share

Report

Posted on by AgentSmith

Bare bones agent with nothing but a single line of "Instructions" and otherwise all default settings. Built in an unmanaged DEV environment, wherein it was published successfully to the Teams + M365 Copilot channel. Deployed via Pipelines to a managed TEST environment. Deployment completed successfully. When attempting to "Publish" in the managed TEST environment: "Failed to publish Channel state cannot be modified on a managed CLI Agent bot -- the solution is read-only in this environment." The channel state was not modified in any way from the configuration that came with the deployment.

Does anyone have any info about this? Do "new experience" agents simply not allow for pipeline deployment to managed environments yet? (I have no problem deploying and publishing "old experience" agents across these same two environments via the same pipeline.)

Categories:

Publish & channel management

I have the same question (0)

All responses (9)

Answers (0)

Sort by

Suggested answer

Haque 3,653 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @EdwinYPTC,

Let's develop and publish new experience agents fully in the unmanaged DEV envrionment. Then use pipeline deployment to move the published solution to TEST and PROD as read-only packages. A thread is developing in this.

We cannot publish or modify the channel state (such as publishing the agent) directly in the managed TEST environment after deployment. However, the old experience agents do not have this restriction, which is why your pipeline deployment and publishing works fine for them.

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
Suggested answer

sannavajjala87 457 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi,
Yes , what you’re seeing is expected behavior with the current “new experience” Copilot Studio agents and how they behave in managed environments. When the agent is deployed as part of a managed solution, the solution becomes read-only in the target (TEST) environment, and channel configuration is not fully solution-aware. That means anything related to channel state (like Teams + M365 Copilot publishing) cannot be modified as part of the managed solution publish step, even if you didn’t explicitly change anything.
In fact, channel configurations (along with things like authentication settings and sharing) are explicitly called out as items that don’t travel cleanly with the solution and require post-deployment setup in each environment.
So what’s happening in your case is:

The pipeline deploy succeeds because the solution itself is valid

But publishing tries to update the channel state

Since the solution is managed (read-only), that update is blocked → hence the error

This is also why your “old experience” agents work , they rely on a different publishing model that doesn’t enforce the same constraints.
What you can do right now:

Treat channel publishing as a post-deployment step in TEST/PROD

Reconfigure or re-enable the channel directly in the target environment (outside solution context)

Avoid expecting channel state to be promoted via pipeline until full ALM support is available for new agents

So to your question , it’s not that pipelines don’t work, it’s that ALM for “new experience” agents is still incomplete around channels. You can deploy the agent, but publishing to channels still needs manual handling in managed environments.
Hope that helps clarify what’s going on.

Was this reply helpful? Yes No
AgentSmith 6 on at

Like
a
(0)

Report
Copy link

Link copied!

@sannavajjala87 thanks for replying! Does "manual handling in managed environments" and "post-deployment setup" mean that I can, actually, fix it after deployment by changing something in the agent/solution/environment? If so, I'd love any direction you could provide around what to do. Or does it rather mean that we simply can't use solution pipeline deployment at all right now with new experience agents?

Was this reply helpful? Yes No
Suggested answer

11manish 3,323 on at

Like
a
(0)

Report
Copy link

Link copied!

This does not appear to be a pipeline configuration issue. The deployment succeeds, but the Publish action attempts to modify channel metadata that is read-only in a managed solution. Given that your "old experience" agents publish successfully through the same pipeline, the behavior strongly suggests a current limitation or product issue specific to the new Copilot Studio agent experience.

If publishing in the target managed environment is a requirement, I recommend opening a Microsoft Support ticket.

Was this reply helpful? Yes No
Suggested answer

Manoj - ManoVerse 28 on at

Like
a
(0)

Report
Copy link

Link copied!

once you deploy to a managed environment, everything becomes read‑only. Publishing an agent is treated like a change, so it’s not allowed there in TEST.
To handle this, you should set up all environment settings (channels, connections, configs) and publish the agent in DEV first, where changes are allowed. Then use your pipeline to deploy that already published agent to TEST/PROD.
If something is different between environments (like URLs or connections), use environment variables and connection references so they can be updated during deployment without changing the solution.

Was this reply helpful? Yes No
AgentSmith 6 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks again to all above for helping to think this through.

When the agent is published in DEV and then pipeline deployed to TEST, it shows up in TEST as "Draft"/unpublished. Publication appears to be environment-specific, but publication from the target TEST environment is blocked because of the read-only channel state. It doesn't seem possible to publish in DEV, then pipeline deploy to TEST and have the state of being published to the Teams + M365 channel carry over. But maybe I'm wrong about that?

Was this reply helpful? Yes No
Suggested answer

sannavajjala87 457 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
@AgentSmith

Publishing state doesn’t move across environments, it's environment‑specific and not solution-aware. Once deployed as managed, you can’t publish in TEST/PROD because it’s read-only, so pipelines can deploy the agent but not handle channel publishing.
Here are Manual Steps for Channel Publishing in TEST (Managed Environment)

Open Copilot Studio in TEST

Go to the TEST environment

Open the agent (it will show as Draft)

Break out of solution context (important)

Open the agent directly from Copilot Studio (not from the Solution view)

This avoids being fully locked by managed solution constraints

Reconfigure the channel

Go to Channels → Microsoft Teams / M365 Copilot

Reconnect or re-enable the channel if needed

In some cases, remove and re-add the channel configuration

Publish from channel UI

Trigger publish from the channel page, not via solution publish

This sometimes bypasses solution-level restrictions

Validate permissions

Ensure:

Proper connection references are valid in TEST

Required environment settings (URLs, auth, connectors) are configured

If publish is still blocked

This confirms current limitation → no true workaround

Use:

DEV for channel publish testing

TEST only for validation via test pane / non-channel scenarios

Was this reply helpful? Yes No
AgentSmith 6 on at

Like
a
(1)

Report
Copy link

Link copied!

Update: I submitted a ticket and heard back from support, confirming a "known issue". Unfortunately, @sannavajjala87, the approach of attempting to open the agent from outside of the solution and then publish won't work until the issue is resolved. It's an issue with agents created in the "new experience". On the plus side, over on Reddit, there's word that MS has identified the issue and aiming to implement a fix by 7/6/2026: New-experience agent won't publish in managed Prod after pipeline deploy — "channel state cannot be modified on a managed CLI Agent bot." Anyone cracked this? : r/copilotstudio

Was this reply helpful? Yes No
Manoj - ManoVerse 28 on at

Like
a
(0)

Report
Copy link

Link copied!

@AgentSmith Thanks for updating this thread with Support response. Appreciate it.

Was this reply helpful? Yes No