Internally, we enabled them and just sort of let Microsoft push people towards setting them up (plus WHfB already being in place). For customers, we are frantically trying to get a good plan together to both help them understand what the heck we're talking to them about and how it will need to work in their environments.

Always like seeing other people's suggestions. I haven't actually used Copilot Cowork itself - do all those workflows actually require Cowork? It seems like M365 Copilot's built in tooling should be able to do a lot of it.

What's your source for the DLP policy operationalization statistic? It's absolutely plausible in my experience but I'd love to be able to point to something.

This is one of those places where some vendors are having to finally pass the actual costs of AI inference along to customers, or are at least unwilling to aggressively subsidize them as much as they have been doing. To ever be profitable, they either need a revolutionary shift in the costs of AI inference (massive efficiency increases without capability hits) or they have to get customers so invested in the platforms that they have little choice but to start paying the real costs. Broadly speaking, I don't think Microsoft has as much of a long-term incentive as Google, Anthropic, or OpenAI to keep playing pretend, and that's why they seem to make some of these product choices that seem at odds with others in the market. Claude Cowork is great, but eventually Anthropic is going to be unwilling or unable to keep providing hundreds per month in inference for $20. (Also - that's consumer pricing. If you are doing Team/Enterprise pricing, you are paying for Claude/Cowork at the API usage rates, just like anyone wanting to use M365 Cowork).