Copilot Studio: Failed to publish agent

Question

Copilot Studio: Failed to publish agent

Sara Smith 10

I have one agent I built with copilot studio. It was published before with no errors, but now when I tried to publish I get an error.

It is only published on Teams and SharePoint only. I disconnected and connected Teams. It did not work. I turn off all the topics, it did not work. Here is the error: copilot error

When I click Details I get this message: "There are open issues with your agent

To continue publishing, fix the listed issues. To exclude a topic from publishing, turn it off."

It also give me the option to see the raw, this is the error raw:

[
  {
    "componentDisplayName": "Agent Errors",
    "diagnosticResult": [
      {
        "$kind": "BotSynchronizationError",
        "errorCode": "SynchronizationSystemError",
        "isFatal": true,
        "message": "Call failed with error Microsoft.CCI.Common.Exceptions.BadRequestException message Bad request",
        "errorDetail": "RecallableFunctions.Core.CallFailedException",
        "errorMessage": "Synchronization error with code 'SynchronizationSystemError'"
      }
    ],
    "errorDescription": "There is an error: 'SynchronizationSystemError'",
    "diagnosticErrorCount": 1
  }
]

Raju Roopani (RAJU) 5 Reputation points Microsoft Employee

2026-03-18T19:03:21.7333333+00:00

Thanks for reaching out Sara!
Do you see this issue consistently? could you please provide more details on the repro steps?
Raju Roopani (RAJU) 5 Reputation points Microsoft Employee

2026-03-18T19:03:38.4733333+00:00

Thanks for reaching out Sara! Do you see this issue consistently? could you please provide more details on the repro steps?
Sara Smith 10 Reputation points

2026-03-18T19:20:50.96+00:00

Hello, thank you very much for your response:

I have a theory that this may have been caused by a spreadsheet I deleted and then re-added with the same name. I didn’t realize that the way Copilot Studio works would change the name in the background.

The deleted file was something like Name.xlsx_VT4.mcs (I don’t remember the exact name, and I have already removed it from everywhere). The new file is Namek.xlsx_kti.mcs. I was not aware that the extension after .xlsx would change.

After deleting the file, and uploading the new one, I cloned the agent to Visual Studio, made my updates, and then pushed them to Copilot Studio, which may have caused the error.

Since then, I have deleted the spreadsheet, updated the code to match the new path to the latest spreadsheet (Namek.xlsx_kti.mcs), and even turned off all the topics, but it still does not allow me to publish the agent
Raju Roopani (RAJU) 5 Reputation points Microsoft Employee

2026-03-18T19:40:27.24+00:00

do you see the same error?
Could you please provide little bit more details on the repro steps?
Sara Smith 10 Reputation points

2026-03-18T20:26:55.9033333+00:00

Yes, it is the same error every time. I click on Publish, I want for the agent to publish. 10-15 minutes after I get the same error:

1.

2.

3.

4.

Thank you,
Sara Smith 10 Reputation points

2026-03-18T21:15:44.2233333+00:00

Yes, the error is the same. After I click on publish the agent, I want for 15-20 minutes and then I get the error.
Raju Roopani (RAJU) 5 Reputation points Microsoft Employee

2026-03-18T21:25:09.36+00:00

Could you please share repro steps?
Sara Smith 10 Reputation points

2026-03-18T21:40:32.98+00:00
Attempt to publish the agent.

Observe the publishing error.
Raju Roopani (RAJU) 5 Reputation points Microsoft Employee

2026-03-18T22:06:38.6166667+00:00

This seems to be related to an outage on Azure Bot Service directline and ARM down with 401s due to auth enablement
I will update here once the outage is resolved
Raju Roopani (RAJU) 5 Reputation points Microsoft Employee

2026-03-18T22:48:13.2533333+00:00

Looks like the issue is mitigated. Could you please verify now?

Sara Smith 10

Hello, I tried to publish the agent again and I got the same error:

[
  {
    "componentDisplayName": "Agent Errors",
    "diagnosticResult": [
      {
        "$kind": "BotSynchronizationError",
        "errorCode": "SynchronizationSystemError",
        "isFatal": true,
        "message": "Call failed with error Microsoft.CCI.Common.Exceptions.BadRequestException message Bad request",
        "errorDetail": "RecallableFunctions.Core.CallFailedException",
        "errorMessage": "Synchronization error with code 'SynchronizationSystemError'"
      }
    ],
    "errorDescription": "There is an error: 'SynchronizationSystemError'",
    "diagnosticErrorCount": 1
  }
]

1 answer

Your answer

Raju Roopani (RAJU) 5 Reputation points Microsoft Employee

2026-03-18T19:03:21.7333333+00:00

Thanks for reaching out Sara!
Do you see this issue consistently? could you please provide more details on the repro steps?
Raju Roopani (RAJU) 5 Reputation points Microsoft Employee

