Publish Offer
Create the listing in Partner Center and publish the offer.
Introduction
Now that we have the “technical assets” prepared for our offer, we can proceed to publish via Partner Center. This involves a number of steps including configuring the offer, setting up the listing details and assets and configuring plans, all done through Partner Center.
Create a New Offer
-
Login to Partner Center and navigate to: Commercial Marketplace -> Overview
-
At the top of the screen, Select: New Offer -> Azure Application
-
Enter an
Offer ID
andOffer alias
. TheOffer ID
must be unique within your account. TheOffer alias
is a friendly name for use within Partner Center.You may want to create an
Offer alias
something like “TEST_OFFER_DO_NOT_PUBLISH_xxxxxxx” to guard against the offer being inadvertently published by another user or in the future.
Offer Setup
Here we enter fundamental details about the offer and can connect a destination for Customer leads generated through the marketplace. For the purposes of the lab, complete as follows:
- Alias
- Leave per above
- Test drive
- Leave unchecked
- Customer leads
- Leave as “No CRM System connected'
Properties
Here we define the relevant categories the offer should appear in the marketplace and the legal terms. For the purposes of the lab, complete as follows:
- Categories
- Add a
Primary category
andSubcategory
eg Media / Media Services
- Add a
- Legal
-
Check the
Use the Standard Contract...
checkboxBe sure to Save draft before exiting the page
-
Offer listing
Here we define how the offer will appear in the marketplace - the offer listing itself and relevant metadata. For the purposes of the lab, complete as follows:
- Marketplace details
- Enter some text in each of the
Name
,Search results summary
,Short description
andDescription
fields - For the
Privacy policy link
enter any valid URL
- Enter some text in each of the
- Product information links
- Leave any non-required fields blank
- Complete the required fields with name, email and phone
- Marketplace media
-
Only the Large logo is required
-
You can use your own image or the image here
Be sure to Save draft before exiting the page
-
Preview audience
A preview audience is able to browse and acquire an offer before it is published in the marketplace. This is intended as a testing mechanism and to provide a limited audience with a preview of the offer. The offer does not go through full certification so it is possible to review and test with the inherent delay that involves. It will take a few hours for a preview to become available as opposed to a few days for a full publish and certification cycle.
As we will not be going through the full publish process it is important a Preview audience is specified otherwise we will not be able to test our efforts. For the purposes of the lab, complete as follows:
-
Enter your Azure Subscription ID in the
Azure Subscription ID
field and a suitable description in theDescription
field -
You can add multiple subscription IDs but for the lab one will be sufficient
Be sure to Save draft before exiting the page
Technical Configuration
- This section can be skipped. It is only required to authenticate solutions using metered billing where the deployed solution is not the source of events being reported to the metered billing API.
Plan overview
At least one plan is required for every offer. You can think of the offer as a container for plans which detail the
- Select
Create new plan
(at the top of the page) - Enter a
Plan ID
andPlan name
and selectCreate
- You will enter a series of pages to define the individual plan
Plan setup
This is the “high-level configuration” for the plan. For the purposes of the lab, complete as follows:
-
Plan type
- selectManaged application
-
Azure regions
- leave asAzure Global
checked andAzure Government
uncheckedBe sure to Save draft before exiting the page
Plan listing
This is the marketplace listing for the plan. eg we might have a bronze, silver, gold plan or “5 users”, “25 users” etc. They share the same offer but may provide different capabilities or licence conditions. For the purposes of the lab, complete as follows:
-
Plan name
should be pre-populated. Leave as is. -
Enter some short text for
Plan summary
andPlan description
Be sure to Save draft before exiting the page
Pricing and Availability
Here we describe which markets we want to make the offer available and the pricing model and price point. For the purposes of the lab, complete as follows:
-
Markets
- selectEdit markets
and add your own market (eg UK) and any other regions you choose -
Pricing
- we will set a flat rate price of $0 per month. Enter 0 in thePrice
field- It is useful to create $0 plans for testing as it is in effect a transactable offer but there is no risk of being billed if we forget to cancel a purchase
- We could enter metering dimensions at this stage for custom billing but we will keep things simple for now
-
Plan visibility
- leave as “Public”Be sure to Save draft before exiting the page
Technical configuration
This is what all the work in the previous sections was leading up to. This is where we reference the assets we’ve created and provide the deployment package to the marketplace. For the purposes of the lab, complete as follows:
-
Reuse technical configuration
- leave unchecked -
Version
- enter 1.0.0 -
Note the Customer usage attribution ID
-
Upload your deployment package zip file. It will take a few moments to be ingested
-
Enable just-in-time (JIT) access
- leave unchecked- JIT access allows the customer to control publisher access to the deployed solution
-
Deployment mode
- leave asComplete
-
Notification Endpoint URL
- leave blank- It is possible to provide a webhook endpoint to get notifications of operations on the managed application
-
Customize allowed customer actions
- leave unchecked- By default, the customer has read-only access to the Managed resource group. The publisher can grant additional permissions via ‘allowed customer actions’
-
Public Azure
- Here we will enter details of the security principals that will be granted RBAC permissions on the Managed resource group in the customer tenant. If you can use an identity from a different AAD tenant than the ‘target’ tenant you will be using for testing, that’s ideal. It will work if the identity is in the same tenant as the Managed resource group but it can be a bit confusing and it doesn’t demonstrate the delegated permissions.-
Azure Active Directory tenant ID
- enter the tenant ID for a security principal (SP) that will manage the deployed resources -
Authorizations
- enter a SP Object ID for the SP that will manage the deployed resources. SelectOwner
for theRole definition
-
-
Policy settings
- leave this blankBe sure to Save draft before exiting the page
Click on
Plan overview
at the top of the page to revert to the offer pages
Co-sell with Microsoft
You are not required to enter anything on the Co-sell tab for the purposed of this lab.
Resell through CSPs
-
Select “No partners in the CSP program”
Be sure to Save draft before exiting the page
Review and Publish
We are now ready to review and publish (to a preview audience) the offer we have created.
-
Select “Review and publish” at the top of the page. You should see a summary like the below:
-
If any of the sections are not marked as “Complete”, go back and review.
-
Select “Publish” at the top of the page.
-
This will start the publish process. It will take a few hours before the preview becomes available.
-
Note the “Publisher signoff” stage in the process. This is a manual step where the publisher must confirm approval before the offer is fully published in the marketplace.
You will not do this for a test offer such as the one we are creating in this lab.
-
Check back after a few hours. Preview links should be created for Azure Marketplace and the Azure Portal.
-
Use the preview links to deploy your offer into your subscription.
Cleanup Resources
- Once completed, you can cleanup resources by deleting the resource created above
Resources
Help us improve
Azure Citadel is a community site built on GitHub, please contribute and send a pull request
Make a change