Designing AI Agent Workflows on Modern Data Platforms
Hi everyone, I have been exploring how AI agents can work with modern data engineering platforms to automate business processes. A common architecture I see is that data pipelines collect and prepare information, AI agents analyze the context and determine the next action, workflow services execute tasks through APIs or connected systems, and the results are stored for reporting or further processing. I am interested in how teams are approaching this with Microsoft Fabric. Are you using AI agents directly with Fabric workflows, or keeping the AI layer separate? What patterns work well for connecting AI agents with Lakehouse, Data Pipelines, or notebooks? How do you manage security and permissions when AI applications need access to enterprise data? Are there recommended approaches for combining Fabric workloads with external AI services? I would be interested to hear what architecture patterns others are using and what challenges you have encountered.How are AI agents changing modern data engineering workflows?
I am exploring how AI agents can assist data engineering teams in managing complex data workflows and reducing repetitive operational tasks. Some areas I am interested in: AI agents for monitoring data pipelines and detecting failures Automated data quality checks and anomaly detection Intelligent assistance for ETL/ELT workflow optimization Generating documentation for datasets and transformations Using AI with Fabric pipelines, notebooks, and data workflows With the growth of AI-powered automation, I would like to understand how data engineers are approaching these patterns in real-world environments. What approaches, architectures, or best practices are teams using to combine Microsoft Fabric capabilities with AI agents?
Azure free account - where to see 27$ spent of 200$ free credit and other questions
Hi All, sorry to disturb but I just opened a free account of 1 year 2 days ago and then I am too unexperience using Azure. I tried to install a free database but I used "Central Spain" as server and then failed. I realised it was because "Central Spain" can not be use in free trial. Then I did a new installation using "Central France" and the deploy of the new database went OK. After that I have simplely run very simple queries using the sample database, things like (I am not going to put the exact commands, but it was something like that I write): - select * from table_1 (not even any kind of join) - $myVar = 1 select coalesces($mivVar,2) as coalesce_value and I have things in the next screencapture that I do not understand and that is why I write this post to see if anyone of you could please help me to understand. Question 1: - In orange arrow (right part) it seems I have consumed 28,27$ of my free 200$ credit but If I go to the "Azure subscription 1" details, it says "your remaining $200 of free credit expires in ...".(yellow arrow at the left) I do not understand "remaining" in "your remaining $200" . Do I have 171,73$ (orange arrow) or 200$ as remaining credit? Question 2: Where can I see where I have spent the 28,27$? If you see in my subsription details on the left, it seems I have not consumed any $, so I do not kwow where those 28,27$ were employed, and I doubt that because running around 10 simple queries as the ones I explained I ran it could be that money. Question 3: In left wodn part with purple arrows it seems my subscriptons has 2 databases but if I do go recource manager window, botton right part in screenshot, I only see 1 database. How is this possible? Many thanks to all in advance and sorry for the inconveniences.Fabric GraphQL — Decimal scalar broken in variables: mutations fail for any non-integer value
Environment Microsoft Fabric — API for GraphQL Data source: SQL Database in Fabric (not Warehouse) Column definition: [Price] DECIMAL(18,4) NOT NULL GraphQL scalar in the auto-generated schema: scalar Decimal Description I'm experiencing a bug with the Decimal custom scalar when passing values through GraphQL variables. Saving non-integer decimal values (e.g. 1.42) always fails, while integer values (e.g. 1, 2) are accepted without any issue. The bug is fully reproducible on any mutation that uses a Decimal-typed variable. Could the Fabric GraphQL / DAB team confirm whether this is a known issue, and provide either a target fix version or a supported variable format that works? The SQL column: CREATE TABLE [dbo].[ItemPrice] ( [Id] BIGINT IDENTITY(1,1) NOT NULL, [PriceListItemId] BIGINT NOT NULL, [CustomerPaymentTypeId] BIGINT NOT NULL, [Price] DECIMAL(18,4) NOT NULL, ... ) The auto-generated GraphQL type and input types: input CreateItemPriceInput { PriceListItemId: Long! CustomerPaymentTypeId: Long! Price: Decimal! UserCreate: String! UserLastUpdate: String! ... } Attempt 1 — Inline literal (✅ Works) When the value is hardcoded directly in the query document, the mutation succeeds: mutation CreateItemPrice { createItemPrice( item: { Price: 1.42 CustomerPaymentTypeId: 9 PriceListItemId: 17 UserCreate: "bg" UserLastUpdate: "bg" } ) { Id PriceListItemId CustomerPaymentTypeId Price UserCreate UserLastUpdate } } Attempt 2 — Variable typed as Decimal!, passed as JSON number (❌ Fails) mutation CreateItemPrice($Price: Decimal!) { createItemPrice( item: { Price: $Price CustomerPaymentTypeId: 9 PriceListItemId: 17 UserCreate: "bg" UserLastUpdate: "bg" } ) { Id PriceListItemId CustomerPaymentTypeId Price UserCreate UserLastUpdate } } Variables (Postman): { "Price": 1.42 } Error response: {"errors": [{"message": "Decimal cannot parse the given value of type `System.Double`."}]} Attempt 3 — Variable typed as Decimal!, passed as JSON string (❌ Fails) Same mutation as Attempt 2, variables: { "Price": "1.42" } Error response: {"errors": [{"message": "Decimal cannot deserialize the given value."}]} Expected behaviour Both of the following variable formats should be accepted by the Decimal implementation, consistent with how other GraphQL servers handle custom decimal scalars: { "Price": 1.42 } { "Price": "1.42" } Thank you! UPDATE 2026-07-29: Looking to escalate the issue to Microsoft GraphQL/DAB team.
Create Sharepoint shortcut in Fabric lakehouse by code/API
I have a Microsoft Fabric connection set up with SharePoint. Manually, I can use that connection to create a shortcut in a Lakehouse for a SharePoint site. I want to perform this process via API/code. I want to be able to create a shortcut in a Lakehouse using the lakehouse_id (the ID of the Lakehouse where I want to create the shortcut), connection_id (the ID of the SharePoint connection), sharepoint_relative_path (the relative SharePoint path I want to save as a shortcut under “Files” in the Lakehouse), and shortcut_name (the name I want to give that shortcut in the Lakehouse). I've tried with: from sempy.fabric import FabricRestClient client = FabricRestClient() shortcut_name = "projects_shortcut" response = client.post( f"/v1/workspaces/{ws_id}/items/{lakehouse_id}/shortcuts", json={ "displayName": shortcut_name, "path": "Files", "target": { "type": "SharePoint", "connectionId": connecion_id, "path": sharepoint_relative_path } } ) if response.status_code not in [200, 201]: raise Exception(response.text) print("✅ Shortcut created") But I get: FabricHTTPException 403 Forbidden for url: I've tried also: from sempy.fabric import FabricRestClient client = FabricRestClient() client.get("/v1/connections") And I get the same 403 Forbidden error. Any ideas?
