Beyond translation: How we’re making Microsoft Copilot work better in Japanese

As we rolled out Microsoft Copilot across Microsoft, our employees and customers in Japan made one thing clear: Accurate translation is only part of the job. Copilot must also get people’s names right, follow meetings that move between Japanese and English, and match the level of politeness that Japanese business communication expects. In Microsoft Digital, the company’s IT organization, we serve as Customer Zero for Microsoft. We use our products first, at enterprise scale, and share what we learn with the teams that build them. In May 2025, we described the language and cultural challenges we were seeing with Copilot in Japan in “Breaking language barriers: Our journey to perfect Microsoft 365 Copilot localization.” Since then, we’ve worked with the Copilot product group and our colleagues in Japan to turn those findings into fixes, a repeatable way of working, and measurable gains in adoption. In this article, we explore what we changed, what it means for our employees in Japan, and what lessons you can apply as you roll out Copilot in other languages at your company. Kevin Kotani explores how feedback from Japan is helping Microsoft make Microsoft Copilot more accurate, natural, and culturally relevant. Kotani is a digital experience lead in Microsoft Digital. Building a feedback loop that scales Our localization work for Copilot in Japan spanned many teams across several organizations. That led to duplicate bug reports, competing priorities, and multiple escalation paths for the same issue, so we decided to start changing how we worked together. We formed a localization virtual team (v-team) in Japan to connect our field teams with our engineering teams. In regular syncs, the Japanese field team, the Copilot product group, and language experts review issues together, agree on priorities, and route each problem to a clear owner. This more streamlined, shared path for reporting issues reduced duplicate reports and got Japanese issues to the right engineers more quickly. We also made changes to make localization measurable. We track: Pre-release catch rate: Localization issues we find during Customer Zero testing, before features reach customers Support volume and speed: The number of localization-related support tickets and how long they take to resolve Internal readiness: How quickly feature announcements and training materials are translated and shared with local teams Sentiment: Feedback trends from Japan, aiming for more feedback overall and a 30–50% drop in “disliked” Copilot responses related to language These measures give us a consistent plan-do-check-act cycle for improving Copilot in Japanese. Improving accuracy in multilingual meetings Meetings at a global company like Microsoft often switch between Japanese and English, which makes accurate transcripts and recaps one of the toughest tests for Copilot. That made meetings an early focus for our localization work with the product team. A series of speech model updates raised name recognition accuracy in Japanese meeting transcripts from about 40% to 66%. The updates also improved how Copilot recognizes English names and terms spoken in Japanese meetings, cutting the transcription error rate for English content from about 90% to 27%. We also helped resolve an issue with how Copilot displayed kanji names. Copilot sometimes read the honorific さん (san) as part of a person’s name, which would garble the names in its output. The fix was rolled out worldwide, removing a major adoption blocker in Japan. The same update also improved how Copilot detects a person’s preferred language, reducing cases where it switched languages by mistake by about 2.5% in mixed-language settings. Together, these changes make meeting notes and recaps in Japanese more coherent and accurate, even when a meeting uses more than one language. Getting tone and etiquette right Early feedback showed us that Copilot Japanese often lacked the politeness and nuance that people expect at work. With native-speaking linguists, localization experts, and the product team, we tuned the Copilot tone and interface text toward more natural professional Japanese, including polite forms and consistent terminology. Model updates trained on more diverse multilingual data made Copilot Japanese responses more fluent and relevant. We’ve also worked to close the gap between what content and features are available in English and in Japanese. By mid-2025, Copilot training modules were available in Japanese and six other languages. We continue to work with the Copilot engineering teams to launch new capabilities in Japanese as early as possible. As a result, employees and customers in Japan now see far fewer “not available in your language” messages. Today, Copilot supports prompts and responses in 48 languages for work and school accounts, including Japanese. Key milestones in Japan Our work to improve the Japanese Copilot experience evolved through several rounds of testing, feedback, and refinement. Each stage helped us identify language and cultural nuances and move the experience closer to what Japanese users expect in their everyday work. July 2025: More than 300 native speakers joined a Japan preview program through Microsoft Elite, helping us identify language and cultural issues before broad rollout. August–September 2025: We addressed key issues involving date and time references, honorifics, and kanji name display. The fixes rolled out worldwide and removed a major usability blocker for people working in Japanese. October 2025: We refined Copilot’s tone and interface text to make professional Japanese feel more natural. Copilot Keyboard also entered public beta, improving cultural fit and trust in business communication. February 2026: We expanded Copilot Keyboard early access through Microsoft Elite, giving us a broader base of employee feedback on Japanese input. April 2026: Copilot Keyboard reached general availability, making the improved Japanese input experience available to anyone using Windows 11. Better Japanese input with Copilot Keyboard Some of the friction with AI tools starts before Copilot ever sees a prompt—at the keyboard. Typing Japanese means converting phonetic input into the right kanji, and when an input method editor (IME) can’t keep up with new words, names, and terms, people spend time correcting conversions instead of working. Copilot Keyboard, built by the Microsoft AI team, is a free Japanese IME for Windows 11. It keeps its vocabulary current with regular dictionary updates and means people can look up a word with Copilot Search directly from the list of conversion candidates without breaking their flow. As Customer Zero, we piloted early versions with about 300 employees in Japan in 2025 and gathered high-quality feedback that helped shape the product. Copilot Keyboard launched as a public beta in October 2025. We then opened it to more employees through Microsoft Elite, our employee early-access program, and it became generally available in April 2026. The impact in Japan Better language quality, together with local adoption programs, helped drive Copilot use among our employees in Japan. Daily active use rose 67% from its earlier baseline to a peak of 93%, the highest of any market at Microsoft. By comparison, companywide daily active use was about 71% at the time. Satisfaction is rising, too. In August 2026, 87% of our employees in Japan said Copilot met or exceeded their expectations, up from about 76% in 2025. Customers noticed the difference. After the kanji name display fix and other improvements, Fujitsu, a major enterprise customer in Japan that had been piloting Copilot, saw a significant improvement in response quality. The corporation subsequently expanded its deployment companywide, growing to more than 100,000 employees. We’ve also seen fewer localization-related support tickets and escalations from customers in Japan. An internal employee Copilot survey in Japan, which drew more than 180 responses, showed that people wanted more than translation fixes. They also wanted a more culturally appropriate tone and faster access to new features in Japanese. That feedback shaped our priorities for 2026. We intend to keep listening to and acting on feedback as we move into 2027 and beyond. What’s next: Agents for localization We’re now exploring how Copilot can help improve its own localization. Ideas we’re evaluating include: Localization test agent: Compares Copilot output across languages, flags translation or functional differences, and confirms that a fix works in every affected language Issue status agent: Gives employees and customers real-time updates on the localization issues they’ve reported Localization support agent: Answers language-specific questions in the person’s own language, drawing on a library of known issues and solutions Coordination agent: Schedules multilingual review meetings, compiles the latest feedback and bug status, and suggests priorities based on impact Our experience in Japan is becoming our blueprint for other markets: Find issues early with native speakers, then scale fixes in a managed way. That approach is shaping how we handle localization and AI readiness worldwide, including in other languages with complex scripts and levels of politeness, such as Korean. Key takeaways Here are our top tips for improving the Microsoft Copilot experience for employees who work in languages other than English: Recruit native speakers to test early. An early-access group for each priority language, like our Microsoft Elite program, can catch language and cultural issues before they reach your whole workforce. Give localization one front door and clear owners. A shared path for reporting issues, joint triage, and named owners can prevent duplicate reports and stalled fixes. Make localization measurable. Track issue volume, time to resolve, how many issues you catch before release, and sentiment so you can improve in steady Plan-Do-Check-Act cycles. Test where language breaks most often. Meetings that switch languages, names with honorifics, and date and time formats are common failure points, so build them into your test plans and release reviews. Look past translation to culture and input. Check tone, etiquette, and name handling along with terminology. If your employees type Japanese on Windows 11, try Copilot Keyboard. Try it out See which languages Microsoft Copilot supports. Related links Read how we first identified Copilot localization challenges in Japan. Download Copilot Keyboard for Windows 11 from the Microsoft Store. Learn how our Microsoft Elite employees help improve our products before they ship. Explore our guide to deploying Microsoft 365 Copilot. The post Beyond translation: How we’re making Microsoft Copilot work better in Japanese appeared first on Inside Track.
Take Your Experience to the Next Level
NewDownload our mobile app for a faster and better experience.
Comments
0U
Join the discussion
Sign in to leave a comment