microsoft / microsoft/Agent365-Samples
Admin Center: Publish wizard shows "Publish failed" UI error despite agent being successfully published via a365 publish CLI
@biswapm is already working on this.
Since Mar 23, 2026.
- Dominant language
- C#
- Stars
- 108
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
Description
After successfully running a365 publish (CLI exits with success) and configuring the agent blueprint in the Teams Developer Portal, the M365 Admin Center publish wizard (admin.cloud.microsoft) consistently shows:
"We couldn't publish your agent agentframework Blueprint. Please try again."
However, the agent is actually published — it appears in the Agents → Requests tab with status Pending review and shows Copilot + Teams as supported channels. The wizard error is a false negative caused by CSP violations in the browser console:
Uncaught (in promise) Error: Publish command did not complete successfully
Connecting to '' violates Content Security Policy directive: connect-src
Link : https://github.com/microsoft/Agent365-Samples/tree/main/python/agent-framework/sample-agent
Expected behavior
The publish wizard should show success after a365 publish completes and the Teams Developer Portal is configured.
SDK Version
a365 v1.1.109.19759
Language/Runtime
Python 3.13.12
OS
Windows 11
How to Reproduce
- Run a365 publish → CLI succeeds
- Configure agent blueprint at https://dev.teams.microsoft.com/tools/agent-blueprint//configuration (Agent Type: Bot Based, Bot ID: )
- Go to M365 Admin Center → Agents → Publish new agent
- Select users → Apply policy → Review and finish → click Publish
- Wizard shows "Publish failed" with CSP errors in browser console
Output
Actual: Wizard shows publish failure. Browser console shows multiple CSP connect-src violations blocking network requests from admin.cloud.microsoft.
Screenshots
Code of Conduct
- I agree to follow the Microsoft Open Source Code of Conduct.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.