Azure Files - Cost/Billing not available at individual File Share level under a Storage Account

Question

Azure Files - Cost/Billing not available at individual File Share level under a Storage Account

Rishikesh V.S 40

Hi Team,

I am working on a recommendation document for Azure File Share

and need per-file-share cost visibility for internal chargeback purposes.

Current Situation:

I have a Storage Account: testingfileshare22
Under this Storage Account, I have multiple File Shares
I am able to get Metrics, Resource details per file share individually
However, Cost/Billing is only available at the Storage Account level

Problem:

In Azure Cost Management and billing exports (FOCUS format),

the ResourceName and ResourceId only reflect the Storage Account,

not the individual File Share name.

There is no way to distinguish cost between individual file shares

within the same Storage Account.

Question:

Does Azure provide any native way to get cost/billing at the individual File Share level under Storage Account?

Sai Charan Bandi 15 Reputation points Microsoft External Staff Moderator

2026-07-01T05:12:10.19+00:00

Hello @Rishikesh V.S ,
Following up to check whether the information provided by Sina and Alex was helpful in addressing your query. If you have any additional questions, require further clarification, or need any further assistance, please do not hesitate to let us know. We will be happy to assist you further.
Sai Charan Bandi 15 Reputation points Microsoft External Staff Moderator

2026-07-02T06:22:38.3166667+00:00

Hello @Rishikesh V.S ,
Following up to check whether the information provided by Sina and Alex was helpful in addressing your query. If you have any additional questions, require further clarification, or need any further assistance, please do not hesitate to let us know. We will be happy to assist you further.
Rishikesh V.S 40 Reputation points

2026-07-02T10:20:29.86+00:00

Hello,

Yes, the information provided by Sina and Alex was helpful. The issue has been resolved now.

Thank you all for your support and assistance!

Answer accepted by question author

0 additional answers

Your answer

Sai Charan Bandi 15 Reputation points Microsoft External Staff Moderator

2026-07-01T05:12:10.19+00:00

Hello @Rishikesh V.S ,
Following up to check whether the information provided by Sina and Alex was helpful in addressing your query. If you have any additional questions, require further clarification, or need any further assistance, please do not hesitate to let us know. We will be happy to assist you further.
Sai Charan Bandi 15 Reputation points Microsoft External Staff Moderator

2026-07-02T06:22:38.3166667+00:00

Hello @Rishikesh V.S ,
Following up to check whether the information provided by Sina and Alex was helpful in addressing your query. If you have any additional questions, require further clarification, or need any further assistance, please do not hesitate to let us know. We will be happy to assist you further.
Rishikesh V.S 40 Reputation points

2026-07-02T10:20:29.86+00:00

Hello,

Yes, the information provided by Sina and Alex was helpful. The issue has been resolved now.

Thank you all for your support and assistance!

Answer 1

Hello Rishikesh V.S,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that your Azure Files - Cost/Billing not available at individual File Share level under a Storage Account.

Azure does not provide native exact Cost Management or FOCUS billing at the individual classic Azure File Share level when multiple file shares are created under the same Storage Account. For classic Azure Files, the billable resource is the Storage Account, therefore Cost Management exports, including FOCUS exports, show the Storage Account in ResourceName and ResourceId, not each individual file share. This is expected behavior and not a portal, export, or tagging issue. - https://learn.microsoft.com/en-us/azure/cost-management-billing/automate/understand-usage-details-fields, https://learn.microsoft.com/en-us/azure/cost-management-billing/dataset-schema/cost-usage-details-focus

The fix to make the chargeback boundary match the Azure billing/resource boundary is:

For classic SMB/HDD Azure Files, create one Storage Account per file share, application, department, or cost center that requires exact chargeback.
If the workload supports it, use the newer Microsoft.FileShares/fileShares top-level resource model, which creates file shares as independent Azure resources with their own provisioning, tags, and billing isolation. This option currently applies to supported NFS/SSD/provisioned v2 scenarios, not every classic SMB/HDD scenario. - https://learn.microsoft.com/en-us/azure/storage/files/create-file-share, https://learn.microsoft.com/en-us/azure/templates/microsoft.fileshares/fileshares, https://learn.microsoft.com/en-us/azure/storage/files/files-whats-new
Do not use Azure Monitor metrics as exact billing. Metrics can support estimated showback, but they are not invoice-grade Cost Management records, and per-share dimensions are not available for every Azure Files billing/model combination. - https://learn.microsoft.com/en-us/azure/storage/files/analyze-files-metrics, https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/files/storage-files-monitoring-reference.md

I hope this is helpful. Please! Do not hesitate to let me know if you have any other questions, steps or clarifications.

Please do not close the thread by upvoting and accepting the answer if any part of it is helpful.

Answer 2

Rishikesh V.S hi & thx for sharing urs issue here at Q&A portal,

Native billing is at the storage account level, not individual Azure File Share level.

So yeah, what u see in Cost Management/FOCUS is expected: ResourceId and ResourceName point to the storage account, not each file share. For chargeback, best clean design is one storage account per chargeback unit/file share owner. Then tags and Cost Management work properly.

If u must keep multiple shares in one storage account, u’ll need an internal allocation model. Use Azure Files metrics per share, like used capacity/transactions, then split the storage account cost by share usage. It won’t be perfect, but that’s the normal workaround.

I mean no native per-share billing line item today. For real chargeback, separate storage accounts are the safer model.

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

and at my blog https://ctrlaltdel.blog/