Skip to content

Microsoft Entra External ID Architecture & Tenant Partitioning Specification


1. Executive Summary

This specification defines the multi-tenant architecture and identity partitioning model for the Event Route Optimiser (ERO) platform using Microsoft Entra External ID (CIAM). It establishes tenant boundaries, Application Registration taxonomy, and developer Git authoring standards.


2. Entra External ID Tenant Partitioning Matrix

To ensure total isolation between non-production environments and live attendee production data, identity infrastructure is partitioned across two distinct Entra External ID tenants:

EnvironmentEntra Tenant NameTenant ID / DomainAzure Resource GroupApp Registration NameTarget Audience
Developmentsknxerodevsknxerodev.onmicrosoft.comrg-sknx-ero-developmentero-devWorkstation Dev / Inner Loop Mock
Testsknxerodevsknxerodev.onmicrosoft.comrg-sknx-ero-testero-testAutomated E2E Testing & QA
Supportsknxeroprodsknxeroprod.onmicrosoft.comrg-sknx-ero-supportero-suppInternal Staging / Ops Verification
Productionsknxeroprodsknxeroprod.onmicrosoft.comrg-sknx-ero-productionero-prodLive Festival Attendees

3. Application Registration Naming Rules

All Entra External ID Application Registrations must strictly follow the ero-<env> naming taxonomy:

  • ero-dev: Registered in sknxerodev tenant. Redirect URIs: http://localhost:4321, http://127.0.0.1:4321.
  • ero-test: Registered in sknxerodev tenant. Redirect URIs: https://ero-test.synkronyx.cloud.
  • ero-supp: Registered in sknxeroprod tenant. Redirect URIs: https://ero-supp.synkronyx.cloud.
  • ero-prod: Registered in sknxeroprod tenant. Redirect URIs: https://ero.synkronyx.cloud, https://synkronyx.cloud.

4. Developer Git Authoring & Identity Governance Rules

All repository commits across Archi1 Laptop and Arch2 Desktop must strictly enforce the authorized developer commit identity:

Workstation Configuration Command

bash
git config --global user.name "peter-neil_digx"
git config --global user.email "[email protected]"