Copilot Not Published in Microsoft 365 Copilot as agent

Question

Copilot Not Published in Microsoft 365 Copilot as agent

Wasiq Khan 70

Hello everyone,

I'm facing an issue where my custom Copilot agent is not appearing or published in the Microsoft 365 Copilot experience. I’ve completed the setup and publishing steps in Copilot Studio, but it doesn’t show up under the Microsoft 365 Copilot.
thanks

Karan Shewale 1,040 Reputation points Microsoft External Staff

2025-08-05T09:36:40.41+00:00

Thanks for bringing this issue to our attention. We will check and update you soon.

1 answer

Your answer

Karan Shewale 1,040 Reputation points Microsoft External Staff

2025-08-05T09:36:40.41+00:00

Thanks for bringing this issue to our attention. We will check and update you soon.

Answer 1

I understand you're having trouble with your custom Copilot agent not appearing in Microsoft 365 Copilot after publishing it through Copilot Studio. This is a common issue that can have several causes. Let me help you troubleshoot this step by step.

Common Causes and Solutions:

Publishing and Deployment Status

Ensure your agent is fully published (not just saved as draft)
Check that the publishing process completed successfully without errors
Verify the agent status shows as "Published" in Copilot Studio

Channel Configuration

Make sure you've enabled the Microsoft Teams channel for your agent
The agent needs to be configured for Microsoft 365 integration specifically
Check if you've selected the correct deployment scope (organization-wide vs. specific users)

Permissions and Access

Verify you have the necessary permissions to publish agents in your organization
Check if your organization has policies restricting custom Copilot agents
Ensure your Microsoft 365 license includes Copilot capabilities

Propagation Delay

It can take 15-30 minutes for published agents to appear in Microsoft 365 Copilot
Sometimes it may take up to 2 hours for full propagation across the tenant

Tenant Configuration

Confirm that custom agents are enabled in your Microsoft 365 admin center
Check the Copilot admin settings in your organization

Troubleshooting Steps:

Re-check Publishing:

Go back to Copilot Studio

Verify the agent status is "Published"

Try republishing if necessary

Verify Channel Settings:

- In Copilot Studio, go to your agent settings

   - Check the "Channels" section

      - Ensure Microsoft Teams/Microsoft 365 integration is enabled

Check Admin Settings:

Have your admin verify that custom Copilot agents are allowed
- I understand you're having trouble with your custom Copilot agent not appearing in Microsoft 365 Copilot after publishing it through Copilot Studio. This is a common issue that can have several causes. Let me help you troubleshoot this step by step.

Common Causes and Solutions:

1. Publishing and Deployment Status

Ensure your agent is fully published (not just saved as draft)
Check that the publishing process completed successfully without errors
Verify the agent status shows as "Published" in Copilot Studio

2. Channel Configuration

Make sure you've enabled the Microsoft Teams channel for your agent
The agent needs to be configured for Microsoft 365 integration specifically
Check if you've selected the correct deployment scope (organization-wide vs. specific users)

3. Permissions and Access

Verify you have the necessary permissions to publish agents in your organization
Check if your organization has policies restricting custom Copilot agents
Ensure your Microsoft 365 license includes Copilot capabilities

4. Propagation Delay

It can take 15-30 minutes for published agents to appear in Microsoft 365 Copilot
Sometimes it may take up to 2 hours for full propagation across the tenant

5. Tenant Configuration

Confirm that custom agents are enabled in your Microsoft 365 admin center
Check the Copilot admin settings in your organization

Troubleshooting Steps:

Re-check Publishing:

Go back to Copilot Studio
Verify the agent status is "Published"
Try republishing if necessary

