Can we enable Copilot in Azure Devops for AI assisted user story and test case generation?
I am currently using Copilot as an enterprise user for github copilot in VSCode and want to have copilot enable in Azure Devops so that it can assist in user story and test case generation. But i am not sure if it's even possible. Please let me know how can i achieve it?
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.Clarity 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
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?
Request to increase context length
Hello, I think users would greatly appreciate the ability to include more context in prompts. In my experience, results can be dramatically improved if you can include more examples and background information directly in the prompt. While you can attach longer files, this is in my experience not nearly as effective as directly including information in the prompt, as attaching files I assume uses something like RAG to pull snippets of your context instead of the entire thing. This is especially important when including examples as in few-shot prompting. If I want to use Copilot to help me write a longer document, I want to provide multiple already completed examples of this longer document. However, with the context limit of Copilot for M365 I might not even be able to fit one example in the prompt. This is not an issue with ChatGPT which has a much longer context length (128k tokens vs. 16k characters in Copilot). If users are able to write prompts with more context I think they will see much better results and therefore see the value of Copilot for M365 in a much clearer way. Thank you for your consideration.Microsoft 365 Copilot Usage Report API General Availability
The Copilot usage report Graph API is now generally available. Like the report APIs for the other workloads, the Copilot usage API helps to understand usage of some very expensive licenses. Even better, the usage data can be combined with data from other Microsoft 365 sources to produce interesting and valuable insights. All it takes is some PowerShell to knit everything together. https://office365itpros.com/2025/10/10/copilot-usage-report-api-ga/
We need help solving a critical integration gap between Microsoft 365 Copilot and Salesforce.
The challenge: We want Copilot to access Salesforce data (including custom objects) while honoring each user’s Salesforce permissions—profiles, field‑level security, and sharing rules. Current out‑of‑box connectors don’t support this. Using an all‑access integration account is a compliance risk. Why it matters: Copilot is only valuable if answers are both accurate and secure. If a user sees data in Copilot they shouldn’t in Salesforce, that’s a governance nightmare. What we’re looking for: ✅ Support for custom objects & fields ✅ Enforcement of Salesforce profiles, FLS, and sharing ✅ Delegated user authentication (Entra ID ↔ Salesforce) ✅ Works with Microsoft 365 Copilot grounding Questions: - Has anyone implemented this successfully? - Is there a Microsoft or Salesforce roadmap for delegated auth in Copilot connectors? - Do you know a partner or expert who can build this securely? Let’s make Copilot + Salesforce both powerful and compliant.Using the Enterprise Website Microsoft 365 Copilot Connector
Microsoft 365 Copilot Search can be extended by ingesting information from external sources through a Microsoft 365 Copilot Connector. In this article, we show how to configure the Enterprise websites prebuilt connector to ingest articles from the Office365ITPros.com and Practical365.com sites, and how Copilot Search presents that information in its results and summaries. It’s quick, easy, and seamless – so really pretty good! https://office365itpros.com/2025/09/29/microsoft-365-copilot-connector/Microsoft Use of Anthropic AI Models Creates Concerns for Tenants
On September 24, Microsoft announced that Anthrophic LLMs could be used with the Copilot Researcher agent and to build agents with Copilot Studio. Although it’s great to enable choice so that customers can choose the AI model they prefer, questions about data security, lack of support for compliance solutions, and adherence to standards like the EU data boundary will concern Microsoft 365 tenants. https://office365itpros.com/2025/09/26/anthrophic-copilot/
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 that
