Plan a solution template for an Azure application offer
This article explains the requirements for publishing a solution template plan for an Azure Application offer. A solution template plan is the only one type of plan supported by Azure Application offers. For more information about the plan type, see Types of plans. If you haven't already done so, read Plan an Azure application offer.
The solution template plan type requires an Azure Resource Manager template (ARM template) to automatically deploy your solution infrastructure.
Solution template requirements
| Requirements | Details |
|---|---|
| Billing and metering | Solution template plans are not transactable, but they can be used to deploy paid VM offers that are billed through the Azure commercial marketplace. The resources that the solution's ARM template deploys are set up in the customer's Azure subscription. Standard Pay-in-Advance Offer virtual machines are transacted with the customer via Azure and billed via the customer's Azure subscription. For bring-your-own-license (BYOL) billing, although Azure bills infrastructure costs that are incurred in the customer subscription, you transact your software licensing fees with the customer directly. |
| Azure-compatible virtual hard disk (VHD) | VMs must be built on Windows or Linux. For more information, see:
|
| Customer usage attribution | Enabling customer usage attribution is required on all solution templates that are published on Azure Marketplace. |
| Use managed disks | Managed disks is the default option for persisted disks of infrastructure as a service (IaaS) VMs in Azure. You must use managed disks in solution templates.
|
| Deployment package | You'll need a deployment package that will let customers deploy your plan. If you create multiple plans that require the same technical configuration, you can use the same plan package. For details, see the next section: Deployment package. |
Deployment package
The deployment package contains all the template files needed for this plan, as well as any additional resources, packaged as a .zip file.
All Azure applications must include these two files in the root folder of a .zip archive:
- A Resource Manager template file named mainTemplate.json. This template defines the resources to deploy into the customer's Azure subscription. For examples of Resource Manager templates, see the Azure Quickstart Templates gallery or the corresponding GitHub: Azure Resource Manager Quickstart Templates repo.
- A user interface definition for the Azure application creation experience named createUiDefinition.json. In the user interface, you specify elements that enable consumers to provide parameter values.
Maximum file sizes supported are:
- Up to 1 Gb in total compressed .zip archive size
- Up to 1 Gb for any individual uncompressed file within the .zip archive
Tip
Make sure your offer is compliant with our recommended practices by using the ARM template test toolkit before publishing your Azure Application.
Choose who can see your plan
For solution template plans, you can also choose to hide the plan from Azure Marketplace. You might want to do this if the plan is only deployed indirectly through another solution template or managed application.
Note
Private plans are not supported with Azure subscriptions established through a reseller of the Cloud Solution Provider program (CSP).
For more information, see Private offers in the Azure commercial marketplace .