2026-03-18T19:03:38.4733333+00:00

Thanks for reaching out Sara! Do you see this issue consistently? could you please provide more details on the repro steps?
Sara Smith 10 Reputation points

2026-03-18T19:20:50.96+00:00

Hello, thank you very much for your response:

I have a theory that this may have been caused by a spreadsheet I deleted and then re-added with the same name. I didn’t realize that the way Copilot Studio works would change the name in the background.

The deleted file was something like Name.xlsx_VT4.mcs (I don’t remember the exact name, and I have already removed it from everywhere). The new file is Namek.xlsx_kti.mcs. I was not aware that the extension after .xlsx would change.

After deleting the file, and uploading the new one, I cloned the agent to Visual Studio, made my updates, and then pushed them to Copilot Studio, which may have caused the error.

Since then, I have deleted the spreadsheet, updated the code to match the new path to the latest spreadsheet (Namek.xlsx_kti.mcs), and even turned off all the topics, but it still does not allow me to publish the agent
Raju Roopani (RAJU) 5 Reputation points Microsoft Employee

2026-03-18T19:40:27.24+00:00

do you see the same error?
Could you please provide little bit more details on the repro steps?
Sara Smith 10 Reputation points

2026-03-18T20:26:55.9033333+00:00

Yes, it is the same error every time. I click on Publish, I want for the agent to publish. 10-15 minutes after I get the same error:

1.

2.

3.

4.

Thank you,
Sara Smith 10 Reputation points

2026-03-18T21:15:44.2233333+00:00

Yes, the error is the same. After I click on publish the agent, I want for 15-20 minutes and then I get the error.
Raju Roopani (RAJU) 5 Reputation points Microsoft Employee

2026-03-18T21:25:09.36+00:00

Could you please share repro steps?
Sara Smith 10 Reputation points

2026-03-18T21:40:32.98+00:00

Attempt to publish the agent.

Observe the publishing error.
Raju Roopani (RAJU) 5 Reputation points Microsoft Employee

2026-03-18T22:06:38.6166667+00:00

This seems to be related to an outage on Azure Bot Service directline and ARM down with 401s due to auth enablement
I will update here once the outage is resolved
Raju Roopani (RAJU) 5 Reputation points Microsoft Employee

2026-03-18T22:48:13.2533333+00:00

Looks like the issue is mitigated. Could you please verify now?
Sara Smith 10 Reputation points

2026-03-19T15:25:22.3+00:00

Hello, I tried to publish the agent again and I got the same error:

[ { "componentDisplayName": "Agent Errors", "diagnosticResult": [ { "$kind": "BotSynchronizationError", "errorCode": "SynchronizationSystemError", "isFatal": true, "message": "Call failed with error Microsoft.CCI.Common.Exceptions.BadRequestException message Bad request", "errorDetail": "RecallableFunctions.Core.CallFailedException", "errorMessage": "Synchronization error with code 'SynchronizationSystemError'" } ], "errorDescription": "There is an error: 'SynchronizationSystemError'", "diagnosticErrorCount": 1 } ]

Answer 1

The error payload shows a BotSynchronizationError with SynchronizationSystemError and a generic “Bad request” message. This indicates a platform-side synchronization failure during publish, not an issue with individual topics.

Use the following steps that align with supported troubleshooting guidance for publishing and channel issues:

Verify the agent configuration
- In Copilot Studio, open the agent and go to the Publish page.
- Confirm that all required configurations are valid: authentication, Teams and SharePoint channels, connections, and knowledge sources.
- Ensure there are no missing dependencies (topics, flows, connectors, or data sources) that were deleted or changed since the last successful publish.
Check for data policy/DLP issues
- Data loss prevention (DLP) changes can silently block publishing and surface as generic errors.
- On the publish error panel, select Show raw (already done) and look for any DlpViolationError or messages like “At least one connector here has been blocked by your admin” or “You need to configure at least one channel…”. If present, contact the Power Platform or tenant admin to review and update data policies in the Power Platform admin center so the agent and its channels/connectors are allowed.
Revalidate channels
- Ensure at least one channel is correctly configured and allowed by policy (for example, Teams).
- If the Telephony channel is enabled in this environment and appears disabled or blocked, ask the Power Platform admin to review tenant data policies that may be blocking channels, as blocked channels can prevent publishing.
Retry a clean publish
- After validating configuration and policies, publish again from Copilot Studio.
- If the agent was modified after the last publish, ensure all changes are saved and that no topics or tools reference removed connectors or channels.
If the error persists
- Because SynchronizationSystemError is a platform synchronization failure, collect the error JSON, agent ID, environment, and timestamp, and open a support ticket with Microsoft so the service team can inspect the backend synchronization issue.

References:

Share via

Copilot Studio: Failed to publish agent

1 answer

Your answer