Create an Azure application offer

This article explains the steps and considerations for creating a new Azure application offer in the commercial marketplace. You should be familiar with these concepts before you create a new Azure application offer.

Before you can publish a new Azure application offer, create a commercial marketplace account in Partner Center and make sure your account is enrolled in the commercial marketplace program.

Before you begin

Designing, building, and testing Azure application offers requires technical knowledge of both the Azure platform and the technologies used to build the offer. Your engineering team should have knowledge about the following Microsoft technologies:

Technical documentation and resources

Review the following resources as you prepare your Azure application offer for the commercial marketplace.

The video Building Solution Templates, and Managed Applications for the Azure Marketplace gives a comprehensive introduction to the Azure application offer type:

  • What offer types are available
  • What technical assets are required
  • How to author an Azure Resource Manager template
  • Developing and testing the app UI
  • How to publish the app offer
  • The application review process

Suggested tools

Choose one or both of the following scripting environments to help manage your Azure application:

We recommend adding the following tools to your development environment:

You can review the available tools in the Azure Developer Tools page. Also if you are using Visual Studio, the Visual Studio Marketplace.

Types of Azure application plans

There are two kinds of Azure application plans: solution templates and managed applications.

  • Solution template is one of the main ways to publish a solution in the Marketplace. Use this plan type when your solution requires additional deployment and configuration automation beyond a single virtual machine (VM). With a solution template, you can automate providing of more than one resource, including VMs, networking, and storage resources to provide complex IaaS solutions. For more information about building solution templates, see Azure Resource Manager.

  • Managed application is similar to solution templates, with one key difference. In a managed application, the resources are deployed to a resource group that's managed by the publisher of the app. The resource group is present in the consumer's subscription, but an identity in the publisher's tenant has access to the resource group. As the publisher, you specify the cost for ongoing support of the solution. Use Managed applications to easily build and deliver fully managed, turnkey applications to your customers. For more information about the advantages and types of managed applications, see the Azure managed applications overview.

Technical requirements

All Azure applications include at least two files in the root folder of a .zip archive:

All new Azure application offers must include an Azure partner customer usage attribution GUID.

To learn about publishing requirements for each application plan, see Solution template offer publishing requirements and Managed application offer publishing requirements.

Create a new offer

Note

After an offer is published, edits you make to it in Partner Center will not appear in online stores until you republish the offer. Make sure to always republish you offer after making changes.

  1. Sign in to Partner Center.

  2. In the left menu, select Commercial Marketplace > Overview.

  3. On the Overview page, select + New offer > Azure Application.

    Illustrates the left-navigation menu.

  4. On the New offer page, enter an Offer ID. This is a unique identifier for each offer in your account.

    • This ID is visible to customers in the web address for the marketplace offer and Azure Resource Manager templates, if applicable.
    • Use only lowercase letters and numbers. It can include hyphens and underscores, but no spaces, and is limited to 50 characters. For example, if you enter test-offer-1, the offer web address will be https://azuremarketplace.microsoft.com/marketplace/../test-offer-1.
    • The Offer ID can't be changed after you select Create.
  5. Enter an Offer alias. This is the name used for the offer in Partner Center.

    • This name isn't used in the marketplace and is different from the offer name and other values shown to customers.
    • The Offer alias can't be changed after you select Create.
  6. Select Create to generate the offer and continue.

Offer setup

The Offer setup page is where you can configure a test drive and lead management for your offer.

Test drive

A test drive is a great way to showcase your offer to potential customers by giving them the option to "try before you buy", resulting in increased conversion and the generation of highly qualified leads. Learn more about test drives.

To enable a test drive for a fixed period of time, select the Enable a test drive check box. To remove test drive from your offer, clear this check box. Configure the test drive environment in the Test drive technical configuration section later in this topic.

For additional information, see Test drive your offer in the commercial marketplace. You can also read about test drive best practices and download the Test drives overview PDF (make sure your pop-up blocker is off)

Note

Because all Azure applications are implemented using an Azure Resource Manager template, the only type of test drive available for an Azure Application is an Azure Resource Manager based test drive.

Customer leads

