Cost Management Export FOCUS format Scope

[Mabdelhalim79]

In FinOps Tool Kit v0.14, We have created the cost export Scope to Subscription level but it increased the ADF cost cause number of subscriptions. now we need to go to higher scope for export and reduce the ingestion cost. this is done with a code in JASNO file in the config container. the question is how to add the Enrollment, or Account Scope to the JASON file code. can someone give an example and paste how the code will look like, because we get errors all the time

Thank you

[Roland Krummenacher (RolandKrummenacher)]

🤖 [AI] The scope value follows the Cost Management scope ID format. Examples are in Settings.json scope examples. For an EA enrollment (billing account):

"scopes": [
  { "scope": "/providers/Microsoft.Billing/billingAccounts/1234567" }
]

EA department: /providers/Microsoft.Billing/billingAccounts/1234567/departments/56789. EA enrollment account: /providers/Microsoft.Billing/billingAccounts/1234567/enrollmentAccounts/123456. For MCA, the scope is the billing profile, /providers/Microsoft.Billing/billingAccounts/{billingAccountId}/billingProfiles/{billingProfileId}, but note that Cost Management doesn't support managed exports for MCA billing accounts or billing profiles; there you create the export yourself and point it at the hub.

Three things that cause the errors people hit with EA scopes:

1. Remove the subscription entries when you add the enrollment scope. Overlapping scopes duplicate the data.
2. For managed exports, the Data Factory managed identity needs the enrollment reader role on the enrollment (department reader for departments). See Configure managed exports.
3. Keep the file valid JSON: scopes is an array of objects, no trailing comma after the last one.

If it still fails, share the exact error text from the config_ConfigureExports pipeline run (IDs redacted) and the hub version.