Verify Channel Settings:

  - In Copilot Studio, go to your agent settings
  
     - Check the "Channels" section
     
        - Ensure Microsoft Teams/Microsoft 365 integration is enabled
        
        **Check Admin Settings:**
        
           - Have your admin verify that custom Copilot agents are allowed
           
              - Check Microsoft 365 admin center for Copilot policies
              
              **Wait and Refresh:**
              
                 - Wait at least 30 minutes after publishing
                 
                    - Refresh your Microsoft 365 Copilot interface
                    
                       - Try signing out and back in to Microsoft 365
                       
                       **Test Access:**
                       
                          - Try accessing from a different browser or incognito mode
                          
                             - Check if other users in your organization can see the agent

If none of these steps resolve the issue, you may need to contact Microsoft Support or your organization's IT administrator to check for specific tenant configurations that might be blocking custom agent deployment.

Thanks,

Karan Shewale.

*************************************************************************

If the response is helpful, please click "Accept Answer" and upvote it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate.

Wasiq Khan 70 Reputation points

2025-08-06T07:41:25.9666667+00:00

Thanks for the reply. I followed the steps, and there was no error. However, after publishing the agent, it still shows the previous publish date and an older version for the organization.
Karan Shewale 1,040 Reputation points Microsoft External Staff

2025-08-06T08:19:28.7+00:00

Hello Wasiq,

Thank you for the follow-up. The issue you're describing - where the agent shows the previous publish date and older version after republishing - indicates a versioning or cache synchronization problem. Here are specific steps to resolve this:

Version Update Issues:

1. Clear Publishing Cache:

In Copilot Studio, go to your agent settings

Navigate to the "Versions" or "Publishing" section

Delete any draft versions that might be conflicting

Create a new version before republishing

2. Force Version Increment:

Make a minor change to your agent (add a space, modify description)

Save the changes

Publish again to ensure a new version is created

3. Admin Center Verification:

Have your admin check the Microsoft 365 admin center

Verify the agent version listed there matches your latest publish

Check if there are any pending approval workflows blocking the update

4. Extended Propagation Time:

Version updates can take longer than initial publishing (up to 4-6 hours)

The organization-wide rollout may be staged, causing version discrepancies

5. Tenant-Level Refresh:

Ask your admin to perform a tenant-level refresh in the admin center

This can force synchronization of the latest agent versions

If the version discrepancy persists after 24 hours, this may require escalation to Microsoft Support as it could indicate a backend synchronization issue.

Thanks,

Karan Shewale.

*************************************************************************

If the response is helpful, please click "Accept Answer" and upvote it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate.
Wasiq Khan 70 Reputation points

2025-08-06T08:56:53.13+00:00

Are there any limitations on publishing custom agents to Microsoft 365 Copilot in the trial version?
Karan Shewale 1,040 Reputation points Microsoft External Staff

2025-08-12T04:24:45.6033333+00:00

Yes, there are several limitations when using the trial version for publishing custom agents to Microsoft 365 Copilot:

Trial Version Limitations

1. Licensing Restrictions

Trial users cannot publish agents to production Microsoft 365 Copilot

Limited to development and testing environments only

No access to organizational app catalog deployment

2. Distribution Limitations

Cannot distribute agents to other users in the organization

No sideloading capabilities for trial accounts

Limited to personal testing scope

3. Feature Restrictions

Reduced API call limits and quotas

Limited access to premium connectors and services

No access to enterprise-grade security features

Restricted integration with organizational data sources

4. Publishing Requirements To publish custom agents to Microsoft 365 Copilot in production, you need:

Valid Microsoft 365 business license (E3/E5 or equivalent)

Copilot for Microsoft 365 license

Azure subscription for backend services

Appropriate admin permissions in Microsoft 365 admin center

5. Development Workflow

Trial version: Build and test agents locally

Production publishing: Requires upgrading to full license

Use M365 Agents Toolkit for development regardless of license type

Recommended Approach

Develop and test your agent using the trial version

Upgrade to appropriate licensing before attempting production deployment

Follow Microsoft's official publishing guidelines for custom agents

For production deployment, ensure you have the necessary Microsoft 365 and Copilot licensing in place.

Share via

Copilot Not Published in Microsoft 365 Copilot as agent

1 answer

Your answer