MS Fabric Showing as Unallocated in Azure Reports Prior to May 2025

Products

• CloudHealth

Issue/Introduction

Customers may notice that MS Fabric usage appears as Unallocated in CloudHealth reports for billing periods prior to May 2025. This can cause confusion when reviewing historical Azure cost allocation data or comparing service-level spend across time.

Resolution

This behavior is expected and results from a limitation in Microsoft’s historical billing data. For Azure billing months prior to May 2025, Microsoft did not include resource IDs for the MS Fabric service in the billing files. Without a resource ID, CloudHealth cannot associate MS Fabric usage with a specific resource or service, which leads to it being categorized as Unallocated.

CloudHealth engineering has verified this by manually recollecting historical Azure billing data to check whether Microsoft retroactively added resource IDs. Microsoft has confirmed that resource IDs remain unavailable before May 2025, and this is expected behavior on Azure’s side.

As a result, CloudHealth is functioning as designed. MS Fabric cost data will only appear accurately allocated starting with the May 2025 billing period, when Microsoft began including the necessary resource IDs in their billing export.