Teilen über

Maintain AppSource apps and Per-Tenant extensions in Business Central online

As a partner, keeping your apps and per-tenant extensions (PTEs) up to date is your responsibility. Business Central is regularly updated with major and minor releases. These updates provide customers with a business application that is always compliant, secure, and enriched with new platform and application functionality. Often customers choose Business Central because of this promise of having an always up-to-date business solution.

To not break this promise, developers that bring apps to Microsoft AppSource, and resellers that provide PTEs to respond to the unique needs of customers, have a responsibility to align their code to the Microsoft release rhythm.

The following diagram illustrates the time for how updates roll out for Business Central online and how you can use previews to test your apps ahead of time:

Timeline for preview environments and major updates

An inability for Microsoft to update tenants because of publishers incompatible code causes serious disruption in the service and must be avoided since it impacts the trustworthiness of the service and customer satisfaction.


To help app publishers keep up with their update responsibilities, Microsoft provides the following resources:

  • Release plans about what's new and planned

    For more information, see Dynamics 365 release plans.

  • Access to pre-release bits

    Business Central partners have access to the next major, next minor, and daily pre-release bits in Docker through Microsoft Collaborate. To get access to Collaborate, follow steps 1 and 4 in the article. Use the pre-release bits to test apps against upcoming updates.

    Learn about the update lifecycle for apps and extensions and automated extension validation. Use the AppSourceCop analyzer rules to keep your code compliant. Get agile with AL Go for GitHub and stay on top of changes that way.

  • Information about what will be deprecated

    With all Business Central releases, Microsoft controls and regulates breaking changes with major releases and communicates upcoming breaking changes at least one year in advance. If developers missed this above info, the compiler in Visual Studio Code also warns for potential controls that will become obsolete in future versions and how to deal with them. Use the analyzers actively to make sure your code is ready for the next update.

  • Policy definitions and terms

    The publisher agreement and the commercial marketplace certification policies describe the responsibilities of app providers for how to publish and maintain apps in the Microsoft monthly rhythm.

    When a PTE gets installed, the publisher also agrees to the terms to keep that code current and updatable.

  • Training and coaching

    Microsoft provides a set of tools, training, and documentation to help partners find the info they need to keep up with these responsibilities on continuous integration and continuous deployment. External providers, including ISV Development Centers, MasterVARs, and training centers, can provide in-person training and coaching.

  • Service notifications

    Business Central online will support app and PTE publishers with extra warnings about potential technical incompatibility. If publishers respond to these notifications in due timing and avoid incompatibilities repeatedly, Microsoft will stand with these publishers to help where needed. If a publisher includes a telemetry key in their app, then, starting with 2020 release wave 2, Business Central also provides publishers with telemetry about upgrade failures that happen in production because of issues in the publisher's upgrade code.

If publishers lack to keep their code updatable, they risk that ultimately their apps or PTEs will be removed from the customer's tenant, and this will most likely result in important data not being captured as it should. For apps, this also means removal from the marketplace.

Since resellers are the first line contact point for customers, they carry responsibility to explain what it means to load code in a customer's environment. The best way is to explain this is with terms.

We advise these terms include articles like intellectual property rights, upgrade responsibilities, associated costs to keep code updatable, support options, data privacy, and so on.

Pre-release publisher support to keep apps and PTEs compatible and up-to-date

Publishers have several tools available for them to keep their code in good shape. Not least, a Public Preview release is made available approximately one month before the announced release date for a major release. In that Public Preview release time frame, Business Central will automatically test and notify publishers of existing apps and PTEs running in production on technical incompatibility with the upcoming release.


Microsoft tests code based on technical compatibility. As the publisher, you are still responsible for all functional and logical validation. For more information, see The Lifecycle of Apps and Extensions for Business Central.


If an app has been published through AppSource, it should not be tested, installed, or in other ways treated as a PTE since this will create conflicts.

When apps or PTEs can't be updated by Microsoft

