New Zealand North is live
Microsoft announced the region open on 12 December 2024; Azure’s infrastructure register lists New Zealand North in Auckland.
Hyperscale cloud · FULL DEEP TRACKER
Microsoft NZ North
A living evidence file separating the launch of Microsoft’s New Zealand cloud region from actual service availability, completed customer migrations, resilience, data-sovereignty outcomes and domestic value capture.
OPERATIONAL · ADOPTION TRACKINGAuckland · New ZealandCONTINUOUSLY MONITOREDUpdated 25 August 2026
REGION STATUSLive
RESILIENCEZones supported
REGION PAIRNone
PUBLIC CAPACITYUndisclosed
WHY IT MATTERS
Strategic significance
NZ North changes the infrastructure available to New Zealand organisations, but opening a region is only the first gate. The material questions are which services and workloads are actually local, how customers configure sovereignty and resilience, how migration commitments convert into production use, and whether the domestic partner and skills economy captures durable value.
CURRENT ASSESSMENT
The region is operational; national outcomes remain an adoption case.
Microsoft opened New Zealand North on 12 December 2024 and Azure’s region register confirms availability-zone support in Auckland. Microsoft offers local storage, processing and backup options, yet the regional product table remains the authoritative service-by-service test. Microsoft does not publicly disclose physical power capacity, capital cost, utilisation or contracted customer load, and New Zealand North has no paired Azure region.
The key question is not whether NZ North exists. It is whether locally available services, completed migrations and zone-resilient architectures create measurable productivity and sovereignty gains without leaving customers dependent on a single in-country cloud region or platform ecosystem.
EVIDENCE GATES
What is confirmed—and what remains open.
Availability-zone support
Azure lists zone support. Zones isolate power, networking and cooling, but are not separate New Zealand regions.
Services are product-specific
Azure maintains a dynamic product-by-region table. Region launch does not mean full parity for every Azure, data or AI service.
Local data residency
Customers can store, process and back up data in New Zealand, but residency depends on service, configuration, keys, logs, support and recovery design.
No second Azure region in New Zealand
Microsoft lists New Zealand North with no paired region. Zone resilience can remain in-country; region-level disaster recovery needs explicit design.
Named customers and partners
Public disclosures mix completed workloads, pilots, staged migrations and future commitments; these are not equivalent measures.
Renewable attributes and air cooling
A ten-year agreement covers renewable attributes from Contact’s 51.4MW Te Huka 3 station; Microsoft also states it uses water-free air cooling. Neither figure discloses regional load.
Capacity, utilisation and investment
No reviewed public source discloses NZ North IT megawatts, total load, capital investment, contracted capacity, utilisation or site-level performance.
CAPACITY RECONCILIATION
Do not treat unlike numbers as equivalent.
Operational status
The region is generally available and supports availability zones; this is not evidence that every customer migration is complete.
Commitment versus production
Spark committed to move a proportion of workloads; Scales planned a transition over time; The Warehouse Group reported roughly one third of applications already on Azure before local opening.
MW and utilisation
The 51.4MW Te Huka 3 figure is generation capacity supporting renewable attributes, not disclosed NZ North electricity demand or IT capacity.
DELIVERY & OPERATING STACK
The layers behind the headline.
Cloud regionOperationalNew Zealand North opened in December 2024 and remains listed in Azure infrastructure.
Zone resilienceSupportedWorkloads must use zonal or zone-redundant designs where supported; resilience is not automatic for every resource.
Regional recoveryNo NZ pairCustomers must distinguish continuity across zones from recovery in a separate Azure region.
Product catalogueDynamicAvailability and preview status vary by service; the official regional table is the live control source.
Data residencyConfigurableLocal infrastructure enables in-country processing, but sovereignty depends on architecture, governance and service-specific data flows.
Enterprise migrationStagedWarehouse, Spark, Scales and others signal adoption; announcements do not prove full migration or NZ North-only operation.
Partner ecosystemCCL · Spark · LAB³Migration, hybrid-cloud and skills partners form the local value chain; delivered work should be measured.
Electricity and cooling10-year attributes · air cooledTe Huka 3 renewable attributes and water-free cooling are disclosed; regional power draw and efficiency are not.
VERIFIED TIMELINE
Key milestones and status changes
- May 2020Microsoft announces plans for its first New Zealand datacentre region; Fonterra is later named the first major customer commitment.
- Dec 2023AvePoint is announced as the first global independent software vendor for the planned region.
- Jun 2024CCL becomes the first at-scale launch migration partner; Scales is identified as a first mover transitioning over time.
- Sep 2024Veeam announces local availability plans for backup services using the region.
- Nov 2024The Warehouse Group reports a multi-year migration, with about one third of applications already on Azure before local opening.
- 12 Dec 2024Microsoft opens New Zealand North and discloses the Contact agreement, water-free cooling and a target to train 100,000 people by 2027.
- 20 Feb 2025Spark and Microsoft announce a major Azure agreement, 2,500 Copilot seats and a commitment to move a proportion of workloads.
- CurrentAzure lists New Zealand North with availability-zone support and no paired region; services vary by product.
STAKEHOLDER MAP
Who shapes the outcome
- Microsoft New Zealand and global Azure operations
- Contact Energy and Te Huka 3
- Spark, CCL, LAB³ and migration partners
- Fonterra, The Warehouse Group, Scales, Te Tumu Paeroa and other customers
- Government agencies, regulated sectors and the Government Chief Digital Officer
- AvePoint, Veeam and other software vendors
- New Zealand cloud, security, data and AI workforce
- Communities near datacentre, grid and connectivity infrastructure
DEPENDENCIES
What must align
- Service-specific availability in New Zealand North
- Customer application modernisation and migration economics
- Zone-aware design and an explicit regional disaster-recovery strategy
- Cloud, cybersecurity, data and AI specialist capacity
- Reliable grid supply, fibre diversity and international connectivity
- Privacy, security and sovereignty assurance
- Portability and exit planning
- Outcome measurement beyond vendor announcements
RISKS & OPEN QUESTIONS
What is not yet resolved
- One in-country Azure region provides zone resilience but no separate New Zealand Azure region pair
- Local data residency can be overstated as complete sovereignty without service-level controls
- Announcements often describe intent, pilots or partial migrations rather than completed production adoption
- Physical capacity, power demand, utilisation, investment and site performance remain undisclosed
- Cloud concentration can increase switching costs and platform dependency
- Renewable-attribute matching is not hourly physical consumption or marginal grid impact
- The NZ$76 billion by 2038 figure is a forecast for broad generative-AI adoption, not realised value attributable to NZ North
- Not every Azure or AI service has identical regional availability or resilience
CORE EVIDENCE REGISTER
Primary and supporting sources
01Microsoft: New Zealand North opens↗02Azure global regions register↗03Azure product availability by region↗04Azure availability zones overview↗05Azure region pairs↗06Microsoft: The Warehouse Group migration↗07Microsoft: CCL launch partnership↗08Microsoft and Spark partnership↗09Microsoft: Fonterra commitment↗10Microsoft: AvePoint ISV↗11Microsoft: Veeam local data residency↗12Microsoft NZ government cloud guidance↗