Copilot Extensibility: Your options to extend Microsoft 365 Copilot

[@Abrekme]

Thanks for the video, Nick! I didn't catch the last part: can something developed in Copilot Studio be deployed as an extension for M365 Copilot or as an independent custom chatbot for a specific task?

[@Abrekme]

Ok, got it, so you can extend the exsisting M365 Copilot.

[@brightideasagency]

Yes, the long term intent seems to be both with Copilot able to orchestrate responses between Copilot for Microsoft 365 and individual Copilots.

[@georgewashington3012]

Good vid. The fact that you had to create a flowchart to explain which deployment method to use (Power, Graph, etc.) shows how confusing Microsoft has made this. Microsoft should use ordinary language to explain when to use which option based on what the company is trying to accomplish. Question - it looks like these plugins/extensions (like ServiceNow) would require someone to enter prompts into an entirely separate Teams channel for the particular service instead of entering it into the generic Copilot chat channel in Teams (or in the Copilot window in Edge/Windows). This seems kludgy as companies will eventually have a dozen or more such integrations and they’ll have to scroll through a laundry list of Copilot plugin channels in Teams just to find the right one into which to type a prompt. It seems like a sloppy approach when most people want one single AI window into which they can enter a prompt regarding ANY Copilot integrated service. Did I confuse something here? This will get unwieldy fast.

[@brightideasagency]

Thanks for watching. The infographic is from Microsoft. I don’t think the way they have approached this is unreasonable, Copilot exists as an interface for M365, and Microsoft has exposed the existing tools for M365 enhancement to Copilot. This seems like the most reasonable path. On your question: No, all “dialog” with Copilot is through M365 chat/Copilot in Teams, you cannot use Copilot plugins in Teams channels.