Skip to content
North Ark

Transformation Engineering

Modernise and secure the environment, built as code and ready to operate.

North Ark designs and delivers the changes that move an environment forward: platform foundations, migrations, network redesign, identity and security uplift. Everything is built to be run afterwards, by your team or by us.

  • Fixed-fee phases
  • Microsoft Partner
  • AZ-104 and AZ-305 certified engineers
  • Senior engineers only
  • Brisbane-based, working across Australia
Start with an Infrastructure Review
Server rack mid-build with neatly dressed white and blue network cabling.

The work

  • Azure landing zones: management group and subscription design, policy, hub-and-spoke or Virtual WAN networking, identity, logging and guardrails
  • Migration: dependency discovery, wave planning, cutover runbooks, rollback and validation, off VMware and legacy hosting
  • Azure Local and hybrid: cluster design, connectivity to Azure and existing WAN, backup and DR across both
  • Network and connectivity: segmentation, firewall rationalisation, ExpressRoute and VPN, DNS and routing that match how applications behave
  • Identity and endpoint: Entra ID, Conditional Access, privileged access, Intune and Defender rollout
  • Security operations: Sentinel onboarding, analytics and playbooks tied to controls you manage
  • Resilience: DR design, tested failover, restore procedures
  • Automation: Terraform or Bicep, pipelines, policy as code, runbooks
Four stages left to right: Design, Build, Cutover with a rollback path, and Handover.

How delivery works

  1. Design against the Infrastructure Review baseline, with decisions and trade-offs written down before anything is built.
  2. Build in code, peer reviewed, in a repository your team can read. Pre-production proves the pattern before production sees it.
  3. Cut over in waves with a rollback path for each, and validation criteria agreed up front.
  4. Hand over with runbooks, diagrams, monitoring and a working session with the people who will operate it. If that is North Ark, handover is to Managed Engineering.

Where the specific problems are

Azure migration is mostly a dependency problem: identity, DNS, shared services, licensing and network paths decide the waves, not the server list. Our migration page covers that in detail.

Troubleshooting is the other half of the work: faults that cross network, identity, certificate and application boundaries and resist single-team diagnosis.

Questions buyers ask

How are projects priced?

In fixed-fee phases once the scope is clear, usually after a review or assessment. Where discovery is still needed, time and materials with a cap.

Do we need an Infrastructure Review first?

Not always. If the problem is well defined, we can scope a project directly. If it isn't, a review or focused assessment avoids pricing the wrong work.

Who owns what is built?

You do. Code, runbooks and documentation are in a repository in your tenant from the first day.

Can our team work alongside yours?

Yes. Pairing with your engineers is the best way to hand over, and it is built into the plan when you want it.

How do you manage cutover risk?

Every cutover has a tested rollback, an agreed change window and a clear decision point. Changes are made through your change process.

What happens after the project?

Your team runs the result with the runbooks and code, or North Ark operates it under Managed Engineering.

Related

Start a conversation

Build the change properly, then run it.

Tell us about the project you have planned.

Talk to an Engineer