When you publish your offer to the commercial marketplace via Partner Center, you need to connect your offer to your CRM system. This way, you can receive customer contact information immediately after a customer expresses interest or deploys your product.

  1. Select a lead destination where you want us to send customer leads. The following CRM systems are supported:

    If your CRM system isn't explicitly supported in this list, you can store the customer lead data by using the following options. Then you can export or import this data into your CRM system.

  2. Read the applicable linked documentation above to learn how to set up your lead destination and receive leads from your commercial marketplace offers.

  3. After you've connected your offer to your lead destination, select Publish on your offer in Partner Center. We'll validate the connection and send you a test lead. When you view the offer before you go live, you can also test your lead connection by trying to acquire the offer yourself in the preview environment.

  4. Make sure the connection to the lead destination stays up to date so you don't lose any leads. Make sure you update these connections whenever something has changed.

For more information, see Lead management overview.

Select Save draft before continuing.

Properties

The Properties page is where you define the categories used to group your offer on the marketplace, your app version, and the legal contracts supporting your offer.

Category

Select categories and subcategories to place your offer in the appropriate marketplace search areas. Be sure to describe how your offer supports these categories in the offer description. Select:

  • At least one and up to two categories, including a primary and a secondary category (optional).
  • Up to two subcategories for each primary and/or secondary category. If no subcategory is applicable to your offer, select Not applicable.

See the full list of categories and subcategories in Offer Listing Best Practices.

Microsoft provides a standard contract template for the commercial marketplace.

  • Use the Standard Contract for the Microsoft commercial marketplace?

To simplify the procurement process for customers and reduce legal complexity for software vendors, Microsoft offers a Standard Contract for the Microsoft commercial marketplace to help facilitate transactions in the marketplace. Rather than crafting custom terms and conditions, commercial marketplace publishers can choose to offer their software under the Standard Contract, which customers only need to vet and accept once. The Standard Contract can be found here: https://go.microsoft.com/fwlink/?linkid=2041178.

You can select to use the Standard Contract instead of providing your own custom terms and conditions by selecting "Use the Standard Contract for the commercial marketplace" checkbox.

Using the Standard Contract checkbox

Note

Once you publish an offer using the Standard contract for Microsoft commercial marketplace, you're not able to use your own custom terms and conditions. It's an "or" scenario. You either offer your solution under the Standard Contract or your own terms and conditions. If you would like to modify the terms of the Standard Contract, you can do so through Standard Contract Amendments.

Standard Contract Amendments

Standard Contract Amendments let publishers select the Standard Contract terms for simplicity and customize the terms for their product or business. Customers only need to review the amendments to the contract, if they have already reviewed and accepted the Microsoft Standard Contract.

There are two kinds of amendments available for commercial marketplace publishers:

  • Universal Amendments: These amendments are applied universally to the Standard Contract for all customers. Universal amendments are shown to every customer of the offer in the purchase flow. Customers must accept the terms of the Standard Contract and the amendment before they can use your offer.
  • Custom Amendments: These amendments are special amendments to the Standard Contract that are targeted to specific customers only via Azure tenant IDs. Publishers can choose the tenant they want to target. Only customers from the tenant will be presented with the custom amendment terms in the offer's purchase flow. Customers must accept the terms of the Standard Contract and the amendment(s) before they can use your offer.

Note

These two types of amendments stack on top of each other. Customers targeted with custom amendments will also get the universal amendment to the Standard Contract during purchase.

Universal amendment terms to the Standard Contract for Microsoft's commercial marketplace: Enter the universal amendment terms in this box. You can provide a single universal amendment per offer. You can enter an unlimited number of characters in this box. These terms are displayed to customers in AppSource, Azure Marketplace, and/or Azure portal during the discovery and purchase flow.

