Can my agent use flows as tools when I'm a licensed M365 Copilot user?
I tried to create an agent in Copilot Studio which drafts responses to emails I receive in Outlook. There is no "draft a reply" tool, there is only "Send a reply" or "Draft a message". I don't want an AI agent to immediately send out email replies, I want to review them first, but I also would like to review them in the context of the original message (as opposed to having a bunch of messages in the drafts folder with no visible connection to the original email I received - like the "Draft a message" tool does). So I "added a tool" (which would be a "Flow") to the agent which just does 2 HTTP calls to the outlook graph api (one creates the reply, the second adds the generated content to the body). The flow checker tells me: More Copilot Credits are needed for this flow to run. Runs from agents by M365 Copilot users and testing don't consume credits. I am a "M365 Copilot user", so I'd expect this to work, and manually testing the flow works. However, when the agent tries to run the flow, it's being blocked with the error: The environment 'Default-<...>' does not have sufficient Copilot Credits to run workflows. So, can an agent by a M365 Copilot user run flows? Alternatively: is there a way to draft email responses which in Outlook end up visually connected to the original message?
Copilot Notebook - No web search enabled
HI, It appears this just isn't a function of Notebook currently, and the only other post I see about it was from last year where someone couldn't get it to work. Does anyone know if this is a planned change to add it in the future? I'm not seeing the usefulness of Notebooks if it can only search internally. My SharePoint can do that without an extra step. If it has since been added since last seen, does anyone know where the settings are for it so I can have our admins look? Our regular Copilot Work chats do allow web searches, so it's not that.Help shape the Microsoft 365 Copilot community experience — your input matters
Do you engage with the Microsoft 365 Copilot community experience on Tech Community? Whether you’re a regular user or just drop in occasionally, we’d love your feedback. We’ve put together a short, anonymous survey (just 7 quick questions) to help us understand: Who you are and what content is most useful to you What you’d like to see more (or less) of How we can make the community more relevant to your day‑to‑day work It takes about 10 minutes, and your input will directly influence future Microsoft 365 Copilot community experience. 👉 Take the survey: https://aka.ms/m365copilotcommunitysurvey Thanks so much for helping us improve the community experience. — Mandy Product Marketing Manager, Microsoft 365 Copilot Experience
Cannot Share Fabric Data Agent
I created Fabric Data Agent. I published it to M365 Copilot. I shared it to user A, B, C. I copy the link https://m365.cloud.microsoft/chat/?titleId=T_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx&source=agentCenterDialog. I generated an QR Code using canva. User A, B, C tried to scan the QR Code using their phone, but it returned an error as seen in picture 1. However, when user A, B, C opened it via laptop browser, it was not error. how to solve this problem?
Feature Request: Add Search Functionality in Copilot Chat History
Hi everyone, I’d like to suggest a feature for Microsoft Copilot that I believe would significantly improve usability and productivity: searching within chat history. Currently, users cannot search past conversations inside Copilot. This makes it difficult to retrieve previous answers, references, or technical instructions—especially in long or complex chats. Adding a search bar or keyword filter would allow users to quickly locate relevant messages without scrolling manually. This feature would be especially helpful for developers, IT professionals, and anyone using Copilot for technical troubleshooting or documentation. It would also reduce repeated questions and improve continuity across sessions. Please consider adding this capability in future updates. If others agree, feel free to upvote or share your use cases. Thanks!
Copilot automation assumes OneDrive—hidden productivity cost in Google‑first environments
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } We’re a Google‑first organization with a limited Microsoft 365 tenant. After recent Copilot updates, automation suggestions appear everywhere and feel “easy,” but nearly all meaningful automation requires files to live in OneDrive or SharePoint. In a hybrid environment, this creates hidden costs: duplicate file management, copying between systems, increased version/corruption risk, and hours of admin work just to discover limitations mid‑workflow. Copilot looks capable, but the storage and identity prerequisites aren’t explicit up front, so users lose time and trust. Are there plans to better support hybrid scenarios (for example, Google Drive as a system of record), or to provide clearer in‑product guidance before suggesting OneDrive‑only automations?Power Apps Vibe + Copilot: Are we moving from coding to just describing apps?
With the new Power Apps Vibe experience, Copilot is making app development feel very different. What used to take hours - planning, data modeling, and UI setup - can now start with just a simple prompt. I recently tried building a non-profit management app, and Copilot generated the full structure (data, roles, UI) in minutes. From there, I refined everything using natural language. It really feels like we’re moving from building apps to describing ideas, and Copilot is doing a lot of the heavy lifting. Curious to hear your thoughts: Is this the future of app development? Or mainly a powerful prototyping tool? I shared a quick walkthrough here if you’re interested: https://medium.com/@sajeda27/power-apps-vibe-coding-build-an-app-from-an-idea-in-minutes-ea9141908346
Suggestion: Allow users to customize the UI name of MS Copilot (with “Powered by Microsoft 365”)
Background Microsoft Copilot is an extremely capable assistant, but its current visual identity is completely fixed (the name “Copilot” is always shown), even though users interact with it daily as a personal or team assistant. From a user experience perspective, this creates a small but important gap between using a tool and working with an assistant. Proposal Allow users to customize the visible name of their Copilot assistant, while maintaining a clear and consistent Microsoft branding indicator, for example: Holiday (name that the user creates for calling Microsoft Copilot 365 IA) Powered by Microsoft 365 Copilot (Text that Microsoft uses to reflect that it's already Microsoft Copilot). This proposal does not aim to change the underlying model, security, governance, or responsibility. It only affects the identity/presentation layer of the assistant. Why this matters (UX & adoption) Allowing users to name their assistant creates: Psychological ownership (“my assistant” instead of “the assistant”) Higher trust and willingness to delegate complex tasks Stronger long-term adoption and recurring usage In daily work, users naturally refer to assistants by name (“Ask Friday to review this document”), which helps integrate Copilot into real workflows instead of keeping it as an external tool. Enterprise perspective In organizational environments, a named assistant feels like part of the team rather than a generic external service. This improves internal communication, clarity, and acceptance of AI-assisted workflows. Importantly, the “Powered by Microsoft 365 Copilot” label keeps: brand visibility transparency technical and legal responsibility clearly with Microsoft This follows well-established patterns such as “Powered by Azure” or “Powered by Microsoft Security”. Strategic fit Microsoft already enables named and branded assistants through Copilot Studio. Extending this concept to the core Copilot experience feels like a natural next step with: Low technical risk (presentation-level feature) High UX impact No compromise on governance or brand integrity Closing Naming the assistant transforms the relationship from using AI to collaborating with AI. This small change could have a disproportionally positive effect on trust, adoption, and everyday productivity. Thanks for considering this feedback.
