# 000001 - Azure Tenant Provisioning **Overview** This entry documents the provisioning of the Microsoft Azure tenant that forms the foundational infrastructure layer of the Life Enterprise System (LES). This was the first technical action taken in Phase 0 of the project and represents the establishment of the cloud environment upon which all subsequent modules, services, and AI systems will be deployed. *** **Decision Rationale — Microsoft Azure** Azure was selected as the primary cloud platform for LES based on four criteria: **Ecosystem alignment.** Microsoft's cloud ecosystem integrates natively with identity management (Microsoft Entra ID), productivity tooling, and enterprise application frameworks — all relevant to the LES architecture. **Certification pathway.** The AZ-900 through AZ-305 certification track provides a structured, industry-recognised learning path aligned with the LES development timeline. **Enterprise credibility.** Azure is the platform of choice for enterprise deployments globally. Building LES on Azure ensures architectural decisions reflect real-world enterprise standards. **AI and agent infrastructure.** Azure AI Foundry and Azure OpenAI Service provide the enterprise-grade AI infrastructure required for the LES multi-agent system planned in Phase 4. *** **Decision Rationale — Primary Region: Germany** The West Europe region (physically located in Germany) was selected as the primary Azure region for LES based on the following criteria: **Latency.** Geographic proximity to the operator's location in Germany and the Netherlands ensures optimal performance for all deployed services. **Regulatory compliance.** West Europe operates under European Union jurisdiction, ensuring full alignment with the General Data Protection Regulation (GDPR) — a non-negotiable requirement for a system processing personal life data across Finance, Health, and Relationship domains. **Service maturity.** West Europe is one of Microsoft's most established regions globally, offering the full Azure service catalogue without feature restrictions. **Disaster recovery pairing.** West Europe pairs natively with North Europe (Ireland) for future redundancy architecture as LES scales. *** **Tenant Configuration — Actions Taken** The following configuration actions were completed immediately upon tenant provisioning, prior to the deployment of any resources: **1. Portal language standardised to English (United Kingdom)** All LES work is conducted in UK English. Portal language was set to English (UK) to ensure consistency between the operational environment and all documentation outputs. **2. Tenant ID recorded** The Azure Tenant ID (GUID format) was retrieved from Microsoft Entra ID and stored securely. This identifier is referenced throughout LES documentation as `[LES-TENANT-ID]` and will be required for security configuration, API integration, and AI agent orchestration. **3. Cost governance implemented** A monthly budget of €10 was established with an alert threshold set at 80% of budget (€8). This governance control ensures notification is triggered before meaningful spend occurs. The budget was named `LES-Monthly-Budget` and configured with a monthly reset period. This action reflects a foundational principle of the LES architecture: **governance is implemented before infrastructure, not after.** *** **Architectural Significance** The provisioning of the Azure tenant establishes the following architectural boundaries for LES: * **Trust boundary** — the tenant defines the outer perimeter of the LES cloud environment. All resources, identities, and data exist within this boundary. * **Identity root** — the Microsoft account used to create the tenant holds Global Administrator privileges. This account is the highest-privilege identity in the LES environment. * **Billing boundary** — all LES Azure costs are consolidated within this single subscription, enabling unified cost management and reporting. * **Compliance boundary** — all data processed within the tenant is subject to West Europe region data residency, maintaining GDPR alignment from day one. *** **Next Steps** The following actions are scheduled following this provisioning session: 1. Begin AZ-900 certification study via Microsoft Learn — foundational cloud literacy required before further infrastructure is deployed 2. Create the first Resource Group — the logical container for LES Phase 0 resources 3. Connect Azure environment to GitHub repository for infrastructure-as-code preparation 4. Publish first LinkedIn article: *"Why I Am Building an ERP for My Life"* *** **References** * Microsoft Azure Free Account: * Microsoft Entra ID Documentation: * Azure Cost Management: * GDPR and Azure Compliance: *** *Document maintained as part of the LES Portfolio — Thinking Layer (GitBook)* *All LES documentation is produced in UK English* --- # 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/02-project-governance/phase-0-foundation/000001-azure-tenant-provisioning.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.