Encountering an issue while importing data from Azure Cost Management into a Lakehouse

Hi fkc38 ,

Thanks for sharing the details. From what you’ve described, it looks like the failure happens specifically during ingestion into the Fabric Lakehouse table. The error message:
Azure Usage details_WriteToDataDestination ... Error code: 999999
suggests the problem occurs at the write-to-destination stage rather than during data retrieval. A few things to try include re-authenticating the data source by refreshing the Azure Cost Management connection in your Dataflow settings, as expired tokens or permissions can cause failures. You might also test smaller data loads by reducing the “Number of Months” parameter or narrowing the scope; if these succeed, the issue could be related to payload size limits during Lakehouse ingestion.

Other helpful steps are creating a new Lakehouse or writing to a Warehouse to see if the issue is tied to your current schema or partitions, validating the API externally via Power BI Desktop or Postman, and checking that your Lakehouse is within capacity and quota limits. If the table schema was manually modified, try restoring or recreating the destination table. If none of these resolve the problem, submitting a Microsoft support ticket with the Request ID or Tracking ID from the failed refresh is recommended, as the generic error code may reflect recent backend changes in the service.