fix: align naming standards with IIC example company

- Replace all ral site code examples with nyc (IIC primary site)
- Replace RAL/ATL secondary site examples with sea (Seattle)
- Replace Azure Local Cloud org in subscription examples with iic
- Update MG display name examples to Infinite Improbability Corp
- Fix corrupted 'Azure Local Cloudnology' text on line 31
- Update witness resources (stwitnessnyceus01, fswit-nyc-01)
- Fix service principal patterns to use org_prefix instead of customer
- Update VPN, IP allocation, VM mapping tables to nyc site code
- Update code examples (PowerShell, Terraform, ARM) to nyc-dc-01
- Add cross-reference from standards/naming.mdx to planning doc
- Variable reference table updated: nyc, sea, iic site codes

Author: Kristopher Turner

docs/planning/01-naming-standards.mdx

@@ -28,7 +28,7 @@ During discovery sessions and environment design, these standards serve as **sug
 - **Microsoft Cloud Adoption Framework (CAF)** - Industry-proven Azure naming patterns
 - **Microsoft Well-Architected Framework (WAF)** - Operational excellence and reliability principles
 - **Azure Best Practices** - Microsoft-recommended resource naming conventions
-- **Azure Local Cloud Azure Local Cloudnology Standards** - Internal consistency and automation enablement
+- **Azure Local Cloud Technology Standards** - Internal consistency and automation enablement
 
 :::warning Existing Standards Take Precedence
 **These naming standards are recommendations, not mandates.** If your organization has established naming conventions, identity standards, or organizational requirements, those must be followed. Use this document as a reference during discovery to understand existing standards, identify gaps or conflicts, and propose alternatives only when existing standards cause technical limitations (e.g., exceeding character limits).
@@ -100,8 +100,8 @@ This section covers all physical and on-premises resources deployed at each site
 **Pattern**: `<site>-<cluster#>-N<node#>` (⚠️ Strict 15-char NetBIOS limit for Active Directory)
 
 **Examples**:
-- Node 1: `ral-01-n01`
-- Node 2: `ral-01-n02`
+- Node 1: `nyc-01-n01`
+- Node 2: `nyc-01-n02`
 
 :::warning NetBIOS Limit
 Azure Local nodes must be domain-joined and follow the 15-character NetBIOS limit for Active Directory computer objects. The simplified N pattern provides maximum flexibility for site codes while maintaining clear identification as cluster nodes.
@@ -112,7 +112,7 @@ Azure Local nodes must be domain-joined and follow the 15-character NetBIOS limi
 **Pattern**: `<site>-clus<nn>` (⚠️ Strict 15-char NetBIOS limit for CNO)
 
 **Examples**:
-- Cluster 1: `ral-clus01`
+- Cluster 1: `nyc-clus01`
 
 :::warning Cluster Name Object (CNO) Limit
 Windows Server Failover Cluster Name Object (CNO) is limited to 15 characters due to Active Directory NetBIOS requirements. The cluster name must be unique in the Active Directory domain.
@@ -123,10 +123,10 @@ Windows Server Failover Cluster Name Object (CNO) is limited to 15 characters du
 **Pattern**: `<site>-<type>-<nn>` (⚠️ 15-char limit for domain-joined servers)
 
 **Examples**:
-- Domain Controllers: `ral-dc-01`, `ral-dc-02` (9 chars)
-- Certificate Authority: `ral-ca-01` (9 chars)
-- WAC Gateway: `ral-wac-01` (10 chars)
-- Tools/Jumpbox Server: `ral-tools` (9 chars)
+- Domain Controllers: `nyc-dc-01`, `nyc-dc-02` (9 chars)
+- Certificate Authority: `nyc-ca-01` (9 chars)
+- WAC Gateway: `nyc-wac-01` (10 chars)
+- Tools/Jumpbox Server: `nyc-tools` (9 chars)
 
 **Variable Mapping**:
 ```yaml
@@ -287,10 +287,10 @@ VM images are stored in the Azure Local cluster gallery and used for VM provisio
 **Pattern**: `<node>-i`
 
 **Examples**:
-- `ral-01-n01-i` (Node 1 iDRAC)
-- `ral-01-n02-i` (Node 2 iDRAC)
-- `ral-01-n03-i` (Node 3 iDRAC)
-- `ral-01-n04-i` (Node 4 iDRAC)
+- `nyc-01-n01-i` (Node 1 iDRAC)
+- `nyc-01-n02-i` (Node 2 iDRAC)
+- `nyc-01-n03-i` (Node 3 iDRAC)
+- `nyc-01-n04-i` (Node 4 iDRAC)
 
 **Variable Mapping**:
 ```yaml
