Facing Ext_StorageConfigurationSettings_ArgumentError Issue while deploying Azure SQL VM via Bicep – Storage Configuration Error and Default File Path Not Applied

Hi nikita tiwari,

Greetings!!

As i understand that you're running into a couple of issues while deploying an Azure SQL VM using Bicep. You're getting the Ext_StorageConfigurationSettings_ArgumentError, which typically happens when there's an issue with the physical disks configuration. Additionally, it seems your custom paths for SQL data and log settings aren't being recognized.

Here's a step-by-step approach to troubleshoot this:

Check Disk Configuration:

• The error message you received, 'Failed to get valid physical disks within given device ID range', usually indicates a problem with the disk configuration. Make sure that the disks are properly defined and available in the specified range.
• Verify that you're using managed disks, as unmanaged disks can lead to issues with SQL Server virtual machines.

Review Disk Count and Type:

• Ensure that the dataDiskCount, dataDiskSizeGB, and other disk-related parameters are correctly defined in your Bicep template.
• Check if you're using compatible disk types (e.g., Premium SSD) for SQL Server as specified in the Microsoft documentation.

https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/storage-configuration?view=azuresql&tabs=windows2016#known-issues

Validate SQL Data and Log Settings:

• For the defaultFilePath settings in sqlDataSettings and sqlLogSettings, make sure that the paths you provide are accessible and correctly formatted. Sometimes, hardcoded paths that don't exist or are incorrectly specified can be ignored during deployment.
• Refer to your SQL Virtual Machine resource configuration and confirm that the specified paths align with your Azure subscription.

Deployment Output:

• Check the Azure portal for detailed logs on the deployment. The logs can provide insights on which part of the configuration is leading to the error.

Check for template syntax errors:

• Syntax errors can often lead to unexpected behaviors. Make sure your Bicep code is free of syntax issues, especially in areas relating to parameters and disk definitions.

For more information, please refer the documents:
https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/create-sql-vm-bicep?view=azuresql&source=recommendations&tabs=CLI

https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/storage-configuration?view=azuresql&source=recommendations&tabs=windows2016

I hope this information helps. Please do let us know if you have any further queries.

Hi nikita tiwari,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Hi @Anonymous

The storage configuration issue has been resolved. However, we still not able to assign the defaultFilePath values for sqlDataSettings, sqlLogSettings, and sqlTempDbSettings within the storageConfigurationSettings section of the SQL Virtual Machine resource.

Please find the relevant code snippet below. Kindly review and let us know if any modifications are needed. Any assistance would be greatly appreciated.

resource sqlVirtualMachine 'Microsoft.SqlVirtualMachine/SqlVirtualMachines@2022-07-01-preview' = {   name: name   location: location   properties: {     virtualMachineResourceId: resourceId('Microsoft.Compute/virtualMachines', name)     sqlManagement: 'Full'     sqlServerLicenseType: 'AHUB'     // leastPrivilegeMode: 'Enabled'     // autoPatchingSettings: {     //   enable: false     // }     keyVaultCredentialSettings: {       enable: false       credentialName: ''     }     storageConfigurationSettings: {       diskConfigurationType: 'NEW'        storageWorkloadType: 'GENERAL'        sqlDataSettings: {         luns: [for i in range(0, dataDiskCount-2): i]

        defaultFilePath: 'F:\SQLData'       }       sqlLogSettings: {         luns: [dataDiskCount-1]         defaultFilePath: 'G:\SQLLogs'       }       sqlTempDbSettings: {           defaultFilePath: 'D:\SQLTemp'          persistFolder: true       }       sqlSystemDbOnDataDisk: false     }     serverConfigurationsManagementSettings: {       sqlConnectivityUpdateSettings: {         connectivityType: 'Private'         port: 1433         sqlAuthUpdateUserName: 'records'         sqlAuthUpdatePassword: VMLocalAdminPassword       }       additionalFeaturesServerConfigurations: {         isRServicesEnabled: false       }     }   }   dependsOn: [     vm     guestAttestationExtension   ] }

Looking forward to your feedback.

Hi @Anonymous

The storage configuration issue has been resolved. However, we still not able to assign the defaultFilePath values for sqlDataSettings, sqlLogSettings, and sqlTempDbSettings within the storageConfigurationSettings section of the SQL Virtual Machine resource.

Please find the relevant code snippet below. Kindly review and let us know if any modifications are needed. Any assistance would be greatly appreciated.

resource sqlVirtualMachine 'Microsoft.SqlVirtualMachine/SqlVirtualMachines@2022-07-01-preview' = {   name: name   location: location   properties: {     virtualMachineResourceId: resourceId('Microsoft.Compute/virtualMachines', name)     sqlManagement: 'Full'     sqlServerLicenseType: 'AHUB'     // leastPrivilegeMode: 'Enabled'     // autoPatchingSettings: {     //   enable: false     // }     keyVaultCredentialSettings: {       enable: false       credentialName: ''     }     storageConfigurationSettings: {       diskConfigurationType: 'NEW'        storageWorkloadType: 'GENERAL'        sqlDataSettings: {         luns: [for i in range(0, dataDiskCount-2): i]

        defaultFilePath: 'F:\SQLData'       }       sqlLogSettings: {         luns: [dataDiskCount-1]         defaultFilePath: 'G:\SQLLogs'       }       sqlTempDbSettings: {           defaultFilePath: 'D:\SQLTemp'          persistFolder: true       }       sqlSystemDbOnDataDisk: false     }     serverConfigurationsManagementSettings: {       sqlConnectivityUpdateSettings: {         connectivityType: 'Private'         port: 1433         sqlAuthUpdateUserName: 'records'         sqlAuthUpdatePassword: VMLocalAdminPassword       }       additionalFeaturesServerConfigurations: {         isRServicesEnabled: false       }     }   }   dependsOn: [     vm     guestAttestationExtension   ] }

Looking forward to your feedback.

Hi nikita tiwari,

Thanks for the response.

You've configured the storageConfigurationSettings section correctly in your Bicep template, including the defaultFilePath values for SQL data, log, and tempDB files. However, I’d like to clarify that this is a known limitation in the current implementation of the SQL IaaS Agent extension on Azure.

Although the API accepts the defaultFilePath values, the SQL IaaS extension does not automatically apply them during deployment. This behavior affects deployments via Bicep, ARM templates, Terraform, and even the Azure Portal in some cases.

Current Workaround:

To apply the desired default file paths, the most reliable approach is to use a Custom Script Extension that:

• Initializes and assigns the correct drive letters (F:, G:, D:, etc.).
• Executes a PowerShell script to set the SQL Server default paths using xp_instance_regwrite or SQLCMD.
• Optionally, restarts the SQL Server service to apply the changes.

For more information, please refer below documents:

https://learn.microsoft.com/en-us/azure/templates/microsoft.sqlvirtualmachine/2022-07-01-preview/sqlvirtualmachines?pivots=deployment-language-bicep

https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/sql-agent-extension-troubleshoot-known-issues?view=azuresql

https://github.com/Azure/azure-rest-api-specs/issues/19517?utm_source=chatgpt.com

I hope this information helps. Please do let us know if you have any further queries.