Replies: 2 comments 1 reply
-
Yeah that is an interesting one. Originally, it only supported a subscription id, so the output was always scoped to a subscription and it did not make sense to fetch and output the subscription id as well (as they would all be the same). With the new options for billing accounts, this is no longer implicit, so I do agree that it needs to be included somewhere. I probably need to include it in the filter request. |
Beta Was this translation helpful? Give feedback.
-
@mivano I have also noted when using the azure-cost dailyCosts -e option to specify an account only the costs of one subscription are exported. |
Beta Was this translation helpful? Give feedback.
-
@mivano I create a json file of all resources under our Enterprise Agreement with the command attached. This works well so far, but I would like to add the account and the subscription of the resources. Is this possible?
azure-cost dailyCosts -b xxxxxxxx --timeframe BillingMonthToDate --dimension ResourceGroupName --includeTags -o json
Beta Was this translation helpful? Give feedback.
All reactions