⚠️ Problem
In https://learn.microsoft.com/en-us/cloud-computing/finops/focus/convert#how-to-convert-cost-management-data-to-focus, the FOCUS column SubAccountId is documented to require no transformation from Cost Management SubscriptionId column.
|
| SubAccountId | SubscriptionId | None | |
In reality, FOCUS column SubAccountId from real observed data has a prefix /subscriptions/ attached before SubscriptionId. The difference looks more like this example:
SubscriptionId = abcdef-12345-ghijk
SubAccountId = /subscriptions/abcdef-12345-ghijk
🛠️ Solution
I would appreciate some clarification to describe that SubAccountId structure will not be the exact same as SubscriptionId to prevent issues in querying FOCUS data, so end users can know whether to query using either of these filter clauses:
WHERE SubAccountId = 'abcdef-12345-ghijk', or
WHERE SubAccountId LIKE '%abcdef-12345-ghijk'
Perhaps the Transform column in the table should be reworked to say something like "add the prefix /subscriptions/ to SubAccountId"
ℹ️ Additional context
A bigger conversation to be had is whether the prefix /subscriptions/ should be added at all as it is not defined by the FOCUS Specification column library, but I am happy to follow Microsoft's definitions as long as it is clear.
🙋♀️ Ask for the community
We could use your help:
- Please vote this issue up (👍) to prioritize it.
- Leave comments to help us solidify the vision.
In https://learn.microsoft.com/en-us/cloud-computing/finops/focus/convert#how-to-convert-cost-management-data-to-focus, the FOCUS column SubAccountId is documented to require no transformation from Cost Management SubscriptionId column.
finops-toolkit/docs-mslearn/focus/convert.md
Line 80 in f5bf284
In reality, FOCUS column SubAccountId from real observed data has a prefix
/subscriptions/attached before SubscriptionId. The difference looks more like this example:SubscriptionId = abcdef-12345-ghijk
SubAccountId = /subscriptions/abcdef-12345-ghijk
🛠️ Solution
I would appreciate some clarification to describe that SubAccountId structure will not be the exact same as SubscriptionId to prevent issues in querying FOCUS data, so end users can know whether to query using either of these filter clauses:
WHERE SubAccountId = 'abcdef-12345-ghijk', or
WHERE SubAccountId LIKE '%abcdef-12345-ghijk'
Perhaps the Transform column in the table should be reworked to say something like "add the prefix /subscriptions/ to SubAccountId"
ℹ️ Additional context
A bigger conversation to be had is whether the prefix /subscriptions/ should be added at all as it is not defined by the FOCUS Specification column library, but I am happy to follow Microsoft's definitions as long as it is clear.
🙋♀️ Ask for the community
We could use your help: