You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When in the landing zone configuration (below LZ 3) the choice is made to set the setting for name : passthrough to false, it is no longer possible to set it to true for an individual resource in a higher landingzone.
In some cases, it is desirable / convenient not to have to use the naming convention generated by the framework. Example; we want to keep WindowsComputername equal to the AzureVM name. So the ability to give an individual resource an alternative name would be very welcome.
The text was updated successfully, but these errors were encountered:
When in the landing zone configuration (below LZ 3) the choice is made to set the setting for name : passthrough to false, it is no longer possible to set it to true for an individual resource in a higher landingzone.
In some cases, it is desirable / convenient not to have to use the naming convention generated by the framework. Example; we want to keep WindowsComputername equal to the AzureVM name. So the ability to give an individual resource an alternative name would be very welcome.
The text was updated successfully, but these errors were encountered: