Copilot Studio

Custom topics missing in localization file downloaded from the agent.

(2) Share

Report

Posted on by CN91

110

Hello everyone,

I am trying to make my agent multilingual but I have an issue with the localization file downloaded from my agent.

When downloading the localization file from my Copilot Studio agent, my authored custom topics are not included in the exported JSON and ResX files. Only a few system topics are included.

The localization file I downloaded should include all authored text, such as messages, prompts, quick replies, and trigger queries, from both system and custom topics so that they can be translated and uploaded back. However, only a few system topics are included in the downloaded file.

MS documentation says to open the solution to download the previous version but there is no clear instruction to follow.

Could someone advise how can I include all the topics and contents in the Localization file?

Thank you in advance.

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

Ehsan Khan 16 on at

Like (1)

Report
Hi @CN91,

You're not alone; this is a common issue when trying to localize Copilot Studio agents. The key is where you export the localization file from.

I think the main cause:
If you export the localization file directly from the agent overview (outside of a solution), it typically includes only system topics. Custom-authored topics, like your messages, prompts, quick replies, and trigger phrases, won’t be included unless the agent is part of a solution.

How to Export a Complete Localization File (Including Custom Topics)

Open Power Platform -> Solutions
Navigate to the solution that contains your Copilot Studio agent.

Open the Agent from Within the Solution
This ensures you're accessing the full context of your agent, including custom topics.

Go to Languages -> Export Localization File
This export will now include all authored content, system, and custom topics alike.

Pro Tip
If your agent was created outside a solution, consider moving it into one. This unlocks full localization support and better lifecycle management.

Hope this helps.

1 people found this reply helpful.

Was this reply helpful? Yes No
CN91 110 on at

Like (0)

Report

Hi @Ehsan Khan,

Thank you very much for the detailed steps but I am still having the same issue although I followed the steps opening the agent via Solution.

Do you have any workaround, please?

Was this reply helpful? Yes No