Connecting Fabric Data Agent via Service Principal or Managed Identities

[amankaran03]

I am trying to build a webapp hosted in azure, with the Fabric Data Agent as a part of it. Locally I used interactive browser authentication to retrieve the user token, but some sources online mentioned that such connection will not work while it's on web. Are there any other way to establish a user connection to fabric data agent from my app? Can we use service principal or Managed Identities for authentication?

[amankaran03]

Hi there,

I didn’t get much of a useful response from the Community regarding the issue I was facing, but fortunately, I received an update from the Microsoft Support Team.

It turns out they had migrated their servers to a different location, and that was causing the problem. Once the migration was completed, everything started working fine again.

Thanks!

[v-prasare]

We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?
If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.
Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

Thank you for your understanding and participation.

[v-prasare]

Hi @amankaran03 ,We would like to confirm if our community members answer resolves your query or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are happy to help you.

@AmiGarala , thansk for your prompt response 

If your blocked on this i suggest you to raise a support ticket here. so, that they can assit you in addressing the issue you are facing. please follow below link on how to raise a support ticket:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are

[amankaran03]

Hi there, I didn’t get much of a useful response from the Community regarding the issue I was facing, but fortunately, I received an update from the Microsoft Support Team. It turns out they had migrated their servers to a different location, and that was causing the problem. Once the migration was completed, everything started working fine again. Thanks!

[AmiGarala]

Hi amankaran03,

Thanks for sharing the details. The error message "invalid_deployment" usually occurs when the API deployment linked to the Fabric Data Agent (AI Skill) is not found or temporarily unavailable. This can happen for a few reasons:

1. Recent Deployment Delay – If the deployment was created or updated recently, it may take a few minutes to fully provision. Try waiting 5–10 minutes and re-triggering the workflow.

2. Deployment Expiration or Removal – Check if the associated AI/ML deployment or endpoint is still active in your Fabric workspace. Sometimes, deployments get deleted or invalidated if the linked model/environment was changed.

3. Agent Configuration – Verify the Data Agent settings in Fabric (under AI Skills / Data Agent connections) to ensure the API deployment is still correctly mapped and hasn’t lost its link.

4. Region / Resource Issue – Very rarely, backend service issues in a specific region can cause this. 

Next steps to try:

• Refresh or re-deploy the Data Agent and re-associate it with the correct deployment.

• If you have multiple deployments, ensure you’re pointing to the right one.

• If nothing has changed on your side and it was working fine earlier, it might be a transient issue. In that case, raising a support ticket with Microsoft Fabric support would be the best option, especially since you’re blocked on timelines.

Hope this helps get your workflow back on track!