This project provides the source code of Linux extensions for Microsoft Azure IaaS.
VM Extensions are injected components authored by Microsoft and Partners into Linux VM (IaaS) to enable software and configuration automation.
You can read the document about virtual machine extensions and features.
Name | Lastest Version | Description |
---|---|---|
Custom Script | 1.5 | Allow the owner of the Azure Virtual Machines to run customized scripts in the VM |
DSC | 2.71 | Allow the owner of the Azure Virtual Machines to configure the VM using Windows PowerShell Desired State Configuration (DSC) for Linux |
OS Patching | 2.0 | Allow the owner of the Azure VM to configure the Linux VM patching schedule cycle |
VM Access | 1.5 | Provide several ways to allow owner of the VM to get the SSH access back |
OMS Agent | 1.0 | Allow the owner of the Azure VM to install the omsagent and attach it to an OMS workspace |
Diagnostic | 3.0.129 | Allow the owner of the Azure Virtual Machines to obtain diagnostic data for a Linux virtual machine |
Backup | 1.0.9124.0 | Provide application consistent backup of the virtual machine(Needs to be used in conjunction with Azure Backup) |
Please refer to the Contribution Guide.
When you run the PowerShell command "Set-AzureVMExtension" on Linux VM, you may hit following error: "Provision Guest Agent must be enabled on the VM object before setting IaaS VM Access Extension".
Root Cause: When you create the Linux VM via portal, the value of provision guest agent on the VM is not always set to "True". If your VM is created using PowerShell or using the Azure new portal, you will not see this issue.
Resolution: Add the following PowerShell command to set the ProvisionGuestAgent to "True".
$vm = Get-AzureVM -ServiceName 'MyServiceName' -Name 'MyVMName'
$vm.GetInstance().ProvisionGuestAgent = $true
The extensions in this repository are tested against Python 2.7 and higher. The extensions in this repository use OpenSSL 1.0 and higher.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.