Custom amendment terms to the Standard Contract for Microsoft's commercial marketplace: Start by selecting Add custom amendment terms. You can provide up to 10 custom amendment terms per offer.

  • Custom amendment terms: Enter your custom amendment terms in the custom amendment terms box. You can enter an unlimited number of characters in this box. Only customers from the tenant IDs you specify for these custom terms will be presented with the custom amendment terms in the offer's purchase flow in the Azure portal.
  • Tenant IDs (required): Each custom amendment can be targeted to up to 20 tenant IDs. If you add a custom amendment, you must provide at least one tenant ID. The tenant ID identifies your customer in Azure. You can ask your customer for this ID and they can find it by navigating to portal.azure.com > Azure Active Directory > Properties. The directory ID value is the tenant ID (for example, 50c464d3-4930-494c-963c-1e951d15360e). You can also look up the organization's tenant ID of your customer by using their domain name URL at What is my Microsoft Azure and Microsoft 365 tenant ID?.
  • Description (optional): Optionally provide a friendly description for the tenant ID that helps you identify the customer you're targeting with the amendment.

Terms and conditions

If you want to provide your own custom terms and conditions, you can elect to enter them in the terms and conditions field. You can enter up to 10,000 characters of text in this field. If your terms and conditions require a longer description, enter a single URL link into this field where your terms and conditions can be found. It will display to customers as an active link.

Customers are required to accept these terms before they can try your offer.

Select Save draft before continuing.

Offer listing

This page is where you manage the copy and images for your commercial marketplace offer.

Marketplace details

Note

Offer listing content (such as the description, documents, screenshots, and terms of use) is not required to be in English, as long as the offer description begins with the phrase, "This application is available only in [non-English language]." It is also acceptable to provide a Useful Link URL to offer content in a language other than the one used in the Offer listing content.

Here's an example of how offer information appears in Azure Marketplace (any listed prices are for example purposes only and not intended to reflect actual costs):

Illustrates how this offer appears in Azure Marketplace.

Call-out descriptions

  1. Logo
  2. Categories
  3. Support address (link)
  4. Terms of use
  5. Privacy policy address (link)
  6. Offer name
  7. Summary
  8. Description
  9. Screenshots/videos


Here's an example of how offer information appears in the Azure portal:

Illustrates how this offer appears in the Azure portal.

Call-out descriptions

  1. Title
  2. Description
  3. Useful links
  4. Screenshots

Name

The name you enter here will be shown to customers as the title of your offer listing. This field is pre-populated with the text you entered for Offer alias when you created the offer, but you can change this value. This name may be trademarked (and you may include trademark or copyright symbols). The name can't be more than 50 characters and can't include any emojis.

Search results summary

Provide a short description of your offer, up to 100 characters. This description may be used in search results.

Long summary

Provide a longer description of your offer, up to 256 characters. This description may be used in search results.

Description

Provide a longer description of your offer, up to 3,000 characters. Customers will see this in the Marketplace listing overview.

Include one or more of the following items in your description:

  • The value and key benefits of your offer
  • Category and/or industry associations
  • In-app purchase opportunities
  • Any required disclosures

Here are some tips for writing your description:

  • Clearly describe the value of your offer in the first few sentences, including:
    • Description of the offer.
    • The type of user who benefits from the offer.
    • Customer needs or issues that the offer addresses.
  • Remember that the first few sentences might be displayed in search results.
  • Don't rely on features and functionality to sell your product. Focus on the value your offer provides.
  • Use industry-specific vocabulary or benefit-based wording.

To make your offer description more engaging, use the rich text editor to apply formatting.

Using the rich text editor

Change text format
Add bullets or numbering
Add or remove text indent
Using the rich text editor to change text format
Using the rich text editor to add lists
Using the rich text editor to indent

Search keywords

You can optionally enter up to three search keywords to help customers find your offer in the marketplace. For best results, also use these keywords in your description.

Enter the URL to your organization's privacy policy. You are responsible for ensuring your app complies with privacy laws and regulations, and for providing a valid privacy policy.

Add links to optional supplemental online documents about your solution by selecting + Add a link.

Contact information

Provide the name, email, and phone number for a Support contact, Engineering contact, and CSP Program contact. This info is not shown to customers, but will be available to Microsoft and may be provided to CSP partners. Some contacts may require additional information.

Marketplace media

Provide logos and images to use with your offer. All images must be in PNG format. Blurry images will cause your submission to be rejected.

Follow these guidelines for your logos:

  • The Azure design has a simple color palette. Limit the number of primary and secondary colors on your logo.
  • The theme colors of the portal are white and black. Don't use these colors as the background color for your logo. Use a color that makes your logo prominent in the portal. We recommend simple primary colors.
  • If you use a transparent background, make sure that the logo and text aren't white, black, or blue.
  • The look and feel of your logo should be flat and avoid gradients in the logo or background. Don't place text on the logo, not even your company or brand name.
  • Make sure the logo isn't stretched.

