Optional Resource Renaming – Make Custom Naming Non-Mandatory #835
Description
Describe the feature end to end, including deployment scenario details under which the feature would occur.
Modify the naming configuration step in the AVD Landing Zone Accelerator (LZA) that allows operators to override names selectively without forcing a complete naming matrix.
Current Default behavior: Use accelerator generated names aligned with CAF standards.
Optional override: Apply custom names only where specified, leaving all other resources named with defaults.
This avoids the current all or nothing approach where enabling custom naming requires providing names for every resource.
Why is this feature important. Describe why this would be important for your organization and others. Would this impact similar orgs in the same way?
- Reduces prep time and validation errors for teams that only need to customize a few critical resources (e.g., resource groups or session hosts or storage accounts).
- Maintains CAF alignment for the rest, improving compliance and consistency.
Please provide the correlation id associated with your error or bug.
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Can you describe any alternatives that you have taken since this feature does not exist?
Teams currently compile full naming tables manually and rerun the accelerator, which is time consuming and error prone. Some operators abandon custom naming entirely to avoid delays.
Feature Implementation
No in product implementation today. No internal branch or code workaround; this requires a Coding or UX/config enhancement in the accelerator wizard.