SystemsMicrosoft Dynamics 365Localization matrix

Where Microsoft Dynamics 365 is localized

Statutory and fiscal localization decides whether a system can be used in a country at all, and it is the question a multi-entity buyer asks first. Every row below was read from the vendor's own availability documentation, cited at the foot of the page.

43 countries recorded16 by the vendor27 by a partnerRetrieved 2026-09-07

Back to the Microsoft Dynamics 365 profile

01How to read this

Microsoft's own table states, per country, whether the localization is delivered by Microsoft or by a partner building on the international (W1) base app. Those two columns are recorded here as native and via partner. The table covers far more countries than are listed here; this record carries the markets Stackmark tracks across vendors.

Localized by the vendor Localized by a partner No localization Not verified by Stackmark

02Countries

CodeCountryLocalizationWhat the source says
ARArgentina Localized by a partnerPartner localization on the W1 base appSuggest a correction
AUAustralia Localized by the vendorAU base appSuggest a correction
ATAustria Localized by the vendorAT base appSuggest a correction
BEBelgium Localized by the vendorBE base appSuggest a correction
BRBrazil Localized by a partnerPartner localization on the W1 base appSuggest a correction
CACanada Localized by the vendorNA base appSuggest a correction
CLChile Localized by a partnerSuggest a correction
COColombia Localized by a partnerSuggest a correction
HRCroatia Localized by a partnerSuggest a correction
DKDenmark Localized by the vendorSuggest a correction
ECEcuador Localized by a partnerSuggest a correction
EGEgypt Localized by a partnerSuggest a correction
FRFrance Localized by the vendorFR base appSuggest a correction
DEGermany Localized by the vendorDE base appSuggest a correction
GTGuatemala Localized by a partnerSuggest a correction
HKHong Kong Localized by a partnerListed as Hong Kong SARSuggest a correction
HUHungary Localized by a partnerSuggest a correction
INIndia Localized by the vendorMicrosoft localization on the W1 base appSuggest a correction
IDIndonesia Localized by a partnerSuggest a correction
ITItaly Localized by the vendorIT base appSuggest a correction
JOJordan Localized by a partnerSuggest a correction
KEKenya Localized by a partnerSuggest a correction
LULuxembourg Localized by a partnerSuggest a correction
MYMalaysia Localized by a partnerSuggest a correction
MXMexico Localized by the vendorNA base appSuggest a correction
NLNetherlands Localized by the vendorNL base appSuggest a correction
NZNew Zealand Localized by the vendorNZ base appSuggest a correction
OMOman Localized by a partnerSuggest a correction
PEPeru Localized by a partnerSuggest a correction
PHPhilippines Localized by a partnerSuggest a correction
PLPoland Localized by a partnerSuggest a correction
RORomania Localized by a partnerSuggest a correction
SASaudi Arabia Localized by a partnerSuggest a correction
SGSingapore Localized by a partnerSuggest a correction
ESSpain Localized by the vendorES base appSuggest a correction
CHSwitzerland Localized by the vendorCH base appSuggest a correction
TWTaiwan Localized by a partnerSuggest a correction
THThailand Localized by a partnerSuggest a correction
AEUnited Arab Emirates Localized by a partnerSuggest a correction
GBUnited Kingdom Localized by the vendorGB base app, migrated to W1 with 2025 wave 2Suggest a correction
USUnited States Localized by the vendorNA base appSuggest a correction
UYUruguay Localized by a partnerSuggest a correction
VNVietnam Localized by a partnerSuggest a correction

Alphabetical by country. A country absent from this table is one the vendor’s documentation does not speak to, which is a gap in our record rather than a statement that the system cannot be used there.

Know a country this table has wrong or missing? Suggest a correction. It opens a public issue, prefilled with what we publish today.

03Questions for the demonstration

The country-specific layer: local chart of accounts, statutory report formats, tax rules, e-invoicing clearance, and the languages the interface and printed documents run in. This is where an otherwise capable system quietly turns out to be unusable in a given market.

  1. Q1

    Which of our countries are covered by your own localisation, and which depend on a partner's add-on?

  2. Q2

    Who maintains a localisation when a tax authority changes the rules mid-year, and what is the usual lag before it ships?

  3. Q3

    Is e-invoicing clearance — ZATCA, Peppol, SAF-T, whichever applies to us — native, or does it go through a certified third party?

  4. Q4

    Can one entity report on a local statutory chart while the group consolidates on a different one?

04The same country in other systems

Stackmark has read localization documentation for 2 of the 53 profiled systems so far. Where another system records a country, its matrix is one link away.

  • Odoo43 countries recorded

05Sources

The vendor’s own availability documentation, retrieved on the date shown. The reading of it — which column counts as the vendor’s own localization and which as a partner’s — is Stackmark’s, and stated above.

  1. [1]Country/Regional Availability and Supported Languages - Business Centralhttps://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/compliance/apptest-countries-and-translations · retrieved 2026-09-07