Microsoft Fabric: AI in Data Warehouse
Microsoft Fabric
Sep 3, 2026 7:58 PM

Microsoft Fabric: AI in Data Warehouse

by HubSite 365 about Reza Rad (RADACAD) [MVP]

Founder | CEO @ RADACAD | Coach | Power BI Consultant | Author | Speaker | Regional Director | MVP

Microsoft Fabric Data Warehouse TSQL AI functions extract, classify, summarize and translate text for Power BI insights

Key insights

  • AI Functions bring LLM-powered text tools into the warehouse so you can extract, classify, summarize, translate, fix grammar, and generate responses directly where your data lives.
  • You call these features inline from T-SQL (for example ai_extract, ai_classify, ai_analyze_sentiment, ai_summarize, ai_translate, ai_fix_grammar, ai_generate_response) or via one-line transforms in a DataFrame in data science experiences.
  • Key benefits: perform text analysis without external pipelines, reduce integration work, and run at scale with row-level isolation and high concurrency for production workloads.
  • Best practices: encapsulate prompts and logic inside a stored procedure or T-SQL function for reuse, governance, and easier auditing of AI calls.
  • Monitoring and cost control use Fabric capacity tools — the Capacity Metrics view and the AI meter show usage and help track billing for AI operations.
  • Roadmap and availability: features moved from preview to general availability, with additions like ai.embed(), wider model support, shorter default execution times, and multimodal improvements planned or rolling out.

Reza Rad (RADACAD) [MVP] published a new YouTube episode in the Fabric Insider series that spotlights built-in AI Functions in the Fabric Data Warehouse. In this conversation, he interviews Jovan Popovic from the Fabric Data Warehouse team and walks viewers through practical demos that show how natural language tasks now run directly inside T-SQL. Consequently, the episode demonstrates how developers and analysts can analyze, classify, and transform unstructured text without moving data outside the warehouse.


What the video demonstrates

The video focuses on several SQL-native AI functions, including ai_extract, ai_classify, ai_analyze_sentiment, ai_summarize, ai_translate, ai_fix_grammar, and ai_generate_response. Reza Rad walks through live demos that extract structured fields from free-text clinical notes, classify incoming text into categories, summarize long fields, and translate content across languages. Moreover, the host and guest show how these functions return JSON or scalar values that can be consumed directly inside queries and views.


In addition, the episode emphasizes operational best practices such as encapsulating prompts and AI calls inside T-SQL functions or stored procedures for reuse and governance. The demos also highlight the ability to run these calls at scale, with Microsoft’s capacity and billing controls tracking AI usage. Thus, the video paints a picture of integrated AI workflows that keep processing close to the data.


Practical implications for developers and analysts

By embedding AI into T-SQL, the Fabric approach reduces the need for separate pipelines, ad hoc notebooks, or external APIs just to analyze text. As a result, SQL developers can add sentiment analysis, classification, or summarization to existing ETL or reporting queries without introducing new infrastructure. Furthermore, the video shows that the same functions appear in other Fabric experiences, like DataFrame transforms, which supports a consistent developer experience across tools.


However, this integration also shifts some responsibilities onto SQL teams. For example, teams must decide how to structure prompts, control model selection, and monitor costs. Reza and Jovan recommend wrapping AI logic in reusable database objects to centralize governance, which helps ensure consistent behavior and makes auditing easier.


Trade-offs and challenges

Embedding AI in the warehouse offers convenience, yet it brings trade-offs that organizations must weigh carefully. On one hand, it improves latency and simplifies architecture by keeping inference next to the data. On the other hand, it can limit flexibility when teams need specialized models or bespoke preprocessing that a separate service might better support.


Also, the episode addresses operational challenges like cost, throughput, and privacy. Calling large language models at scale raises billing and concurrency considerations, and teams must balance model complexity against execution time and capacity. Moreover, sensitive data in text fields introduces governance and compliance questions that require careful prompting, access controls, and possibly data redaction before inference.


Governance, performance, and observability

Reza and his guest stress best practices that help manage these risks, such as encapsulating AI calls, versioning prompts, and restricting access through roles and stored procedures. In addition, the Fabric environment offers capacity metrics and AI meters that surface usage and help teams monitor spend and performance. Therefore, organizations can combine technical policies with monitoring to maintain control as they scale AI usage.


Performance-wise, the video shows that AI functions can operate with high concurrency while maintaining row-level content isolation, but developers should still test for latency-sensitive queries. Where response time matters, teams may prefer batch processing or cached results instead of invoking AI on every query. Consequently, a hybrid approach often balances fresh analysis with predictable performance.


Roadmap and final observations

The episode also touches on roadmap items and recent platform updates that expand model choices and add configuration options, such as embedding functions and support for newer model families. Reza highlights that Microsoft continues to evolve these capabilities, improving execution times and adding parameters that give developers finer control over behavior. As a result, the platform is moving from preview toward broader production readiness.


Overall, the YouTube discussion gives a practical view of how AI Functions change the data warehouse role in text analytics: they simplify workflows, reduce external dependencies, and bring new governance and cost considerations. In short, teams should evaluate the benefits of inline AI alongside the trade-offs in flexibility, cost, and compliance before adopting these features at scale.


Microsoft Fabric - Microsoft Fabric: AI in Data Warehouse

Keywords

AI functions Fabric Data Warehouse, Microsoft Fabric AI features, Fabric Insider Episode 18, Jovan Popovic Fabric, AI in data warehousing Fabric, Power BI Fabric AI capabilities, automated analytics Fabric Data Warehouse, Fabric data warehouse AI tools