{"id":6043,"date":"2014-04-21T00:00:00","date_gmt":"2014-04-21T00:00:00","guid":{"rendered":"https:\/\/azure.microsoft.com\/blog\/custom-data-and-cloud-init-on-windows-azure"},"modified":"2025-09-12T09:06:48","modified_gmt":"2025-09-12T16:06:48","slug":"custom-data-and-cloud-init-on-windows-azure","status":"publish","type":"post","link":"https:\/\/azure.microsoft.com\/en-us\/blog\/custom-data-and-cloud-init-on-windows-azure\/","title":{"rendered":"Custom Data and Cloud-Init on Microsoft Azure"},"content":{"rendered":"\n

What is Custom Data?<\/h2>\n\n\n\n

Customers often ask how they can inject a script or other metadata into a Microsoft Azure virtual machine at provision time.  In other clouds this concept is often referred to as user data<\/em>.  In Microsoft Azure we have a similar feature called custom data.<\/em> Custom data is sent to the VM along with the other provisioning configuration information such as the new hostname, username, password, certificates and keys, etc.  This data is passed to the Azure API as base64-encoded data.  On Windows this data ends up in %SYSTEMDRIVE%AzureDataCustomData.bin<\/em> as a binary file.  On Linux, this data is passed to the VM via the ovf-env.xml file, which is copied to the \/var\/lib\/waagent directory during provisioning.  Newer versions of the Microsoft Azure Linux Agent will also copy the base64-encoded data to \/var\/lib\/waagent\/CustomData<\/em> as well for convenience.<\/p>\n\n\n\n

What About Cloud-Init?<\/h2>\n\n\n\n

Currently, only the Ubuntu images in the Microsoft Azure Gallery have cloud-init preinstalled and configured to act on the custom data sent during provisioning.  This means that for Ubuntu you can use custom data to provision a VM using a cloud-init configuration file, or just simply send a script that will be executed by cloud-init during provisioning.  See the cloud-init documentation<\/a> for more information. If cloud-init is not available on the image, then you can still make use of the custom data provided you preinstall a script or other tool on the system that can read the data.  In this case a script could be installed to run at boot time that can read in the custom data via the %SYSTEMDRIVE%AzureDataCustomData.bin<\/em> (Windows) or the \/var\/lib\/waagent\/ovf-env.xml<\/em> (Linux) file, decode it and act on the data.  Once the script is installed the Windows<\/a> or Linux<\/a> image can then be deprovisioned and captured for reuse.<\/p>\n\n\n\n

How Does It Work?<\/h2>\n\n\n\n

Currently, the easiest way to inject custom data into an IaaS VM is to use the Windows Azure command-line tools<\/a>.  Support for this feature in the Microsoft Azure Powershell cmdlets is not yet available, but is coming soon in an upcoming release. As of version 0.7.5 of the CLI tools there is a new parameter called –custom-data.<\/em>  This parameter takes a file name as an argument, and the tools will then base64 encode the contents of the file and send it along with the provisioning configuration information.  The only limit here is that the file must be less than 64KB or the Azure API will not accept the request. The following is a simple example of how to provision and pass custom data to an Ubuntu Linux VM: <\/p>\n\n\n

\"block<\/figure>\n\n\n\n

In this example, custom-data.txt<\/em> could be a cloud-init configuration file, or simply a shell script (as long as it starts with #!, then cloud-init will execute it). Give it a try.<\/p>\n\n\n\n

Additional References:<\/h4>\n\n\n\n