Developing for extensibility with Miro and Microsoft 365
summary
Adds a composeExtension section to the Teams bot manifest (bot ID, domain, commands) and implements handlers for composeExtensionQueryLink and composeExtensionQuery to return adaptive card JSON; adaptive cards win because they adapt to host UI and support quick actions. Search uses the search command with parameters (Teams exposes 10 predefined commands) and returns lists of cards. Miro reuses the same cards to extend from Teams into Outlook and Copilot, cutting lift vs graph connectors and shipping faster.
AI-written summary · about
chapters (5)
- 0:00Miro and M365 integration
- 1:59Link unfurling with message extensions
- 8:03Extending to Copilot and Outlook
- 14:55Reusing adaptive cards
- 15:57Closing and call to action
related talks
43mBuilding Adaptive Card-based Loop components for Microsoft 365
47mBeyond 300M users: How to bring your Teams app to Outlook and Microsoft 365
50mAdaptive Cards in Office 365 processes
53mThe Latest in Microsoft Teams
43mHarness the power of AI: Extend Copilot and beyond
22mLive Q&A – Karuana Gatimu
08mOffice Extensibility Overview
20mPowering the Cockpit: Boost Your M365 Flight Crew | Boost Microsoft 365 with Cowork, Scout & More