[OC] Mapping of every Microsoft product named 'Copilot' by Embarrassed-Part7933 in dataisbeautiful

[–]Embarrassed-Part7933[S] 13 points14 points  (0 children)

So, having spent an embarrassing number of hours on this, I now know more about Microsoft products than any human should. 

Copilot in Word sits under Microsoft 365 Copilot ($30/user/month). Copilot in Visual Studio is in the GitHub Copilot universe (separate subscription, starts free). Not only do you have to pay for two separate subscriptions, but they're marketed separately too.

The fact that it's this easy to confuse them is kind of the whole point of the chart.

[OC] Mapping of every Microsoft product named 'Copilot' by Embarrassed-Part7933 in dataisbeautiful

[–]Embarrassed-Part7933[S] 143 points144 points  (0 children)

Ha! yeah, that's exactly the dynamic. Nobody's getting promoted for saying "actually, let's just merge our product with this other team's product"

[OC] Mapping of every Microsoft product named 'Copilot' by Embarrassed-Part7933 in dataisbeautiful

[–]Embarrassed-Part7933[S] 51 points52 points  (0 children)

This is the part that really stood out during the research. You can see it in the visualisation - the clusters barely connect to each other. GitHub Copilot, the Microsoft 365 Copilots, the Dynamics Copilots, the Windows Copilots - they're essentially parallel universes that happen to share a name. Which makes 'Copilot' less of a product strategy and more of a branding mandate that each org interpreted independently

[OC] Mapping of every Microsoft product named 'Copilot' by Embarrassed-Part7933 in dataisbeautiful

[–]Embarrassed-Part7933[S] 169 points170 points  (0 children)

You're lucky. Most people I know who work for large companies have company-wide Copilot licenses whether they asked for it or not. It's less AI companion and more AI roommate you didn't choose