| title | description | services | documentationcenter | author | manager | editor | ms.assetid | ms.service | ms.devlang | ms.topic | ms.tgt_pltfrm | ms.workload | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Guide to creating a Data Service for the Marketplace | Microsoft Docs |
Detailed instructions of how to create, certify and deploy a Data Service for purchase on the Azure Marketplace. |
marketplace-publishing |
HannibalSII |
hascipio |
96194198-6991-43b4-918e-ee337e250339 |
marketplace |
na |
article |
na |
na |
08/26/2016 |
hascipio; avikova |
Important
At this time we are no longer onboarding any new Data Service publishers. New dataservices will not get approved for listing. If you have a SaaS business application you would like to publish on AppSource you can find more information here. If you have an IaaS applications or developer service you would like to publish on Azure Marketplace you can find more information here.
After completing the step 1, Account Creation and Registration, we guided you through the General Non-Technical and Technical Requirements of a Data Service offer on Azure Marketplace. Now we will walk you through the steps for creating a Data Service offer on the Publishing Portal for the Azure Marketplace.
Go to https://publish.windowsazure.com
For first time login to Publishing Portal, use the same account with which your company’s Seller Profile was registered in Developer Center. (Later you can add any employee of your company as a co-admin in the Publishing Portal).
Click on the Publish a Data Services tile if this is the first login into the publishing portal.
Fill in the title for your new Data Service Offer and click on “+” on the right.
Click on the Walkthrough tab and review all necessary steps needed to publish properly the Data Service on the Azure Marketplace.
Tip
You always can click on the links in the “Walkthrough” page or use tabs on the Data Service offer’s sub-menu on the left side.
Each Offer can have multiple Plans, but must have at least one (1) Plan. When end-users subscribe to your offer they subscribe for one of the offer’s Plan. Each plan defines how end-users will be able to use your service.
Currently Azure Marketplace support only Monthly Subscription Transaction Based model for Data Services, i.e. end-users will pay monthly fee according to the price of the specific plan they subscribed to and will be able to consume each month number of transaction defined by the plan.
Each Transaction usually defined as number of records your Data Service will return based on the query sent to the Service. The default is 100. Number of transactions returned to each query will be number of records divided by 100 and rounded up to the closest integer.
It’s Azure Marketplace Service layer responsibility to monitor (meter) number of transactions consumed by each query.
Important
End-Users which reached the transaction limit during the month will be blocked from continuing to use the service until end of their monthly subscription cycle.
The plan or one of the plans can (but not must) include unlimited number of transactions.
-
Click on “+” next to the “Add a new plan”.
-
Choose one of the options: Unlimited or Limited usage for this plan. If Limited then provide the number of transaction the plan will allow to consume in a month.
Publishing Portal will also suggest “Plan Identifier”, which will be used to communicate to the end-users the name of the plan in the UI and also used by the Market Place Service to identify the Plan. You can change the “Plan Identifier” if you want.
[!NOTE] The “Plan Identifier” must be unique within the scope of each offer. As many other Identifiers used in the Publishing Portal Plan identifier will be locked after the first publishing to production and you will not be able to change this identifier.
-
Click to accept your choice.
-
Then you will be asked few additional questions regarding your newly created Plan.
| Question | Significance |
|---|---|
| This Plan is free and available world-wide? | You can create a completely free-of-charge plan. If it’s the only plan for this offer – it means that you are publishing “Free Offer” in the Marketplace. If it’s only for one (of few) Plan, the it gives you an option to offer end-users to learn more about your service with a relatively small number of transactions per month. If the answer is "Yes," then no further questions will be asked. |
Note
End users can always upgrade to the paid plans.
| Question | Significance |
|---|---|
| Is free trial available? | You can choose between “No Trial” at all or give an option to use your Plan for “One Month”. Publishers like to use this option to provide end-users the possibility to understand the benefits of the offer for free for one month. |
Important
End-users will only be able to purchase a free trial if they have established payment instrument e.g. credit card, enterprise agreement.
After one month of the free trial, Azure Marketplace will start charging customers the price as of the date of the subscription, unless the customer initiated the subscription cancellation. No special notification will be provided to the end-users.
| Question | Significance |
|---|---|
| This plan requires a promotion code to purchase? | Publishers have an option to limit access to their Service Plans by providing a special code, called “A Promocode” to specific customers. Only end-users which will have this Promocode will be able to subscribe to the Plan. If you choose “No”, then you agree that everyone from the region where the offer is available (See Marketplace Marketing Content Guide for more details) will be able to subscribe to this plan. No further questions will be asked. |
| Also hide this plan from anyone who doesn’t have a valid promotion code? | If the answer to the previous question is “Yes” the Publisher has an option to completely remove this plan from appearing in the UI of the Marketplace. It means, customers will not see this plan in the Offer’s details page. End-users which will receive a promocode to purchase it, will be able to subscribe to it using this promocode. |
For How to provide information required in Marketing, Pricing, Support and Categories tabs please visit Marketplace Marketing Content Guide which is common to all artifacts published in the Azure Marketplace.
Click on the Data Services sub-menu.
On the upper half of the page you’ll be asked to provide the offer’s Namespace.
The below question will define how the Publisher is going to expose newly created offer to Azure Marketplace. (For more details see the Data Services Technical Prerequisite Guide).
Publishing the Database based service
Click on Database. The following page will appear:
To create a CSDL mapping for the Dataset based on the SQL Azure DB:
And then for each table
If Web Service
Important
Read Mapping an existing web service to OData through CSDL for detailed instructions and examples for creating a CSDL Web Service.
Now that you've created your Data Service offer, please ensure that you complete the instructions in the Marketplace Marketing Content Guide before you move forward to Testing your Data Service in Staging.
- Getting Started: How to publish an offer to the Azure Marketplace
- If you are interested in understanding the overall OData mapping process and purpose, read this article Data Service OData Mapping to review definitions, structures, and instructions.
- If you are interested in learning and understanding the specific nodes and their parameters, read this article Data Service OData Mapping Nodes for definitions and explanations, examples, and use case context.
- If you are interested in reviewing examples, read this article Data Service OData Mapping Examples to see sample code and understand code syntax and context.