Small and medium business | Business Central, N...

Publishing Business Central extensions to AppSource

(4) Share

Report

Posted on by AK-13051749-0

314

Hello, can someone please guide me with instructions and best practices for publishing Business Central extensions to AppSource?

Any help would be greatly appreciated. Thank you!

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (8)

Answers (0)

Sort by

Suggested answer

Teagen Boll 3,471 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

There is some information from Microsoft here: Add your App to Marketplace - Business Central | Microsoft Learn

You'll have to pass technical validation and make sure you follow the best practices outlined here: Technical validation checklist - Business Central | Microsoft Learn

And for each update you will have to maintain your application and ensure its compliant with any business central application changes.

You can also find a reference for rules and guidelines when developing AL extensions here: Rules and guidelines for AL code - Business Central | Microsoft Learn

Best,

Teagen Boll

Work: Catapult ERP

Social: LinkedIn

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 18,530 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Hello,

For AppSource, start from Microsoft’s Business Central submission checklist and treat it as your main validation list: test the app in a Business Central online sandbox, make sure the extension publishes/installs without errors, don’t use -skipverification, run the self-validation tools before submitting, confirm your app.json metadata is complete, follow AL/code rules, avoid breaking changes, include proper permissions, upgrade logic, test coverage where needed, and prepare the Partner Center/AppSource listing items like description, screenshots, support URL, privacy policy, and EULA. In practice, the best approach is: build clean AL, validate technically first, test install/upgrade/uninstall in SaaS, then submit through Partner Center only when the checklist is clean.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No
Assisted by AI

Saif Ali Sabri 2,805 Moderator on at

Like (1)

Report
Copy link

Link copied!
Publishing Business Central extensions to AppSource involves several important steps and best practices to ensure your app meets Microsoft’s requirements and provides value to customers. Here’s a structured guide:
1. Prepare your extension

Develop your extension using AL language in Visual Studio Code.

Make sure your extension is compatible with the latest Business Central version.

Test thoroughly in a sandbox environment to validate functionality and performance.

2. Meet technical requirements

Extensions must be cloud-ready and follow Microsoft’s coding standards.

Ensure your app passes the AppSourceCop and PerTenantExtensionCop code analyzers.

Provide automated tests using the Business Central test framework.

3. Prepare documentation

Write clear user documentation and setup instructions.

Provide marketing material (screenshots, descriptions, videos) for AppSource listing.

Include support contact details and privacy policy.

4. Submit through Partner Center

Sign in to Microsoft Partner Center.

Create a new offer for Business Central and upload your extension package (.app file).

Fill in required metadata: description, categories, pricing, regions, and languages.

5. Validation and certification

Microsoft runs automated and manual validation checks.

You may be asked to fix issues or provide clarifications.

Once approved, your extension will be published to AppSource.

6. Best practices

Keep your extension lightweight and modular.

Follow naming conventions and avoid hardcoding values.

Provide regular updates to stay compatible with new Business Central releases.

Monitor customer feedback and improve your app continuously.

Was this reply helpful? Yes No
Suggested answer

Pallavi Phade 5,742 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Namaste @AK-13051749-0

To publish an app in marketplce , you need to follow guidelines as mentioned by Microsoft .

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-sell-apps-appsource

I can summarize the steps as per my past experience , but you need to flow the below checklist by MS

1) Checklist for Marketing Team . Offer and its pricing and marketing content . Add test cases , screenshots

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/readiness/readiness-checklist-marketing

2) Checklist for Technical Team . Prefixes for business partner , it should be version compatible . Avoid code on companyopen () triggers. Avoid hardcoding , proper fixes , proper rollback approach , standard should not be affected .

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-checklist-submission

3) Your .app file should be digitally signed on its successful validation it will be processed further for making offer live

Still you have queries we can discuss on this .

Warm Regards

Pallavi Phade

www.linkedin.com/in/pallaviphade131116

Was this reply helpful? Yes No
Pallavi Phade 5,742 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Namaste @AK-13051749-0

Hope above information helped . Please let us know in any case of queries

Warm Regards

Pallavi Phade

www.linkedin.com/in/pallaviphade131116

Was this reply helpful? Yes No
Suggested answer

