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
Tool version
Current version of the Azure Naming Tool you are running.
V4.0
Is your feature request related to a problem? Please describe.
The Azure naming tool is currently missing the option to specify the resource type for Virtual Desktop resources. When attempting to name resources related to Azure Virtual Desktop, users are unable to select the appropriate resource type, which impacts the consistency and clarity of resource naming conventions.
Describe the solution you'd like
I implemet it manuall in the Json File and import it again.
Expected Behavior:
The Azure naming tool should include an option to specify the resource type for Azure Virtual Desktop resources, allowing users to adhere to consistent naming conventions and ensure clarity in resource naming.
The text was updated successfully, but these errors were encountered:
@Crallbit Hi,
The json file can be uploaded using the API. Add a new item to the end of the list, specify the next sequence number for the ID, select the rest of the parameters, and upload the whole file again.
Tool version
Current version of the Azure Naming Tool you are running.
V4.0
Is your feature request related to a problem? Please describe.
The Azure naming tool is currently missing the option to specify the resource type for Virtual Desktop resources. When attempting to name resources related to Azure Virtual Desktop, users are unable to select the appropriate resource type, which impacts the consistency and clarity of resource naming conventions.
Describe the solution you'd like
I implemet it manuall in the Json File and import it again.
Expected Behavior:
The Azure naming tool should include an option to specify the resource type for Azure Virtual Desktop resources, allowing users to adhere to consistent naming conventions and ensure clarity in resource naming.
The text was updated successfully, but these errors were encountered: