Back to Azure Resource templates index <–
SQL Server 2016 SP1 on Windows Server 2016
Template Locations
Infrastructure As Code Advisor (Beta)
WAF-compliance
The WAF-compliance advisor validates templates based on the Well Architected Framework practices. Every day a GitHub Action updates the templates compliance data and lists the recomendations.
Sustainbility Advisor
The sustainability advisor is based on the Sogeti Cloud Reference Architecture with sustainble practices. These sustainble practices cover application code, cloud infrastructures and data. The global Sogeti community is continously evolving the sustainble practices and every day new and tuned are added. For cloud infrastructures the sustainble practices are automatically validated and reported below.
note: when 100% it can be that there is no sustainble practices yet for this Cloud infrastructure.
Online documentation
Template reference
Service description
Requirements
- Valid Virtual Network with Subnet should already be created.
Input values
- tagBillingIdentifier: Cost Center.
- zone: Enter abbreviation for Zone. e=External, i=Internal, p=Production, m=Management.
- vmIndexOffset: Index from where the Virtual Machine creation will be started.
- virtualMachineSize: Size of the Virtual Machine.
- adminUsername: Username for the Virtual Machine.
- virtualNetworkName: Name of the existing Virtual Network.
- subnetName: Name of the subnet in the existing Virtual Network.
- publicIpAddressType: Provisioning type of the Public IP address of the VM (Static or Dynamic).
- sqlConnectivityType: This defines the access level of the SQL server, whether it should be accessed Locally, or from within the VNet or publicly.
- sqlPortNumber: This defines the port for the SQL server to work on.
- sqlSku: Pricing tier of the SQL Server SP1 (Web, Standard or Enterprise).
- sqlAuthenticationLogin: Username for the SQL server.
Output values
- adminPassword: Password for accessing the Virtual Machine
- sqlAuthPassword: Password for accessing the SQL in the Virtual Machine
- VMName: Name of the Virtual Machine
- dnsLabel: DNS Name of the Virtual Machine
Compliance Advisor details
Resource Health Result
| Message | ResourceType | Severity |
|---|---|---|
| Location for the resource should not be hardcoded, it should be parameterized and should refer from Resource Group's location i.e. [resourceGroup().location] | Microsoft.Compute/virtualMachines | 2 |
| Install the extension to enable a vulnerability assessment solution on your virtual machines. | Microsoft.Compute/virtualMachines | 2 |
| It is recommended to implement Auto-Shutdown option for your virtual Machine if you are using non production or Dev/Test lab virtual machines, this will enable us to save compute power | Microsoft.Compute/virtualMachines | 2 |
| Your current API Version i.e.2018-06-01 for the resource Microsoft.Compute/virtualMachines is outdatedconsider updating to new recent version available i.e. 2023-03-01 or 2022-11-01 | Microsoft.Compute/virtualMachines | 2 |
| Location for the resource should not be hardcoded, it should be parameterized and should refer from Resource Group's location i.e. [resourceGroup().location] | Microsoft.SqlVirtualMachine/SqlVirtualMachines | 2 |
| Your current API Version i.e.2017-03-01-preview for the resource Microsoft.SqlVirtualMachine/SqlVirtualMachines is outdatedconsider updating to new recent version available i.e. 2023-01-01-preview or 2022-08-01-preview | Microsoft.SqlVirtualMachine/SqlVirtualMachines | 2 |
| Location for the resource should not be hardcoded, it should be parameterized and should refer from Resource Group's location i.e. [resourceGroup().location] | Microsoft.Network/networkInterfaces | 2 |
| Your current API Version i.e.2018-10-01 for the resource Microsoft.Network/networkInterfaces is outdatedconsider updating to new recent version available i.e. 2023-04-01 or 2023-02-01 | Microsoft.Network/networkInterfaces | 2 |
| Location for the resource should not be hardcoded, it should be parameterized and should refer from Resource Group's location i.e. [resourceGroup().location] | Microsoft.Network/publicIpAddresses | 2 |
| Your current API Version i.e.2018-08-01 for the resource Microsoft.Network/publicIpAddresses is outdatedconsider updating to new recent version available i.e. 2023-04-01 or 2023-02-01 | Microsoft.Network/publicIpAddresses | 2 |
| Location for the resource should not be hardcoded, it should be parameterized and should refer from Resource Group's location i.e. [resourceGroup().location] | Microsoft.Compute/virtualMachines/extensions | 2 |
| It is recommended to use below property for your resource Microsoft.Compute/virtualMachines { "priority": "Spot" }Using Azure Spot Virtual Machines allows you to take advantage of our unused capacity at a significant cost savings. At any point in time when Azure needs the capacity back, the Azure infrastructure will evict Azure Spot Virtual Machines. Therefore, Azure Spot Virtual Machines are great for workloads that can handle interruptions like batch processing jobs, dev/test environments, large compute workloads, and more | Microsoft.Compute/virtualMachines | 1 |
| To help other contributors understand the purpose of the resource, specify comments for each resource in the template | Microsoft.Compute/virtualMachines | 1 |
| Azure Backup should be enabled for virtual machines | Microsoft.Compute/virtualMachines | 1 |
| Use B-series VMs, B-series VM are used for typically idle applications that have sudden usage bursts. B-series VMs use baseline-level CPU power having you paying only for the minimal usage. When there’s a sudden burst, CPU power increases and you pay extra for the extra used capacity. | Microsoft.Compute/virtualMachines | 1 |
| It is recommended to parameterized your tag and make it as object type | Microsoft.Compute/virtualMachines | 1 |
| To help other contributors understand the purpose of the resource, specify comments for each resource in the template | Microsoft.SqlVirtualMachine/SqlVirtualMachines | 1 |
| It is recommended to parameterized your tag and make it as object type | Microsoft.SqlVirtualMachine/SqlVirtualMachines | 1 |
| To help other contributors understand the purpose of the resource, specify comments for each resource in the template | Microsoft.Network/networkInterfaces | 1 |
| It is recommended to parameterized your tag and make it as object type | Microsoft.Network/networkInterfaces | 1 |
| To help other contributors understand the purpose of the resource, specify comments for each resource in the template | Microsoft.Network/publicIpAddresses | 1 |
| It is recommended to use tags for your resource, which is currently missing | Microsoft.Compute/virtualMachines/extensions | 1 |
| To help other contributors understand the purpose of the resource, specify comments for each resource in the template | Microsoft.Compute/virtualMachines/extensions | 1 |
| It is recommended to parameterized your tag and make it as object type | Microsoft.Compute/virtualMachines/extensions | 1 |
TemplateParameterHealthResult
| Message | Severity |
|---|---|
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. tagBillingIdentifierRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. dnsLabelPrefixcustomnameRead More | 1 |
| It is recommended to make your parameter as camel case, wherever possible for i.e. zoneRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. virtualMachineSizeRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. adminUsernameRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. virtualNetworkNameRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. subnetNameRead More | 1 |
| Define default values for parameters that aren't sensitive. By specifying a default value, it's easier to deploy the template, and users of your template see an example of an appropriate value i.e. sqlAuthenticationLoginRead More | 1 |
TemplateVariableHealthResult
| Message | Severity |
|---|---|
| It is recommended to make your variable as camel case, wherever possible for e.g. locationRead More | 1 |
| It is recommended to make your variable as camel case, wherever possible for e.g. environmentRead More | 1 |
TemplateOthersHealthResult
| Message | Severity |
|---|---|
| Current schema version is not valid, Please change the version year to 2019-04-01 or greater | 2 |
Sustainable Advisor details
| Message | ResourceType | Severity |
|---|---|---|
| It is recommended to implement Auto-Shutdown option for your virtual Machine if you are using non production or Dev/Test lab virtual machines, this will enable us to save compute power | Microsoft.Compute/virtualMachines | 2 |
| It is recommended to use below property for your resource Microsoft.Compute/virtualMachines { "priority": "Spot" }Using Azure Spot Virtual Machines allows you to take advantage of our unused capacity at a significant cost savings. At any point in time when Azure needs the capacity back, the Azure infrastructure will evict Azure Spot Virtual Machines. Therefore, Azure Spot Virtual Machines are great for workloads that can handle interruptions like batch processing jobs, dev/test environments, large compute workloads, and more | Microsoft.Compute/virtualMachines | 1 |
| Use B-series VMs, B-series VM are used for typically idle applications that have sudden usage bursts. B-series VMs use baseline-level CPU power having you paying only for the minimal usage. When there’s a sudden burst, CPU power increases and you pay extra for the extra used capacity. | Microsoft.Compute/virtualMachines | 1 |