Feature Overview (aka. Goal Summary)  

As a customer, I would like to be able to name my resource with up to 30 characters. This is the name length currently supported in ARO classic:
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules

Goals (aka. expected user outcomes)

Be able to specify a cluster name with up to 30 characters
 

Requirements (aka. Acceptance Criteria):

I can provide a name via CLI, portal, ARM that is up to 30 characters in length and have a successful cluster deployed

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

Interoperability Considerations

Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.