Note

If you have an issue uploading files, ensure your local network does not block the https://upload.xboxlive.com service used by Partner Center.

Store logos

Provide a PNG file for the Large size logo. Partner Center will use this to create a Small and a Medium logo. You can optionally replace these with different images later.

  • Large (from 216 x 216 to 350 x 350 px, required)
  • Medium (90 x 90 px, optional)
  • Small (48 x 48 px, optional)

These logos are used in different places in the listing:

  • The large logo appears on your offer listing page in Azure Marketplace.
  • The medium logo (optional) appears when you create a new resource in Microsoft Azure.
  • The small logo (optional) appears in Azure Marketplace search results.

Follow these guidelines for your logos:

  • The Azure design has a simple color palette. Limit the number of primary and secondary colors on your logo.
  • The theme colors of the portal are white and black. Don't use these colors as the background color for your logo. Use a color that makes your logo prominent in the portal. We recommend simple primary colors.
  • If you use a transparent background, make sure that the logo and text aren't white, black, or blue.
  • The look and feel of your logo should be flat and avoid gradients in the logo or background. Don't place text on the logo, not even your company or brand name.
  • Make sure the logo isn't stretched.

Screenshots

Add up to five screenshots that show how your offer works. Each screenshot must be 1280 x 720 pixels in size and in PNG format. Each screenshot must include a caption.

Videos

Add up to five videos that demonstrate your offer. These should be hosted on an external video service. Enter each video's name, web address, and a thumbnail PNG image of the video at 1280 x 720 pixels.

Additional marketplace listing resources

Select Save draft before continuing.

Preview audience

On the Preview tab, choose a limited Preview Audience for validating your offer before you publish it live to the broader marketplace audience.

Important

After checking your offer in Preview, select Go live to publish your offer to the commercial marketplace public audience.

Your preview audience is identified by Azure subscription ID GUIDs, along with an optional description for each. Neither of these fields can be seen by customers. You can find your Azure subscription ID on the Subscriptions page in Azure portal.

Add at least one Azure subscription ID, either individually (up to 10) or by uploading a CSV file (up to 100). By adding these subscription IDs, you define who can preview your offer before it is published live. If your offer is already live, you may still define a preview audience for testing offer changes or updates to your offer.

Note

A preview audience differs from a private audience. A preview audience can access to your offer before it's published live in the marketplaces. They can see and validate all plans, including those which will be available only to a private audience after your offer is fully published to the marketplace. A private audience (defined in the plan Pricing and Availability tab) has exclusive access to a particular plan.

Select Save draft before continuing.

Technical configuration

Complete this section only if your offer includes a managed application that will emit metering events using the Marketplace Metering Service API. Enter the Azure Active Directory tenant ID and Azure Active Directory application ID your service will use when emitting metering events.

Select Save draft before continuing.

Technical configuration (offer level)

Note

Offer-level technical details are optional. You only need to configure these details if you are publishing a managed application with metered billing and have a service which will be authenticating with an Azure AD security token. For more information, see authentication strategies on the different authentication options.

The technical configuration defines the details (tenant ID, and app ID) used to identity your service, which will emit metering events for a managed application using the Marketplace metering service APIs. Enter the identity that your service will use when emitting metering events.

  • Azure AD tenant ID (required): Inside the Azure portal, you must create an Azure Active Directory (AD) app so we can validate the connection between our two services is behind an authenticated communication. To find the tenant ID), go to your Azure Active Directory and select Properties, then look for the Directory ID number listed (for example 50c464d3-4930-494c-963c-1e951d15360e).
  • Azure AD app ID (required): You also need your application ID) and an authentication key. To get those values, go to your Azure Active Directory and select App registrations, then look for the Application ID number listed (for example 50c464d3-4930-494c-963c-1e951d15360e). To find the authentication key, go to Settings and select Keys. You will need to provide a description and duration and will then be provided a number value.

Note

The Azure application ID will be associated to your publisher ID, and can only be re-used within this publisher account.

