Microsoft Dynamics 365 Translation Service support ends on October 15, 2025

(6) Share

Report

Posted on by CU08052056-0

1,292

Hi experts!

You know that Microsoft Dynamics 365 Translation Service support ends on October 15, 2025, below.

Removed or deprecated platform features - Finance & Operations | Dynamics 365 | Microsoft Learn

Which tools do you recommend translating Dynamics 365 Business Central UI language from Englich to Japanese?

Hope your suggestions!

Nobuhara

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Verified answer

YUN ZHU 101,995 Super User 2026 Season 1 on at

Like (4)

Report
Copy link

Link copied!

Hi, Microsoft recommended Custom Translator, which I am testing now. It is much more complicated than the previous one and requires a paid environment. You can also research it first...

Microsoft Dynamics 365 Translation Service support ends on October 15, 2025

Thanks.

ZHU

Was this reply helpful? Yes No
Suggested answer

Ramesh Kumar 7,566 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Microsoft recommend using https://learn.microsoft.com/en-us/azure/ai-services/translator/custom-translator/overview

I have not tried it but it is on Microsoft documentation

Thanks

Ramesh

If this was helpful, please check the "Does this answer your question?" box and mark it as verified.

Was this reply helpful? Yes No
Suggested answer

Sohail Ahmed 11,177 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

adding more details

https://learn.microsoft.com/en-us/azure/ai-services/translator/custom-translator/overview

✅ Mark this answer as verified if it helps you.

Was this reply helpful? Yes No
Suggested answer

Jeffrey Bulanadi 9,128 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!
Hi Nobuhara,

With the Microsoft Dynamics 365 Translation Service (DTS) reaching end-of-support on October 15, 2025, it’s important to pivot to sustainable alternatives for UI translation in BC.

The recommended approach is to use XLIFF (.xlf) translation files, which BC supports natively. You can generate these by enabling "TranslationFile" in your app.json, then translating the <source> strings to Japanese in the /Translations folder. This method is fully supported and aligns with AppSource requirements.

For translation tooling, here are a few solid options:

Microsoft Custom Translator — a neural machine translation service that supports domain-specific training for Japanese. You can upload translation memory files and train models for better accuracy.

Multilingual App Toolkit (MAT) — includes a free XLIFF editor that works well for manual translation and review.

XLIFF Sync (VS Code Extension) — streamlines translation workflows by auto-generating target files and syncing untranslated strings.

Partner Translation Toolkit — useful for legacy NAV/BC platform strings, though limited to On-Prem scenarios.

If you’re translating standard extensions like Base Application, you can extract their .xlf files, merge them, and create a Japanese language pack. Just be sure to rename the files properly and set the correct target-language (e.g., ja-JP).

Helpful References:
Working with translation files – Microsoft Learn
Custom Translator Overview – Microsoft Learn
XLIFF Translation Guide – Dynamics 365 Lab
Partner Translation Toolkit – Microsoft Download Center
Translation files tips – Simplanova

If you find this helpful, feel free to mark this as the suggested or verified answer.

Cheers
Jeffrey

Was this reply helpful? Yes No