Skip to main content

Azure Automation variables in Bicep

If you want to create an Azure Automation variable in Bicep you will use a resource definition like this.
resource existingAutomationAccountResource 'Microsoft.Automation/automationAccounts@2023-11-01' existing = {
  name: 'automationAccountName'
}

resource variablesResource 'Microsoft.Automation/automationAccounts/variables@2023-11-01' = {
  name: 'variableName'
  parent: existingAutomationAccountResource
  properties: {
    description: 'description'
    isEncrypted: 'false'
    value: 'value'
  }
}
For variables Azure Automation supports different types: String, Boolean, DateTime, Integer and Not Specified. Below you can find some examples how to define these values in Bicep format.

String values should be put between double quotes.
resource stringVariablesResource 'Microsoft.Automation/automationAccounts/variables@2023-11-01' = {
  name: 'stringVariable'
  parent: existingAutomationAccountResource
  properties: {
    value: '"This is a string"'
  }
}
Boolean values are simple true or false values within the single quotes.
resource booleanVariablesResource 'Microsoft.Automation/automationAccounts/variables@2023-11-01' = {
  name: 'booleanVariable'
  parent: existingAutomationAccountResource
  properties: {
    value: 'true'
  }
}
DateTime values are specified in epoch format and need a special notation which also require double quotes. The value 22-12-2024, 11:04:56 is the value that will be shown in the variable if you deploy this Bicep resource.
resource dateTimevariablesResource 'Microsoft.Automation/automationAccounts/variables@2023-11-01' = {
  name: 'dateTimeVariable'
  parent: existingAutomationAccountResource
  properties: {
    value: '"\\/Date(1734865496153)\\/"'
  }
}
Integer values are simple integer values within the single quotes.
resource integerVariablesResource 'Microsoft.Automation/automationAccounts/variables@2023-11-01' = {
  name: 'integerVariable'
  parent: existingAutomationAccountResource
  properties: {
    value: '123'
  }
}
Not Specified values are objects which need escaped inner single quotes. This value will be shown as 'not specified value' in the variable.
resource notSpecifiedVariablesResource 'Microsoft.Automation/automationAccounts/variables@2023-11-01' = {
  name: 'notSpecifiedVariable'
  parent: existingAutomationAccountResource
  properties: {
    value: '\'not specified value\''
  }
}
If you specify a string value with only single quotes you will get a deploy error like "Invalid JSON - Kindly check the value of the variable."

Comments

Popular posts from this blog

CS8357: The specified version string contains wildcards, which are not compatible with determinism.

Today I was busy with creating a WCF service solution in Visual Studio Enterprise 2017 (15.9.2). In this solution I use a few C# class libraries based on .NET 4.7.2. When I compiled the solution I got this error message: Error CS8357: The specified version string contains wildcards, which are not compatible with determinism. Either remove wildcards from the version string, or disable determinism for this compilation The error message is linking to my AssemblyInfo.cs file of the Class library projects. In all the projects of this solution I use the wildcard notation for generating build and revision numbers. // Version information for an assembly consists of the following four values: // // Major Version // Minor Version // Build Number // Revision // // You can specify all the values or you can default the Build and Revision Numbers // by using the '*' as shown below: // [assembly: AssemblyVersion("1.0.*")] [assembly: AssemblyVersion("1.0....

Assign an existing certificate to your IIS website with WiX

Recently I had to change the bindings of existing IIS hosted websites and APIs from HTTP to HTTPS. They are installed with a MSI file created with the WiX Toolset . Because I have to use an already on the server installed certificate I cannot use the Certificate element from the IIS Extension because this element only supports installing and uninstalling certificates based on PFX files. After doing some research I found the blog article Assign Certificate (Set HTTPS Binding certificate) to IIS website from Wix Installer which described the usage of Custom Actions for this purpose. I adopted this approach and rewrote the code for my scenario. With WiX I still create the website. <iis:WebSite Id="WebSite" ConfigureIfExists="yes" AutoStart="yes" Description="MyWebsite" Directory="IISROOT" StartOnInstall="yes"> <iis:WebAddress Id="WebSite...

Fixing HTTP Error 401.2 unauthorized on local IIS

Sometimes the Windows Authentication got broken on IIS servers so you cannot log in locally on the server. In that case you get the dreadfully error message HTTP Error 401.2 - Unauthorized You are not authorized to view this page due to invalid authentication headers. To fix this issue you can repair the Windows Authentication feature with the following PowerShell commands: Remove-WindowsFeature Web-Windows-Auth Add-WindowsFeature Web-Windows-Auth