Azure Consulting in New Zealand

Start with what you already own

Azure's strongest argument for a Microsoft-centred business is not technical. It is that you are probably already paying for a good deal of it.

Before anyone proposes anything, have them check:

• Azure Hybrid Benefit. Windows Server and SQL Server licences with Software Assurance can be applied to Azure virtual machines, which cuts those line items substantially.
• What your Microsoft 365 plan already includes. Higher tiers bundle security and device management tooling that businesses routinely go and buy again.
• Existing agreements. Enterprise Agreements and reseller arrangements change the effective price.
• Azure credits attached to Visual Studio subscriptions, which cover development environments.

A consultant who begins here rather than with an architecture diagram is looking after your money.

Ask for the monthly figure, and its assumptions

The project fee is once. The Azure bill is every month, and over three years it is usually the bigger number.

A serious proposal states the monthly running cost, what it assumes, and what it looks like at twice the volume — with the pricing calculator workings attached.

Check for the lines people forget:

• Non-production environments running around the clock.
• Backups and their retention period.
• Bandwidth out of Azure.
• Managed disks left behind when a virtual machine was deleted.
• Support plan, if you are buying one.

Identity is the decision that outlasts the project

Most Azure migrations are also identity projects, and this is where the real long-term value sits — or the long-term mess.

The questions worth settling:

• Are we keeping on-premises Active Directory and synchronising, or moving to Entra ID properly?
• If we are synchronising, for how long — is there a date, or is this permanent by default?
• Is multi-factor authentication enforced, and for whom?
• Do conditional access policies exist, and does anyone review them?
• What happens to a departing staff member's access, across everything?

A hybrid identity arrangement described as temporary in 2021 and still running is one of the most common things a consultant finds in a New Zealand business. It works, and it doubles the number of places a permission can be wrong.

Know where the data sits, including backups

Microsoft's established regions serving New Zealand are in Australia, with a New Zealand region coming. For most businesses Australia East is the practical default and the latency is unremarkable.

If a customer contract or your own policy requires data to remain in New Zealand, put that in the brief — it changes what is possible and what it costs.

Either way, ask specifically where backups are stored. They are frequently in a different region from the workload, which is good for resilience and matters for a data residency commitment. Get the answer in writing.

Insist on infrastructure as code

An environment assembled through the Azure portal works and cannot be reproduced, reviewed or rebuilt reliably. Nobody can say what changed last Tuesday.

Bicep or Terraform describes the environment in files in a repository you own. That gives you review, repeatability, a genuine disaster recovery position, and the ability to change consultant without starting again.

If it is not in the quote, ask why. The answer tells you how the relationship ends.

A cost review before anything else

If you are already on Azure and the bill has been climbing, buy the review first. It is the highest-return engagement in this category.

What it reliably finds:

• Virtual machines sized for a peak that never comes.
• Development and test environments running overnight and at weekends.
• Disks and snapshots orphaned when something was deleted.
• Reserved Instances or savings plans not taken on workloads unchanged for two years.
• Hybrid Benefit not applied to eligible machines.
• Premium storage on things that do not need it.

Ask for a prioritised list with a dollar saving and an effort estimate against each line, so you can choose what to do. A report without numbers is an opinion.

Lift and shift, then improve

There are two ways to move: pick up the virtual machines as they are, or redesign onto managed services as you go.

The second is better and it is not the right first step. Moving and redesigning at once means that when something breaks, nobody knows which change caused it — and something always breaks.

Move first, stabilise, then improve deliberately: SQL Server to Azure SQL, file servers to SharePoint or Azure Files, scheduled tasks to Functions. Each of those is a project with its own case, and each is easier once the migration is behind you.

A consultant proposing to redesign everything during the cutover is proposing a harder project than you asked for.

Comparing five quotes

Read for:

• Who checked your existing licences and Hybrid Benefit first?
• Who gave a monthly running cost with assumptions?
• Who proposed infrastructure as code and offered you the repository?
• Who asked where data and backups are allowed to sit?
• Who separated the migration from the modernisation?

Describe what you run today, what Microsoft licensing you hold, your current bill if you have one, and any requirement about data location. Consultants who do this work will ask about your licences before they ask about your servers.