This section describes the processes that are initiated during and after upgrade attempts of code provided by publishers of apps or PTEs. For information about handling a PTE that has conflicts with another extension, see Upgrading Per-Tenant Extensions that Conflicts with Other Extensions.

  • T+1 – T+30: Microsoft alerts administrators, resellers, and ISVs

    Shortly after a service update of Business Central online (Day T), Microsoft will initiate daily updates attempts on all tenants. In these update attempts, the publisher's provided upgrade code is triggered and run. These attempts run repeatedly in a time frame of approximately one month until the upgrade is successful. For more information, see Major Updates of Business Central Online.

    With every unsuccessful upgrade attempt, stakeholders will receive notifications. Customers and their reselling partners can follow these notifications in the Business Central administration center.

    ISVs who provide third-party AppSource apps might not be listed in the customer's admin center. The reseller will in most cases have worked with the ISV to test compatibility, but after two weeks (Day T+15) of failed upgrade attempts, the Microsoft AppSource team will also send the app provider a warning message that action within the next few days is required. Incompatible extensions can be uninstalled within 14 days if they prevent deployment of security updates.

    This message will explain that if they fail to respond correctly, their app will be removed from AppSource at Day T+30.

  • T+30 – T+60: Microsoft alerts the customer

    After one month of failed upgrade attempts (Day T+30), the customers will be notified again that apps or PTEs are incompatible with the new version of Business Central, and that no further automatic upgrade attempts will be planned until further notice. Although the publisher's code continues to run on an outdated version of Business Central online, the customer must work with their reseller to resolve these issues immediately so that the tenant can be updated. Next to messages in the Business Central administration center, all users in the customer's tenant will also get more active warning about the incompatibilities when they use the product in the browser or their mobile device.

    For AppSource apps, if no appropriate action or follow-up was taken by the publisher since the release (T - T+30days), the app will be removed from AppSource. This means no new customer will be able to install the app in a new tenant. The main reason for removing an app from the marketplace is to ensure that no new customers will be affected by incompatibilities with the latest version of the base product, Business Central.

    If the publisher wants to have their app available again, they must mitigate all existing incompatibility issues and go through the full validation process again.

    If the source of the incompatibility has been resolved by the publisher, they'll have to submit a support request to schedule a new set of upgrade attempts for any tenants that are blocked because of this incompatibility. They'll also have to work with their resellers to inform them about the compatibility resolution.

  • T+60 – T+150: Microsoft initiates the customer wind-down period

    If the incompatibility issues aren't resolved at T+60, and the publisher remained unresponsive to the request to resolve the incompatibility, Microsoft might choose to send out a wind-down communication to the customer about removal of the publisher's code.

    This communication will share that the code from the publisher will be removed in 90 days from the day of the communication from Microsoft (T+150).

    During this wind-down time, the customer and their reselling partner are fully responsible for finding a solution on how to proceed in this situation. If the customer decides to leave Business Central, or decides to use another publisher, they can access their data by exporting the database, use RapidStart Services, or copy data to Excel. For more information, see Exporting Your Business Data to Excel in the business functionality content.

    Microsoft may also choose to remove all existing apps by this publisher from AppSource and block the publisher from publishing new apps for Business Central.

    If this wind-down period is initiated, and the customer was able to fix the incompatible issues with their reseller and potential publishers, it will be at Microsoft discretion if the publisher's code will be removed from Business Central or not.

Get notified about incompatibilities by Microsoft

It's crucial for you to keep contact details correctly up to date. We advise you to use global team aliases instead of individual mail addresses. Here are the mail addresses that we'll use in the process that is described in the When apps or PTEs can't be updated by Microsoft section:

  • PTE publishers

    The mail addresses specified in the Business Central administration center; this could be both a customer user and a partner user.

  • App publishers

    The mail addresses specified during App publication in the partner center during app publication as support and engineering contact details.

  • Customers

    The mail addresses specified in the Business Central administration center; this could be both a customer and a partner user.

See also

The Lifecycle of Apps and Extensions
Update Lifecycle for Customizations
Microsoft Responsibilities for Apps on Business Central online
Technical Support for Business Central online
Sending Extension Telemetry to Azure Application Insights
Major Updates and Minor Updates for Business Central Online