Come To Think of It...

It’s happening. Microsoft is finally pulling the plug on the Outlook Web Access (OWA) Light client in Exchange Server. For the veterans who remember when web-based email was a luxury of low-bandwidth connections and stripped-down interfaces, this is more than just a feature deprecation; it’s the end of an era of functional minimalism. The move is being framed as a way to "streamline" the Exchange experience and push users toward more modern, feature-rich interfaces. But for many sysadmins and users in environments where resource overhead actually matters—or where a simple, no-frills browser interface was the go-to for quick checks—this feels like another step toward the inevitable bloat. Modern OWA is powerful, sure, but it’s heavy. It’s a sprawling web application that demands significantly more client-side resources than the old Light client ever did. The transition isn't just about UI; it's about the underlying shift in how Microsoft views the web client. By retiri...

There is a new vulnerability in Microsoft 365 Copilot Enterprise called SearchLeak, and on its own it is the kind of finding that generates a CVE, a Microsoft blog post, and a few security team ticket updates. But the architecture of the attack tells a bigger story about what happens when prompt injection meets the old bug classes that security teams have been wrestling with for decades. SearchLeak chains three separate weaknesses into a silent data exfiltration pipeline. The first is a parameter-to-prompt injection: the search q parameter in Copilot Enterprise Search passes user input directly into the AI engine, treating it as both a search query and executable instructions. Unlike the regular Copilot chat feature, Enterprise Search is designed to pull from company data — emails, SharePoint files, OneDrive documents — so an injected prompt can surface anything the victim user has access to. The second weakness is an HTML rendering race condition: during Copilot's streaming res...

It’s a subtle but significant admission of defeat from Microsoft. At Build 2026, they didn't just announce a new feature; they announced a surrender to the reality of modern developer workflows. By releasing 'Coreutils for Windows'—built on the Rust-based uutils project—they are effectively admitting that the native Windows command-line experience has been a friction point for far too long. The technical implementation is actually quite clever, if a bit unorthodox. Instead of a massive overhaul of the kernel or even just another layer of WSL, they've bundled the functionality into a single coreutils.exe binary and used NTFS hardlinks to create individual command wrappers like ls.exe , cat.exe , and rm.exe . This gives the illusion of a native toolkit while maintaining a single, maintainable executable. It’s a pragmatic patch for a decade-old problem: the cognitive load of switching between ls and dir , or grep and findstr . While some might see this as just anot...

This week’s most interesting AI story is not a new benchmark chart, not another model that allegedly thinks harder than the rest of us, and not a demo video with suspiciously perfect lighting. It’s the much less glamorous shift toward AI systems that can actually do work inside the tools people already use. Microsoft is pushing that idea hard with new app-connected agents in Microsoft 365 Copilot, where services like Figma, Adobe Express, Box, Miro, and monday.com can surface directly inside the chat experience. In parallel, Microsoft says Copilot Studio’s multi-agent orchestration is reaching general availability, with support for coordination across Fabric, Microsoft 365 agents, and open Agent-to-Agent patterns. Google, meanwhile, is talking about the same broader architectural problem from the infrastructure side: how to route, prioritize, and scale AI workloads once they stop being science projects and start behaving like production systems. That’s the part I find refreshing. The c...