Cortana Intelligence AppSource publishing guide
AppSource is the single destination for Business Decision Makers (BDMs) to discover and seamlessly try business solutions/apps built by partners and evaluated by Microsoft. Watch this video to learn how AppSource works.
As a Microsoft Partner, you can really benefit from publishing on AppSource if you have:
- Built an intelligent solution/app using Cortana Intelligence Suite.
- Your solution or app addresses a specific business problem.
- You built modules or intellectual property that your customers can reuse relatively quickly in a predictable manner.
Take a look at Cortana Intelligence solutions that are already published on AppSource.
This article will walk through the steps to get a partner's Cortana Intelligence solution published to AppSource
- In the Partner Community Benefits Guide (PDF), see page 9 to get listed as an Advanced Analytics partner.
Complete the Submit your app form.
For the question “Choose the products that your app is built for”, check the Other checkbox and list “Cortana Intelligence” in the edit control.
- Before a Cortana Intelligence app can get onboarded to AppSource, it must get certified by Cortana Intelligence’s Partner Solution Technology team. To get that process started, kindly share details about your app by filling in survey form at Cortana Intelligence solution evaluation for AppSource publishing. This site is password protected and the site has instructions on how to get the password.
Solution evaluation criteria
Here is the list of criteria the app needs to meet
- App needs to address specific business use case problem within a given functional area in a repeatable manner with minimal configurations for predefined value propositions implementable within a short period.
Solution should use at least one of the following components:
- Machine Learning
- Data Lake Analytics
- Stream Analytics
- Cognitive Services
- Bot Framework
- Analysis Services
- Microsoft R Server stand alone
- R services on SQL 2016 or HDInsight Premium
- Solution should be generating at least $1000 a month per customer using DPOR/CSP.
Solution should use the Azure Active Directory federated single signon (AAD federated SSO) with consent enabled for user authentication and resource access controls. You will need to show to the evaluation team that your solution is AAD federated SSO enabled before your app can be onboarded to AppSource.
To see what it means to be AAD federated SSO enabled, seek to position 02:35 in AppSource trial experience walk through video. If your app is not enabled with AAD federated SSO yet, here is some documentation about it
Use Power BI in your solution: Optional but highly recommended as it is proven to generate higher number of leads.
DevCenter account setup
This is the process of registering your company to become a publisher with Microsoft. If you are already a registered publisher with an existing DevCenter account, share the email ID associated with your DevCenter account. Once your application is approved for publishing, you will get access to full documentation about Cloud Portal Manage publisher profile
If you don't have one, below are the key steps to setup a DevCenter account.
- Create a Microsoft account here.
- Go to the Microsoft DevCenter registration page and click "sign up".
- When prompted for payment, use the code that we provided to you. If you don't have a code, contact firstname.lastname@example.org.
- Select the country/region in which you live, or where your business is located. You won't be able to change this later.
- Select your developer account type For AppSource, select Company. For a company account, be sure to review these guidelines.
- Enter the contact info you want to use for your developer account. For detailed step by step instruction on how to setup DevCenter account, see the instructions here.
Provide info for Microsoft sellers
One of the key value propositions of AppSource for partners is to be able to collaborate with Microsoft Sellers in positioning partner apps in front of potential customers.
Build a compelling customer walkthrough on AppSource
First, take a look at Neal Analytics Inventory Optimization on AppSource. Every app entry in AppSource has title, summary (100 chars max), description (1300 chars max), images, videos (optional), pdf documents apart from entry point for a trial experience. Partners should leverage all these to build a compelling customer experience.
Partners should think of the content they put on AppSource as an end to end sales orchestration. Customers read the title and description to understand the value proposition and then go through images & videos to understand what the solution is about. Case studies help potential customers see how existing customers are getting value.
All this should make the customer feel interested and wanting to know more. Think of these as pitch decks based presentation a good technical sales person would walk the new customers through. The suggested format of description is to break up the text into sub-sections based on value propositions, each with highlighted with a sub-heading.
Visitors usually glance over the "offer summary" field and sub-headings to get gist of what the app addresses and why should they consider the app in just a quick glance. So, it is important to get the user's attention give them a reason to read on to get the specifics.
See what these partners have done.
The final act of sales is to show a demo of the app/solution showing how the value proposition is delivered. That is exactly what a customer trial experience on AppSource is meant for. A good demo will do the following:
- Re-summarize the value proposition of the app in short and list out the personas within the customer firm who would interact with the solution
- Tell a story and sets the context about a sample customer dealing with specific issues
- Explain how the situation can generally devolve and impact the customer (before) VS what would happen if the solution is in use. This can be shown using PowerBI dashboards etc.
- Summarize how the solution makes it happen by using any specific Machine Learning algorithms etc.
The content being added in AppSource should be of high quality and stitched up enough to enable the following:
- A partner's technical sales folks should be using it for their sales orchestration. Your sales teams using it is a good sign that you can expect MS sales folks also being able to do the same. This will enable customer point of contact to be able to consistently relay the same story to their team mates and higher ups to get budget and approvals before a purchase deal can be done.
- A customer visiting the site organically can go through the content all by themselves and feel excited to respond back to partner communication to move ahead with next steps.
That's why partners should think of the content they put on AppSource as an end to end sales orchestration. Based on the story line and features to be shown in trial experience, type of offer can be decided.
Publish your app on the publishing portal
Once we have evaluated the above steps for your application, you will get access to the publishing portal and can see How to publish a Cortana Intelligence offer via Cloud Partner Portal for detailed instructions on next steps.
If you need information about any of the fields, email email@example.com.
My app is published on AppSource - now what?
Firstly, Congratulations on getting your app published. The level of returns you get from publishing your app on AppSource heavily depends on how you influence the target audience. See Growth-Hacking your Cortana Intelligence app on AppSource for more details of how you can maximize the returns.
If you have any questions or suggestions, kindly reach out to us at firstname.lastname@example.org.