Localization opportunities and (current) limitations

After we launched Microsoft Dynamics 365 Business Central, we started receiving lots of questions about localization. Transitioning Business Central to the cloud has created limitations and opportunities for localization that weren’t present for Dynamics NAV.

We want to expand the use of Business Central by making the product available in more countries. To this end we’re using a partner-driven localization approach to roll out the product to new countries, and we’re getting great feedback.

However, there are also many questions about how localization works compared to Dynamics NAV, and how to achieve certain scenarios. Some of those scenarios are currently not achievable and this post is meant to help clarify the current status by describing some of the options and limitations. 

Frequently asked questions on localizations

Question #1: I want to have Business Central available in a new country that is not already on this list. What is needed for that?

There must be at least two localization apps available for the country: one that covers regulatory functionality and one that covers translation of Business Central.

Question #2: What is a localization app?

A localization app can be an add-on app, a connect app, or any combination of those, that adds local functionality to Business Central. It is showcased on AppSource and installed by partners. See the guidance below regarding the minimum scope for localization apps.

Question #3: How do I get started with localization apps?

Most importantly, reach out to your local or regional Microsoft contacts. They can help you build a business case for enabling Business Central in your country. Also, please read the guidance for the process on https://aka.ms/BusinessCentralLocApps. Building localization apps is the same as building other apps. What you need to do is consider how you bring functionality to the user. By extending the Business Central user interface with Add-on apps or by connecting external services through APIs with connect apps, or both.

Question #4: Where do I get started with developing apps for Business Central?

The best place to get started is at https://aka.ms/readytogo, where you'll find all the information you need. Also, we highly encourage you to ramp up your app development skills with one of our ISV Development centers, which are also available through Ready to Go.

Question #5: How do I get access to Business Central to start developing localization apps?

You start by signing up on http://aka.ms/collaborate. Here you will get access to daily builds of both current and future versions of Business Central that you can download as Docker images. This lets you run a cloud-like instance of Business Central on which you base your development.

Question #6: What is the minimum scope of a localization app?

Be sure to include functionality that covers regulatory requirements. Consider if this functionality can be split up into multiple apps. It will have the advantage of easier maintenance and troubleshooting as well as creating opportunities for up-selling functionality.

Question #7: There are user scenarios that I cannot satisfy by building an add-on app (extension) for Business Central. What do I do?

Are you sure? Try rethinking the functionality. Could it be achieved using other technology? Could you build an external system or service that could connect to Business Central through APIs? If you have built a localization for on-premises Dynamics NAV in the past, chances are that you can rethink and restructure your functionality.

Question #8: There is other non-regulatory functionality that customers want in my country. Can I bundle this in the localization app with regulatory functionality?

No. functionality that is not related to regulatory requirements must go into other localization apps. As a general rule, consider splitting up functionality into several apps with the minimum of separating regulatory functionality, national standards, and other local features. We want to be enable customers to pick and choose apps as they see fit, and building large monolithic apps with a lot of functionality prevents them from doing so. Also, consider the monetization models for having different apps and subscriptions and how you can benefit from the recurring revenue coming from app usage.

Question #9: How do I monetize my localization apps?

Just like with any other apps on AppSource, you have to implement monetization code yourself. This gives you total flexibility to call external services and handle payment and usage. See more about monetization in this whitepaper.

Question #10: How do I make sure I fulfill all the requirements for my localization apps to pass technical and marketing validation?

We have made detailed checklists that provide details about what you should pay attention to and make sure to cover before submitting your apps for validation. For more information, see this technical checklist.

Question #11: My localization apps have passed technical and marketing validation. When will Business Central go live in my country?

Stay in contact with the Business Central localization team at Microsoft. The team will inform you of the estimated service enablement timeframe.

Question #12: About languages - can I add language packs to a Business Central tenant like with Dynamics NAV?

Currently you can only add AppSource translation localization apps for the country for which the app was built. You cannot use this translation app for other country tenants. This is due to a limitation in the Business Central server that limits the languages on the tenant to the primary country language, plus English. Another reason is that these translation apps are currently meant for enabling Business Central in new countries by partner localization, and not as extra languages in other countries. We want to enable multi-language for any country and the platform languages that currently exist actually live in every country's tenant. It is just not surfaced due to the server limitation.

Question #13: My company has subsidiaries in different countries. How can I setup an environment where I use one Microsoft 365 account and several localizations of Business Central?

Currently, when you sign up up your organization for Business Central, we automatically provision the localization that matches the country specified in your Microsoft 365 account. You can find more details about that here. As a result, to get a different or additional localization of a Business Central tenant in another country - to serve another subsidiary – you need to create and use a Microsoft 365 account in the country and create a separate Business Central and Office 365 subscription for it too. Users in subsidiaries in different countries will have to use different credentials for Business Central. We are working on finding a more convenient option for you to set up a multi-country environment in the future. In our early assessment, the future design will allow you to use the same Microsoft 365 account to work with multiple Business Central production environments, each deployed within their own region and following data compliance rules. At this point, the feature is planned for the Fall 2019 release of Business Central.