Copilot in Power Automate: An Honest Hands-On Test (Officially “Optimized for English”)

Copilot in Power Automate promises that you can simply describe flows in plain language and the automation almost builds itself. Sounds great, and in many demos that's exactly how it looks. What's rarely mentioned in those demos: Microsoft states explicitly in its own documentation that Copilot is optimized for English and only supports other languages to a limited extent. For a German-speaking team, that's not a footnote, it's information that directly affects how well the tool works in everyday use.

This article is an honest hands-on test in German. We show you what Microsoft officially says about it, what actually works in practice with German prompts, where it falls short, and which prerequisites and tricks get you better results. In the end, you stay in control of whether you use Copilot in German, switch to English, or combine both depending on the task.

What Microsoft officially says about the language caveat

This note isn't hidden away in a footnote, it sits right in the important callout box of the official guide Create your first cloud flow using Copilot. It states verbatim: "Copilot is a new technology in active development. It's optimized for use in the English language and offers only limited support for other languages. As a result, portions of it may appear in English instead of your preferred language."

It's even clearer in the Copilot in cloud flows FAQ. There, in the section on functionality, a single, unambiguous sentence states: "The cloud flow Copilot only supports the English language for models." That's not a vague limitation, it's a clear statement you should factor into your automation planning before rolling out Copilot to a German-speaking team.

The hands-on test: what actually works in German

In practice, the picture is mixed. Simple, clearly structured prompts in German are usually understood reliably by Copilot, for example phrasing like "If an email arrives from a specific sender, send a notification in Teams." Triggers and actions are suggested correctly, connections are set up, and you can keep editing the flow as usual.

It gets harder as soon as you ask Copilot to explain your flow or answer product questions. The official guide explicitly names examples like *What does my flow do?* or *How do I access licenses?* for exactly these features, and this is precisely where the answers are most likely to slip into English in practice, or a mixed text of German and English sentence fragments emerges. Multi-part, nested instructions in German also see a noticeably higher error rate, though regardless of language that's inherent to Copilot anyway, as Microsoft's own tips page acknowledges.

Where it falls short in practice

The Tips for Copilot in Power Automate designer openly lists what Copilot currently can't do, regardless of language: it doesn't read runtime errors or execution logs, it doesn't access your SharePoint lists or Dataverse tables, and deeply nested conditions with many branches frequently lead to unexpected results. In German, an additional source of errors is that field names, technical terms, and connector names are often named in English, while your prompt is phrased in German. This language mix adds to the risk of misunderstandings on top of the tool's existing limits.

There's also an interesting detail at the bottom of the tips page: Microsoft itself notes there that the article was created with the help of AI. That fits the overall picture: Copilot in Power Automate is a tool under active development, one where Microsoft itself is open about its limits rather than hiding them.

Prerequisites many people overlook

Beyond language, there are other points from the official FAQ that are often overlooked in practice. Copilot in cloud flows is available by default only in certain regions; outside those regions, an administrator must explicitly enable data movement for generative AI features in the Power Platform admin center. Personal Microsoft accounts such as an @live.com account don't work, you need a work, school, or university account. And in terms of licensing, you need either a standalone Power Automate license or a suitable seed license from Microsoft 365, PowerApps, or Dynamics, otherwise the Copilot area in the designer simply stays grayed out.

Practical tips for everyday use with Copilot in German

A few rules that make a difference emerge from the hands-on test and the official recommendations:

• Phrase prompts short and with only one intent per message, instead of chaining several steps into one sentence.
• Name field names, connectors, and values specifically, for example "Status" instead of "the approval," so Copilot doesn't have to guess.
• Feel free to use English terms for technical jargon when you know that's what the connector or field is actually called.
• Check the generated parameters in detail after every Copilot action, especially with dynamic content, before you save.
• Save your flow before larger Copilot changes, so you can easily revert to the last version if the result is unexpected.
• If an answer slips into English or becomes imprecise, rephrase the prompt shorter and more precisely instead of repeating it.

Conclusion: Is Copilot still worth it for German-speaking teams?

Yes, with realistic expectations. For quickly setting up simple trigger-action combinations, Copilot works well enough in German to save time. As soon as it comes to explanations, more complex logic, or product questions, the tool noticeably switches to English more often or delivers less accurate results, exactly as Microsoft itself states. Anyone who knows this in advance can consciously decide when a German prompt is worthwhile and when a short English prompt gets to a clean result faster. If you want to use Copilot productively in your team and also need to clarify questions about licensing, region, and governance, the NordFlux Power Automate consulting can help you turn the hands-on test into a solid rollout plan.

Frequently asked questions

Is Copilot in Power Automate usable in German at all?

Yes, simple prompts in German are usually understood reliably and translated into matching triggers and actions. For explanations, product questions, and more complex customizations, however, the risk increases that answers appear partly or entirely in English.

Why does Copilot sometimes switch to English mid-conversation?

Because the underlying model, according to the official documentation, is optimized for English and only supports other languages to a limited extent. Microsoft explicitly points out that parts of the output can therefore appear in English, even if your input was in German.

What prerequisites do I need to use Copilot in Power Automate?

You need a work, school, or university account, a suitable license such as a standalone Power Automate license or a seed license from Microsoft 365, PowerApps, or Dynamics, and your environment must either be in a region with Copilot availability or be enabled for it by an administrator.

Should I just write my prompts in English right away?

For technical jargon, field names, and connector names, that can improve the hit rate, because these are often named in English behind the scenes anyway. For the basic description of your task, German is usually enough for simple, clearly phrased prompts.

Will Copilot's language support improve further?

Microsoft describes Copilot in its own documentation as a new technology that remains under development. Microsoft does not name a concrete date for better support of languages other than English in the currently available official sources, which means the current limitation should be understood as the current state of things, not a permanent one.