Top five AppSource validation errors for Office Add-ins submissions – March 2023
AppSource validation ensures your Office Add-in submission follows Microsoft’s quality standards. Don’t lose valuable time getting to market – learn how to avoid these common validation pitfalls!
Between December 2022 and February 2023, the following were the top AppSource errors affecting Office Add-ins’ submissions.
- Doesn’t work on Office for Mac
- Functionality doesn’t work as described
- Outlook add-in doesn’t work on Safari
- Provides insufficient value
In this post, you’ll learn about what the affected AppSource policies are looking for so you can be confident your Office Add-in submission won’t hit these issues.
Your add-in should work properly in all operating systems, browsers, and devices compatible with and supported by the minimum required set of APIs declared in the Requirements element in its manifest. For example, if the add-in runs successfully in Office on Windows, it should also work properly in Office on Mac.
- Related policy: 1120.3 Office Add-ins: Word, Excel, PowerPoint, and Outlook > Functionality
- Office Add-ins manifest documentation – Requirements element
Your add-in should deliver what it promises. It must provide the functionality, features, and deliverables noted in its marketplace description and related materials. The add-in should work properly without displaying any errors. If your add-in is an Excel add-in with custom functions, each custom function must be visible and verifiable.
- Related policy: 100.12 General: Functionality
- AppSource submission checklist Step 7
- AppSource submission guide Step 7
As mentioned previously, add-ins should work on all supported operating systems, browsers, and devices. In general, add-ins should work on the latest versions of Microsoft Edge, Chrome, Firefox, and Safari. Your Outlook add-in should therefore work properly on supported browsers. To avoid this error, when you verify your add-in in Outlook on Mac, make sure to also verify your add-in in Outlook on the web using Safari.
- Related policy: 1120.4 Office Add-ins: Outlook add-ins functionality
- Browsers used by Office Add-ins
- Outline how you handle users’ personal information.
- Specifically refer to your add-in or your overall service, not only to your website.
- Have a service description that includes the name of the add-in being submitted.
- Related policy: 100.6 General: Personal information
- AppSource submission checklist Step 6
- AppSource submission guide Step 5
Add-ins that are simple utilities or of limited scope are not a good fit for the commercial marketplace. Therefore, your add-in must provide enough value to justify the investment it takes for users to learn and use it. Your add-in should provide a usable software solution and significant benefits, such as enhanced efficiency, innovative features, or strategic advantages.
Your Office Add-in must read or write document information and interact with the Office application, which can include reading data from the document or inserting data into the document.
However, if your add-in isn’t intended for the commercial marketplace and instead targets larger organizations or enterprises, make sure to provide an email contact or link in the add-in UI so users can learn more about your services. For more information about this situation, see the Enterprise only section of the December 2022 post in this series.
- Office Add-ins community call blog post: Top 5 AppSource Validation Errors during December 2022 to February 2023
- December 2022: Top 5 AppSource validation errors for Office Add-ins submissions
- Office Add-ins Dev Center
- Follow us on Microsoft 365 Developer (@Microsoft365Dev) / Twitter for the latest news and announcements!