Changing copilot rules during python development.
Working on developing an application and copilot (personal) unexpectantly 1) says "I can't post code" 2) shifted from me pasting a code segment that was automatically converted to a compressed code block to avoid the char limit in the chat window, to pasting the text in and then refusing to send since it is outside the char limit. Any help or guidance would be greatly appreciated, i am retired and this application was to be one of my new engineering activities to keep me going. I am a hardware engineer, so AI assisted code development is new to me. thank you in advance?Copilot + SharePoint Search: How AI Changes Information Discovery
Traditional SharePoint Search has always relied on keywords, filters, and user intuition. While it often assumes users know what they’re looking for and how it’s stored. With the introduction of Microsoft Copilot, SharePoint Search is undergoing a fundamental transformation from keyword-based retrieval to AI-driven information discovery. https://dellenny.com/copilot-sharepoint-search-how-ai-changes-information-discovery/
Microsoft copilot stops while giving a response.
Why is this happening? Is there a solution for this? It just stops while giving response. And it has happened several times. And you can't even give prompt to continue from there. You should restart it. Does anyone have a solution for this? and I have restarted and reinstalled it 1000 times.
Painful behavior of "slash" ("/") in chat prompts
I know about the /commands (/reset, /help, ...) in Copilot powered applications where hitting "/" triggers auto-completion suggestions. Here we are talking about Copilot chat (Teams or Web app for instance) Each time you hit the "/" key, it pops up a menu inviting you to upload files, preventing you from going on typing until you hit the <esc> key. That's too disruptive. That would be ok if the upload menu what acting like a suggestion -- You may select with arrow keys if you wish, or just go on typing if you just need a "/" in your prompts. Please consider disabling this "feature" or I at least enhancing it so the upload menu is not modal and gets dismissed when you go on typing. Comments positive or negative are welcome, thumbs up too 😉The “Agentic” Intranet: Securing and Scaling M365 Copilot with SharePoint & Teams
Microsoft 365 Copilot has crossed an important threshold. It is no longer just a clever chat interface that summarizes documents or drafts emails. In 2025, Copilot is becoming agentic—capable of acting, orchestrating tasks, and reasoning across your organization’s knowledge landscape. And that’s exactly why many IT leaders are nervous. https://dellenny.com/the-agentic-intranet-securing-and-scaling-m365-copilot-with-sharepoint-teams/📌 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...
