Operations | Monitoring | ITSM | DevOps | Cloud

You can already break down cloud spend by team, product, or customer in Explorer. But AI spend has been harder to decompose. Which models is each team running? What activity is driving the cost growth you saw this month? Before AI Explorer, answering those questions meant exporting raw event data and building your own breakdowns, or waiting days for reconciled billing to land in Explorer.

Enterprises are putting hard ceilings on AI spend. Accenture now centrally funds $29 a month per person for Claude and charges anything above that to a project budget code. Uber used up its 2026 AI budget in four months and restricted access. A cap stops waste and useful work at the same rate. The alternative is seeing AI cost by team, by project and by outcome, then funding what returns. Companies spent the past year telling employees to use more AI. Now a lot of them are putting a lid on it.

Why OneDrive stops syncing a SharePoint library: the 300,000-item limit, invalid names, 400-character paths, 250 GB files, read-only libraries and full storage.

What a SharePoint hub site is, the 2,000 hub limit, how to register one in the admin center, who can associate sites, and how to delete or archive a hub.

When something breaks on a large network, the alerts arrive from every direction. Routers, firewalls, cloud gateways, and applications each report their own symptoms. The evidence that explains the incident is scattered across anomalies, configuration changes, topology, and past incidents, and an engineer has to piece it together by hand. Loom is the correlation and root cause agent in Selector Foundry, the agentic NetOps platform built on Selector’s existing AIOps and Observability platform.

October was about making Scout’s data easier for AI tools to use and easier for your team to trust. Scout is now in Claude’s connector directory, the MCP server got leaner and more careful about what it returns, and Scout Trails opened its beta. Anomaly Detection also became easier to read and better at catching short spikes. Here’s what shipped in October.

Qovery now sends your organization ID as the sts:ExternalId when it assumes the IAM role in your AWS account, and the role's trust policy only accepts it on behalf of your organization. Your role is already updated. If you manage it with the qovery-role-creation CloudFormation stack, update the stack to the latest template. Romain is a staff engineer at Qovery working on the control plane and AI integrations. He writes about distributed systems, incident response, and MCP-based tooling.