Note

This configuration is required if you want to use Batch usage event). In case you want to submit usage event), you can also use the instance metadata service to get the JSON web token (JWT) bearer token).

Plan overview

This tab enables you to provide different plan options within the same offer. These plans (formerly called SKUs) can differ in terms of plan type (solution template vs. managed application), monetization, or audience. Configure at least one plan in order to list your offer in the marketplace.

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.

Once created, you will see your plan names, IDs, plan type, availability (Public or Private), current publishing status, and any available actions on this tab.

Actions available in the Plan overview vary depending on the current status of your plan and may include:

  • If the plan status is Draft – Delete draft.
  • If the plan status is Live – Stop sell plan or Sync private audience.

Create new plan

Plan ID – Create a unique plan ID for each plan in this offer. This ID will be visible to customers in the product URL. Use only lowercase, alphanumeric characters, dashes, or underscores. A maximum of 50 characters are allowed for this plan ID. This ID cannot be modified after selecting create.

Plan name – Customers will see this name when deciding which plan to select within your offer. Create a unique offer name for each plan in this offer. The plan name is used to differentiate software plans that may be a part of the same offer (For example, offer name: Windows Server; plans: Windows Server 2016, Windows Server 2019).

Plan setup

This tab enables you to set the high-level configuration for the type of plan, whether it reuses packages from another plan, and what clouds the plan should be available in. Your answers on this tab will affect which fields are displayed on other tabs for the same plan.

Plan type

Select the type of plan for your offer. A Solution template plan is managed entirely by the customer. A Managed application plan enables publishers to manage the application on behalf of the customer. For details, see Types of Azure application plans.

Re-use technical configuration

If you have more than one plan of the same type and the packages are identical between them, you may select this plan reuses packages from another plan. When you select this option, you will be able to select one of the other plans of the same type for this offer to reuse packages from.

Note

When you re-use packages from another plan, the entire Technical configuration tab will disappear from this plan. The Technical configuration details from the other plan, including any updates that you make in the future, will be used for this plan as well.

This setting cannot be changed after this plan is published.

Azure regions (cloud)

Your plan must be made available in at least one Azure region.

Select the Azure Global option to make your plan available to customers in all Azure Global regions that have commercial marketplace integration. For details, see Geographic availability and currency support.

Select the Azure Government option to make your plan available in the Azure Government region. This region provides controlled access for customers from U.S. federal, state, local, or tribal entities, as well as partners eligible to serve them. You, as the publisher, are responsible for any compliance controls, security measures, and best practices. Azure Government uses physically isolated data centers and networks (located in the U.S. only).

Before publishing to Azure Government, test and validate your plan in the environment as certain endpoints may differ. To set up and test your plan, request a trial account from Microsoft Azure Government trial.

Note

After your plan is published and available in a specific Azure region, you can't remove that region.

Azure Government certifications

This option is only visible if you selected Azure Government.

Azure Government services handle data that is 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 visible to Azure Government customers only.

Select Save draft before continuing.

Plan listing

This is where you configure listing details of the plan. This tab displays specific information that can differ between plans in the same offer.

Plan name

This is pre-filled in with the name you gave your plan when you created it. This name appears in the marketplace as the title of this plan and is limited to 100 characters.

Plan summary

Provide a short summary of your plan (not the offer). This summary is limited to 100 characters.

Plan description

Describe what makes this software plan unique, as well as differences between plans within your offer. Don't describe the offer, just the plan. The plan description can contain up to 2,000 characters.

Select Save draft before continuing.

Availability (solution template plans only)

You can make the plan visible to everyone, only to specific customers (a private audience), and whether to make the plan hidden for use by other solution template or managed applications only.

Plan visibility

You can configure each plan to be visible to everyone or to only a specific audience of your choosing. You can assign membership in this restricted audience using Azure subscription IDs.

Select This is a private plan to make your plan private and visible only to the restricted audience of your choosing. Once published as a private plan, you can update the audience or choose to make the plan available to everyone. Once a plan is published as visible to everyone, it must remain visible to everyone; it cannot be reconfigured as a private plan.

