Dynamics 365 Business Central: Universal Code and Microsoft’s apps problems.

In these days lots of partners raised a problem appearing on lots of Dynamics 365 Business Central on-premises customers after upgrading their licenses (I’ve personally received lots of requests on my socials about this problem by many of you, so I suspect that the problem is hot and not well known).

The error appears after the user’s login and it’s something like the following:

Starting from October 2022, all apps in a Dynamics 365 Business Central environment have to support the Universal Code initiative. The Universal Code initiative is designed to encourage the use of a modern architecture in customer implementations of Business Central. As of October 2022, new Dynamics 365 Business Central customers deploying on-premises and customers transitioning to Dynamics 365 Business Central on-premises deployments will have to deploy a “cloud-optimized extensions” architecture (Universal Code) or license payable modules that unlock classic customization behavior. I’ve talked about that in the past here.

What does that mean practically? That your extension need to avoid having target = onPrem in the app.json file. Otherwise you need to insert in your customer’s license one or both the above modules:

  • Module “Implemented code is not in extensions”: if implemented partner code includes base application modifications, this module must be licensed.
  • Module “Implemented code is not cloud-optimized”: if the implemented extensions have target = OnPrem, this module must be licensed.

The problem here is that the above error appears on customer’s environment where no custom apps are installed or where all installed apps are cloud-compliant extensions. So, how to fix this error?

This error appears only if you have an on-premises customer running Dynamics 365 Business Central version <= 21.5 and where you have updated the license (server restart). This is mainly due to a code-signing certificate expiration date.

To fix this problem, a technical upgrade is required. Here is a summary of the updates that you need to apply to fix the problem:

VersionMinimum CU to fix the problemFixed Platform
1919.1854863
2020.1254861
2121.654757
2222.055180

Please note that ONLY a technical upgrade is required (no need to update the Application). Standard full upgrade is however my personal recommended solution.

8 Comments

  1. Microsoft forces its partners and clients to comply with a set of rules and restrictions that it itself does not follow. What a beautiful world we live in.

    Like

  2. This problem was a real doozy and caused me so much issue. If I hadn’t worked out I could back date the server while starting the service, our company could have ground to a halt! Pretty poor by Microsoft, at least the fix was quick.

    Like

  3. Thank you for the great info.
    The Base App that comes with BC21.6 installation media also expires on 11.05.2023, but it’s working with that anyway.
    Do you know if the Certificate is auto-renewed from now on, or will we run into the same issue a year from BC21.6 release?

    Best regards,
    Jesper

    Like

      1. Thank you for this positive answer 🙂 We have a customer that is rather nervous after all this and he is asking for a link or similar to an official post about this (that the problem is fixed for good). Can you help us with that? Your help is highly appreciated.

        Like

  4. Hi Demiliani
    We are still in BC22.2 experiencing this issue, also with MS apps, but not your complete list.
    Any thoughts?

    Something went wrong.
    Sorry, we can’t sign you in. You’re using a customized version of the following Microsoft applications, which doesn’t meet our Universal Code requirement:

    Application by Microsoft
    Base Application by Microsoft
    System Application by Microsoft

    You must either upgrade the apps to meet the requirement or license the non-Universal Code module that grants an exception to the requirement.

    For more information, see https://aka.ms/bcUniversalCode.
    Date and time: Thu, 05 Oct 2023 07:07:58 GMT
    Azure AD tenant: common
    Operation: fbfe70389a5d451c9342bfc36cfbef44

    Executable is 22.0.57579.0

    /Erik

    Like

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.