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.
Most are just trying to get through the overwhelming amount of work they need to do. Learning a new tool isn’t on their radar unless it can help them get that work done right this very moment. Meanwhile, we’ve got a bunch of IT leaders spending a ton of time learning these tools or testing the compliance issues involved in using them, which we should do. How much is enough, though? How much time do we dedicate to tools that are going to be used by less than 10% of the workforce?
The first question was always a little trickier, and though Tony’s method would work, there is still a trick to it; you have to take the snapshots occasionally. You still can’t look back over a long period and see who was in a Teams channel at a given time unless you’re thinking ahead and taking snapshots.
You’re often flying blind when someone leaves the organization and leaves Loop Workspaces behind, because I can take ownership, but I couldn’t review the content. Now, I can review the content and share it with a new owner as necessary.
This should help many of us govern Loop Workspaces much, much more effectively.
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?
When I saw the headline, I immediately thought about how Business Copilot uses a number of Compliance rules that would make that data available to employers. Employers should not be trusted with that. So, good for Microsoft for remembering that before they pushed out this new agent.
You may read that and think that means your employer can see every prompt you enter in Copilot. To some extent, that is true; in the same way, they can see every email message or Teams chat you type with your work account. It is a work account after all. The key piece missing from that simple statement is that it’s not easy to do, and, by design, there are usually very few people who can collect and review that data. Usually, the effort required to do that isn’t worth it. So, if it has happened to you, it’s likely because someone or something has raised a suspicion that warranted an investigation. Most users never reach this level of scrutiny.
I do appreciate that the water between the two tools is less muddy. It’s still not clear. There is still confusion among the average users, but it’s a little less murky. That’s a good thing.
How many organizations have a tenant and have simply left a lot of the default settings from when they bought their first licenses? What would that look like now?