If you make the plan private, enter an Azure subscription IDs and its description. Each is an audience that will have access to this private plan. Access is assigned using Azure subscription IDs with the option to include a description of each Azure subscription ID assigned. Add up to 10 customers subscription IDs individually, or 20,000 by importing a CSV file. Azure subscription IDs are represented as GUIDs and letters must be lowercase.

Note

A private or restricted audience is different from the preview audience you defined on the Preview tab. A preview audience can access your offer before its published live in the marketplace. While the private audience choice only applies to a specific plan, the preview audience can view all plans (private or not) for validation purposes.

Hide plan

If your solution template is intended to be deployed only indirectly when referenced though another solution template or managed application, check this box to publish your solution template but hide it from customers searching and browsing for it directly.

Select Save draft before continuing.

Pricing and availability (managed application plans only)

Use it to configure the Markets this plan will be available in, the Pricing per month of the management of the solution, and the Plan visibility if only specific customers should see it (a private audience).

Select Save draft before continuing.

Markets

Every plan must be available in at least one market. Select the checkbox for any market location where you would like to make this plan available. A search box and button for selecting "Tax Remitted" countries/regions, in which Microsoft remits sales and use tax on your behalf, are included to help.

If you have already set prices for your plan in United States Dollars (USD) and add another market location, the price for the new market will be calculated according to the current exchange rates. Always review the price for each market before publishing. Pricing can be reviewed by using the "Export prices (xlsx)" link after saving your changes.

Pricing

Provide the per-month price for this plan. This price is in addition to any Azure infrastructure or pay-as-you-go software costs incurred by the resources deployed by this solution.

In addition to the per-month price, you can also set prices for consumption of non-standard units using metered billing. You may set the per-month price to zero and charge exclusively using metered billing if you like.

Prices set in USD (USD = United States Dollar) are converted into the local currency of all selected markets using the current exchange rates when saved. Validate these prices before publishing by exporting the pricing spreadsheet and reviewing the price in each market. If you would like to set custom prices in an individual market, modify and import the pricing spreadsheet.

Note

You must first save your pricing changes to enable export of pricing data.

Review your prices carefully before publishing, as there are some restrictions on what can change after a plan is published.

Note

Once a price for a market in your plan is published, it can't be changed later.

Plan visibility

You can configure each plan to be visible to everyone or to only a specific audience of your choosing. You can assign membership in this restricted audience using Azure subscription IDs.

Select This is a private plan to make your plan private and visible only to the restricted audience of your choosing. Once published as a private plan, you can update the audience or choose to make the plan available to everyone. Once a plan is published as visible to everyone, it must remain visible to everyone; it cannot be reconfigured as a private plan.

Note

A private or restricted audience is different from the preview audience you defined on the Preview tab. A preview audience can access your offer before its published live in the marketplace. While the private audience choice only applies to a specific plan, the preview audience can view all plans (private or not) for validation purposes.

If you make the plan private, enter an Azure subscription IDs and its description. Each is an audience that will have access to this private plan. Access is assigned using Azure subscription IDs with the option to include a description of each Azure subscription ID assigned. Add up to 10 customers subscription IDs individually, or 20,000 by importing a CSV file. Azure subscription IDs are represented as GUIDs and letters must be lowercase.

Note

Private offers are not supported with Azure subscriptions established through a reseller of the Cloud Solution Provider program (CSP).

Technical configuration

This tab lets you upload the deployment package that will allow customers to deploy your plan.

Note

This tab will not be visible if you configured this plan to re-use packages from another plan on the Plan setup tab.

Package details

This tab lets you edit the draft version of your technical configuration.

Version – Assign the current version of the technical configuration. Increment this version each time you publish a change to this page. Version must be in the format {integer}.{integer}.{integer}.

Package file (.zip) – This package contains all of the template files needed for this plan, as well as any additional resources, packaged as a .zip file.

All Azure application plan packages must include these two files in the root folder of a .zip archive:

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

All new Azure application offers must also include an Azure partner customer usage attribution GUID.

Note

If you have an issue uploading files, make sure your local network does not block the https://upload.xboxlive.com service used by Partner Center.

Managed application plans require additional information on this tab.

Previously published packages

The Previously published packages sub-tab enables you to view all published versions of your technical configuration.

