Azure ARM Tempalte - Unexpected character

Legacy Execution
1

This ARM template is now generating an error for us and I don’t believe it is fixed in upcoming releases.
I am on version 2019.3.3 LTS

{
    "$schema": "http://schema.management.azure.com/schemas/2014-04-01-preview/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "parameters": {
        "AAD Admin Login": {
            "type": "String"
        },
        "AAD Admin ObjectID": {
            "type": "String"
        },
        "AAD TenantId": {
            "type": "String"
        },
        "Location (Region)": {
            "type": "String"
        },
        "Server Name": {
            "type": "String"
        }
    },
    "variables": {},
    "resources": [
        {
            "type": "Microsoft.Sql/servers",
            "name": "[parameters('Server Name')]",
            "apiVersion": "2014-04-01-preview",
            "location": "[parameters('Location (Region)')]",
            "properties": {
                "version": "12.0"
            },
            "resources": [
                {
                    "type": "administrators",
                    "name": "activeDirectory",
                    "apiVersion": "2014-04-01-preview",
                    "location": "[parameters('Location (Region)')]",
                    "properties": {
                        "administratorType": "ActiveDirectory",
                        "login": "[parameters('AAD Admin Login')]",
                        "sid": "[parameters('AAD Admin ObjectID')]",
                        "tenantId": "[parameters('AAD TenantID')]"
                    },
                    "dependsOn": [
                        "[concat('Microsoft.Sql/servers/', parameters('Server Name'))]"
                    ]
                }
            ]
        }
    ]
}

image
image.png1222×361 23.6 KB

2

Our ‘AAD Admin Login’ value is: SQL Admins

5

Hi David,

Thanks for getting in touch! I’m terribly sorry to hear you’ve been hitting this issue. This is a known bug with variable types being treated as case sensitive. Changing the type to string instead of String (lowercase s) should get you up and running. You can reference the bug report at the following link.

We’re shipping a fix to this issue in 2019.5.4, and also back porting the fix to the next LTS patch (2019.3.4). Both versions should be shipped very soon.

Don’t hesitate to reach out if you have any questions or concerns going forward!

Best regards,

Kenny

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.