@@ -307,9 +307,9 @@ The `-i` suffix indicates the iDRAC/BMC interface for out-of-band management. Th
 **Pattern**: `<site>-sw-<##>`
 
 **Examples**:
-- `ral-sw-01` (Rack switch 1)
-- `ral-sw-02` (Rack switch 2)
-- `ATL-sw-01` (Atlanta site switch 1)
+- `nyc-sw-01` (Rack switch 1)
+- `nyc-sw-02` (Rack switch 2)
+- `sea-sw-01` (Seattle site switch 1)
 
 **Variable Mapping**:
 ```yaml
@@ -322,9 +322,9 @@ network_devices:
 **Pattern**: `<site>-fw-<##>`
 
 **Examples**:
-- `RAL-fw-01` (Primary firewall)
-- `RAL-fw-02` (Secondary firewall)
-- `ATL-fw-01` (Atlanta site firewall)
+- `nyc-fw-01` (Primary firewall)
+- `nyc-fw-02` (Secondary firewall)
+- `sea-fw-01` (Seattle site firewall)
 
 **Variable Mapping**:
 ```yaml
@@ -337,9 +337,9 @@ network_devices:
 **Pattern**: `<site>-og-<##>`
 
 **Examples**:
-- `RAL-og-01` (Opengear console server 1)
-- `RAL-og-02` (Opengear console server 2)
-- `ATL-og-01` (Atlanta site Opengear)
+- `nyc-og-01` (Opengear console server 1)
+- `nyc-og-02` (Opengear console server 2)
+- `sea-og-01` (Seattle site Opengear)
 
 **Variable Mapping**:
 ```yaml
@@ -352,10 +352,10 @@ network_devices:
 **Pattern**: `<site>-pdu-<##>`
 
 **Examples**:
-- `RAL-pdu-01` (PDU 1)
-- `RAL-pdu-02` (PDU 2)
-- `RAL-pdu-03` (PDU 3)
-- `RAL-pdu-04` (PDU 4)
+- `nyc-pdu-01` (PDU 1)
+- `nyc-pdu-02` (PDU 2)
+- `nyc-pdu-03` (PDU 3)
+- `nyc-pdu-04` (PDU 4)
 
 **Variable Mapping**:
 ```yaml
@@ -411,15 +411,15 @@ The `{prefix}` is whatever the organization chooses — there is no universal de
 **Pattern**: `{Organization} {Purpose}` or `{Tenant} {Purpose}`
 
 **Display Name Examples**:
-- `Azure Local Cloud Root`
-- `Azure Local Cloud Platform`
-- `Azure Local Cloud Platform - Identity`
-- `Azure Local Cloud Platform - Security`
-- `Azure Local Cloud Platform - Connectivity`
-- `Azure Local Cloud Platform - Management`
-- `Azure Local Cloud Landing Zones`
-- `Azure Local Cloud Sandbox`
-- `Azure Local Cloud Decommissioned`
+- `Infinite Improbability Corp Root`
+- `Infinite Improbability Corp Platform`
+- `Infinite Improbability Corp Platform - Identity`
+- `Infinite Improbability Corp Platform - Security`
+- `Infinite Improbability Corp Platform - Connectivity`
+- `Infinite Improbability Corp Platform - Management`
+- `Infinite Improbability Corp Landing Zones`
+- `Infinite Improbability Corp Sandbox`
+- `Infinite Improbability Corp Decommissioned`
 
 ---
 
@@ -434,15 +434,15 @@ For smaller deployments that don't require full Azure Landing Zone governance. O
 ```text
 Tenant Root Group
 └── {prefix}-{tenant}-root (e.g., iic-prod-root)
