NEW Copilot Customer Adoption | Train the Trainer Digital Series
Join us for a monthly Train the trainer session on how to use the Partner-led Copilot Immersion Experience, providing partners the ability to demo unique scenarios and help customers (including spaces); make clear what you’re promoting and why it matters with hands-on experiences with Copilot for Microsoft 365. In this session, we will walk you through role/persona scenarios showcasing how Copilot can help businesses solve common problems and streamline business processes, automate repetitive tasks, and unlock productivity. Train the Trainer | Copilot Customer Adoption Schedule Americas/EMEA: September 18 | 8:00 AM – 9:00 AM, Pacific Time APAC: September 18 | 5:00 PM – 6:00 PM, Pacific Time Register Today! or invite your resellers with the attached invite.
Issues while trying to build a graph connector to Azure SQL in M365 copilot
Dear All, I tried to create a Graph Connector to Azure SQL. I wanted to ingest data from Azure SQL and ask questions about it within Copilot for Microsoft 365. The graph connector was created in this Microsoft 365 Admin Centre within the 'Data sources' section in 'Search and Intelligence' menu: https://admin.microsoft.com/#/homepage The Microsoft documentation (https://learn.microsoft.com/en-us/graph/connecting-external-content-experiences#copilot-for-microsoft-365) screenshot below states that in order for the information to surface in Copilot for Microsoft 365, the fields "title," "url," and "iconUrl" need to be filled out during the configuration process. However, during the configuration process, I noticed that the 'iconUrl' field is greyed out. Hence, I am not able surface data from Azure SQL in Copilot for Microsoft 365. On the other hand, Microsoft Search and Sharepoint both displayed the Azure SQL data as I proceeded to configure the connector anyway. Is there any workaround for this? Are there any alternative approaches that I can take to surface the data in Copilot chat? Would appreciate any help regarding the same.
Copilot sidebar in Edge "unable to connect to the service"
Hello Everyone, We are having intermittent issues with the Copilot sidebar in Edge. It works sometimes, and other times we get an error that says "We're sorry but we're unable to connect to the service at this time." It has a refresh button which doesn't help. What's weird, is that we have Copilot licenses enabled for our users and going to https://bing.com/chat works fine in all cases (and shows the user signed in and "protected" as expected). Anyone else have this issue? Any suggestions to fix this issue? Brian
Copilot Chat in Office Tools
Hit of the press! Copilot Chat will start to be published in the Office Apps. Copilot Chat will still have no access to Graph. admins can pin it for all users to have a nice experience. have a look on my announcement https://www.linkedin.com/posts/andre-thiemann-bb888646_microsoft365copilot-copilotchat-microsoft365-activity-7341100014070378498-xhxE?utm_source=share&utm_medium=member_ios&rcm=ACoAAAm9dzwB9gBW8cfBuj0IBk3MpR03ArNpnaY
The Copilot in Edge sidebar refreshed during generating answers
Since there's no history available in the Enterprise version, I've experienced the issue of losing my entire prompt, and it's been a problem since day one. Never encountered this issue in any other LLM products (ChatGPT, Gemini, Perplexity, Poe...). Just curious if this is "by design" or a known bug.Copilot for Teams Phone
In the current documentation on Copilot for Microsoft 365 requirements (Microsoft Copilot for Microsoft 365 requirements | Microsoft Learn) it is stated that Copilot for Teams Phone requires a calling plan license. Does this mean that Copilot for Microsoft 365 will not be able to assist with PSTN calls when you have a Direct Routing or Operator Connect setup??
Copilot CORS errors
We are getting CORS errors when using https://copilot.microsoft.com to create images (screenshot attached). First started yesterday I think and happening in both Chrome and Edge browsers. This does not occur when using the https://bing.com/chat site. I can't tell if the issue is on the Microsoft server side or with us - I've asked our security team to investigate as well. Anyone else experiencing this?
