Use the Seller Dashboard to submit your solution to AppSource
If you want your Office Add-in, Office 365 web app, or Power BI custom visual to appear in AppSource and the in-product Store, you need to submit it to the Seller Dashboard for approval. First, familiarize yourself with the AppSource validation policies. You can add and save your submission as a draft in your Seller Dashboard account until you're ready to submit it for approval.
If your SharePoint Add-in requires an Open Authorization (OAuth) client ID and client secret, you can add a client ID and client secret in the Seller Dashboard before you add your add-in. For more information, see Create or update client IDs and secrets in the Seller Dashboard.
For information about the AppSource approval process, see Make your solutions available in AppSource and within Office.
This section lists the information that you need to provide when you submit your solution in the Seller Dashboard.
Add a new app
Select Add a new app. On the Listing type page, select the type of solution that you are submitting:
- Office Add-in
- Outlook Add-in
- Power BI custom visual
- SharePoint Add-in
- Teams app
For more information, see Upload your submission package.
|Release date (UTC)||Required. This controls the date on which your add-in will be made available after it passes validation. If this is set to a date in the future, your add-in will not be available until that date. If your submission is an update and you set this field to a date in the future, your existing add-in will be unpublished until the release date you specified.|
|Category||One required; two optional|
|Testing notes||Optional, but recommended|
|Cryptography and encryption information||Optional|
|Apple developer ID||Optional|
|Support document link||Required|
|Privacy document link||Required|
|End User License Agreement||Optional|
|App name||Required. One entry per language.|
|Short description||Required. One entry per language.|
|Long description||Required. One entry per language.|
|Screenshots||At least one is required.|
For more information, see Create your AppSource listing.
Block access page
|Block access for specified countries/regions||By default, available in all countries or regions.|
For more information, see Regional availability.
|Trial support||By default, no trial support|
For details, see Decide on a pricing model.
Submit for approval
After your account in the Seller Dashboard is approved, you can submit your solution for approval. To submit an app for purchase, your payout and tax information must also be validated. Your approved apps will be listed in product-specific stores.
To submit a new solution
Complete the items listed in the checklist.
Select SUBMIT FOR APPROVAL.
To submit a solution that you saved to the Seller Dashboard as a draft and need to edit
On the Manage tab, select the item that you want to edit and submit.
On your summary page, select EDIT DRAFT and make your changes. Select SUBMIT FOR APPROVAL.
To submit a solution that you saved to the Seller Dashboard as a draft
On the Manage tab, select the entry that you want to submit.
On your summary page, select SUBMIT FOR APPROVAL.
After you submit a solution for approval, you cannot make changes to it during the approval process. When the approval process is complete, you receive an email message indicating that your app was approved or that you need to make changes before it can be approved.
- Upload your package to AppSource
- Create your AppSource listing
- Add lead management details for your Office Add-ins in the Seller Dashboard
- Decide on a pricing model for your AppSource submission
- Create or update client IDs and secrets in the Seller Dashboard
- AppSource submission FAQ
- Create effective AppSource listings
- Register as an app developer
- Have your app appear in the Office 365 app launcher
- Publish Power BI custom visuals to AppSource
- Make your solutions available in AppSource and within Office
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.