Your cloud and infrastructure, run by senior engineers.

What we run

• Azure: subscriptions and management groups, landing zone governance, Azure Policy, networking (virtual networks, peering, route tables, private endpoints, VPN and ExpressRoute), monitoring, identity for the platform, and cost.
• Hybrid and servers: Windows Server and Linux, Active Directory, file services, line-of-business servers, patching and lifecycle.
• Virtualisation: VMware, Hyper-V and Azure Local, including hosts, clusters, storage and capacity.
• Networks and firewalls: firewall rules and policy, routing, site-to-site connectivity, VPN, DNS, DHCP and certificates.
• Backup and disaster recovery: backup platforms run, restores tested on a schedule, recovery runbooks kept current, and a recovery plan you've seen work.
• Observability: monitoring that tells you something useful, alerts tuned so they mean something, and a root cause for every critical incident.
• Cost and performance: right-sizing, reservations, waste removed, and a cost review on a set cadence.

Operated as code

Changes we make to your infrastructure are written as infrastructure as code where the platform supports it, reviewed by a second engineer, and stored in a repository in your own tenant.

That gives you three things: every change is visible and reversible, the configuration your environment should have is written down, and if you ever change provider, the environment's definition stays with you.

Repetitive work becomes automation: patch reporting, configuration checks, certificate expiry, capacity trends, cost reports. That's what lets senior engineers look after a large estate without the price climbing with every server.

Engineering capacity, every month

Managed Complete includes engineering capacity for improvement: 10 minutes per user per month, from 6 to 30 hours, used across the quarter. It's for the things that otherwise wait for a proposal:

• Automating a manual task your team does every week
• Fixing a recurring fault properly
• Tidying a firewall rule base or an Azure Policy set
• Building a Power Automate flow or an integration your business asked for
• Hardening a server build
• Getting an employee's AI workflow ready for production

Work is planned at your monthly review. A single piece of work over two days of engineering is quoted as a project, so capacity is always spent on improvement, not swallowed by one big job.

When something breaks

Critical issues are covered after hours by an on-call engineer. Faults that cross network, identity, cloud and application boundaries go straight to a senior engineer, who can see all of them.

Every critical incident ends with a root cause and a permanent fix, captured as code or a runbook so it doesn't come back.

Two ways to buy it

• Managed Complete, per user. Your users, devices, Microsoft 365, security, cloud and infrastructure in one plan, from $259 per user per month ex GST, minimum 15 users. Prices assume a typical number of servers and sites for your user count; larger estates carry a platform fee, quoted with the plan.
• Managed Engineering, for your platform. For organisations that keep their own service desk or MSP for users and want North Ark on the infrastructure only. Scoped by domain (cloud operations, platform and infrastructure, network, backup and resilience, cost, automation), with a written responsibility matrix and a set review cycle. Quoted after a conversation about the domains you'd hand over.

Running versus changing

The managed service runs your infrastructure and improves it in steps. Changing what it is, is a project, quoted as a fixed fee after scoping:

• Azure migration and landing zones
• VMware exit and Azure Local
• Network redesign, firewall replacement, new sites and office moves
• Platform engineering and infrastructure as code at scale
• Server migrations and major upgrades

Projects are delivered by the same engineers who run your environment, so nothing is lost between the build and the running of it.