Everyone's Cloud Migration Just Got a Deadline
Distributed teams are rushing to cloud infrastructure and remote-friendly CI/CD as office access disappears.
Six weeks into working from kitchen tables and spare bedrooms, a pattern has become impossible to ignore: teams that already lived in the cloud are shipping like normal, and teams that didn’t are scrambling to get there. This isn’t a controlled migration with a project plan and a rollback window. It’s happening because the office server room is locked, the badge doesn’t work from home, and the release still has to go out Friday.
The obvious casualty is anything that depended on physical proximity to infrastructure — build machines under someone’s desk, deploy scripts that only run from a specific office network, staging environments reachable only over an internal VPN appliance nobody provisioned enough licenses for. All of that is either being replaced this month or causing daily pain for whoever’s stuck maintaining it.
CI/CD as the forcing function
Continuous integration and deployment pipelines are turning out to be the clearest lens on who was already prepared. If your builds and deploys ran through a hosted service before all this started, the transition to remote work barely touched your workflow — commit, pipeline runs, tests pass, ship. If your pipeline lived on physical hardware in an office, you’re now dealing with two problems at once: getting people working remotely, and rebuilding your delivery pipeline in the cloud under time pressure.
GitHub Actions has been picking up a lot of this traffic, helped by its recent Azure-focused workflow integrations that make it easier to build and deploy straight into Azure resources without hand-rolling deployment scripts. For teams that were already on GitHub for source control, that’s a meaningfully lower-friction path than standing up a separate CI product and wiring credentials across two vendors. I’d expect other CI providers to keep pushing similar cloud-native integrations over the next few months — this is clearly where the demand is.
Not just CI — the whole toolchain
It’s not only pipelines. Collaborative tooling generally is getting a forced upgrade: teams that resisted moving code review, documentation, and planning into cloud-hosted tools are finding that “we’ll just walk over and ask” doesn’t work anymore. Everything has to be legible to someone who isn’t in the room, which usually means it has to live somewhere everyone can reach over the internet, with permissions that don’t assume a shared office network.
The interesting question is how much of this sticks. Some of it is obviously pandemic-specific improvisation that will unwind once offices reopen. But cloud-hosted CI/CD and remote-accessible dev tooling aren’t really pandemic-specific — they’re just good practice that a lot of teams had been putting off. My guess is the migrations happening right now under duress don’t get reversed later; nobody’s going to voluntarily move their build pipeline back onto a machine in a closet once it’s been running fine in the cloud for a few months. The circumstances are miserable, but the infrastructure decisions being made under them look like the right ones anyway.