Azure / Azure/azure-quickstart-templates

sqlmi-new-vnet Template & SQL MI Naming Convention

Open
#13,347 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Bicep
Stars
14.9k
Forks
16.2k
Avg merge
6d 21h
Merged PRs (30d)
6

Description

[sqlmi-new-vnet](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.sql/sqlmi-new-vnet)

This template allows the user to create a new SQL MI instance with a name which does not follow SQL MI naming convention requirements seen [here](https://azure.github.io/PSRule.Rules.Azure/en/rules/Azure.SQLMI.Name/). I was able to use this template to create a new SQL MI instance with a camel case name and all validation came back clean and the SQL MI instance was created successfully.

I realized this issue after the fact when trying to leverage the Nov 2022 Feature Wave start/stop functionality for the SQL MI instance mentioned above, when trying to stop the instance it throws an error saying:

> The server name 'RedactedSQLMI' cannot be empty or null. The server name can only be made up of lowercase letters 'a'-'z', the numbers 0-9 and the hyphen. The hyphen may not lead or trail in the server name. Please fix the server name and retry. Please contact Microsoft support if the issue persists.

Contributor guide

No contributing guide indexed for this repository

Research direction

Open the linked quickstarts/microsoft.sql/sqlmi-new-vnet template and compare its SQL MI naming inputs with the Azure SQL MI naming requirements in the linked PSRule rule. Reproduce the behavior with a camel-case name, then verify that invalid names are rejected while valid lowercase, numeric, and hyphenated names remain supported.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, sql
Domain
cloud, databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.