01
Telstra-hosted virtual servers to Microsoft Azure
Moving virtual machines out of a telco's hosting and into Azure. It sounds
like a file copy. It isn't.
You have to know what every server does and who depends on it, deal with
operating systems that were fine on the old platform and aren't supported
on the new one, re-licence Windows correctly, get the network addressing
right so nothing loses sight of anything else, and cut over in a window
short enough that the business doesn't notice on Monday.
The upside of getting there is that you stop paying a fixed price for a
fixed box. You can resize, you can turn things off, and you can back up to
somewhere that isn't the same building.
02
A VPN between the office and Azure
Once the servers live in a data centre owned by Microsoft, the office needs
a private, encrypted road to reach them.
That's what a site-to-cloud VPN is. Without it, you're either exposing
those servers to the open internet, which is how ransomware gets in, or
you're making staff jump through a login process so annoying that someone
finds a way around it.
It also has to stay up. A VPN tunnel that drops twice a day is worse than
no VPN, because people stop trusting the system and start emailing
themselves files.
03
Consolidating everything onto one managed package
Karen calls it a Priority Managed Services Package. The point of it is
simpler than the name.
Instead of a support arrangement here, a backup arrangement there and a
hosting bill from someone else, it all sits under one agreement with one
organisation accountable for it.
That's the bit that turns a migration into an improvement. A better
platform with the same fragmented support around it just relocates the
problem.