The Azure Landing Zones (Enterprise-Scale) architecture provides prescriptive guidance coupled with Azure best practices, and it follows design principles across the critical design areas for organizations to define their Azure architecture
This pull request primarily introduces updates to the telemetry system of the Azure Landing Zones (ALZ) Accelerator project, along with updates to the project documentation. The main changes include the addition of new unique identifiers (PIDs) for different deployment scenarios, updates to the deployment script eslzArm.json to handle these new PIDs, and updates to the project's documentation to reflect these changes.
Documentation updates:
docs/wiki/Deploying-ALZ-CustomerUsage.md: Added new PIDs for various ALZ Accelerator/ESLZ ARM Deployment scenarios, including single platform subscription, multiple platform subscriptions, and different networking configurations.
docs/wiki/Whats-new.md: Included a new section for April 2024 updates, mentioning the addition of optional telemetry to help the ALZ team identify styles of deployments [1][2].
Telemetry system updates:
eslzArm/eslzArm.json: Added new variables for the newly introduced PIDs and updated the deployment names to include these new PIDs [1][2].
eslzArm/eslzArm.json: Updated the API version for telemetry-related deployments and added conditions to handle the deployment of the new PIDs based on the deployment scenario [1][2][3].
Overview/Summary
This pull request primarily introduces updates to the telemetry system of the Azure Landing Zones (ALZ) Accelerator project, along with updates to the project documentation. The main changes include the addition of new unique identifiers (PIDs) for different deployment scenarios, updates to the deployment script
eslzArm.jsonto handle these new PIDs, and updates to the project's documentation to reflect these changes.Documentation updates:
docs/wiki/Deploying-ALZ-CustomerUsage.md: Added new PIDs for various ALZ Accelerator/ESLZ ARM Deployment scenarios, including single platform subscription, multiple platform subscriptions, and different networking configurations.docs/wiki/Whats-new.md: Included a new section for April 2024 updates, mentioning the addition of optional telemetry to help the ALZ team identify styles of deployments [1] [2].Telemetry system updates:
eslzArm/eslzArm.json: Added new variables for the newly introduced PIDs and updated the deployment names to include these new PIDs [1] [2].eslzArm/eslzArm.json: Updated the API version for telemetry-related deployments and added conditions to handle the deployment of the new PIDs based on the deployment scenario [1] [2] [3].Breaking Changes
None
Testing
https://portal.azure.com/#view/Microsoft_Azure_CreateUIDef/CustomDeploymentBlade/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2FEnterprise-Scale%2Fusers%2Fjtracey93%2Ffeat%2Fadd-additional-telem%2FeslzArm%2FeslzArm.json/uiFormDefinitionUri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2FEnterprise-Scale%2Fusers%2Fjtracey93%2Ffeat%2Fadd-additional-telem%2FeslzArm%2Feslz-portal.json
As part of this Pull Request I have
mainbranch/docs/wiki/whats-new.md)