There are some solid ideas in the article below, the first ones should be obvious: limit who can create Teams and have an approval process. Without that, you may as well start a pool to guess how many “test” Teams will be created in the first few months.
The surprising part is that someone put the word in a memo. They wrote it down. (Or maybe Copilot wrote it and they didn’t catch it?)
What’s not surprising is that this is the market strategy for an AI tool. Microsoft has a ton of money invested in AI. In many ways, they bet the company on the success of AI generally, and Copilot in particular, and the market just hasn’t developed the way they expected. So, what’s the next step?
As I’ve said many times, Microsoft has invested too much money in AI to let users opt out of using it, even if it does ruin everything Microsoft has been known for.
We can publicly measure the cost of someone using AI against the output of their work. If the user can’t tell the total cost of their AI work, we can create a dashboard of costs and let the workforce judge themselves openly. Since users can’t tell themselves how much compute they’re using, we make it public and make them prove the value.
That seems significant. As someone who works in the legal industry, this is concerning. Some of our clients will not look kindly on us using any third-party tool that can’t provide SOC reports, and I know anyone working with the federal government is looking at that first bullet point about FedRAMP and wondering if they should make sure this isn’t enabled in their environment.
Will that ever be enough revenue to offset the massive investments they’ve made in AI? Time will tell. Right now, these are some early warning signs, but also small enough that I can’t imagine they’ll move the needle one way or the other. I’m not jumping to any conclusions based on them, but I do have my eyes open.
Reposts