For organizations where not everything is going to the cloud, and what stays still has to be run well.
We run and upgrade what stays on-premises, from Windows Server and your hypervisors to storage and the Exchange server you keep for relay. Azure Arc manages it from Azure, alongside the cloud.
Azure Arc brings what stays on-premises under the same management as the cloud. Upgrades replace or move aging servers, hypervisors, and storage. Hybrid identity keeps one sign-in and the Exchange server that stays. Day-to-day running is Monitoring, Patching, and Change, under Managed IT Services.
Azure Arc and hybrid management
Typically 5–8 weeks per server tier
On-premises servers and VMware guests onboarded to Azure Arc, so patching, policy, monitoring, and inventory work the same way for what stays and what moved.
What you get
Arc agents on servers, with the resource bridge for VMware
Azure Update Manager patching in rings, with isolated tiers where needed
Azure Monitor and Policy across on-premises and cloud
Access to Arc objects secured to your tiering model
Training on Arc onboarding and Update Manager
Best for
Servers patched three different ways, and a tiering model that keeps domain controllers on separate tooling.
Windows Server upgraded or rebuilt, virtual machines moved off VMware to Hyper-V, Azure Local, or Nutanix AHV, and file shares migrated with permissions kept.
What you get
Source servers and applications assessed
VMware to Hyper-V, Azure Local, or Nutanix AHV, VM by VM
Windows Server replacement builds
Share migration with a design document and per-share checklist
Drive mapping and ACL updates
Best for
Windows Server 2012 still running, or a VMware renewal you would rather not sign.
Hybrid identity and Exchange
One sign-in across on-premises and cloud through Entra Connect, and the last Exchange server kept on Subscription Edition where applications still relay mail through it.
What you get
Entra Connect design, with one sync source per object
Hybrid-joined workstations with a step-by-step guide
Exchange Server Subscription Edition sized for relay, not mailboxes
Decommission plan for servers that no longer earn their keep
Best for
Applications that still send mail through Exchange, or sign in against the old directory.
A global engineering nonprofit ran its systems from two aging data centers.
Delivered 2020Read more
Questions we get
Do we have to move everything to Azure?
No. Azure Arc and Azure Local let workloads that belong on-premises stay there, under the same management and policy as the cloud. We decide workload by workload, on cost, risk, and dependencies.
We want off VMware. What are the options?
Hyper-V on your existing hosts, Azure Local for a hybrid platform managed from Azure, Nutanix AHV where you already run Nutanix, or Azure itself for workloads that should move. A move to Nutanix AHV can take the file shares to Nutanix Files at the same time. The Assess phase weighs each path for your environment.
What happens to on-premises Exchange?
Mailboxes can move to Exchange Online. A server needs to stay only where applications still relay mail through it, and it should run Exchange Server Subscription Edition, sized for that role. Exchange and Microsoft 365 Migration has the full picture, including what to do about Exchange 2016 and 2019.
Can you manage servers that are out of support?
We can take them on as a project to upgrade or replace, not as steady state. Managed operations assume hardware under OEM support and operating systems Microsoft still patches, and the Assess phase lists what falls outside that.
What sets the scope of a hybrid project?
The number of hosts, clusters, and storage systems, and which hypervisor and storage you run. Whether servers need upgrading, and whether we also run it afterwards, decide the rest.
How long does Azure Arc onboarding take?
It depends on how many servers are in the tier and whether the tier needs isolated tooling. The Azure Arc offering above lists its typical length per server tier, delivered remotely. Servers are patched in the same rings as Monitoring, Patching, and Change, test servers first and identity servers last, and your team is trained at the end.
It starts with a 60-minute call. If we need more to scope it, a short questionnaire follows. Then a written proposal and statement of work. Once you approve, we begin with the Assess phase.
