Agent not visible in M365 Copilot
I created an agent in M365, including its name, description, instructions, and required actions. The agent is properly tested in Copilot Studio and published, but it is not visible in the M365 Copilot agent list. Interestingly, one agent is visible while the other is not, and I am unable to determine the issue.
Copilot Agent Cannot Create a Word Document
I have created an agent to help users create their own SOPs. I would like for the final document provided to the user to be a word document, not simply the text response the agent provides in the chat window. Example of what the agent's final output is below. You will notice at the very bottom, the agent states it will create a word file with the SOP for the user. This is based on the instructions I configured for the agent. Despite saying that it will create the word document, the agent does not actually do that. If prompted again to provide a word document, the same thing happens again. This is strange given that when I use regular copilot, I can ask it to turn almost any response it gives me into a word document. So what am I missing?
Use Copilot with Microsoft ToDo
It would be great if I could have Microsoft Copilot Pro talk to and be able to query these few responses. 1. What are my important task that I am missing? 2. What task do I need to focus on in the next few days? 3. Look at this project/doc/sharepoint file and add additional task to my ToDo that isn't currently on my list.
Web content plug-in management in M365 Copilot
Hi, Referring to this announcement MC882258 in message center, MS informed that web content plug-in management will be removed from M365 admin center, rather it will be managed as part of Optional Connected Experience for M365. We have currently disabled this web content plug-in in our environment but allowed Optional Connected Exp for the users. After this announced change, how web content plug-in will behave? Will it enabled because we have Optional connected exp. enabled? Secondly, what is the reason behind this change? Why MS has taken individual control setting away and mixed it with so many optional connected exp. where we do not have an option to choose which optional connected exp. we want to enable/disable. Its like all or nothing.How to build custom Copilot agents grounding SharePoint lists
Imagine the scenario where the user can ask to a Copilot Agent to create a list item, update a single column, delete or extract data filtering by columns. In this video we'll see how to build a custom agent which is able to perform CRUD operations in a SharePoint list. #Copilot #Agents #Microsoft365 #MPVbuzz #AI #CopilotStudio
Copilot Agent with Salesforce
I am currently developing a custom agent in Microsoft Copilot Studio to streamline access to key information from our Salesforce sandbox, including Leads, Opportunities, I have successfully integrated Salesforce as a knowledge source using the Salesforce connector, authenticated via a service account with admin privileges in Salesforce. The integration is technically working as expected. However, I’ve encountered a security concern: At present, any user interacting with the Copilot agent can retrieve all data from Salesforce, regardless of their individual permissions in Salesforce. This appears to be due to the elevated privileges of the service account used for the connector. I would like assistance with configuring user-level access control within this integration. Specifically, I want to ensure that: Only authorized users can access specific Salesforce data through the Copilot agent. Users can only perform actions or retrieve records that their Salesforce permissions allow. Could you please guide me on how to properly implement permission scoping or data access control within Copilot Studio when using a high-privilege service account in the Salesforce connector?
What the hack is a "Microsoft 365 Copilot Bizchat"?
I am taking a training course on learn.microsoft and this word "Microsoft 365 Copilot Bizchat" just came out of nowhere... I went few slides/pages of the training course and even googled it but there is no definition or clarification of it either sigh... What is thatClarity around the different types of connectors available for Microsoft 365 Copilot
Working with some of the largest and most technical of Microsoft's partners in the Global System Integrators (GSI) team, we are still often met with confusion around the different types of connectors available in M365 Copilot. While agent extensibility could easily be a full week or more of discussion topics and sessions, I wanted to spend a moment to focus specifically on some of the various types of connectors available to agent makers working with M365 Copilot. GRAPH CONNECTORS Graph Connectors play a crucial role in enhancing the knowledge scope of Microsoft 365 Copilot, by enabling the integration of external data sources into the Microsoft Graph. This integration allows Copilot to reason over a broader range of enterprise content, thereby improving the relevance and accuracy of responses to user queries. By ingesting unstructured business data through Graph Connectors, organizations can ensure that their critical content is indexed and accessible within Microsoft 365 Copilot. This process involves semantic indexing, which optimizes data retrieval and enhances the matching of search queries to content, providing more relevant results than simple keyword matches. The relevance of Graph Connectors to Microsoft 365 Copilot is particularly significant in the context of enterprise search and data utilization. Copilot leverages these connectors to access and summarize information from various external sources, such as third-party applications, databases, and cloud services. This capability allows users to find, summarize, and learn from their business data through natural language prompts in Copilot. For example, when a user asks Copilot to summarize recent communications or project updates, Graph Connectors enable Copilot to utilize relevant data from integrated sources, ensuring comprehensive and accurate responses. As an agent maker using M365 Copilot, one important consideration of Graph Connectors is that they offer high-performance operations, due to direct access to information via the Large Language Model (LLM). However, keep in mind that data accessed is not pulled from the external data sources in real-time, as the Graph Connectors sync this business data on a set schedule. Additionally, your operations will be limited to retrieval-based ("read only") tasks when interacting with externally-synchronized Graph data. It should also be noted that these types of connectors will work best for working with unstructured data. Moreover, Graph Connectors are not limited to Microsoft 365 Copilot; they also power other intelligent experiences within the Microsoft ecosystem, such as Microsoft Search and Context IQ. This extensibility allows users to hover over in-text citations to preview external items referenced in responses and dive deeper into the referenced content by selecting links at the bottom of Copilot responses. The ability to configure custom connectors and utilize pre-built ones further enhances the flexibility and utility of Graph Connectors, making them a valuable tool for organizations looking to leverage their external data within Microsoft 365. By integrating these connectors, organizations can ensure that their data is not only accessible but also actionable, driving better decision-making and productivity. POWER PLATFORM (FLOW) CONNECTORS Power Platform Connectors are integral to extending the capabilities of Microsoft 365 Copilot by enabling seamless integration with various external applications and services. These connectors act as proxies or "wrappers" around APIs, allowing Copilot to interact with other apps and services within the Microsoft ecosystem and beyond. By leveraging Power Platform connectors, users can connect their accounts and utilize prebuilt actions and triggers to build sophisticated workflows and applications. This integration enhances Copilot's ability to retrieve and process data from diverse sources, thereby providing more comprehensive and actionable insights to users. In the context of Microsoft 365 Copilot, Power Platform connectors enable the creation of custom agents that can perform specific actions based on enterprise data. For instance, connectors can be used to retrieve sales opportunities, manage orders, or even check the weather at a customer's location for site visits. This functionality is particularly valuable for businesses looking to automate routine tasks and streamline operations. By integrating these connectors, Copilot can ground its responses in real-time data from various enterprise systems, ensuring that users receive accurate and relevant information. While the performance of a Power Platform Connector will inherently not be as speedy as data retrieval via Graph Connectors, agent makers should consider advantages to using Power Platform Connectors in the right scenarios. The API wrapper can perform real-time operations with the external business data, not requiring data synchronization to the Graph to access. Additionally, these types of connectors offer the ability to add and update records, in addition to retrieval. I have also seen use cases where Power Platform Connectors are preferred when dealing with structured data, even in retrieval-only agents and tasks. Beyond that, Power Platform Connectors are essential for extending Copilot's capabilities through Copilot Studio. This platform allows makers to add custom knowledge and skills to agents using connectors, thereby expanding the range of actions that Copilot can perform. For example, connectors can bring in data from Microsoft Graph, Dynamics 365, and other non-Microsoft enterprise sources, enabling Copilot to provide more nuanced and detailed responses. The ability to use these connectors in a no-code environment makes it accessible for users with varying technical expertise, empowering them to create intelligent, automated experiences that address unique business challenges. CONCLUSION By understanding the different types of connectors, the advantages and disadvantages of each, and the scenarios where each work best, agent makers can use one of the most powerful tools for working with external business data. For additional technical detail, please see the links below: Copilot connectors and actions overview (preview) - Microsoft Copilot Studio | Microsoft Learn Use Power Platform connectors (preview) - Microsoft Copilot Studio | Microsoft Learn Extend Copilot for Microsoft 365 with connectors | Microsoft Learn Build Microsoft Graph Connectors for Microsoft 365 Copilot | Microsoft Learn
Schedule a meeting using copilot in outlook
We need to explore how to build a Copilot for scheduling meetings. This Copilot should automatically suggest meeting times, check availability across company calendars, and manage invites. Our users already have Copilot licenses. Since we’re not experts in Copilot, we need to clarify if this functionality is available in Copilot for Outlook in the US. If it is, how can we use and customize these features? If not, what would be the approach to build something similar using the Copilot interface in Outlook?"Copilot in Edge at work" isn't available
For the past few days, 'Copilot in Edge at work' has not been available. The user is assigned an M365 E5 license and is signed into Microsoft Edge with their company account. The Copilot button is present but points to the Copilot for personal use. When using it, the message 'Unfortunately, you have reached the limit for messages you can send to Bing within 24 hours. Please check back soon!' appears directly. Access via m365.cloud.microsoft/chat works perfectly. However, it would be great if access was also possible in Edge in the secure corporate environment.
