Automation account naming #782
-
|
Is it a spell mistake as there is a double "a" infront of aauto.
Also please advise how to run the eslzARM powershell commands in Devops as a pipeline? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
See details around this here: https://github.com/Azure/Enterprise-Scale/blob/main/docs/EnterpriseScale-FAQ.md#can-we-take-the-arm-templates-for-enterprise-scale-reference-implementations-and-check-them-into-our-repository-and-deploy-it-from-there-instead-of-via-the-azure-portal The gist of it is that we recommend using AzOps (you can integrate during deployment - as well as any time post deployment and reconcile the templates back into Git). If you want to take the templates as is in a 'do it yourself' fashion, we have documented the strict sequence and deployment steps here: https://github.com/Azure/Enterprise-Scale/tree/main/eslzArm Regarding the suffix of the automation account, this is not a mistake, but by design with regards to min character lenght for the automation account resourceType |
Beta Was this translation helpful? Give feedback.
See details around this here: https://github.com/Azure/Enterprise-Scale/blob/main/docs/EnterpriseScale-FAQ.md#can-we-take-the-arm-templates-for-enterprise-scale-reference-implementations-and-check-them-into-our-repository-and-deploy-it-from-there-instead-of-via-the-azure-portal
The gist of it is that we recommend using AzOps (you can integrate during deployment - as well as any time post deployment and reconcile the templates back into Git).
If you want to take the templates as is in a 'do it yourself' fashion, we have documented the strict sequence and deployment steps here: https://github.com/Azure/Enterprise-Scale/tree/main/eslzArm
Regarding the suffix of the automation account, this i…