- └── sub-{org}-azurelocal-{site} (e.g., sub-iic-azurelocal-ral)
+ └── sub-{org}-azurelocal-{site} (e.g., sub-iic-azurelocal-nyc)
 ```
 
 **Deployment Example** (Org: `iic`, Tenant: `prod`):
 
 | **Resource** | **ID / Name** | **Display Name** |
 |-------------|---------------|-------------------|
 | Management Group | `iic-prod-root` | `Infinite Improbability Corp Root` |
-| Subscription | `sub-iic-azurelocal-ral` | — |
+| Subscription | `sub-iic-azurelocal-nyc` | — |
 
 :::tip When to Use Model A
 - Organization has a single Azure Local cluster
@@ -569,46 +569,46 @@ Subscriptions organize Azure resources for billing, governance, and access contr
 
 | **Purpose** | **Pattern** | **Example** | **Variable** |
 |-------------|-------------|-------------|--------------|
-| Bootstrap | `sub-<org>-bootstrap` | `sub-Azure Local Cloud-bootstrap` | `sub_bootstrap_name` |
-| Connectivity | `sub-<org>-connectivity` | `sub-Azure Local Cloud-connectivity` | `sub_connectivity_name` |
-| Management | `sub-<org>-management` | `sub-Azure Local Cloud-management` | `sub_management_name` |
-| Security | `sub-<org>-security` | `sub-Azure Local Cloud-security` | `sub_security_name` |
-| Identity | `sub-<org>-identity` | `sub-Azure Local Cloud-identity` | `sub_identity_name` |
-| Azure Local | `sub-<org>-azurelocal-<site>` | `sub-Azure Local Cloud-azurelocal-ral` | `sub_azure_local_name` |
-| Workloads | `sub-<org>-workloads-<env>` | `sub-Azure Local Cloud-workloads-prod` | `sub_workloads_name` |
+| Bootstrap | `sub-<org>-bootstrap` | `sub-iic-bootstrap` | `sub_bootstrap_name` |
+| Connectivity | `sub-<org>-connectivity` | `sub-iic-connectivity` | `sub_connectivity_name` |
+| Management | `sub-<org>-management` | `sub-iic-management` | `sub_management_name` |
+| Security | `sub-<org>-security` | `sub-iic-security` | `sub_security_name` |
+| Identity | `sub-<org>-identity` | `sub-iic-identity` | `sub_identity_name` |
+| Azure Local | `sub-<org>-azurelocal-<site>` | `sub-iic-azurelocal-nyc` | `sub_azure_local_name` |
+| Workloads | `sub-<org>-workloads-<env>` | `sub-iic-workloads-prod` | `sub_workloads_name` |
 
 **Variable Mapping** (from `config/variables.yml`):
 ```yaml
 subscriptions:
  sub_bootstrap_id: "00000000-1111-2222-3333-444444444444"
- sub_bootstrap_name: "sub-Azure Local Cloud-bootstrap"
+ sub_bootstrap_name: "sub-iic-bootstrap"
  sub_connectivity_id: "12345678-1234-1234-1234-123456789015"
- sub_connectivity_name: "sub-Azure Local Cloud-connectivity"
+ sub_connectivity_name: "sub-iic-connectivity"
  sub_management_id: "12345678-1234-1234-1234-123456789016"
  sub_security_id: "12345678-1234-1234-1234-123456789017"
- sub_security_name: "sub-Azure Local Cloud-security"
+ sub_security_name: "sub-iic-security"
  sub_identity_id: "12345678-1234-1234-1234-123456789018"
- sub_identity_name: "sub-Azure Local Cloud-identity"
+ sub_identity_name: "sub-iic-identity"
  sub_azure_local_id: "00000000-1111-2222-3333-444444444444"
- sub_azure_local_name: "sub-Azure Local Cloud-azurelocal-ral"
+ sub_azure_local_name: "sub-iic-azurelocal-nyc"
  sub_workloads_id: "12345678-1234-1234-1234-123456789019"
