search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.25k stars 21.43k forks source link

KeyVault Naming Limits #34230

Closed derekschauland closed 4 years ago

derekschauland commented 5 years ago

Please update this list to include limits on the number of characters allowed in the name of a key vault resource. I think this is 24 characters as an attempt to create a resource with a 26 character name. This naming limitation would be useful for all Azure resources, but key vault is top of mind for me right now.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

femsulu commented 5 years ago

Thanks for your comment. The feedback has been shared with the content owner for further review. Thanks for your patience.

rothja commented 5 years ago

@derekschauland Thank you for this feedback! I sincerely apologize for the delay. I need to get someone on the key vault team to take a look at this request. I believe that @msmbaldwin is the right contact to start with. @msmbaldwin, could you help out with this issue? Thank you.

reassign:@msmbaldwin

derekschauland commented 5 years ago

Thanks for following up - I think the key vault creation screen in the portal calls this limitation out, but having this listed explicitly in the documentation would be extremely helpful to avoid confusion and issues if CLI or PowerShell fails for some reason and the user is unaware of the limitation.

thanks

Derek Schauland | MCSE | Microsoft MVP 2008 - 2018

From: Jason Roth notifications@github.com Sent: Monday, July 22, 2019 11:32 AM To: MicrosoftDocs/azure-docs azure-docs@noreply.github.com Cc: Derek Schauland derek@derekschauland.com; Mention mention@noreply.github.com Subject: Re: [MicrosoftDocs/azure-docs] KeyVault Naming Limits (#34230)

@derekschaulandhttps://github.com/derekschauland Thank you for this feedback! I sincerely apologize for the delay. I need to get someone on the key vault team to take a look at this request. I believe that @msmbaldwinhttps://github.com/msmbaldwin is the right contact to start with. @msmbaldwinhttps://github.com/msmbaldwin, could you help out with this issue? Thank you.

reassign:@msmbaldwinhttps://github.com/msmbaldwin

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/34230?email_source=notifications&email_token=AEWWFIM2JZG6JJXRF3YKEBTQAXOIXA5CNFSM4H4IM4L2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2QNOLY#issuecomment-513857327, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEWWFIMUYLG4MLLZ4CXQUSTQAXOIXANCNFSM4H4IM4LQ.

PRMerger14 commented 5 years ago

Only Microsoft employees can manage issues via commenting in this repo.

markgar commented 5 years ago

I'd like to amplify this request. Naming limitations are limitations. I don't see why they wouldn't be listed here. For instance, another limitation that would be good to call out is Azure Storage Account names. 24 characters, no caps, no dashes. But my suggestion is to gather naming restrictions for all services and put them here.

bandersmsft commented 4 years ago

@femsulu Can you please assign this issue to the Azure Resource Manager service? This isn't an issue for billing/svc. Thanks

femsulu commented 4 years ago

adding @tfitzmac - ARM Doc owner for comments.

tfitzmac commented 4 years ago

I added a new article recently that lists naming limitations. You can find Key Vault at https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules#microsoftkeyvault.

I'll add a link from the quotas and limits page to the new article.

tfitzmac commented 4 years ago

The link was added. It should get published in the next few hours.

tfitzmac commented 4 years ago

please-close

Matthew0x commented 1 year ago

It's 2023 and the 24 character limit is still in place. Your official guidelines suggest to name resources the following way: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-naming

Let's count the amount of characters: pip - 3 sharepoint - 10 prod - 4 westus - 6 001 - 3

That gives the total of 26 + the separators, which are "-", so 30 in total. Your official example proposes a convention that can be barely enforced using these limitations (if even).

Is there any particular reason for it? How are DevOps Engineers supposed to deploy and maintain resources in a neat and organized way if they are not able to properly name the Storage Accounts and Key Vaults for example?

JorgenSQ commented 6 months ago

hopeless that these arbitrary limits are still in place. 24 characters are useless when trying to enforce any naming convention across azure-resources.