Skip to main content Skip to local navigation

Microsoft Copilot is not meant for work.

At York University management tells us that Microsoft Copilot can "[enhance] your productivity with our advanced AI tools—YU AURA and Microsoft Copilot. These services streamline tasks, improve efficiency, and support your everyday activities." (source). Policy documents exhort the work potential for Copilot and Copilot Premium, with helpful tips about guardrails and data types:

UIT usage limits table for data vs. tool.  Copilot and Copilot premium are highlighted.
UIT usage limits table for data vs. tool. Copilot and CoPilot premium are highlighted. (Source)

It's hard to not get the impression that management is firmly of the opinion that the Copilot AI tools are the bees knees when it comes to productivity tools. Turns out, though, that Microsoft disagrees.

"Copilot is for entertainment purposes only"

Microsoft, itself, is unequivocal in its terms of use: "Copilot is for entertainment only". (source). No ifs. No ands. No buts.

IMPORTANT DISCLOSURES & WARNINGS

    Copilot may include advertising.
    Copilot may include both automated and manual (human) processing of data. You shouldn’t share any information with Copilot that you don’t want us to review.
    We plan to continue to develop and improve Copilot, but we make no guarantees or promises about how Copilot will operate or that it will operate as intended.
    Sometimes, we may offer certain features or services as part of “Copilot Labs.” These features and services are highly experimental and may not always work as intended. We may add, modify, or remove features or services from Copilot Labs at any time for any reason.
    We may limit the speed or performance of Copilot as we think necessary.
    When you request that Copilot take Actions on your behalf, you are solely responsible for those Actions and any results or consequences.
    Copilot is for entertainment purposes only. It can make mistakes, and it may not work as intended. Don’t rely on Copilot for important advice. Use Copilot at your own risk.
    WITHOUT LIMITING SECTION 12 OF THE MICROSOFT SERVICES AGREEMENT IN ANY WAY, BUT FOR THE SAKE OF CLARITY, WE DO NOT MAKE ANY WARRANTY OR REPRESENTATION OF ANY KIND ABOUT COPILOT. For example, we can’t promise that any Copilot’s Responses won’t infringe someone else’s rights (like their copyrights, trademarks, or rights of privacy) or defame them. You are solely responsible if you choose to publish or share Copilot’s Responses publicly or with any other person.
    You agree to indemnify us and hold us harmless (including our affiliates, employees and any other agents) from and against any claims, losses, and expenses (including attorneys' fees) arising from or relating to your use of Copilot, including without limitation your use, sharing, or publication of any Prompt, Responses, or Creations, or your breach of these Terms or violation of applicable law.
    You may stop using Copilot at any time. If you want to close your Microsoft Account, please see the Microsoft Services Agreement.
Microsoft's terms and conditions for Copilot say that it's for entertainment only. (source)

Let that sink in a moment. Microsoft is not saying "for work, too" -- Microsoft is saying that it's for fun and games ONLY.

And, of course, this isn't just some random professor saying it. Many mainstream media outlets, including Tom's Hardware, PCMag and The Register have confirmed Microsoft's admission:

Press articles
News articles about MS's Copilot warning.

LLMs are just glorified predictors -- for the easy problems

As remarked upon in The Register's story about Microsoft Azure's stability issues, the rush to replace people with LLMs is revealing negative impacts at both primary and secondary levels. What layoff-happy managers don't realize is that LLMs aren't magical thinking machines. They're just "very good at reproducing patterns" and so even seemingly amazing tasks they perform like finding errors in code or data is by "observing deviations from their probabilistic expectations".

When a student discovers that a chatbot is able to write an essay or Python coding homework solution it's not because the chatbot is smart -- it's because the chatbot assimilated millions and millions of lines of code and text written by humans and posted online. When an office worker tells the Zoom AI assistant to take notes it's only able to do so because it has already been trained on curated meeting minutes. Likewise for all the pie charts and white papers that managers share with each other. These are all mundane, routine tasks. There's nothing novel about them. They're low-hanging fruit, intellectually.

But by routinely outsourcing our cognition to the chatbots we're forgetting that we need to hone those same skills to work on the harder, more challenging -- and rewarding -- tasks that chatbots can't do. The can't do them because they can't be trained on the hardest, most novel problems... because the data simply isn't there for them to be able to suck up into their models.

Universities are supposed to be bastions for thinking -- at all levels. We need to keep the chatbots at bay because we need our students to practice thinking, starting with easy chatbot-able tasks and then working their way up to the problems and concepts that aren't chatbot-able. But it's not just about the students. If university staff and faculty routinely offload their cognition to chatbots then that will permeate down to the student experience, too. We need to set the example, because in higher education an uncritical adoption of AI is unacceptable.

Remediation of digital asbestos

There is no doubt that lots of employees and students are using AI tools here at York. Whether it's AI assistants for recording Zoom meetings or chatbots to answer homework questions and write essays, we're hooked.

I've seen AI referred to as "digital asbestos". Useful, but dangerous. And incredibly hard to remediate.

It's going to take a massive effort to fix this, but it will start with trying to get people to read Microsoft's warning.

Updates

April 5: new section (LLM predictors) added about MS Azure, instability and the difficulties that LLMs have with respect to novelty. Link to Dr. Olivia Guest et al's work and reference to digital asbestos added.


a pen

James Andrew Smith is a Professional Engineer and Associate Professor in the Electrical Engineering and Computer Science Department of York University’s Lassonde School, with degrees in Electrical and Mechanical Engineering from the University of Alberta and McGill University.  Previously a program director in biomedical engineering, his research background spans robotics, locomotion, human birth, music and engineering education. While on sabbatical in 2018-19 with his wife and kids he lived in Strasbourg, France and he taught at the INSA Strasbourg and Hochschule Karlsruhe and wrote about his personal and professional perspectives.  James is a proponent of using social media to advocate for justice, equity, diversity and inclusion as well as evidence-based applications of research in the public sphere. You can find him on Twitter.  You can find him on BlueSky. Originally from Québec City, he now lives in Toronto, Canada.