Common Causes
Missing or Incorrect Permissions
The agent may lack required permissions for the M365 Copilot channel. Double-check that the agent is published with the correct permissions and that your environment allows M365 Copilot integration.
Channel Configuration Delay
Sometimes, after enabling a new channel (like M365 Copilot), it can take several hours for the configuration to propagate. Try waiting and testing again later.
Environment or Tenant Restrictions
Some environments or tenants have policies or Data Loss Prevention (DLP) rules that block communication between Copilot Studio agents and M365 Copilot.
Agent Not Set as “Available to Organization”
Ensure the agent’s availability is set to “Show to my teammates” or “Available to organization” in Copilot Studio.
Input Format or Trigger Issue
M365 Copilot may require a specific invocation phrase or format to trigger the agent. Try using the agent’s exact name or a supported command.
Publishing Not Completed
After publishing, make sure the agent status is “Published” and not “Draft” or “Pending.”
Troubleshooting Steps
Check Channel Status
In Copilot Studio, verify that the M365 Copilot channel is enabled and shows as “Connected.”
Review Agent Availability
Confirm the agent is set to be visible to your teammates or organization.
Test in Different Environments
If possible, try publishing the agent in a different environment to see if the issue persists.
Check Activity Transcript
If the transcript is empty, it means the agent is not receiving the input at all—pointing to a channel or configuration issue, not an agent logic problem.
Review Admin Center Policies
Ask your Power Platform or M365 admin to check for any DLP, security, or channel restrictions.
Wait and Retry
If you just enabled the channel, wait a few hours and try again.
Re-publish the Agent
Sometimes, unpublishing and republishing the agent can resolve propagation issues.