Copilot Studio: Fabric Data Agent connection fails silently - returns to "Not connected" without error after authentication

Question

Summary

When attempting to connect a Fabric data agent in Microsoft Copilot Studio, the authentication dialog completes successfully but the connection silently fails and returns to "Not connected" state without any error message. The user cannot browse available data agents after this failure.

Environment Details

Power Platform / Copilot Studio:

Billing model: Pay-As-You-Go (Azure subscription)

Environment region: Europe

Environment type: Production (Default) with Dataverse provisioned

User role in environment: Environment Maker + Basic User

Tenant setting: Security group assigned to "Copilot Studio authors" role (no individual Copilot Studio user licenses)

Microsoft Fabric:

Capacity: F2 in Switzerland region

Workspace: User is Admin via security group membership

Data agent: Published and functional when tested in Fabric

Underlying data source: Semantic model in same workspace

User permissions: Admin on workspace, Build permissions on semantic model

Fabric Tenant Settings (confirmed enabled):

Fabric data agent feature

Copilot and Azure OpenAI Service

Cross-geo processing for AI disabled (requirement)

XMLA endpoints for semantic models

Steps to Reproduce

User signs into Copilot Studio (https://copilotstudio.microsoft.com)

Selects the Default environment from environment picker

Creates a new agent (agent creation works successfully)

In agent editor, navigates to Agent section

Clicks "Add Agent" → Connect to External Agent --> selects "Microsoft Fabric"

Clicks "Create new connection"

Authentication dialog appears

User authenticates with their credentials (same account with workspace admin rights)

Dialog closes

Expected Result

Connection should be established successfully

User should see workspace selector with F2 workspace listed

User should be able to browse published data agents in the workspace

Data agent should be selectable and connectable to the Copilot Studio agent

Actual Result

Dialog closes without error message

UI returns to "Not connected" state

No workspace selector appears

Cannot browse data agents

No error is logged in the UI

Process can be repeated indefinitely with same silent failure

What I've Verified

Data agent is published and working in Fabric

User is member of "Copilot Studio authors" security group

User has Environment Maker role in the target environment

User is Workspace Admin in Fabric workspace (via security group)

User has Build permissions on underlying semantic model

Dataverse is provisioned in the environment

Issue persists even when using an environment in Switzerland

Both services accessed with same user account

Fabric tenant settings for Copilot/AI features are enabled

Questions

What is the correct way to diagnose silent connection failures when the UI provides no error feedback? Are there logs or connection diagnostics available?

Are there additional permissions or role requirements beyond what's documented for consuming Fabric data agents in Copilot Studio?

Additional Context

I have successfully implemented this same scenario in my own tenant with the same configuration pattern, so I know it's technically possible. I'm trying to identify what specific configuration difference in the client tenant is causing this silent failure so I can systematically address it.

---

Additional Notes

This is for a client tenant where I'm implementing the solution. I have a user inside the client tenant (not external guest account)

The same Fabric data agent works when accessed directly in Fabric

User can create and publish Copilot Studio agents without issues - only the Fabric connection fails

No error appears in browser console during the connection attempt

Any guidance on systematic troubleshooting steps or known configuration requirements that might be missing would be greatly appreciated.

Answer 1

I further tested the following:

• It is not related to User Privileges, tested now with Global Admin assigned to Security Group and manually set as Environment Maker in Power Platform Admin Center
• I also tested within my own tenant and connection works even when not being Environment Maker (only publishing the agent is not possible)

Anyone came across this issue? I currently do not know how to proceed.

Cheers

Marc

Answer 2

To diagnose silent connection failures in Microsoft Copilot Studio when connecting to a Fabric data agent, consider the following systematic troubleshooting steps:

1. Check Permissions: Ensure that the user has all necessary permissions, including any additional roles that may not be documented. Since you have confirmed the user is an Environment Maker and Workspace Admin, verify if there are any specific permissions required for the Fabric data agent that might be missing.
2. Review Tenant Settings: Double-check the Fabric tenant settings to ensure that all relevant features are enabled, particularly those related to Copilot and Azure OpenAI Service. Confirm that the settings are consistent with those in your own tenant where the connection works.
3. Inspect Logs: Although no errors appear in the UI or browser console, check if there are any logs available in the Azure portal or within the Copilot Studio that might provide insights into the connection attempts. Look for any logs related to authentication or connection failures.
4. Cross-geo Processing: Since cross-geo processing is disabled, ensure that all services involved (Copilot Studio, Fabric, and Dataverse) are in compatible regions. Sometimes, region mismatches can lead to silent failures.
5. Test with Different Accounts: If possible, test the connection with another user account that has similar permissions to see if the issue is account-specific.
6. Network and Firewall Settings: Verify that there are no network or firewall settings that might be blocking the connection between Copilot Studio and the Fabric data agent.
7. Recreate the Agent: As a last resort, try recreating the Copilot Studio agent to see if that resolves the issue. Sometimes, configuration issues can arise during the initial setup.

If the problem persists after these steps, consider reaching out to Microsoft support for further assistance, as they may have additional tools or insights into the issue.

---

References:

• Troubleshoot errors in Copilot Studio Kit
• Set up Microsoft authentication for Copilot Studio Kit testing