Operations | Monitoring | ITSM | DevOps | Cloud

Most disaster recovery plans are designed to survive infrastructure failures — a zone goes down, a region becomes unavailable — but assume the cloud provider itself stays up. That assumption fails more often than engineering teams expect, and when it does, the gap between a team that keeps running and a team writing incident reports isn’t luck: it’s whether DR was an architectural default or a runbook nobody has tested.

Purview retention policies can now archive inactive SharePoint files into Microsoft 365 Archive. What MC1472601 and MC1325441 change, the Copilot indexing trade-off, and what to configure before the rollout reaches your tenant.

Recently, Amazon announced WorkSpaces Applications in-console monitoring. This is a big shift forward for AWS, who is quietly building market share with their Amazon WorkSpaces Applications (previously called Amazon AppStream 2.0) virtual applications offering. This announcement validates that observability matters for Amazon WorkSpaces Applications customers – they need to see what’s going on in their virtual application and desktop fleets, hosts and sessions.

Base44 is fast at the part that used to take a week. Describe an application, and you have a working interface in minutes. Base44's built-in Cloud backend, enabled by default, is a reasonable place to start. But it doesn't put your data in an account you already own, in the cloud and region you picked, next to the rest of your data platform. That's the gap this post closes.

Replay and recap of our live session: an AI agent reads a Heroku Rails app and deploys the full stack to AWS through Qovery from one prompt. Chapters, timestamps, the four ways teams leave Heroku, and the steps a human should still own. Romaric founded Qovery to make Kubernetes accessible to every engineering team. He writes about platform strategy, developer experience, and the future of cloud infrastructure.

Sovereign cloud is a system design problem. It asks where workloads run, where data lives, who can administer the system, which legal authorities can compel access, who controls encryption keys, and where backups, telemetry, and control-plane metadata land. Selecting a region answers only part of that problem.

99.999% availability allows about 5 minutes 15 seconds of downtime per year, or about 26 seconds per month. That budget includes every failed deploy, certificate expiry, DNS misconfiguration, and provider incident in the request path. One regional outage lasting an hour consumes more than 11 years of five-nines budget. This guide explains which architecture tiers can reach that number, which cannot, and why.