Automating parts of the technical validation in the AppSource submission process
Important
This content is archived and is not being updated. For the latest documentation, go to New and Planned for Dynamics 365 Business Central. For the latest release plans, go to Dynamics 365 and Microsoft Power Platform release plans.
| Enabled for | Public preview | General availability |
|---|---|---|
| Admins, makers, marketers, or analysts, automatically | - | 
May 1, 2021 |
Business value
When submitting an app to AppSource, the app must pass the application validation criteria. We want to decrease the time that partners, and ultimately customers, must wait for approval. We also want to scale validation for an increasing number of AppSource apps. Therefore, we are continuously investing in automating this process.
Feature details
When an app is submitted to AppSource, various validations are performed. To improve the time to validation, we have automated the following technical validation steps and moved them to earlier in the submission validation process:
- Affixes must be registered for the publisher and used.
- The .app file must be digitally signed.
- The app.json file has mandatory properties that must be included.
- Extensions submitted must not be runtime packages.
- Publisher name has been validated.
To reduce the risk of failing the AppSource validation process, we highly recommend that you review the technical validation checklist before submitting, as well as automate the AppSource validation as part of Continuous Integration/Continuous Development, as outlined in that help topic.
See also
Automating parts of the technical validation in the AppSource submission process (docs)