The fact that your agent works in Teams, Word, Excel, and Microsoft 365 Copilot Chat but not Outlook on the web strongly suggests this is more of a deployment/availability issue than a problem with the agent itself.
One important detail: publishing to the Microsoft 365 channel in Copilot Studio does not always guarantee immediate visibility across every M365 surface, especially Outlook on the web.
A few things to check:
1. Deploy the app through the Microsoft 365 Admin Center
In many tenants, Outlook visibility becomes more reliable once the agent is deployed as an app:
- Go to admin.microsoft.com
- Navigate to:
- Settings → Integrated apps
- Locate your Copilot agent / Teams app
- Deploy it to:
- specific users/groups, or
- the whole organization
Since these agents are packaged similarly to Teams apps, admin deployment can affect whether Outlook surfaces them consistently.
2. Allow time for propagation
Even after publishing or deployment, M365 surfaces can take time to sync.
It’s not unusual for:
- Teams to show the agent first,
- while Outlook on the web lags behind.
Propagation can sometimes take several hours (occasionally longer).
3. Verify licensing and app availability
Make sure:
- the affected users have the required Microsoft 365 Copilot licensing,
- custom apps are allowed in Teams/M365 policies,
- and the app is not blocked by admin governance policies.
4. Recheck the Outlook client experience
Since you mentioned the agent briefly appeared and disappeared, it may also help to:
- sign out/in,
- clear browser cache,
- try another browser,
- or test with another user account.
That behavior often points to a client-side sync/cache or entitlement refresh issue.
References:
Vishnu WR
Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥
