Skip to content

AI and Data Agent readiness

Fabric can support AI workflows when data is discoverable, well defined, and protected. The source demo introduces Azure OpenAI, LangChain, SynapseML, machine learning examples, and Fabric Data Agent as ways to explore data through models and natural-language interactions.

flowchart TB D[Curated retail data] --> M[Lakehouse, warehouse, semantic model, or KQL database] M --> C[Business context and access controls] C --> A[Fabric Data Agent or AI workflow] A --> U[Analyst or business user] U --> F[Feedback and evaluation] F --> C

Capability map

Capability Learning purpose Production question
Azure OpenAI and LangChain Explore model calls, prompting, and text transformations. How are identities, secrets, model deployments, and content controls governed?
SynapseML Apply scalable ML and model-serving patterns to data. Which evaluation, monitoring, and lifecycle controls govern the model?
Fabric Data Agent Ask questions over approved Fabric data sources. Which data sources, instructions, users, and actions are appropriate?
Power BI Copilot experiences Support analytical exploration from governed semantic models. Are the semantic model, tenant settings, and user permissions ready?

Data Agent readiness checklist

  • Confirm the required tenant setting and current preview or feature eligibility in the official documentation.
  • Use a workspace assigned to suitable Fabric capacity and supply at least one supported, populated data source.
  • Restrict the agent's data scope to approved tables, models, or databases; do not assume a natural-language layer changes underlying permissions.
  • Create representative retail questions, expected answers, and review criteria before exposing the experience to broader users.
  • Keep sensitive data, harmful prompts, overbroad instructions, and unsupported actions out of the initial pilot.

Warning

Data Agent and connected AI features can be preview or capacity-dependent. Verify current prerequisites and limitations in Fabric Data Agent documentation before implementation.

Explore further