Grigorios Mavrogeorgis 2,892 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi,
First thing before any code, you need to register in Partner Center and create a commercial marketplace account, sign the publisher agreement there. This is the step people forget, without it you can not submit anything to AppSource. That is your starting point, not the AL.
Good news, after you sign up you can join ISV Success, it is a Microsoft program for app builders and they give you technical consultations, basically Microsoft assign you help to guide the onboarding and the validation, it took a lot of pain out for us.
On the app itself, it must pass technical validation (AppSourceCookbook rules, app.json, affixes, test app, no breaking objects) and marketing validation for the listing. Then you create the offer in Partner Center, upload, submit. One thing many miss, you must re-certify every 6 months to stay live.
Which area is your app, and on-prem experience already or first cloud one?

Glad to help - follow up if anything is unclear.
► If this solved it, marking it verified helps others too.
Regards,
Grigorios Mavrogeorgis
Business Central Consultant & AL Developer
Work: Gmsoft Limited
Blog: insidebusinesscentral
LinkedIn: linkedin.com/in/gregorymavrogeorgis

Was this reply helpful? Yes No
Assisted by AI

Saif Ali Sabri 2,805 Moderator on at

Like (0)

Report
Copy link

Link copied!
Microsoft Copilot’s analysis: Publishing Business Central extensions to AppSource requires following Microsoft’s validation and certification process. The key steps are:

Develop your extension in AL using cloud‑compliant patterns.

Run the AppSourceCop analyzer to fix compliance issues.

Package with proper manifest metadata and localization.

Test thoroughly in a sandbox tenant for install/upgrade/uninstall scenarios.

Submit via Partner Center with marketing assets (description, screenshots, keywords).

Best practices include avoiding hardcoded IDs, ensuring GDPR compliance, supporting upgrade paths, and enabling telemetry for monitoring. The most critical step is passing Microsoft’s automated validation pipeline, which ensures your extension meets SaaS certification requirements.
______________________________________________________
The best practice for publishing Business Central extensions to AppSource is to follow Microsoft’s official validation pipeline: prepare your extension with AppSource-compliant code, test it against the AppSourceCop analyzer, package it with correct manifest metadata, and submit via Partner Center. The most critical step is ensuring your extension passes automated validation and meets Microsoft’s SaaS certification requirements.
🔑 Key Steps for Publishing Extensions

Prepare your extension

Use the latest AL language version.

Ensure compatibility with cloud (SaaS) environments.

Avoid direct file access, client-side printing, or restricted APIs.

Run AppSourceCop Analyzer

This tool validates your code against AppSource rules.

Fix warnings/errors before submission.

Common issues: missing permissions, hardcoded IDs, or non‑compliant dependencies.

Package with correct manifest

Include app.json with proper versioning, publisher name, and dependencies.

Provide translation files for localization.

Add permissions.xml if your extension requires specific access.

Test in a sandbox

Deploy to a Business Central sandbox tenant.

Validate installation, upgrade, and uninstallation scenarios.

Ensure performance is acceptable (no long-running loops or blocking calls).

Submit via Partner Center

Upload your .app file.

Provide marketing assets: description, screenshots, and keywords.

Define pricing/licensing if applicable.

Microsoft runs automated validation + manual review.

📋 Best Practices

Follow SaaS certification checklist

No breaking changes between versions.

Support upgrade paths.

Ensure GDPR compliance (no personal data stored improperly).

Use telemetry

Add Application Insights logging for monitoring.

Helps diagnose issues post‑deployment.

Document thoroughly

Provide clear user guides.

Include setup instructions.

Add troubleshooting notes.

⚠️ Common Pitfalls to Avoid

Hardcoding IDs → Use symbolic names.

Unsupported APIs → Stick to public AL APIs.

Missing upgrade codeunits → Always handle schema changes.

Poor performance → Avoid nested loops on large datasets.

Incomplete marketing package → Screenshots and descriptions are mandatory.

Was this reply helpful? Yes No
Gerardo Rentería Ga... 27,553 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Hi, good day
I hope this can help you, and give you some hints.

Add your App to Marketplace - Business Central | Microsoft Learn

Submit Your Business Central Extension Like a Pro: A Complete AppSource Guide with Progress Tracking Macro – Learn With Dr. Gomathi

Submit Your Business Central Extension Like a Pro: Complete AppSource Guide

A Step-by-Step Guide to Publishing Apps on Microsoft AppSource

Business Central Extensions & AppSource: Complete Guide...

Best Regards
Gerardo

Was this reply helpful? Yes No