# ADR 000001 Azure Primary Cloud GitBook **Date:** May 2026\ **Status:** Accepted\ **Decider:** NikiDigitals\ **Version:** GitBook — Thinking Layer ## The Question Every system needs a home. For LES — a project that will span five years, encompass thirteen modules, and eventually incorporate AI agents, real-time analytics, and enterprise-grade security — the choice of cloud platform is not a tactical decision. It shapes everything that follows: the tools available, the certifications pursued, the career narrative built, and the cost structure managed. Three platforms were considered: Microsoft Azure, Amazon Web Services, and Google Cloud Platform. All three are capable of hosting what LES requires. The decision came down to something more strategic than raw capability. ## The Decision Microsoft Azure is the primary cloud platform for LES. All infrastructure, databases, AI services, identity management, and compute resources are provisioned in Azure by default. Exceptions are permitted only where an alternative platform is demonstrably superior for a specific function — and every exception is documented in its own ADR. ## Why Azure The answer is coherence. LES does not exist in isolation. It is built alongside a career objective — Finance Transformation Architect — and a professional identity — NikiDigitals. Azure is the dominant cloud platform in enterprise finance environments. Building on Azure means every skill developed, every certification earned, and every architectural pattern learned is directly transferable to the organisations this career trajectory leads to. The Microsoft ecosystem compounds this advantage. GitHub for version control, Microsoft 365 for productivity, Power Platform for low-code automation, Azure OpenAI Service for the AI agent layer — these are not separate tools requiring integration overhead. They are a coherent stack that shares identity, security, and data boundaries. There is also a personal data governance dimension. For a system that holds deeply personal data — finance, health, relationships — the ability to specify EU-based data residency, enforce encryption at rest and in transit, and maintain full visibility over who accesses what matters. Azure provides this within a single, auditable boundary. ## What This Means Going Forward Azure is the default answer to every infrastructure question in LES. When something cannot be done well in Azure, or when a specific tool outside the Azure ecosystem is clearly superior for a bounded function, a new ADR documents that exception. The platform choice is not tribal loyalty — it is a reasoned default that will be revisited if the reasoning changes. The certification pathway follows from this decision: AZ-900 through AZ-305, with AI-102 and DP-600 as the intelligence and agent layers mature. Each certification is earned when the relevant phase of LES is being built — not collected in advance. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://nikidigitals.gitbook.io/les/03-architecture/decision-log/phase-0-foundation/adr-000001-azure-primary-cloud-gitbook.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.