- sub_workloads_name: "sub-Azure Local Cloud-workloads-prod"
+ sub_workloads_name: "sub-iic-workloads-prod"
 ```
 
 **CAF Enterprise-Scale Subscription Alignment**:
 
 | **Landing Zone** | **Subscription Purpose** | **Example Name** |
 |------------------|--------------------------|------------------|
-| Platform - Management | Monitoring, Log Analytics, Automation | `sub-Azure Local Cloud-management` |
-| Platform - Connectivity | Hub networking, VPN, ExpressRoute | `sub-Azure Local Cloud-connectivity` |
-| Platform - Identity | Domain Controllers, Entra ID Connect | `sub-Azure Local Cloud-identity` |
-| Platform - Security | Defender, Sentinel, Key Vaults | `sub-Azure Local Cloud-security` |
-| Landing Zones - Corp | Azure Local clusters, internal workloads | `sub-Azure Local Cloud-azurelocal-ral` |
-| Landing Zones - Online | Internet-facing workloads | `sub-Azure Local Cloud-workloads-prod` |
+| Platform - Management | Monitoring, Log Analytics, Automation | `sub-iic-management` |
+| Platform - Connectivity | Hub networking, VPN, ExpressRoute | `sub-iic-connectivity` |
+| Platform - Identity | Domain Controllers, Entra ID Connect | `sub-iic-identity` |
+| Platform - Security | Defender, Sentinel, Key Vaults | `sub-iic-security` |
+| Landing Zones - Corp | Azure Local clusters, internal workloads | `sub-iic-azurelocal-nyc` |
+| Landing Zones - Online | Internet-facing workloads | `sub-iic-workloads-prod` |
 
 :::tip Subscription Strategy
 - **Dedicated Azure Local Subscription**: Each Azure Local cluster site should have its own subscription for clear billing, governance, and RBAC boundaries
-- **Site Code in Name**: Include site code (e.g., `ral`, `atl`) for multi-site deployments
+- **Site Code in Name**: Include site code (e.g., `nyc`, `sea`) for multi-site deployments
 - **Environment Separation**: Production and non-production workloads in separate subscriptions
 :::
 
@@ -693,8 +693,8 @@ VPN Gateways provide site-to-site (S2S) VPN connectivity between Azure and on-pr
 | **Resource Type** | **CAF Pattern** | **Example** |
 |-------------------|-----------------|-------------|
 | Virtual Network Gateway | `vgw-<workload>-<environment>-<region>-<instance>` | `vgw-azlocal-prod-eus-001` |
-| Local Network Gateway | `lgw-<site>-<environment>-<region>` | `lgw-ral-prod-eus` |
-| VPN Connection | `vcn-<source>-to-<destination>-<environment>` | `vcn-azure-to-ral-prod` |
+| Local Network Gateway | `lgw-<site>-<environment>-<region>` | `lgw-nyc-prod-eus` |
+| VPN Connection | `vcn-<source>-to-<destination>-<environment>` | `vcn-azure-to-nyc-prod` |
 | Public IP (VPN) | `pip-vgw-<environment>-<instance>` | `pip-vgw-prod-001` |
 
 **Variable Mapping**:
@@ -903,16 +903,16 @@ vlans:
 
 | **Device/Service** | **Hostname** | **IP Pattern** | **Variable** |
 | ------------------ | ------------- | --------------------- | ---------------------- |
-| Cluster IP | ral-clus01 | mgmt_network.10 | cluster_ip |
-| Node 1 | ral-01-n01 | mgmt_network.11 | node_01_ip |
-| Node 2 | ral-01-n02 | mgmt_network.12 | node_02_ip |
-| Node 3 | ral-01-n03 | mgmt_network.13 | node_03_ip |
-| Node 4 | ral-01-n04 | mgmt_network.14 | node_04_ip |
+| Cluster IP | nyc-clus01 | mgmt_network.10 | cluster_ip |
+| Node 1 | nyc-01-n01 | mgmt_network.11 | node_01_ip |
+| Node 2 | nyc-01-n02 | mgmt_network.12 | node_02_ip |
+| Node 3 | nyc-01-n03 | mgmt_network.13 | node_03_ip |
+| Node 4 | nyc-01-n04 | mgmt_network.14 | node_04_ip |
 | Reserved | - | mgmt_network.15-20 | (Future expansion) |
-| iDRAC Node 1 | ral-01-n01-i | oob_network.11 | node_01_idrac_ip |
-| iDRAC Node 2 | ral-01-n02-i | oob_network.12 | node_02_idrac_ip |
-| iDRAC Node 3 | ral-01-n03-i | oob_network.13 | node_03_idrac_ip |
-| iDRAC Node 4 | ral-01-n04-i | oob_network.14 | node_04_idrac_ip |
+| iDRAC Node 1 | nyc-01-n01-i | oob_network.11 | node_01_idrac_ip |
+| iDRAC Node 2 | nyc-01-n02-i | oob_network.12 | node_02_idrac_ip |
+| iDRAC Node 3 | nyc-01-n03-i | oob_network.13 | node_03_idrac_ip |
+| iDRAC Node 4 | nyc-01-n04-i | oob_network.14 | node_04_idrac_ip |
 
 ### 2.3 Compute
 
@@ -944,25 +944,25 @@ Every VM deployment must set **both** the Azure resource name and the OS hostnam
 **Pattern**: `<site>-<role>-<nn>` (⚠️ **15-character NetBIOS limit** for domain-joined Windows machines)
 
 **Examples**:
-- `ral-dc-01` (9 chars)
-- `ral-wac-01` (10 chars)
-- `ral-jmp-01` (10 chars)
-- `ral-tools` (9 chars)
+- `nyc-dc-01` (9 chars)
+- `nyc-wac-01` (10 chars)
+- `nyc-jmp-01` (10 chars)
+- `nyc-tools` (9 chars)
 
 ##### VM Name Mapping Table
 
 The following table shows how Azure resource names map to Windows hostnames for common VM roles:
 
 | **Role** | **Azure Resource Name** | **Hostname (≤15 chars)** | **Chars** |
 |----------|------------------------|--------------------------|-----------|
-| Domain Controller 1 | `vm-azlocal-prod-eus-dc-01` | `ral-dc-01` | 9 |
-| Domain Controller 2 | `vm-azlocal-prod-eus-dc-02` | `ral-dc-02` | 9 |
-| Certificate Authority | `vm-azlocal-prod-eus-ca-01` | `ral-ca-01` | 9 |
-| Windows Admin Center | `vm-azlocal-prod-eus-wac-01` | `ral-wac-01` | 10 |
-| Jumpbox / Tools | `vm-azlocal-prod-eus-jmp-01` | `ral-jmp-01` | 10 |
-| backup server | `vm-azlocal-prod-eus-Azure Backup-01` | `ral-Azure Backup-01` | 11 |
-| Utility Server | `vm-azlocal-prod-eus-util-01` | `ral-util-01` | 11 |
-| NDM Server | `vm-azlocal-prod-eus-ndm-01` | `ral-ndm-01` | 10 |
+| Domain Controller 1 | `vm-azlocal-prod-eus-dc-01` | `nyc-dc-01` | 9 |
+| Domain Controller 2 | `vm-azlocal-prod-eus-dc-02` | `nyc-dc-02` | 9 |
+| Certificate Authority | `vm-azlocal-prod-eus-ca-01` | `nyc-ca-01` | 9 |
+| Windows Admin Center | `vm-azlocal-prod-eus-wac-01` | `nyc-wac-01` | 10 |
+| Jumpbox / Tools | `vm-azlocal-prod-eus-jmp-01` | `nyc-jmp-01` | 10 |
+| backup server | `vm-azlocal-prod-eus-Azure Backup-01` | `nyc-bkup-01` | 11 |
+| Utility Server | `vm-azlocal-prod-eus-util-01` | `nyc-util-01` | 11 |
+| NDM Server | `vm-azlocal-prod-eus-ndm-01` | `nyc-ndm-01` | 10 |
 
 ##### VM Scale Sets (VMSS)
 
@@ -983,14 +983,14 @@ Always configure both names during VM deployment:
 ```powershell
 New-AzVM -ResourceGroupName "rg-azlocal-prod-eus-001" `
  -Name "vm-azlocal-prod-eus-dc-01" `
