An Azure service that is used to provision Windows and Linux virtual machines.
If your goal is for your extension to appear under “Extensions + applications” in the Azure portal, this scenario requires VM Extension Publisher onboarding. Please note that this process is separate from publishing an offer through Partner Center.
VM Extension publishing is not a self-service process. Access to the detailed publisher documentation and tooling is restricted to approved publishers. Onboarding requires engagement with the Microsoft VM Extension team, and typically includes:
- Azure subscription ID
- Reference link to the Q&A thread or support request
- Availability to schedule an onboarding discussion
Additionally, the publicly visible azure-extensions-cli tooling is intended only for Microsoft employees or approved (whitelisted) extension publishers. It acts as a wrapper around Azure’s internal extension publishing APIs and is not available for general public use - https://learn.microsoft.com/en-us/partner-center/marketplace-offers/azure-vm-offer-setup
If your objective is to deploy your SaaS agent or configuration components onto customer VMs, you do not need to become a VM Extension publisher.
The following supported approaches are recommended:
- Azure Virtual Machine Offer (Marketplace) - https://learn.microsoft.com/en-us/partner-center/marketplace-offers/marketplace-virtual-machines
You can publish an Azure Virtual Machine offer through Partner Center with your software pre-installed in the VM image. Customers can then deploy the image directly from the Marketplace.
This option is appropriate when:
- Your software needs to be baked into the OS image.
- You require Marketplace distribution.
- Azure Application Offer (Marketplace)
You can publish an Azure Application offer that deploys infrastructure (including VMs) and performs post-deployment configuration using supported VM extensions (for example, Custom Script Extension).
This is suitable when:
- You need to orchestrate infrastructure deployment.
- Your components can be installed during or after deployment using standard VM extension mechanisms.
- Use Existing VM Extension Mechanisms (Without Marketplace Packaging)
If Marketplace listing is not required, you can install and configure your solution using built-in VM extension capabilities. VM extensions are designed for post-deployment configuration and automation.
Examples include: az vm extension set
Custom Script Extension to download and execute installation scripts
This approach works well for direct deployments where Marketplace distribution is not necessary.