Create a Managed Service offer

Managed Service offers help to enable Azure Lighthouse scenarios. When a customer accepts a Managed Service offer, they are then able to onboard resources for Azure delegated resource management. Before starting, Create a Commercial Marketplace account in Partner Center if you haven't done so yet. Ensure your account is enrolled in the commercial marketplace program.

You must have a Silver or Gold Cloud Platform competency level or be an Azure Expert MSP to publish a Managed Service offer.

Create a new offer

  1. Sign in to Partner Center.

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

  3. On the Overview page, select + New offer > Managed Service.

    Illustrates the left-navigation menu.

Note

After an offer is published, edits made to it in Partner Center only appear in online stores after republishing the offer. Make sure you always republish after making changes.

New offer

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.

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.

Select Create to generate the offer and continue.

Offer setup

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.

Per the Managed Services certification policies, a Lead Destination is required. This will create a record in your CRM system each time a customer deploys your offer.

For more information, see Lead management overview.

Select Save draft before continuing.

Properties

This page lets you define the categories used to group your offer on the marketplace and the legal contracts supporting your offer.

Category

Select a minimum of one and a maximum of five categories which will be used to place your offer into the appropriate marketplace search areas. Be sure to call out how your offer supports these categories in the offer description.

Terms and conditions

Provide your own legal terms and conditions in the Terms and conditions field. You can also provide the URL where your terms and conditions can be found. Customers will be required to accept these terms before they can try your offer.

Select Save draft before continuing.

Offer listing

This page lets you define marketplace details (such as offer name, description, and images) for your offer.

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 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), which may be used in marketplace search results.

Long summary

Provide a longer description of your offer (up to 256 characters). This long summary may also be used in marketplace 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.

Use HTML tags to format your description so it's more engaging. Most tags require both an opening and closing component, as shown in this table.

To do this Use Like this To get this
Bold <b> & </b> <b>Example</b>: Free trial Example: Free trial
Italics <i> & </i> Select the <i>first</i> row. Select the first row.
New line <br> This is my first line.<br>This is my second line. This is my first line.
This is my second line.
Paragraphs <p> & </p> <p>This is my first paragraph.</p>
<p>This is my second paragraph.</p>

This is my first paragraph.

This is my second paragraph.

Bullets <ul> & </ul>, <li> & </li> <ul>
<li>Your bullet item</li>
<li>Your bullet item</li>
<li>Your bullet item</li>
</ul>
• Your bullet item
• Your bullet item
• Your bullet item
Numbering <ol> & </ol>, <li> & </li> <ol>
<li>Your numbered item</li>
<li>Your numbered item</li>
<li>Your numbered item</li>
</ol>
1. Your numbered item
2. Your numbered item
3. Your numbered item
New line without new number (or bullet) <ol> & </ol>, <li> & </li>, <br> <ol>
<li>add text here</li>
<li>add text here<br>add text here</li>
</ol>
1. add text here
2. add text here
    add text here
New paragraph without new number (or bullet) <ol> & </ol>, <li> & </li>, <br> <ol>
<li>add text here</li>
<li>add text here<br><br>add text here</li>
</ol>
1. add text here
2. add text here

    add text here

Use headings <h1> & </h1>, <h2> & </h2>, up to <h6> & </h6> <h1>This is heading 1</h1>
<h2>This is heading 2</h2>
<h3>This is heading 3</h3>
This is heading 1
This is heading 2
This is heading 3

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

Provide optional supplemental online documents about your solution. Add additional useful links by clicking + Add a link.

Contact Information

In this section, you must provide the name, email, and phone number for a Support contact and an Engineering contact. This info is not shown to customers, but will be available to Microsoft, and may be provided to CSP partners.

Support URLs

If you have support websites for Azure Global Customers and/or Azure Government customers, provide those URLs here.

Marketplace images

In this section, you can provide logos and images that will be used when showing your offer to customer. All images must be in .png format.

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, make sure 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. All screenshots must be 1280 x 720 pixels.

Videos

You can optionally add up to five videos that demonstrate your offer. These videos should be hosted on YouTube and/or Vimeo. For each one, enter the video's name, its URL, and a thumbnail image of the video (1280 x 720 pixels).

Additional marketplace listing resources

Select Save draft before continuing.

Preview

Before you publish your offer live to the broader marketplace offer, you'll first need to make it available to a limited preview audience. This lets you confirm how you offer appears in the Azure Marketplace before making it available to customers. Microsoft support and engineering teams will also be able to view your offer during this preview period.

You can define the preview audience by entering Azure subscription IDs in the Preview Audience section. You can enter up to 10 subscription IDs manually, or upload a .csv file with up to 100 subscription IDs.

Any customers associated with these subscriptions will be able to view the offer in Azure Marketplace before it goes live. Be sure to include your own subscriptions here so you can preview your offer.

Select Save draft before continuing.

Plan overview

Each offer must have one or more plans (formerly called SKUs). You might add multiple plans to support different feature sets at different prices or to customize a specific plan for a limited audience of specific customers. Customers can view the plans that are available to them under the parent offer.

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.

On the Plan overview page, select + Create new plan. Then enter a Plan ID and a Plan name. Both of these values can only contain lowercase alphanumeric characters, dashes, and underscores, with a maximum of 50 characters. These values may be visible to customers, and they can't be changed after you publish the offer.

