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.
GraphQL update... mutation for Fabric SQL DB failing
Hi everybody, I want to update items in a Fabric SQL DB via GraphQL mutation query. But that fails with "InternalServerError" (and nothing else). What I tried: ❌ mutation update.... ✅ mutation create... ✅ mutation delete... ✅ (directly in the SQL DB): UPDATE dbo.product SET product_name = 'CHANGED' WHERE ROWID = '<UUID>' Did someone else here experience something similar? Is this a defect 🐞 in the GraphQL API / Fabric SQL DB / their combination? What was your solution? (And what was the issue exactly?) A workaround might be to create a stored proc and let that do the update. I'd prefer to be able to use a working update mutation though. So Any help highly appreciated! <3 --> Snippets below Best Martin (Snippets stripped down for readability) The failing mutation: mutation { updateproduct ( ROWID: "<UUID>", item: { product_name: "CHANGED" }) { ROWID product_name } } //// Definitions from the GraphQL schema: """Updates a product""" updateproduct ( """The ID of the item being updated.""" ROWID: UUID! """Input representing all the fields for updating product""" item: UpdateproductInput! ): product """Input type for updating product_mapping""" input UpdateproductInput { """Input for field ROWID on type UpdateproductInput""" ROWID: UUID """Input for field product_name on type UpdateproductInput""" product_name: String } The table in Fabric SQL DB (as by "Script as create") CREATE TABLE [dbo].[product]( [ROWID] [uniqueidentifier] NOT NULL, [product_name] [nvarchar](255) NOT NULL, ) ON [PRIMARY] ALTER TABLE [dbo].[product_mapping] ADD PRIMARY KEY CLUSTERED ( [ROWID] ASC ) WITH ( STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF) ON [PRIMARY] ALTER TABLE [dbo].[product_mapping] ADD DEFAULT (newsequentialid()) FOR [ROWID]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?Fabric Copy Activity Upsert Needs Native Audit Columns
𝗠𝗶𝗰𝗿𝗼𝘀𝗼𝗳𝘁 𝗙𝗮𝗯𝗿𝗶𝗰 𝗖𝗼𝗽𝘆 𝗔𝗰𝘁𝗶𝘃𝗶𝘁𝘆 + 𝗗𝗲𝗹𝘁𝗮 𝗨𝗽𝘀𝗲𝗿𝘁 is honestly one of the most underrated features in Fabric for high-performance operational data loading. We can now: • Read directly from sources such as SQL Server / SQL DB • Write directly into Lakehouse Delta Tables • Use native Upsert mode • Avoid Spark notebooks completely • Avoid Parquet staging/intermediate layers • Achieve very fast sync performance with only ONE Copy Activity I’m currently using this approach to dynamically load and merge data from multiple SQL Server store databases into consolidated Delta tables in Microsoft Fabric Lakehouse. However, there is one very important feature still missing from Copy Activity Upsert. 𝗜 𝘄𝗼𝘂𝗹𝗱 𝗹𝗼𝘃𝗲 𝘁𝗼 𝘀𝗲𝗲 𝗻𝗮𝘁𝗶𝘃𝗲 𝘀𝘂𝗽𝗽𝗼𝗿𝘁 𝗳𝗼𝗿 𝗮𝘂𝘁𝗼-𝗺𝗮𝗻𝗮𝗴𝗲𝗱 𝗮𝘂𝗱𝗶𝘁 / 𝗗𝗪 𝗰𝗼𝗹𝘂𝗺𝗻𝘀 during Upsert operations. My requirement is: In the destination Delta table, I need these columns: • DW_DATE_INSERT → Datetime when a NEW record is inserted through Upsert • DW_DATE_UPDATE → Datetime when an EXISTING record is updated through Upsert • DW_LOAD_DATE → Maximum of DW_DATE_INSERT and DW_DATE_UPDATE (meaning the latest insert/update datetime) Expected behavior: • If INSERT occurs: DW_DATE_INSERT should be populated DW_DATE_UPDATE should remain NULL • If UPDATE occurs: DW_DATE_UPDATE should be updated DW_DATE_INSERT should remain unchanged with its original value Currently, adding these columns dynamically in the Source → Additional Columns section is NOT a solution. Why? Because these datetime values change every execution, the Upsert process detects every row as changed and re-updates all records again and again, even when business data has not changed. Of course, I know this can be handled using Spark / Notebook MERGE logic. But the whole beauty of this approach is: 𝗡𝗼 𝗻𝗼𝘁𝗲𝗯𝗼𝗼𝗸𝘀. 𝗡𝗼 𝗦𝗽𝗮𝗿𝗸 𝘀𝘁𝗮𝗿𝘁𝘂𝗽 𝗹𝗮𝘁𝗲𝗻𝗰𝘆. 𝗡𝗼 𝗲𝘅𝘁𝗿𝗮 𝗺𝗲𝗿𝗴𝗲 𝗹𝗮𝘆𝗲𝗿. 𝗝𝘂𝘀𝘁 𝗼𝗻𝗲 𝗳𝗮𝘀𝘁 𝗖𝗼𝗽𝘆 𝗔𝗰𝘁𝗶𝘃𝗶𝘁𝘆. It would be amazing if Microsoft could add native insert/update audit column handling directly inside Copy Activity Upsert for Delta Lakehouse tables. This would make Copy Activity even more powerful for very fast enterprise operational sync workloads. If you think this feature would be useful, please vote/support this idea so we can hopefully get it added to Fabric 🙌 #MicrosoftFabric #DataEngineering #DeltaLake #Lakehouse #ETL #ELT #OneLake #SQLServer #Fabric #Microsoft #AnalyticsEngineeringData connection rules combined with block public acces
Hi all, I am trying to set up a secure fabric environment with outbound and inbound rules. Combined with block public internet access, so people within the company can only go to Fabric via a dedicated VM. As you can see in the picture i created 3 Managed Private Endpoints for the data extraction, this works fine with notebooks. I also have 2 connections that needs pipelines for the extraction, so that is why I have configured a VnetGateway. Because I block outbound Public access, it is a good way out to use the connection rules to allow the VnetGateway. It worked a few days ago. It looks like that since I Block Public Internet Access this feature wont work anymore. Is this a bug, or is this just not working because of another reason?
