GraphConnectors capability not working

[arunpandi1]

Describe the Bug
We recently created a declarative agent using the Copilot Studio toolkit and configured Graph Connectors to enable integration with external data sources. However, after successfully provisioning the agent, it is not functioning as expected, and Graph Connectors fail to return any data. The deployed microsoft graph connectors working properly with sharepoint search.

To Reproduce
Steps to reproduce the behavior:

1. Open VS Code and create a declarative agent using the Teams Toolkit.
2. Select "Declarative Agent" and choose "No Action" as the setup option.
3. Choose a folder path for scaffolding the project.
4. Add the following JSON snippet to the connections section in the declarativeAgent.json file:

{ "name": "GraphConnectors", "connections": [ { "connection_id": "graph_id" } ] }
5. Provision the agent and attempt to query data using Graph Connectors.
6. Observe that no response or an error is returned.

Expected Behavior

Graph Connectors should function correctly, allowing Copilot to access and return data from external sources.

Screenshots

Teams Toolkit & Environment Details (please complete the following information):

• OS: Windows
• Version 5.14.0

Additional Context

Please provide any relevant logs or error messages to help troubleshoot the issue.

[m365-agent-toolkit-assistant]

👋 Hi @arunpandi1,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 2 business days

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

To troubleshoot your issue with the Graph Connectors functionality not working as expected in your declarative agent, please follow these steps:

1. Verify Graph Connector Configuration: Ensure that the configuration in the declarativeAgent.json file is correct. Double-check the connection_id for any typos or issues.

2. Check Permissions and Authentication: Ensure that the appropriate permissions are granted and the authentication method configured properly for accessing the Graph Connectors.

3. Enable Logging: Enhance the logging to capture detailed information about the Graph Connectors' responses and possible errors.

4. Microsoft Graph Connector Deployment Logs: Review the deployment logs for the Graph Connector for any issues or errors during provisioning.

5. Integration Testing: Isolate and test the Graph Connector outside the agent to ensure it returns expected data when queried directly.

6. Debugging with Teams Toolkit: Use the debugging tools available in the Teams Toolkit to step through the agent execution and identify where things might be going wrong.

Refer to the following typical setup for a Graph Connector in a declarative agent:

{
  "name": "GraphConnectors",
  "connections": [
    {
      "connection_id": "graph_id",
      "resource": "CONNECTOR_RESOURCE"  // Adjust this resource parameter according to the specific Graph Connector being configured
    }
  ]
}

Sample Configuration

Make sure your configuration is similar to a working Graph Connector sample:

{
   "name": "GraphConnectors",
   "connections": [
     {
       "connection_id": "sample_graph_connector_id",
       "resource": "https://graph.microsoft.com/v1.0/externalConnections/sampleConnectionId"
     }
   ]
}

Additional Tips:

1. Microsoft Graph API: Ensure that your settings comply with Microsoft Graph API access conventions.
2. Documentation Review: Review the official documentation on configuring Graph Connectors and integrating them with Teams apps.

If the problem persists and you cannot find a resolution within the standard configurations and troubleshooting steps provided, sharing detailed logs and error messages can help provide more precise recommendations.

To gain more understanding, refer to the existing issues and discussions shared previously related to Graph Connectors and declarative agents to identify similar problems and potential solutions.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

[Nivedipa-MSFT]

Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[xzf0587]

@arunpandi1.
Thanks for reaching out. Can you paste the content of declarativeAgent.json ?
Since the Graph Connector works properly with sharepoint search, you can confirm the connection id referring to https://learn.microsoft.com/en-us/microsoft-365-copilot/extensibility/declarative-agent-capabilities-ids?tabs=explorer#microsoft-graph-connectors.

By the way, new version of TTK provides the Add capability to add graph connector. You can upgrade the TTK to the newest version and try it. Thanks.

[Nivedipa-MSFT]

@arunpandi1 - Could you share the content of declarativeAgent.json as requested by @xzf0587?

[arunpandi1]

@Nivedipa-MSFT Sure! Here is the content of declarativeAgent.json as requested by @xzf0587 :

{ "name": "GraphConnectors", "connections": [ { "connection_id": "graph_id" } ] }

Please let me know if you need any modifications or additional details.

[xzf0587]

@arunpandi1 It seems that the schema is right.
Do you try to click F12 to launch the debug mode? what is the response of the network request?
And do you try the search in Copilot not Copilot Agent? It should work and get result in Copilot if the Graph connector is setup correctly.

[priyanshu-28]

@xzf0587, @Nivedipa-MSFT Even I'm facing this issue. Please tell the exact information you require to debug this issue. I'm attaching network response of client, console logs, and declarativeAgent.json content below:

{ "sigsStatus": 0, "sigsErrorResponse": null, "cosmosStatus": 0, "cosmosErrorResponse": null, "cosmosEventResponses": [ { "eventName": "CopilotResultsRendered", "status": 0 }, { "eventName": "CopilotResultsRendered", "status": 0 }, { "eventName": "CopilotResultsRendered", "status": 0 }, { "eventName": "CopilotResultsRendered", "status": 0 }, { "eventName": "CopilotResultsRendered", "status": 0 }, { "eventName": "CopilotActions", "status": 0 } ] }

DeclarativeAgent.json:

{ "$schema": "https://developer.microsoft.com/json-schemas/copilot/declarative-agent/v1.2/schema.json", "version": "v1.2", "name": "ConfluenceJiraAgent", "description": "Declarative agent created with Teams Toolkit", "instructions": "$[file('instruction.txt')]", "capabilities": [ { "name": "GraphConnectors", "connections": [ { "connection_id": "ConfluenceCloud1" }, { "connection_id": "Jira3" } ] } ] }

[xzf0587]

@priyanshu-28
Thanks for reaching out. It seems the response is OK.
Please input -developer on in your DA to open the debug mode and try it again. You can find some debug information as following shows.
Or if you remove the Graph Connector capability and try it to make sure whether it is an error triggered by Graph Connector.

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

[microsoft-github-policy-service]

Due to lack of details for further investigation, we will archive the issue for now. In case you still have following-up questions on this issue, please always feel free to reopen the issue by clicking ‘reopen issue’ button below the comment box. We will get back to you as soon as possible.