Enable just-in-time (JIT) access

Select this option to enable Just-in-time (JIT) access for this plan. JIT access enables you to request elevated access to a managed application's resources for troubleshooting or maintenance. You always have read-only access to the resources, but for a specific time period you can have greater access. For more information, see Enable and request just-in-time access for Azure Managed Applications. To require that consumers of your managed application grant your account permanent access, leave this option unchecked.

Note

Be sure to update your createUiDefinition.json file in order to support this feature.

Deployment mode

Select whether to configure Complete or Incremental deployment mode when deploying this plan:

  • In complete mode, a redeployment of the application by the customer will result in removal of resources in the managed resource group if the resources are not defined in the mainTemplate.json.
  • In incremental mode, a redeployment of the application leaves existing resources unchanged.

To learn more about deployment modes, see Azure Resource Manager deployment modes.

Notification endpoint URL

Specify an HTTPS Webhook endpoint to receive notifications about all CRUD operations on managed application instances of this plan version.

Customize allowed customer actions

Select this option to specify which actions customers can perform on the managed resources in addition to the "*/read" actions that is available by default.

List the additional actions you would like to enable your customer to perform here, separated by semicolons. For more information, see Understanding deny assignments for Azure resources. For available actions, see Azure resource provider operations. For example, to permit consumers to restart virtual machines, add Microsoft.Compute/virtualMachines/restart/action to the allowed actions.

Global Azure / Azure Government Cloud

Indicate who should have management access to this managed application in each supported cloud. Users, groups, or applications that you want to be granted permission to the managed resource group are identified using Azure Active Directory (AD) identities.

Azure Active Directory Tenant ID – The Azure AD Tenant ID (also known as directory ID) containing the identities of the users, groups, or applications you want to grant permissions to. You can find your Azure AD Tenant ID on the Azure portal, in Properties for Azure Active Directory.

Authorizations – Add the Azure Active Directory object ID of the user, group, or application that you want to be granted permission to the managed resource group. Identify the user by their Principal ID, which can be found at the Azure Active Directory users blade on the Azure portal.

For each principal, select one of the Azure AD built-in roles from the list (Owner or Contributor). The role you select will describe the permissions the principal will have on the resources in the customer subscription. For more information, see Azure built-in roles. For more information about Azure role-based access control (Azure RBAC), see What is Azure RBAC.

Note

Although you may add up to 100 authorizations per cloud, it's generally easier to create an Active Directory user group and specify its ID in the "Principal ID." This will allow you to add more users to the management group after the plan is deployed and reduce the need to update the plan just to add more authorizations.

Policy settings

Apply Azure Policies to your managed application to specify compliance requirements for the deployed solution. For policy definitions and the format of the parameter values, see Azure Policy Samples. You can configure a maximum of five policies, and only one instance of each Policies option. Some policies require additional parameters. The Standard SKU is required for audit policies. Policy Name is limited to 50 characters.

Select Save draft before continuing.

Co-sell with Microsoft

Providing information on the Co-sell tab is entirely optional for publishing your offer. It is required to achieve Co-sell Ready and IP Co-sell Ready status. The information you provide will be used by Microsoft sales teams to learn more about your solution when evaluating its fit for customer needs. It is not available directly to customers.

For details on this tab, see Co-sell option in Partner Center.

Resell through CSPs

Expand the reach of your offer by making it available to partners in the Cloud Solution Providers (CSP) program. This allows resellers to sell your offer to their customers and create bundled solutions.

Select Save draft before continuing.

Test drive

Set up a demonstration (test drive) that lets customers try your offer before purchasing it. To create a demonstration environment that lets customers try your offer for a fixed period of time, see Test Drive your offer in the commercial marketplace.

To enable a test drive, select the Enable a test drive check box on the Offer setup tab. To remove test drive from your offer, clear this check box.

Test drive technical configuration

  • Azure AD app ID (required): Enter your Azure Active Directory (AD) application ID). To find this ID, sign in to the Azure portal, select the Active Directory tab in the left-menu, select App registrations, then look for the Application ID number listed (such as 50c464d3-4930-494c-963c-1e951d15360e).

Deployment subscription details

