AZ-01
Cloud, Microsoft 365 and the workplace
Azure infrastructure design and implementation
Who it's for: an organisation extending its infrastructure into Azure — datacenter extension, recovery site, hosting of applications or of new projects — and wanting to frame the requirement and the cost before committing.
The problem: Azure is billed on consumption, which shifts the risk: there is no longer any visible oversizing at order time, but an invoice that drifts month after month. An Azure infrastructure designed without a requirements study, without a cost model and without governance rules ends up costing more than an on-premises foundation — without its predictability.
What I do
- requirements study: candidate workloads, data volumes, performance, availability and data location requirements
- design of the target architecture: subscriptions, management groups, virtual networks, segmentation and addressing plans
- connectivity to the existing information system: site-to-site VPN, point-to-site VPN, ExpressRoute depending on the context, hybrid name resolution
- sizing of virtual machines, storage and databases, with the choice of families and service tiers
- monthly and annual budget estimate, comparing commitment models — pay-as-you-go, reserved instances, savings plans
- security and identity: Entra ID integration, conditional access, privileged access management, network security groups and firewall
- implementation: deployment of the virtual machines, network, storage and services, using infrastructure as code where the context allows
- backup and recovery: Azure Backup, Site Recovery, or integration with the existing backup platform
- cost governance: tagging, budgets, alerts, monitoring dashboards
- operating documentation and skills transfer
Deliverables
- architecture document with flow diagrams and addressing plan
- sizing study and budget estimate per scenario
- security and governance matrix
- platform deployed and documented
- operating and recovery procedures
- skills transfer session
What changes
you know what your Azure infrastructure will cost before you build it, and you hold the governance rules that keep the invoice from drifting afterwards.
Prerequisites: an Azure subscription or enterprise agreement in place, administrator access to the tenant, command of the existing network addressing and flows, a security contact for exposure decisions.
Quoted on request — reply within 48h