Welcome

If you're developing business applications for Microsoft Dynamics 365 Business Central, one of the key platforms for distributing your solutions is Microsoft AppSource. This marketplace allows you to showcase your app to a global audience, but there are several steps involved in getting your app listed. In this post, we will walk through the essential steps you need to follow when publishing an app to Microsoft AppSource.

Before you can begin developing your app, you need to ensure that you have a unique object range from Microsoft. This is necessary for creating your app's objects like tables, pages, and other components. To request your object range:

• Download the Object Range Request Form from the Partner Source portal.
• Send the completed form to Microsoft APOC Team, specifying your requirements.
• Microsoft typically assigns 1,000 object IDs per module. If you need more object IDs for future apps or additional features, you can request more. These object IDs can be used across multiple apps, but make sure they don't clash with IDs assigned to other extensions, as this can cause conflicts in customer environments.

Once you receive the object range from Microsoft, make sure to track it properly. For example, your object range might look something like:
Object Range: 71xxx575 - 71xxx574 (1000 objects for each ISV mentioned in Form).

Microsoft requires you to register a unique three-character affix that will be associated with your publisher name. For example, if you want to publish apps under your company’s name, you’ll need to request the affix specifically for that name.

• Contact Microsoft (d365val@microsoft.com) to register your publisher name and affix.
• If you have multiple publisher names or change your publisher name, you will need to request separate affixes for each.

The affix will be used in your object names, such as "CustomMaster_LCS", and in other components like actions and procedures. This ensures that your objects are properly identified in Microsoft’s ecosystem.

With the object range and publisher affix in hand, you can now begin developing your app according to Microsoft’s standards. Ensure that the app is built to be a "cloud-fit" solution, meaning it meets all the technical requirements and is optimized for deployment in the cloud.

At this stage, your development team should follow best practices and the latest guidelines provided by Microsoft for Business Central extensions, ensuring that your app will function smoothly in the Microsoft ecosystem.

Once your app is developed, the next critical step is thorough testing. Microsoft does not test apps manually, so it’s your responsibility to ensure that your app does not cause any issues for customers, especially data corruption or loss.

• Test your app rigorously to ensure it functions as expected.
• Create two key documents:
  • A supporting document outlining how to use the app.
  • A Key Usage and Benefits document highlighting the features and advantages of the app.

After testing, you will need to upload these documents along with your app on the Microsoft Partner Center portal. To create a new offer, log in to your Microsoft Partner Center account, and navigate to the Marketplace Offers section to create a new offer.

Before uploading your app to AppSource, you must ensure it is signed with a Code Signing Certificate. Microsoft requires this certificate to verify the authenticity and integrity of your app.

• You can purchase a Code Signing Certificate from a provider like GlobalSign.
• Once you have the certificate, use tools like signtool to sign your .app file.

For example, you would run the following command to sign your app:

cd C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x64

signtool sign /a /tr http://timestamp.globalsign.com/tsa/r6advanced1 /td SHA256 /fd SHA256 " path_to_your_app_file.app"

Be sure to keep your credentials and passwords secure, especially if you are using a USB token for code signing.

Once your app is digitally signed, you can upload it to the Microsoft Partner Center. Go to the Technical Configuration tab and upload the signed app file. After filling out all the necessary information, click on the Review and Publish button.

After submitting your app, Microsoft will perform an automatic validation process, which typically takes a few hours. You’ll receive an email notification if there are any issues or errors related to the app’s technical validation checklist.

It's important to note that Microsoft’s validation process checks for things like compatibility, performance, and security standards. If there are issues, you will need to fix them and resubmit your app.

While the process might seem straightforward, there are a few critical factors to keep in mind to avoid common pitfalls:

When publishing your app, you will be asked to define its availability across different countries. Be cautious when selecting global availability, as some countries may have outdated versions of Microsoft products or specific regional dependencies that could cause errors during validation. If such errors arise, you may need to adjust your app’s source code to accommodate country-specific requirements.

When updating an app on AppSource, always remember to increment the version number in your app.json file. This is crucial for ensuring that the new version is recognized properly. Additionally, make sure that no breaking changes are introduced, such as deleting tables or changing data types in a way that could impact existing installations.

If you want to offer a free trial of your app, there are no built-in options in Partner Center to set an expiration date. You can either:

• Provide a limited-feature version that doesn't impact your licensing model.
• Implement a custom licensing system, such as using PowerApps, to generate unique license keys for each installation. This system can track when a trial should expire and allow you to deactivate the app when needed.

Providing a "Test Drive" option for your app is a great way to give potential users a taste of your product without them needing to install it. This is typically done via a sandbox environment with pre-configured data.

However, be careful not to test the feature using your own Microsoft account if you are part of the development organization. Doing so may convert your account to an external user, losing your admin rights in your company’s Azure Active Directory.

If you choose to sell your app through Microsoft, you will need to configure purchase plans, including options for annual or monthly payments. Ensure that your app’s AL code supports entitlements, which manage user access to purchased products. Microsoft provides detailed documentation on how to configure these plans and entitlements.

Publishing an app on Microsoft AppSource is a powerful way to expand your reach and offer your solutions to a global audience. By following the steps outlined above and keeping in mind the critical technical and administrative requirements, you can ensure a smooth and successful submission process.

#MSDyn365BC #MSDyn365 #MSDyn365BusinessCentral #BusinessCentral #MicrosoftAppSource #Microsoft #AppSource #BizzApps #PublishonAppsource