How to: Add apps in the Microsoft Seller Dashboard
Updated: June 4, 2013
Developers can use the Microsoft Seller Dashboard to submit apps for Office and SharePoint to the Office Store. Learn how to submit your apps for approval and inclusion in the Office Store.
Applies to: Office 2013 | Office 365 | SharePoint Foundation 2013 | SharePoint Server 2013
Verify your paid Office 365 subscription, review regional information, validation policies, and supported languages
Before you submit apps in the Seller Dashboard, verify the following:
-
Paid Office 365 subscription: Before you submit an app in the Seller Dashboard for the first time, you need to link your paid Office 365 subscription to your Seller Dashboard account. As long as your Seller Dashboard account is associated with a valid subscription, you only need to do this once. After you link your accounts, you can submit your apps directly in the Seller Dashboard. For more information, see How to: Verify your paid Office 365 subscription so you can publish apps to the Office Store.
-
Regional information: Check the Regional Information for the Microsoft Seller Dashboard to make sure you reside in a country or region that the Seller Dashboard supports.
-
Validation policies: Review the current Validation policies for the apps submitted to the Office Store (version 1.4) and Validation checklist for apps for Office and SharePoint to avoid common mistakes and help make sure your app will pass validation when submitted to the Office Store.
-
Languages: If you want to offer your app in languages beyond the primary language, you’ll need localized metadata for each additional language. The best customer experience is by apps with web services and functionality that support these additional languages. You’ll also need to create app descriptions in the languages your app is localized to. The Seller Dashboard currently accepts English, French, German, Japanese, and Spanish.
Note
For information about localizing apps for Office and apps for Outlook, see Designing an app for Office for specific locales and How to: Build a localized app for Office. For information about localizing apps for SharePoint, see Designing an app for Office for specific locales and How to: Localize apps for SharePoint.
If you want to distribute your app in additional languages, you can edit the app details in the Seller Dashboard using the corresponding app package or manifest. After you have added additional languages, you’ll need to submit it for approval again.
In the case of previously approved apps, if you updated your manifest, you’ll need to ensure that you update the version in the manifest and in the submission form. The current version of your app will remain in the Office Store until your new version is approved, unless you unpublish the current version of your app. For more information, see Update, Unpublish, and Track Your Apps with Metrics in the Microsoft Seller Dashboard.
Note
If you want to block customers in certain country/region from acquiring or using your app, you’ll be given the opportunity to do so when you add or edit your app in the Seller Dashboard.
Prepare your app information
Before you add apps in the Seller Dashboard, prepare the information in the following checklist.
|
What you need |
Notes |
||||
|---|---|---|---|---|---|
|
App type |
Your choices are app for Office, app for Outlook, and app for SharePoint. |
||||
|
App title |
Your App Title appears in the listing on the Office Store. A shorter title displays well on web pages, so we recommend that your App Title is no more than 15 characters. The title can be up to 50 characters.
|
||||
|
App name |
If you want to offer your apps in multiple languages, you can provide an App Name in each language. The Seller Dashboard currently accepts English, French, German, Japanese, and Spanish.
|
||||
|
Version |
The version number you provide for the Version must exactly match the version number in the app manifest file of the app you submit. For more information, see current Validation policies for the apps submitted to the Office Store (version 1.4). |
||||
|
Release date |
The Release Date does not determine the date on which your app is made available on the Office Store. Rather, it is the date your app is released and listed in the store. |
||||
|
Category |
Choose at least one category. You can choose up to three categories that will help customers filter in the Office Store to find your app. |
||||
|
App logo |
A picture you want customers to associate with your app that will appear in the store listing for your app.
|
||||
|
App package |
This is your app binary file or manifest file that you upload to the Seller Dashboard.
For more information about maintaining consistency between this app logo image and the one you include in the app package, see Create a consistent visual identity for your app in How to: Create an effective Office Store listing for your app for Office or SharePoint. |
||||
|
OAuth Client ID (if required) |
If your app is a service and requires server-to-server authorization, you’ll need a client ID and client secret. You create the client ID and secret in the Seller Dashboard. For more information, see How to: Create Client IDs and secrets in the Microsoft Seller Dashboard. |
||||
|
Testing notes |
Provide instructions and links to resources that will help validation testers validate your app as part of the app approval process. For example, provide valid credentials or a password if your app requires them. The credentials or password are not for public use and will only be used by Microsoft. Your Testing Notes are solely for validation purposes and will not be published in your store listing. If you provide complete Testing Notes, they can assist in the validation and approval of your app. |
||||
|
Cryptography and encryption information |
You’ll need to specify if your app calls, supports, contains, or uses cryptography or encryption. For more information about encryption, see EAR Controls For Items That Use Encryption. |
||||
|
App description |
This includes a Short Description and a Long Description that will appear in the store listing for your app. The Short Description can be up to 100 characters, and the Long Description can be up to 4,000 characters. If you want a tailored experience for users in regional store, you can add additional languages so your app appears in other language store with localized metadata. You can add a language and must write a Short Description and a Long Description in that language. The Seller Dashboard accepts English, French, German, Japanese, and Spanish.
|
||||
|
Screenshots |
Provide at least one screen shot of your app. You can provide up to five screen shots for customers who want to learn more about your app. Customers will be able to see these images in the store listing for your app, so do not include any private or personal information that you do not want customers to see. If you add additional languages to your app submission, you can add language-specific screen shots for your app. Screenshots that match each language provides the best customer experience.
|
||||
|
Support document link |
Provide a link to your support documentation, including http:// or https:// in your URL. The support link should include contact details so that users can contact you or a support person about your app. |
||||
|
Privacy policy notification link (optional) |
Provide a link to a privacy policy
|
||||
|
Video link (optional) |
If you have a video that demonstrates your app, you can provide a link to it. This video will appear in the listing page for the app. |
||||
|
Customized end user license agreement (optional) |
If you have a customized license agreement, you can upload it. If not, the store will provide a license agreement for your app. For details, see Office Store Standard Application License Terms |
||||
|
Pricing information |
You can list your app for purchase or for free. If you plan to list your app for purchase, add pricing information. You can add this information at any time, so if you decide to list your app for purchase at a later date, you can add pricing information at that time.
|
||||
|
Trial information |
If your app supports a trial, you’ll need to specify the duration of the trial, and the number of users. You need to also take licensing into consideration. For more information about licensing, see Licensing your apps for SharePoint and Creating and verifying licensing in a paid app for Office. |
||||
|
Payout and tax information |
If you want to list your app for purchase, you must also provide payout and tax information. This information must be validated before you can submit an app for purchase. For more information, see Create Your Account and Add Payout Information in the Microsoft Seller Dashboard. |
||||
|
App appropriately localized |
If your app supports multiple languages, make sure that your app has been appropriately localized, or it will not pass validation and won’t be approved. For information about localizing apps for Office and apps for Outlook, see Designing an app for Office for specific locales and How to: Build a localized app for Office. For information about localizing apps for SharePoint, see Designing an app for Office for specific locales and How to: Localize apps for SharePoint.
|
You can add and save your app as a draft in your Seller Dashboard account. This is available even while your account is pending approval, if you don’t have all the information you need, or if you want to begin the process of adding an app but don’t want to submit it for approval yet.
Note
|
|---|
|
If your app requires an Open Authorization (OAuth) client ID and client secret, you can add a client ID and client secret in the Seller Dashboard before adding your app. For more information, see How to: Create Client IDs and secrets in the Microsoft Seller Dashboard. |
To add an app and save it as a draft
-
Sign in to the Seller Dashboard with your Microsoft account.
-
On the APPS tab, choose add a new app.
-
In the NEW APP wizard, on the listing type page, choose the Office Types that matches your app.
-
If it’s the first time you are creating an app for the store that lists your app type, an agreement will appear. Under marketplace terms and conditions, read the agreement, and if you agree, select the check box, and then choose NEXT or cancel.
Note
If you add an app at a later date that will be listed in a different store, you’ll see a different store agreement. If you add an app at a later date that will be listed in the same store, the same agreement applies. If you agree, you’ll only see the agreement for that store once. However, if an updated version of the agreement becomes available, you’ll see the updated version that requires agreement.
After you add your app, if you want to see a list of accepted agreements, choose the ACCOUNT tab. On the manage tab, under terms and conditions, you’ll see the list of the agreements you have accepted. To see the details of an agreement, choose the name of the agreement.
-
On the overview page, do the following:
-
Under general info, provide the information, which can include App Title, Version, and Release Date, depending on your app type.
Important
The number you provide for the Version must exactly match the version number in the app manifest file of the app you submit. Release Date is the date you want displayed as the date your app is released.
-
Choose at least one Category. You can choose up to three categories that will help customers filter in the Office Store to find your app.
-
Under logo, choose the App Logo tile, and upload your logo.
-
Under app package do the following:
-
Choose the app package tile, and upload your app.
If your app uses OAuth, select the My app is a service and requires server to server authorization option check box. Selecting the check box displays the OAuth Client ID drop-down field. Select the OAuth client ID that you want your app to use.
Note
You’ll not see the My app is a service and requires server to server authorization option check box if you’re adding an app for Office or app for Outlook.
-
Under Testing Notes, provide instructions and links to resources that will help validation testers validate your app as part of the app approval process. For example, provide valid credentials or a password if your app requires them. The credentials or password are not for public use and will only be used by Microsoft. Your Testing Notes are solely for validation purposes and will not be published in your store listing. If you provide complete Testing Notes, they can assist with the approval of your app.
If your app calls, supports, contains, or uses cryptography or encryption, select the My app calls, supports, contains, or uses cryptography or encryption. check box. Verify the information, and then choose Yes or No.
-
Under support documents, provide a link to your support documentation for your app. Include http:// or https:// in your URL. Optionally, you can provide a Privacy Document Link, a Video Link, and a customized End-User License Agreement. If you don’t have a customized license agreement, the store will provide one for your app.
-
-
Choose NEXT, SAVE AS DRAFT, or cancel.
-
On the details page, do the following for language selection:
Note
You must repeat the following steps for each language that your app has been localized to and supports.
-
In the Choose Language drop-down list, choose the language that your app has been localized to and supports.
-
Under description, provide your App Name, Short Description and Long Description in the appropriate language. For example, if you chose English in the previous step, type your App Name, Short Description and Long Description in English.
-
Under screenshots, choose Primary tile to upload at least one screen shot of your app. You can upload up to five images.
Important
-
Customers will see your screen shots in the store listing for your app, so do not include any private or personal information that you do not want customers to see.
-
You can add language-specific screen shots to match each language. Screenshots that match each language provides the best customer experience.
-
Note
-
If you want to add another language, choose ADD A LANGUAGE and repeat the previous three steps for each language that your app has been localized to and supports.
-
If you want to remove a language that you’ve added, choose remove language.
-
-
Choose NEXT, SAVE AS DRAFT, or cancel.
-
On the Block Access page, choose the countries/regions where you do not want your apps listed and sold, if any. If there are countries/regions you want to block customers from purchasing the app, do the following:
-
Select the Block customers in certain countries/regions from purchasing this app check box.
-
Choose the SELECT COUNTRIES/REGIONS button.
-
In the Select which countries/regions you would like to block dialog box, choose the countries/regions you want to block from purchasing your app.
-
Choose BLOCK COUNTRIES/REGIONS or Cancel after making your selections. If you block a particular country/region, users in that region will not be able to acquire or use your app.
-
-
-
Choose NEXT, SAVE AS DRAFT, or cancel.
-
On the pricing page, do the following:
Note
If your app cannot be offered for purchase, you may not see the pricing page.
-
If you want to list your app for purchase, you must also provide payout and tax information. For more information, see Create Your Account and Add Payout Information in the Microsoft Seller Dashboard.
-
You can also add pricing information later. Choose SAVE AS DRAFT and come back later to finish adding your pricing information.
-
If your app is free, leave My app is free selected.
-
If your app is for purchase, choose My app is for one-time purchase, and select the Price Per User.
If you want to place a limit on the maximum a buyer pays, choose a Price Threshold. If you choose No threshold, then the buyer pays the Price Per User for each user.
Note
-
App price is set at the app level. You don’t set a price for each language. You set a price tier.
-
If the Price Per User equals $1.99, with a Price Threshold equal to 10 users, then the maximum price for unlimited users equals $19.90. The buyer pays $1.99 for each user up to 10 users, with no additional charge for 11 or more users.
-
-
Under trial support, if you offer a trial of your app, select the My app supports a trial check box, and select the duration and number of users for your trial from the Duration of Trial and Number of Users in Trial drop-down fields.
You need to also take licensing into consideration. For more information about licensing, see Licensing your apps for SharePoint and Creating and verifying licensing in a paid app for Office.
-
-
Choose SAVE AS DRAFT or cancel.
To submit an app for approval
After your account in the Seller Dashboard is approved, you can submit apps for approval. If you want to submit an app for purchase, your payout and tax information must also be validated before you can submit an app for approval. See Create Your Account and Add Payout Information in the Microsoft Seller Dashboard if you have not yet added this information in the Seller Dashboard. Your approved apps will be listed in product-specific stores.
Note
|
|---|
|
To submit apps for the Office Store, you must have an Office 365 subscription that is not a trial and that includes a Developer Site. |
To submit an app for approval, do the following:
-
If your account is approved and you are adding a new app, follow the steps in the previous section to add an app. In the final step of that procedure, click SUBMIT FOR APPROVAL instead of SAVE AS DRAFT.
-
If you are submitting an app that you saved to the Seller Dashboard as a draft, and you want to make changes before submitting it, choose the apps tab, and then choose the app you want to edit and submit. On your app summary page, choose EDIT DRAFT and make your changes. Choose SUBMIT FOR APPROVAL.
-
If you want to submit an app that you saved to the Seller Dashboard as a draft without making changes, choose the apps tab, and then choose the app you want to submit. On your app summary page, choose SUBMIT FOR APPROVAL.
Note
After you submit an app for approval, no changes can be made to your app during the approval process. When the approval process is complete, you will receive an email message. You can then edit or update your app, if necessary. For more information, see the Edit your app section in Edit, Unpublish, and Track Your Apps with Metrics in the Microsoft Seller Dashboard.
You can submit apps for approval after your account is approved. You can make changes to your app at any point before you submit it for approval. During the approval process, you won’t be able to make changes to your app. If you make changes to an approved app, it must go through the approval process again.
Some of the requirements for approval are:
-
Your app must be free of viruses. If you need virus detection software, see the Microsoft Safety & Security Center.
-
Your app must not contain inadmissible or offensive material.
-
Your app must be stable and functional.
-
Any material that you associate with your app, such as descriptions and support documentation, must be accurate. Use correct spelling, capitalization, punctuation, and grammar in your descriptions and materials.
-
If you want a tailored experience for users in regional store, you can add additional languages so your app appears in other language store with localized metadata. Your service and your app manifest must be appropriately updated, if applicable. You must also provide app descriptions for each language you add.
Note
|
|---|
|
For more information about validation policies, see Validation policies for the apps submitted to the Office Store (version 1.4). |
You’ll receive a message when validation process is complete, alerting you that your app is approved or your app requires changes and resubmission. You can also follow these steps to check the status in the :
-
Sign in to the Seller Dashboard with your Microsoft account.
-
On the APPS tab, under manage, your app status appears under the app name.
-
If the status is pending approval, your app is still being verified. When in this state, you can’t update or resubmit your app.
-
If the status is approved, your app is approved to be listed in the appropriate marketplaces.
Note
Once your app is approved in the Seller Dashboard, there may be a delay before it is published in a store. After approval, an app typically appears in the store within 24 hours. If you’ve questions or issues with the approval process, see Support Resources.
-
If the status is changes requested, your app needs changes in order to be approved. Click the app, and then on the app summary page, click View the app report for details about the required changes.
-
-
How to: Create an effective Office Store listing for your app for Office or SharePoint
-
How to: Verify your paid Office 365 subscription so you can publish apps to the Office Store
-
How to: Create Client IDs and secrets in the Microsoft Seller Dashboard
-
How to: Create or edit your seller account in the Microsoft Seller Dashboard
-
Validation policies for the apps submitted to the Office Store (version 1.4)
|
Date |
Description |
|---|---|
|
June 04, 2013 |
Added new steps and prerequisites for apps that support multiple languages, and information about how to block access to your app in certain countries/regions. |
|
July 16, 2012 |
Initial publication |
Security Note