Skip to content

Solutions

Azure infrastructure

Subnet assesses, builds and manages Microsoft Azure infrastructure for South Australian organisations, moving the workloads that belong in the cloud and saying so when they do not.

45+

Azure projects

100+

migration projects

Since 2001

a Microsoft partner

WHAT WE DELIVER

The right workloads in Azure, built on sound foundations

These are the parts Subnet delivers, and the technology we use for each.

Assess

Cloud assessment

A review of applications, dependencies and costs that shows what should move, what should stay and what it will cost to run.

What it solves

  • Servers due for replacement
  • Cloud quotes that are hard to compare
  • Fear of bill shock

How Subnet works with it

We model running costs against a like-for-like on-premises option.

Foundations

Networking, identity and security

The landing zone: virtual networks, connectivity to your sites, identity, and firewalls in Azure.

What it solves

  • Cloud resources built without a plan
  • Weak separation between systems
  • Sites that cannot reach cloud services reliably

How Subnet works with it

We build the foundations first, including FortiGate firewalls in Azure where needed.

Desktops

Azure Virtual Desktop

Desktops and applications delivered from Azure to any device, replacing remote desktop servers.

What it solves

  • Ageing remote desktop servers
  • Applications that only work in the office
  • Slow sessions for remote staff

How Subnet works with it

We build and test images with real users and manage capacity to control cost.

Veeam resilience diagram covering immutability, off-site diversity and recoverability

Recovery

Backup and disaster recovery

Backups and recovery sites in Azure, designed to agreed recovery times and tested.

What it solves

  • No second site for recovery
  • Recovery plans never tested
  • Backups kept in one place

How Subnet works with it

We design to agreed recovery times and run a test failover.

WORK WITH SUBNET

How an Azure project runs

1. Assess

We review workloads, dependencies and costs.

2. Design

The target design and migration order are agreed at a fixed price.

3. Deploy

Foundations are built, then workloads move in stages.

4. Manage

Cost, security and backups are monitored.

5. Review

Spend and sizing are reviewed regularly.

WORK WE HAVE COMPLETED

Azure infrastructure work by sector

Professional services

A full Azure migration, followed by a move to Azure Virtual Desktop with Intune device management.

Retail and distribution

Migration from a third-party hosting provider into Azure, with file shares moved to Azure Files.

Construction

FortiGate firewalls in Azure with professional services, and Microsoft 365 licensing across offices.

CONNECTED EXPERTISE

FIND THE NEXT PART OF YOUR PLAN.

PROJECT DELIVERY

TURN THE REQUIREMENT INTO A DEFINED SCOPE.

Capabilities, licences, prerequisites and service responsibilities are agreed for your environment.

YOUR QUESTIONS

A LITTLE MORE CLARITY.

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.

BEFORE WE TALK

A useful starting point.

You do not need a finished technical brief. Start with the outcome, what you know today and the questions you need answered.

  • What outcome matters to your organisation?
  • Which users, applications, systems and risks are involved?
  • What would a practical first step look like?
Discuss these priorities

LET’S TALK

WHAT WOULD YOU LIKE TO DO NEXT?

Tell us about your organisation and what you need. Start a conversation, discuss a project or request a meeting.

Prefer to talk?(08) 7127 9400Already a customer and need help? Go to Support.
PROPOSED FORM · PRIVATE PREVIEW ONLY

Preview only. Nothing is sent, stored or booked.

A live version will need final routing, consent and privacy review. Subnet privacy policy

Contact us