- -ComputerName "ral-dc-01"
+ -ComputerName "nyc-dc-01"
 ```
 
 **Terraform**:
 ```hcl
 resource "azurerm_windows_virtual_machine" "dc_01" {
  name = "vm-azlocal-prod-eus-dc-01" # Azure resource name
- computer_name = "ral-dc-01" # Windows hostname (≤15 chars)
+ computer_name = "nyc-dc-01" # Windows hostname (≤15 chars)
  # ...
 }
 
@@ -1004,7 +1004,7 @@ resource "azurerm_linux_virtual_machine_scale_set" "cicd" {
 **ARM Template / Bicep**:
 ```json
 "osProfile": {
- "computerName": "ral-dc-01",
+ "computerName": "nyc-dc-01",
  "adminUsername": "..."
 }
 ```
@@ -1158,15 +1158,15 @@ entra_groups:
 **Examples**:
 - `sp-azlocal-prod-deployment` (Azure Local deployment automation)
 - `sp-azlocal-prod-monitoring` (Monitoring integration)
-- `sp-cicd-customer-prod` (CI/CD pipeline service principal)
+- `sp-cicd-iic-prod` (IIC production CI/CD)
 - `sp-backup-prod-recovery` (Backup and recovery automation)
 
 **Variable Mapping**:
 ```yaml
 service_principals:
  deployment: "sp-{{workload}}-{{environment}}-deployment"
  monitoring: "sp-{{workload}}-{{environment}}-monitoring"
- cicd: "sp-cicd-{{customer}}-{{environment}}"
+ cicd: "sp-cicd-{{org_prefix}}-{{environment}}"
 ```
 
 #### Managed Identities
@@ -1415,7 +1415,7 @@ azure_arc:
 
 **Examples**:
 - `stwitnessclus01eus01` (Cluster 01 cloud witness - 20 chars)
-- `stwitnessraleus01` (RAL site cloud witness - 17 chars)
+- `stwitnessnyceus01` (NYC site cloud witness - 17 chars)
 
 **Variable Mapping**:
 ```yaml
@@ -1435,7 +1435,7 @@ witness:
 
 **Examples**:
 - `fswit-clus01-01` (Cluster 01 file share witness)
-- `fswit-ral-01` (RAL site file share witness)
+- `fswit-nyc-01` (NYC site file share witness)
 
 **Variable Mapping**:
 ```yaml
@@ -1515,17 +1515,17 @@ cicd:
 
 ### 3.3 CI/CD Service Principal
 
-**Pattern**: `sp-cicd-<customer>-<environment>`
+**Pattern**: `sp-cicd-<org>-<environment>`
 
 **Examples**:
-- `sp-cicd-acme-prod` (ACME Corp production CI/CD)
-- `sp-cicd-globaltech-prod` (GlobalTech production CI/CD)
+- `sp-cicd-iic-prod` (IIC production CI/CD)
+- `sp-cicd-iic-dev` (IIC development CI/CD)
 - `sp-cicd-internal-dev` (Internal development CI/CD)
 
 **Variable Mapping**:
 ```yaml
 cicd:
- service_principal: "sp-cicd-{{customer}}-{{environment}}"
+ service_principal: "sp-cicd-{{org_prefix}}-{{environment}}"
 ```
 
 ---
@@ -1621,7 +1621,7 @@ For automation via `variables.yml`, use these variable patterns:
 
 | **Variable** | **Description** | **Example Value** |
 | --------------------- | --------------------------------- | ----------------- |
-| `site_code` | Site code identifier (2-5 chars) | `RAL`, `ATL`, `iic` |
+| `site_code` | Site code identifier (2-5 chars) | `nyc`, `sea`, `iic` |
 | `environment` | Environment name | `prod`, `dev` |
 | `azure_region` | Azure region code | `eastus`, `westus`|
 | `workload` | Workload/product name | `azlocal`, `azurelocal` |