To allow the Test Drive to be deployed on your behalf, create and provide a separate, unique Azure Subscription (not required for Power BI test drives).

  • Azure subscription ID (required for Azure Resource Manager and Logic apps) – Enter the subscription ID to grant access to your Azure account services for resource usage reporting and billing. We recommend that you consider creating a separate Azure subscription to use for test drives if you don't have one already. You can find your Azure subscription ID by logging in to the Azure portal and navigating to the Subscriptions tab of the left-side menu. Selecting the tab will display your subscription ID (such as "a83645ac-1234-5ab6-6789-1h234g764ghty").
  • Azure AD tenant ID (required) – Enter your Azure Active Directory (AD) tenant ID). To find this ID, sign in to the Azure portal, select the Active Directory tab in the left-menu, select Properties, then look for the Directory ID number listed (such as 50c464d3-4930-494c-963c-1e951d15360e). You can also look up your organization's tenant ID using your domain name URL at: https://www.whatismytenantid.com.
  • Azure AD tenant name (required for Dynamic 365) – Enter your Azure Active Directory (AD) name. To find this name, sign in to the Azure portal, in the upper right corner your tenant name will be listed under your account name.
  • Azure AD app ID (required) – Enter your Azure Active Directory (AD) application ID). To find this ID, sign in to the Azure portal, select the Active Directory tab in the left-nav menu, select App registrations, then look for the Application ID number listed (such as 50c464d3-4930-494c-963c-1e951d15360e).
  • Azure Active Directory application client secret (required) – Enter your Azure AD application client secret). To find this value, sign in to the Azure portal. Select the Azure Active Directory tab in the left-nav menu, select App registrations, then select your test drive app. Next, select Certificates and secrets, select New client secret, enter a description, select Never under Expires, then choose Add. Make sure to copy down the value before leaving this page.)

Select Save draft before continuing.

Marketplace listing (optional)

Describe the test drive experience.

  • Description (required) – Describe your test drive, what will be demonstrated, objectives for the user to experiment with, features to explore, and any relevant information to help the user determine whether to acquire your offer. Up to 3,000 characters of text can be entered in this field.
  • Access information (required for Azure Resource Manager and Logic test drives) – Explain what a customer needs to know in order to access and use this test drive. Walk through a scenario for using your offer and exactly what the customer should know to access features throughout the test drive. Up to 10,000 characters of text can be entered in this field.
  • User Manual (required) – An in-depth walk-through of your test drive experience. The User Manual should cover exactly what you want the customer to gain from experiencing the test drive and serve as a reference for any questions that they may have. The file must be in PDF format and be named (255 characters max) after uploading.
  • Videos: Add videos (optional) – Videos can be uploaded to YouTube or Vimeo and referenced here with a link and thumbnail image (533 x 324 pixels) so a customer can view a walk-through of information to help them better understand the test drive, including how to successfully use the features of your offer and understand scenarios that highlight their benefits.
    • Name (required)
    • Address (YouTube or Vimeo only; required)
    • Thumbnail (Image file must be in PNG format and 533 x 324 pixels).

Select Save draft before continuing.

Publish

When you have completed all the required sections of the offer, select Review and publish in the top-right corner of the portal.

Review the completion status for each section of the offer. - Not started – means the section has not been touched and needs to be completed. - Incomplete – means the section has errors that need to be fixed or requires more information to be provided. Go back to the section(s) and update it. - Complete – means the section is complete, all required data has been provided and there are no errors. All sections of the offer must be in a complete state before you can submit the offer.

If this is your first time publishing this offer, you can provide testing instructions to the certification team to ensure that your app is tested correctly, in addition to any supplementary notes helpful for understanding your app.

Select Submit to submit your offer for publishing. We will send you an email to let you know when a preview version of the offer is available for you to review and approve.

Return to Partner Center and select Go-live for the offer to publish your offer to the public (or if a private offer, to the private audience).

Errors and review feedback

The Manual validation step in the publishing process represents an extensive review of your offer and its associated technical assets (especially the Azure Resource Manager template), issues are typically presented as pull request (PR) links. An explanation of how to view and respond to these PRs, see Handling review feedback.

If you have errors in one or more of the publishing steps, correct them before republishing your offer.

Next steps