Operations | Monitoring | ITSM | DevOps | Cloud

Spring Boot version upgrades—whether moving from 2.x to 3.x, 3.x to 4.x, or even minor bumps like 3.2.5 to 3.3.1—regularly introduce subtle, breaking changes that unit and integration tests miss. JSON serialization shifts, autoconfiguration reordering, and transitive dependency conflicts can silently alter your API contract.

Sovereign cloud conversations usually center on where customer data sits at rest. The provider points at a UK data center, the contract gets signed, and procurement marks the box. For most workloads, that's a defensible position. For GPU workloads, it isn't.

Microsoft 365 Backup, M365 Archive, Purview retention, EOA, and inactive mailbox - what each one actually does, and where third-party archivers fit.

Training a model is a project with an end date. Inference is what happens for the rest of the model's working life. The two workloads share GPUs, frameworks, and a lot of vocabulary, but the infrastructure decisions that make sense during training are usually the wrong ones in production. Teams that treat inference as "training, but smaller" tend to discover the gap somewhere around their first traffic spike.

Audit OneDrive and SharePoint Online sites over their licensed storage quota with PowerShell - useful for MC1310684 remediation and routine storage management.

Org admins can now see each user’s last login directly in Settings > Users, making it easy to spot inactive accounts, manage licenses, and run security reviews without opening a support ticket.

The Shai-Hulud lineage has a new face. On June 1, 2026, security teams independently flagged a fresh supply chain compromise inside the @redhat-cloud-services npm namespace. 32 packages and 96 versions were all republished with a credential-stealing worm. These aren't typosquats. They are the official packages in a trusted scope, pulling somewhere 80,000-117,000 average weekly downloads.

Environment drift persists when teams standardize code but leave infrastructure, data, and access decisions to individual teams and manual setup. Most teams know their environments are not identical. What they underestimate is how quietly the gap widens. A database version is out of sync between production and staging; an environment variable is added manually to one server but never tracked; a cron job runs in production but was never captured in the dev config.

Discover the Megaport MCP Server and how it enables AI-powered, agentic networking through natural language access to network infrastructure. By Miwa Fujii, Community Manager - Terraform and Ryan Tucker, Solutions Architect In the cloud networking era, we’ve moved from manual configurations in the Portal to Infrastructure as Code (IaC), Terraform. But the next frontier isn’t just code, it’s intelligence. We are pleased to announce the release of the Megaport MCP Server (Open Beta).