Skip to main content

Microsoft 365 Copilot Connector Guide

Setup notes, example prompts, and troubleshooting for connecting Fugo's MCP connector to Microsoft 365 Copilot.

Written by Fugo

Table of contents


About this guide

This is the setup guide for connecting Fugo's MCP connector to Microsoft 365 Copilot - covering the connection steps, example prompts, and troubleshooting specific to Copilot.

For what the connector is, what it can do across every supported assistant, and how permissions and security work, see the Fugo MCP Overview first if you haven't already.


Setting up the connector

Unlike Claude, Microsoft 365 Copilot connectors are typically added and assigned at the organization level rather than by an individual user. A Microsoft 365 admin adds Fugo as an agent for Copilot through the Microsoft 365 admin center, then assigns it to the people or groups who should have access - after that, anyone it's assigned to can use it directly from Copilot.

⚠️ Internal note - confirm before publishing: the exact steps here (whether Fugo is available as a one-click listing for admins to add, or requires a manual connector/agent registration; how sign-in to the Fugo account is handled during setup; and whether this is available to all Fugo customers today or only in limited rollout) are not yet confirmed against product/eng. Hold this article back from publishing until that's verified - see the chat summary for details.

Once connected, the same Fugo account permissions apply as with any other assistant - see Permissions and security in the Overview article.


What's different in Copilot

The underlying connector is the same one Claude uses, so it exposes the same screens, media, playlists and triggers, share-to-screen, and workspace administration capabilities described in the Fugo MCP Overview. A couple of things are specific to how Copilot presents that data:

  • Results render as Adaptive Cards. Instead of plain text, things like a screen's live status come back as a formatted card - for screen health lookups, this can include a live screenshot of what's currently on the screen.

  • Cards link back to the CMS. Results include a clickable link back to the corresponding screen, playlist, or content item in the Fugo CMS, so you can jump from the Copilot conversation straight into the CMS to make further changes.

  • It's a natural fit for Outlook, Teams, and SharePoint content. Because Copilot already has your Outlook/Teams/SharePoint context, "share to screen" prompts built around that content (e.g. publishing an email or a Teams message to a screen) tend to be the most common starting point.


Example prompts

Try starting with prompts like these:

  • "Put this email on the lobby screen until I stop it."

  • "List all screens in our London Spaces and show which playlist each one is running right now."

  • "Upload this week's promo video to the Marketing space and create a playlist called 'Weekly Promo' that runs it on every UK screen starting Monday."

  • "Create a manual trigger called 'Fire Drill' that I can fire on every screen in the Warehouse space."

Be specific about Space names, screens, and dates - Copilot will confirm the details with you before anything changes, so being precise up front catches mistakes early.


Troubleshooting

  • "Copilot can't see my Spaces or screens" - confirm with your Microsoft 365 admin that the Fugo agent is assigned to you, and that your Fugo account sign-in during setup completed successfully.

  • "Uploading from a URL failed" - the URL needs to be publicly accessible without a login. If your file lives in a private SharePoint or Google Drive folder, generate a public share link first, or upload the file a different way.

  • "Copilot took the wrong action" - be specific about Space name, screens, and dates in your request, and read the confirmation step carefully before approving it - that's your chance to catch a mistake before it happens.

  • "I want to test this without touching real screens" - create a test Space in Fugo with a couple of demo screens and ask Copilot to work only within that Space.


Need more help?

Run into something that isn't covered here? Reach out via the support chat inside the Fugo CMS, or email us at support@fugo.ai. Include a screenshot of what Copilot said and the prompt you used so we can investigate quickly.

Don't have a Fugo account yet? Start a free trial.

Did this answer your question?