Azure Local, planned for your workloads.
In your facility.
Choose an Azure Local configuration around your applications and facility. We can help define the hardware, connectivity, identity, recovery and operating work in a scoped implementation plan.
Six phases from procurement to production sign-off.
Use these phases to discuss dependencies and acceptance. Timing and deliverables are agreed in the project scope. Select a phase to read its details.
Assess workloads and site readiness, including power, cooling, space and connectivity. Confirm the hardware and procurement plan.
Select a phase to review it. This sequence is illustrative; the agreed scope sets timing, dependencies and acceptance.
What to evaluate before deployment.
Review the selected deployment model, supported integrations and service charges before choosing a configuration.
Management integration
Azure Local uses Azure Arc for management. Confirm supported tools and workflows for the selected deployment model.
Workload fit
Assess application and Kubernetes requirements against the selected platform configuration and support matrix.
Data boundaries
Map application data, backups, diagnostics and support flows. Define what must remain local and how that will be verified.
Identity and access
Define user and service identities, authorization and supported sign-in controls for each management and workload path.
Monitoring and security
Select the monitoring and security services needed, including their coverage, configuration, licensing and operating responsibilities.
Connected or disconnected
Choose the appropriate operating model and verify eligibility, connectivity, update and support requirements before procurement.
Make the requirements explicit.
| Planning question | Scope to confirm |
|---|---|
| What hardware and capacity are needed? | Validate the hardware configuration against the workloads, resilience requirements and supported deployment model. |
| Which services and charges are included? | List platform licensing, additional Azure services, implementation and ongoing operations separately. |
| How will recovery be proved? | Agree backup coverage, restore tests, recovery objectives and the people responsible for execution. |
| When can the environment be accepted? | Set the schedule after site readiness, procurement, dependencies and acceptance criteria are understood. |
Where Azure Local earns its keep.
Healthcare
Map patient-data flows, access, backups, diagnostics and support paths. Hosting location alone does not establish regulatory compliance or contain the full data boundary.
Finance
Review payment-data boundaries, audit logging and residency requirements with your compliance advisers. Deployment location alone does not establish compliance.
Public sector
Confirm procurement, residency and control requirements for the proposed deployment. No authorization for classified workloads or FIPS-validated Ultiblob build is established on this page.
Azure Local, asked + answered.
Azure Local is Microsoft's current distributed infrastructure offering. Review the selected deployment model and supported configuration rather than assuming an older Azure Stack HCI design is interchangeable.
The supported topology depends on the deployment model and hardware solution. Confirm capacity, resilience and current vendor requirements during design.
Confirm the subscription, identity, licensing and agreement requirements for the selected connected or disconnected deployment model before procurement.
Evaluate application, identity, management and update dependencies for an Azure or network outage. Define continuity requirements and test the agreed failure scenarios; this page does not promise uninterrupted operation.
Assess the specific workload, target platform, data-transfer path and migration tooling before planning a move. Compatibility and operating requirements must be validated for the chosen configuration.
Plan your Azure Local rollout.
Discuss your workloads, site readiness and operating requirements. Confirm the assessment deliverables, commercial terms and delivery schedule before committing to a rollout.