Demystifying Copilot for End Users

Iron Contributor

Hello All, I am attempting to demistify Copilot for end users. Here is what I have: 

AI Copilots: Your Versatile Assistants for Diverse Tasks!

Microsoft Copilot: Meet your daily AI companion, Copilot is integrated into Bing, is designed to assist you with a variety of tasks. Whether you need to refine written material, condense extensive notes, or delve into research on various subjects, Copilot is here to provide support every step of the way.

Copilot for Microsoft 365 (M365): Imagine having a personal assistant integrated within your preferred Microsoft 365 applications. These copilots enhance your productivity by streamlining tasks in Word, Excel, PowerPoint, Teams, Outlook, and more, enabling you to accomplish more in less time. (Additional Licensing) 

Microsoft 365 Chat: This feature extends the capabilities of Microsoft Copilot by not only connecting to the internet but also integrating with your organization’s data. It empowers you to query M365 documents, Teams conversations, emails, and more, synthesizing information to provide comprehensive insights. (Additional Licensing)

Copilot for Power Platform: Elevate your experience with Power Automate and Power Apps by utilizing the built-in AI assistant, Copilot. This tool is at your disposal to answer questions, assist in developing solutions, and offer guidance in resolving any issues you encounter.

Copilot for GitHub: Think of GitHub Copilot as your coding buddy that offers helpful suggestions while you write code. It works with popular coding tools and uses artificial intelligence to understand what you’re trying to do. (Additional Licensing)

The first one is Bing Chat Enterprise currently, and I am finding just calling it Copilot very confusing. As when I say "Microsoft Copilot" end users think M365 Copilot. I was corrected on a recent call when I called it Copilot in Bing, but I just feel that makes more sense. Any thoughts on how to make this less confusing for end users????

2 Replies

@jamielwatson This is a good effort. It does feel like a bit of a mess at the moment and I like that you've highlighted the 'free' ones vs the paid versions (which seem to be increasing moment by moment!)


I think ideally, we'll just see Copilot everywhere and the context of how we use Copilot will depend on the application we're in. We can just tell end users - "Hey, when you see Copilot in your app, it's there to help you in your application" and then we just need to explain where it isn't available.


It does assume you have an E3, E5, or an F license I believe. I think I’m wrapping my head more and more around it!!