Who can migrate our servers to Microsoft Azure in Adelaide?
Subnet does. We are based in Forestville, Adelaide, and have been a Microsoft partner since 2001. We assess which workloads belong in Azure, compare running costs with an on-premises option, build the networking and security foundations, and migrate in planned stages.
Does an Azure assessment commit us to migrating?
No. A cloud feasibility engagement can produce an assessment and roadmap without committing you to a migration, and a proof of concept can test specific requirements before any production change is approved. The assessment looks at your applications, workloads, dependencies and constraints, so you can decide what belongs in Azure, what stays where it is, and why. A server and application list, with owners, is a useful start.
Will moving to Azure cause downtime, and how long will it take?
It depends on the workload, the volume of data, your connectivity and how each application behaves, so no single answer applies. For each workload the plan should state the cutover approach, any outage window, testing before go-live and how you would step back if something fails. Timeframes and outage windows are agreed per project during scoping, not assumed in advance.
What is an Azure landing zone, and does every Azure project need a full one?
Microsoft describes an Azure landing zone as an architecture for governing, securing and scaling an Azure environment. It has a platform landing zone for governance, security and shared services such as networking, identity and management, and workload landing zones that run within its guardrails. Microsoft offers accelerators and also describes custom builds. The foundations should match the scope you agree, not a fixed template.
Which Azure regions are in Australia, and does choosing one keep our data in Australia?
Microsoft's regions list shows four: Australia East (New South Wales), Australia Southeast (Victoria), and Australia Central and Australia Central 2 (both Canberra; Central 2 has restricted access). At the time of writing, only Australia East is listed with availability zones; check the current list. Region choice is a configuration decision to agree up front, not a guarantee of data residency or sovereignty. Confirm the region for each service, including backups and replicas.
Who is responsible for what once our servers run in Azure?
Microsoft is responsible for the underlying cloud infrastructure, including physical datacentres, hosts and network. For virtual machines you remain responsible for the operating system and applications, and in every deployment type you keep responsibility for your data, user accounts and access management. Platform services shift more to Microsoft, such as the operating system and runtime. Operating responsibilities should be written into the project scope, so it is clear who looks after what after go-live.
What does an Azure Virtual Desktop project involve beyond building a host pool?
A host pool is only the platform. The work includes reviewing images, applications, user profiles, policy, capacity and the user experience, then testing with a representative pilot group and user acceptance testing before a defined cutover. Who owns each application, how users are moved over, and whether a third-party management platform is involved should all be explicit before work begins.
Can we use our existing Windows Server licences in Azure?
Possibly. Azure Hybrid Benefit lets eligible customers apply existing Windows Server licences, with active Software Assurance or qualifying subscription licences, to Azure virtual machines, so you pay the base compute rate. There are conditions, including minimum core counts and licence terms, and Microsoft reserves the right to audit eligibility. Check your licence agreement and include the result in the cost assumptions for your design.
Is a test failover the same as a full recovery exercise?
No. Microsoft describes a test failover in Azure Site Recovery as a drill that validates your replication and recovery approach, and recommends an isolated test network. It does not prove that applications, users, DNS, identity and third-party services work together. A full business recovery exercise, and a permanent migration, are separate things with their own planning.
What is the difference between Azure Backup and Azure Site Recovery, and do we need both?
Microsoft's Site Recovery overview describes Site Recovery as replicating workloads from a primary site to a secondary location so apps keep running during an outage, and presents Azure Backup as a separate service that keeps your data safe and recoverable. Whether you need one or both depends on your requirements. Which systems are protected, which are tested, and the recovery targets, dependencies, runbooks and owners should be agreed for your scope.