Select Create once you have entered these values to continue working on your plan. There are three sections to complete: Plan listing, Pricing and availability, and Technical configuration.

Plan listing

First, provide a Search results summary for the plan. This is a short description of your plan (up to 100 characters), which may be used in marketplace search results.

Next, enter a Description that provides a more detailed explanation of the plan.

Pricing and availability

Currently, there is only one pricing model that can be used for Managed Service offer: Bring your own license (BYOL). This means that you will bill your customers directly for costs related to this offer, and Microsoft does not charge any fees to you.

The Plan visibility section lets you indicate if this plan should be private. If you leave the This is a private plan box unchecked, your plan will not be restricted to specific customers (or to a certain number of customers).

Note

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

To make this plan available only to specific customers, select Yes. When you do so, you'll need to identify the customers by providing their subscription IDs. These can be entered one by one (for up to 10 subscriptions) or by uploading a .csv file (for a maximum of 10,000 subscriptions across all plans). Be sure to include your own subscriptions here so you can test and validate the offer.

Important

Once a plan has been published as public, you can't change it to private. To control which customers can accept your offer and delegate resources, use a private plan. With a public plan, you can't restrict availability to certain customers or even to a certain number of customers (although you can stop selling the plan completely if you choose to do so). You can remove access to a delegation after a customer accepts an offer only if you included an Authorization with the Role Definition set to Managed Services Registration Assignment Delete Role when you published the offer. You can also reach out to the customer and ask them to remove your access.

Technical configuration

This section of your plan creates a manifest with authorization information for managing customer resources. This information is required in order to enable Azure delegated resource management.

Be sure to review Tenants, roles, and users in Azure Lighthouse scenarios to understand which roles are supported and the best practices for defining your authorizations.

Note

As noted above, the users and roles in your Authorization entries will apply to every customer who purchases the plan. If you want to limit access to a specific customer, you'll need to publish a private plan for their exclusive use.

Manifest

First, provide a Version for the manifest. Use the format n.n.n (for example, 1.2.5).

Next, enter your Tenant ID. This is a GUID associated with the Azure Active Directory (Azure AD) tenant ID of your organization; that is, the managing tenant from which you will access your customers' resources. If you don't have this handy, you can find it by hovering over your account name on the upper right-hand side of the Azure portal, or by selecting Switch directory.

If you publish a new version of your offer and need to create an updated manifest, select + New manifest. Be sure to increase the version number from the previous manifest version.

Authorization

Authorizations define the entities in your managing tenant who can access resources and subscriptions for customers who purchase the plan. Each of these entities are assigned a built-in role that grants specific levels of access.

You can create up to twenty authorizations for each plan.

Tip

In most cases, you'll want to assign roles to an Azure AD user group or service principal, rather than to a series of individual user accounts. This lets you add or remove access for individual users without having to update and republish the plan when your access requirements change. When assigning roles to Azure AD groups, be sure that the the Group type is Security and not Office 365. For additional recommendations, see Tenants, roles, and users in Azure Lighthouse scenarios.

For each Authorization, you'll need to provide the following. You can then select + Add authorization as many times as needed to add more users and role definitions.

  • Azure AD Object ID: The Azure AD identifier of a user, user group, or application which will be granted certain permissions (as defined by the Role Definition) to your customers' resources.
  • Azure AD Object Display Name: A friendly name to help the customer understand the purpose of this authorization. The customer will see this name when delegating resources.
  • Role Definition: Select one of the available Azure AD built-in roles from the list. This role will determine the permissions that the user in the Azure AD Object ID field will have on your customers' resources. For descriptions of these roles, see Built-in roles and Role support for Azure Lighthouse.

    Note

    As applicable new built-in roles are added to Azure, they will become available here, although there may be some delay before they appear.

  • Assignable Roles: This option will appear only if you have selected User Access Administrator in the Role Definition for this authorization. If so, you must add one or more assignable roles here. The user in the Azure AD Object ID field will be able to assign these roles to managed identities, which is required in order to deploy policies that can be remediated. Note that no other permissions normally associated with the User Access Administrator role will apply to this user.

Tip

To ensure you can remove access to a delegation if needed, include an Authorization with the Role Definition set to Managed Services Registration Assignment Delete Role. If this role is not assigned, delegated resources can only be removed by a user in the customer's tenant.

Once you've completed all of the sections for your plan, you can select + Create new plan as many times as you need to create additional plans. When you're done, select Save.

Select Save draft before continuing.

Publish

Submit offer to preview

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

If it's your first time publishing this offer, you can:

  • See the completion status for each section of the offer.
    • Not started - The section has not been touched and needs to be completed.
    • Incomplete - 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 - 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.
  • In the Notes for certification section, 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.
  • Submit the offer for publishing by selecting Submit. We will send you an email 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).

Customer experience and offer management

When a customer deploys your offer, they will be able to delegate subscriptions or resource groups for Azure delegated resource management. For more about this process, see The customer onboarding process.

You can publish an updated version of your offer at any time. For example, you may want to add a new role definition to a previously-published offer. When you do so, customers who have already added the offer will see an icon in the Service providers page in the Azure portal that lets them know an update is available. Each customer will be able to review the changes and decide whether they want to update to the new version.

Next steps