📌 Enhancing Arabic Language Support and Multilingual Intent Accuracy in Microsoft 365 Copilot
Hello Microsoft 365 Copilot Team, I would like to submit a formal proposal requesting an enhancement to the Arabic language experience and the multilingual intent-handling capabilities within Microsoft 365 Copilot. This proposal is based on practical observations across real usage scenarios in environments where users actively switch between Arabic and English for daily productivity tasks. 1. Background and Context Microsoft 365 Copilot has demonstrated exceptional performance in English-language workflows. However, in regions such as the Middle East—where a significant portion of users operate in bilingual environments—there remain notable gaps in language interpretation, UI localization, and multilingual intent retention. Enhancing Arabic language capabilities would meaningfully improve accessibility and align Copilot with the linguistic diversity of Microsoft’s global user base. 2. Observed Challenges in Current Behavior While Copilot excels in English, several recurring issues appear when interacting in Arabic or mixed Arabic–English contexts, including: Limited accuracy in understanding complex Arabic phrasing Reduced reliability when maintaining intent after switching languages within a single prompt Lower naturalness and structure in Arabic text generation when compared to English output Restricted availability of Arabic UI options for Copilot-specific interfaces Occasional misinterpretation of instructions containing blended terminology (Arabic user phrasing + English technical terms) These challenges collectively impact productivity and consistency for users who depend on Arabic as a primary working language. 3. Proposed Enhancements To ensure a more inclusive and reliable multilingual experience, the following improvements are recommended: 3.1 Full Arabic UI Support Across Copilot Surfaces Enable comprehensive Arabic interface options in all Copilot experiences, including Word, Excel, Outlook, Teams, and online applications. 3.2 Improved Arabic Natural Language Processing Enhance Copilot’s ability to understand and process Arabic grammar structures, context, dialectal variations, and hybrid Arabic–English prompts. 3.3 High‑Quality Arabic Text Generation Ensure outputs are clear, natural, and aligned with the stylistic expectations of native Arabic-speaking users. 3.4 Intelligent Multilingual Context Preservation Implement mechanisms that allow Copilot to maintain accurate intent when users transition between languages within the same instruction. 3.5 User‑Controlled Language Preference Settings Provide configurable options enabling users to define preferred input and output languages on a per-application or global basis. 4. Anticipated Benefits Implementing these enhancements is expected to: Improve overall accessibility for Arabic-speaking users Strengthen productivity across bilingual workflows Expand the suitability of Copilot for enterprise and governmental organizations operating in Arabic-speaking regions Increase adoption and satisfaction within a key growth market Align Copilot’s capabilities with diverse global language expectations These improvements would strongly support Microsoft’s broader mission of delivering inclusive, globally relevant AI-driven experiences. 5. Closing Statement Thank you for taking the time to review this proposal. Advancing Arabic language support and strengthening multilingual intent handling would provide significant value to a large and growing segment of Microsoft 365 users. I appreciate your continued commitment to improving the Copilot experience for users worldwide.
What's difference creating Agent from Copilot page vs from Copilot Studio -> Copilot for M365?
Hello, I am learning about Copilot and was very confused by these two different ways to do it. My understanding is both are "Declarative Agents" which lets the Microsoft 365 Copilot do the most heavy lifting. Method 1. First way is to go to Copilot page and clicking 'Create an Agent' w3 Method 2: Going to Copilot Studio -> Agents -> Copilot for Microsoft 365 -> New Agent (Couldn't find a screenshot) Q1. Anyway, first, I created an Agent using the first Method 1 above, and now I see it on the Copilot page under 'Agents' section. However, when I go to Copilot Studio -> Agents -> Copilot for Microsoft 365, I don't see that Agent there. Is this normal and intended? Q2. Is an Agent created using the Method 1 only available to people who have Copilot license? (as long as they are shared; I see options are only me, anyone in the organization, and specific users in the organization) Q3. Could you please confirm agents created using either way above are both "Declarative Agents"? Sorry for the newbie questions in advance... I took the course MS-4010 and reviewed several posts but still confusing...Incomplete ansers in code boxes
Lately, Copilot gives me more an more incomplete one line commands in code boxes. I often get an empty code box as well. When telling copilot to fix this, the next answer will contain the complete and correct commands. I would expect copilot not to make such errors. I usually tell copilot to check the ansers before presenting to me. My prompting is surely not perfect, but it seems to me that this is more a cache or buffer problem. Anyone has experienced similar issues? Is there a solution? Examples: I get blockdev --getsize64 the correct answer would be blockdev --getsize64 /dev/drbd3 copilot corrects this when I tell it to check it's output. Another example, I get: xfs_growfs /var/lib/lxc/smb/rootfs/home df -h /var/lib/lxc Correct answer would be xfs_growfs /var/lib/lxc/smb/rootfs/home df -h /var/lib/lxc/smb/rootfs/home Another one: blockdev --getsize64 /dev/dr Correct would be: blockdev --getsize64 /dev/drbd3
Allow new line on Enter / CTRL-Enter to submit instead of Enter submits
Allow ENTER to give a new line and CTRL-ENTER to submit in the Microsoft Copilot 365 desktop app in Windows/Copilot in all Microsoft Office applications. (Third time posting this as both previous attempts mysteriously vanished with no reason/explanation given. So this time it's just the TL;DR from the removed posts. If it survives, I'll add more commentary.)What’s new in Copilot Chat quality roadmap — December
We’re building Copilot Chat in the open. Every month we publish a quality roadmap that turns what we learn from customer feedback into improvements that make Copilot Chat’s responses more accurate, complete, relevant, and useful. Features shown here are available at no additional cost to users with a qualifying Microsoft 365 or Office 365 license. December Highlights: What’s New and What’s Next? 🚀 Discover What’s New: Try the latest quality features today Microsoft 365 Copilot Library: View your Copilot‑generated images and Pages in one place for easy access. Try this: After creating an image or Page, open the Library and find it. Expandable input box: Expand or collapse to write comfortably without scrolling; view everything at once. Try this: Expand the input box before typing a long, detailed prompt. Temporary chat mode: Ask sensitive questions without saving to memory. Try this: In the upper-right corner, select the drop-down arrow next “Start new chat” icon” and switch to temporary chat and ask, “Give me best practices for this sensitive scenario?” 🚧 What’s Next: Explore upcoming quality features in development Search chats from main navigation: Find past conversations quickly from the navigation pane 📌 Bookmark the monthly Copilot Chat quality roadmap and tell us what you want to see next: https://aka.ms/copilotchatroadmap
