Create plans for a virtual machine offer
On the Plan overview page (select from the left-nav menu in Partner Center) you can provide a variety of plan options within the same offer. An offer requires at least one plan (formerly called a SKU), which can vary by monetization audience, Azure region, features, or VM images.
You can create up to 100 plans for each offer; up to 45 of these can be private. Learn more about private plans in Private offers in the Microsoft commercial marketplace.
After you create your plans, select the Plan overview tab to display:
- Plan names
- License models
- Audience (public or private)
- Current publishing status
- Available actions
The actions available on this pane vary depending on the current status of your plan.
- If the plan status is a draft, select Delete draft.
- If the plan status is published live, select Deprecate plan or Sync private audience.
Create a new plan
Select + Create new plan at the top.
In the New plan dialog box, enter a unique Plan ID for each plan in this offer. This ID will be visible to customers in the product web address. Use only lowercase letters and numbers, dashes, or underscores, and a maximum of 50 characters.
The plan ID can't be changed after you select Create.
Enter a Plan name. Customers see this name when they're deciding which plan to select within your offer. Create a unique name that clearly points out the differences between plans. For example, you might enter Windows Server with Pay-as-you-go, BYOL, Advanced, and Enterprise plans.
Select Create. This opens the Plan setup page.
Set the high-level configuration for the type of plan, specify whether it reuses a technical configuration from another plan, and identify the Azure regions where the plan should be available. Your selections here determine which fields are displayed on other panes for the same plan.
Your plan must be made available in at least one Azure region.
Select Azure Global to make your plan available to customers in all Azure Global regions that have commercial marketplace integration. For more information, see Geographic availability and currency support.
Select Azure Government to make your plan available in the Azure Government region. This region provides controlled access for customers from US federal, state, local, or tribal entities, as well as for partners who are eligible to serve them. You, as the publisher, are responsible for any compliance controls, security measures, and best practices. Azure Government uses physically isolated datacenters and networks (located in the US only).
Before you publish to Azure Government, test and validate your plan in the environment, because certain endpoints may differ. To set up and test your plan, request a trial account from the Microsoft Azure Government trial page.
After your plan is published and available in a specific Azure region, you can't remove that region.
Azure Government certifications
This option is visible only if you selected Azure Government as the Azure region in the preceding section.
Azure Government services handle data that's subject to certain government regulations and requirements. For example, FedRAMP, NIST 800.171 (DIB), ITAR, IRS 1075, DoD L4, and CJIS. To bring awareness to your certifications for these programs, you can provide up to 100 links that describe them. These can be either links to your listing on the program directly or links to descriptions of your compliance with them on your own websites. These links are visible to Azure Government customers only.
Select Save draft before continuing to the next tab in the left-nav Plan menu, Plan listing.
Configure the listing details of the plan. This pane displays specific information, which can differ from other plans in the same offer.
This field is automatically filled with the name that you gave your plan when you created it. This name appears on Azure Marketplace as the title of this plan. It is limited to 100 characters.
Provide a short summary of your plan, not the offer. This summary is limited to 100 characters.
Describe what makes this software plan unique, and describe any differences between plans within your offer. Describe the plan only, not the offer. The plan description can contain up to 2,000 characters.
Select Save draft before continuing to the next tab in the left-nav Plan menu, Pricing and availability.
Pricing and availability
On this pane, you configure:
- Markets where this plan is available. Every plan must be available in at least one market.
- The price per hour.
- Whether to make the plan visible to everyone or only to specific customers (a private audience).
Every plan must be available in at least one market. Most markets are selected by default. To edit the list, select Edit markets and select or clear check boxes for each market location where this plan should (or shouldn't) be available for purchase. Users in selected markets can still deploy the offer to all Azure regions selected in the "Plan setup" section.
Select Select only Microsoft Tax Remitted to select only countries/regions in which Microsoft remits sales and use tax on your behalf. Publishing to China is limited to plans that are either Free or Bring-your-own-license (BYOL).
If you've already set prices for your plan in US dollar (USD) currency and add another market location, the price for the new market is calculated according to current exchange rates. Always review the price for each market before you publish. Review your pricing by selecting Export prices (xlsx) after you save your changes.
When you remove a market, customers from that market who are using active deployments will not be able to create new deployments or scale up their existing deployments. Existing deployments are not affected.
Select Save to continue.
For the License model, select Usage-based monthly billed plan to configure pricing for this plan, or Bring your own license to let customers use this plan with their existing license.
For a usage-based monthly billed plan, use one of the following three price entry options:
- Per core – Provide pricing per core in USD. Microsoft calculates the pricing per core size and converts it into local currencies by using the current exchange rate.
- Per core size – Provide pricing per core size in USD. Microsoft calculates the pricing and converts it into local currencies by using the current exchange rate.
- Per market and core size – Provide pricing for each core size for all markets. You can import the prices from a spreadsheet.
Enter a Price per core, then select Price per core size to see a table of price/hour calculations.
Save pricing changes to enable the export of pricing data. After a price for a market in your plan is published, it can't be changed later. To ensure that the prices are right before you publish them, export the pricing spreadsheet and review the prices in each market.
You can offer a one-, three-, or six-month Free Trial to your customers.
You can design each plan to be visible to everyone or only to a preselected audience. Assign memberships in this restricted audience by using Azure subscription IDs.
Public: Your plan can be seen by everyone.
Private: Make your plan visible only to a preselected audience. After it's published as a private plan, you can update the audience or change it to public. After you make a plan public, it must remain public. It can't be changed back to a private plan.
Assign the audience that will have access to this private plan using Azure subscription IDs. Optionally, include a Description of each Azure subscription ID that you assign. Add up to 10 subscription IDs manually or up to 20,000 if you're importing a CSV spreadsheet. Azure subscription IDs are represented as GUIDs and all letters must be lowercase.
A private or restricted audience is different from the preview audience that you defined on the Preview pane. A preview audience can access your offer before it's published live to Azure Marketplace. Although the private audience choice applies only to a specific plan, the preview audience can view all private and public plans for validation purposes.
Private offers are not supported with Azure subscriptions established through a reseller of the Cloud Solution Provider program (CSP).
If your virtual machine is meant to be used only indirectly when it's referenced through another solution template or managed application, select this check box to publish the virtual machine but hide it from customers who might be searching or browsing for it directly.
Any Azure customer can deploy the offer using either PowerShell or CLI. If you wish to make this offer available to a limited set of customers, then set the plan to Private.
Hidden plans do not generate preview links. However, you can test you them by following these steps.
Select Save draft before continuing to the next tab in the left-nav Plan menu, Technical configuration.
Provide the images and other technical properties associated with this plan.
Reuse technical configuration
If you have more than one plan of the same type, and the packages are identical between them, select This plan reuses the technical configuration from another plan. This option lets you select one of the other plans of the same type for this offer and reuse its technical configuration.
Select the Windows or Linux operating system family.
Select the Windows Release or Linux Vendor.
Enter an OS friendly name for the operating system. This name is visible to customers.
Recommended VM sizes
Select the link to choose up to six recommended virtual machine sizes to display on Azure Marketplace.
Add open public or private ports on a deployed virtual machine.
Here is a list of properties that can be selected for your VM.
Supports backup: Enable this property if your images support Azure VM backup. Learn more about Azure VM backup.
Supports accelerated networking: Enable this property if the VM images for this plan support single root I/O virtualization (SR-IOV) to a VM, enabling low latency and high throughput on the network interface. Learn more about accelerated networking.
Supports cloud-init configuration: Enable this property if the images in this plan support cloud-init post deployment scripts. Learn more about cloud-init configuration.
Supports hotpatch: Windows Server Azure Editions supports Hot Patch. Learn more about Hot Patch.
Supports extensions: Enable this property if the images in this plan support extensions. Extensions are small applications that provide post-deployment configuration and automation on Azure VMs. Learn more about Azure virtual machine extensions.
Is a network virtual appliance: Enable this property if this product is a Network Virtual Appliance. A network virtual appliance is a product that performs one or more network functions, such as a Load Balancer, VPN Gateway, Firewall or Application Gateway. Learn more about network virtual appliances.
Remote desktop or SSH disabled: Enable this property if virtual Machines deployed with these images do not allow customers to access it using Remote Desktop or SSH. Learn more about locked VM images.
Requires custom ARM template for deployment: Enable this property if the images in this plan can only be deployed using a custom ARM template. To learn more see the Custom templates section of Troubleshoot virtual machine certification.
Generating a virtual machine defines the virtual hardware it uses. Based on your customer’s needs, you can publish a Generation 1 VM, Generation 2 VM, or both.
When creating a new offer, select a Generation type and enter the requested details:
To add another generation to a plan, select Add generation...
...and enter the requested details:
- To update an existing VM that has a Generation 1 already published, edit details on the Technical configuration page.
To learn more about the differences between Generation 1 and Generation 2 capabilities, see Support for generation 2 VMs on Azure.
Provide a disk version and the shared access signature (SAS) URI for the virtual machine images. Add up to 16 data disks for each VM image. Provide only one new image version per plan in a specified submission. After an image has been published, you can't edit it, but you can delete it. Deleting a version prevents both new and existing users from deploying a new instance of the deleted version.
These two required fields are shown in the prior image above:
- Disk version: The version of the image you are providing.
- OS VHD link: The image stored in Azure shared image gallery. Learn how to capture your image in a shared image gallery.
Data disks (select Add data disk (maximum 16)) are also VHD shared access signature URIs that are stored in their Azure storage accounts. Add only one image per submission in a plan.
Regardless of which operating system you use, add only the minimum number of data disks that the solution requires. During deployment, customers can't remove disks that are part of an image, but they can always add disks during or after deployment.
If you provide your images using SAS and have data disks, you also need to provide them as SAS URI. If you are using shared image, they are captured as part of your image in shared image gallery. Once your offer is published to Azure Marketplace, you can delete the image from your Azure storage or shared image gallery.
Select Save draft, then select ← Plan overview at the top left to see the plan you just created.
Once your VM image has published, you can delete the image from your Azure storage.