Okay so I enjoyed my chat with @kevmcdonk so much that I made him stick around and give me a deep-dive into how he is seeing customers at @Avanade (and the world!) think about #Copilot Adoption. A big topic? What to do when the out-of-the-box Copilot is not enough and people want to get results from their own data? It's Copilot Extensibility time! There are many ways to do this, some of them being: 📈Graph Connectors - use APIs to crawl data from external sources such as file systems, databases, and SaaS applications. This data is then indexed and made available within Microsoft experiences. A VERY common scenario is connecting to external CRM systems and being able to access that data from within a Copilot. 👯‍♂️Teams Message Extensions - provide a way to extend the functionality of MS Teams by allowing users to interact with your services and data directly from Teams messages. They can be categorized into Search Message Extensions (look up status of a project) and Action Message Extensions (change status of a project) all from within a Teams convo. 👮🏽Declarative Copilots - use config files or low-code tools to define how they should interact with users and data sources. These can specify triggers, responses, and integrations with other services like monitoring a SharePoint list for new entries and sending a notification to a Teams channel whenever a new item is added. This is something you can do from Copilot Studio. 📚Teams AI Library - provides tools and frameworks for building Copilots within Microsoft Teams. This AI library includes pre-built models so you can build a Copilot that helps your team schedule meetings easier. The Copilot could understand natural language requests, check people's availability, and suggest good meeting times, all within a Teams convo. These are some of the ones people have been using so far with so many more things coming soon!