Skip to content

Conversation

@AhmadAbdullah91
Copy link
Contributor

Added details about the integration of Azure AI Foundry Agent with Microsoft Fabric data agent, including usage support and authorization notes.

Added details about the integration of Azure AI Foundry Agent with Microsoft Fabric data agent, including usage support and authorization notes.
@prmerger-automator
Copy link
Contributor

@AhmadAbdullah91 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 39cf7b4:

✅ Validation status: passed

File Status Preview URL Details
articles/ai-foundry/agents/how-to/tools/fabric.md ✅Succeeded

For more details, please refer to the build report.

@ktoliver ktoliver requested a review from Copilot October 30, 2025 15:38
@ktoliver
Copy link
Contributor

@aahill

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged C+L Pull Request Review Team label label Oct 30, 2025
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds an important technical limitation note to the Fabric data agent documentation, clarifying that service principal names (SPNs) are not supported for authentication.

Key Changes

  • Added a NOTE block explaining that Fabric Data Agent only supports user identity authentication, not service principal names (SPNs)

You need to first build and publish a Fabric data agent and then connect your Fabric data agent with the published endpoint. When a user sends a query, the will first determine if the Fabric data agent should be leveraged or not. If so, it will use the end user’s identity to generate queries over data they have access to. Lastly, the agent will generate responses based on queries returned from Fabric data agents. With Identity Passthrough (On-Behalf-Of) authorization, this integration simplifies access to enterprise data in Fabric while maintaining robust security, ensuring proper access control and enterprise-grade protection.

> [!NOTE]
> Fabric Data Agent can't use any SPN (service principal name), only user identity is supported.
Copy link

Copilot AI Oct 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The NOTE could be clearer and more precise. Consider rephrasing to: 'Fabric Data Agent supports only user identity authentication. Service principal name (SPN) authentication is not supported.' This follows the active voice and clarity guidelines from the Microsoft Writing Style Guide.

Suggested change
> Fabric Data Agent can't use any SPN (service principal name), only user identity is supported.
> Fabric Data Agent supports only user identity authentication. Service principal name (SPN) authentication is not supported.

Copilot uses AI. Check for mistakes.

Integrate your Azure AI Foundry Agent with the [**Microsoft Fabric data agent**](https://go.microsoft.com/fwlink/?linkid=2312815) to unlock powerful data analysis capabilities. The Fabric data agent transforms enterprise data into conversational Q&A systems, allowing users to interact with the data through chat and uncover data-driven and actionable insights.

You need to first build and publish a Fabric data agent and then connect your Fabric data agent with the published endpoint. When a user sends a query, the will first determine if the Fabric data agent should be leveraged or not. If so, it will use the end user’s identity to generate queries over data they have access to. Lastly, the agent will generate responses based on queries returned from Fabric data agents. With Identity Passthrough (On-Behalf-Of) authorization, this integration simplifies access to enterprise data in Fabric while maintaining robust security, ensuring proper access control and enterprise-grade protection.
Copy link

Copilot AI Oct 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grammar error: 'the will first determine' is missing a subject. This should be 'the agent will first determine' or 'the system will first determine'.

Suggested change
You need to first build and publish a Fabric data agent and then connect your Fabric data agent with the published endpoint. When a user sends a query, the will first determine if the Fabric data agent should be leveraged or not. If so, it will use the end user’s identity to generate queries over data they have access to. Lastly, the agent will generate responses based on queries returned from Fabric data agents. With Identity Passthrough (On-Behalf-Of) authorization, this integration simplifies access to enterprise data in Fabric while maintaining robust security, ensuring proper access control and enterprise-grade protection.
You need to first build and publish a Fabric data agent and then connect your Fabric data agent with the published endpoint. When a user sends a query, the agent will first determine if the Fabric data agent should be leveraged or not. If so, it will use the end user’s identity to generate queries over data they have access to. Lastly, the agent will generate responses based on queries returned from Fabric data agents. With Identity Passthrough (On-Behalf-Of) authorization, this integration simplifies access to enterprise data in Fabric while maintaining robust security, ensuring proper access control and enterprise-grade protection.

Copilot uses AI. Check for mistakes.
@aahill
Copy link
Contributor

aahill commented Nov 4, 2025

Merged in #8133 internally

#please-close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants