This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
We’re introducing billing reporting updates that make it easier to track AI-related usage in Microsoft Fabric.
To provide more transparency, Fabric AI functions will have a dedicated operation called AI Functions, which will enable you to see their consumption clearly, whether you call them from a Notebook or other Fabric items, such as Dataflows Gen2.
This operation will also include Azure OpenAI Service calls with REST API, Python SDK, and Synapse ML.
The following table outlines how the new operations map to Fabric items and Azure billing meter:
| Operation | Description | Item | Azure billing meter |
| AI Functions | Compute cost associated with using Fabric AI functions and Azure OpenAI Service | Notebook | Copilot and AI Capacity Usage CU |
| AI Functions | Compute cost associated with using Fabric AI functions | Dataflow Gen2 | Copilot and AI Capacity Usage CU |
| AI Services | Compute cost associated with using Azure AI Services in Fabric (Text Analytics and Azure AI Translator) | Notebook | Copilot and AI Capacity Usage CU |
These are reporting changes only; the underlying consumption rates are unchanged.
To learn more about AI functions, visit the AI functions documentation.
Based on your feedback, these updates are designed to make AI Functions consumption clearer and easier to understand. If you have any additional feedback, please feel free to post on Fabric ideas.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.