-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not able to get Kind = Modern usage details #19086
Comments
Thanks for the report @dejan-shuki! |
hi @dejan-shuki Could you provide a more detailed example about it? |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @TiagoCrewGitHubIssues. Issue Details
Describe the bug
To Reproduce Expected behavior BillingPeriodEndDate | BillingProfileId | BillingProfileName | AccountOwnerId | AccountName | SubscriptionId | SubscriptionName | Date | Product | PartNumber | MeterId | ServiceFamily | MeterCategory | MeterSubCategory | MeterRegion | MeterName | Quantity | EffectivePrice | Cost | UnitPrice | BillingCurrency | ResourceLocation | AvailabilityZone | ConsumedService | ResourceId | ResourceName | ServiceInfo1 | ServiceInfo2 | AdditionalInfo | Tags | InvoiceSectionId | InvoiceSection | CostCenter | UnitOfMeasure | ResourceGroup | ReservationId | ReservationName | ProductOrderId | ProductOrderName | OfferId | IsAzureCreditEligible | Term | PublisherName | PlanName | ChargeType | Frequency | PublisherType | PayGPrice | PricingModel received cols: type | tags | billing_period_id | usage_start | usage_end | instance_name | instance_id | instance_location | currency | usage_quantity | pretax_cost | is_estimated | meter_id | subscription_guid | subscription_name | account_name | department_name | product | consumed_service | cost_center
|
@dejan-shuki I apologize for the confusion here. We have two types of usage details records, "legacy" and "modern". The kind of record is related to the agreement you have signed with Microsoft. Since you have an Enterprise Agreement, your usage details records will always come in the legacy format. Only customers who have signed a Microsoft Customer Agreement will receive usage details of kind "modern". |
@dejan-shuki We are closing this issue now as it has been > 1 week since my last reply here. If you are still having issues you can reopen as needed. |
Closing this based on above comment from @adwise3 . @dejan-shuki we will be happy to help if above guidance does not work. Please free free to re-open the thread if more help is needed. |
Review request for Microsoft.ContainerService to add version 2022-05-02-preview (Azure#19262) * Adds base for updating Microsoft.ContainerService from version preview/2022-04-02-preview to version 2022-05-02-preview * Updates readme * Updates API version in new specs and examples * update readmes (Azure#19081) * add blob csi driver into 0502preview (Azure#19095) Co-authored-by: weizhichen <weizhichen@microsoft.com> * Add read only field for `currentOrchestratorVersion` (Azure#19107) * currentOrchestratorVersion is read-only property * Only apply change to 2022-05-02-preview * Add keyVaultNetworkAccess and keyVaultResourceId into securityProfile.azureKeyVaultKms to support key vault with private link (Azure#19086) * Add keyVaultNetworkAccess and keyVaultResourceId into securityProfile.azureKeyVaultKms to support key vault with private link * fix * Add KEDA configuration options (Azure#19153) * 2022-05-02-preview defender updates (Azure#19172) * 2022-05-02-preview defender updates * update example * Typo * Update sample * typo * another typo Co-authored-by: weizhi <ftdchenwz@gmail.com> Co-authored-by: weizhichen <weizhichen@microsoft.com> Co-authored-by: Thalia Wang <58485997+wenxuan0923@users.noreply.github.com> Co-authored-by: Bin Xia <binxi@microsoft.com> Co-authored-by: Jatin Sanghvi <20547963+JatinSanghvi@users.noreply.github.com> Co-authored-by: Or Parnes <orparnes@microsoft.com>
Package Name:
Package Name: azure.mgmt.consumption
Operating System:
Win 10
Python Version:
3.9
Describe the bug
To Reproduce
Steps to reproduce the behavior:
SCOPE = '/providers/Microsoft.Billing/enrollmentAccounts/{}/providers/Microsoft.Billing/billingPeriods/{}'.format(BILLING_ACC_ID, BILLING_PERIOD)
bill_consumption = consumption_client.usage_details.list(SCOPE)
Expected behavior
When we specify Enrollment as scope we expect to receive data for all subscriptions.
We expect more columns:
BillingPeriodEndDate | BillingProfileId | BillingProfileName | AccountOwnerId | AccountName | SubscriptionId | SubscriptionName | Date | Product | PartNumber | MeterId | ServiceFamily | MeterCategory | MeterSubCategory | MeterRegion | MeterName | Quantity | EffectivePrice | Cost | UnitPrice | BillingCurrency | ResourceLocation | AvailabilityZone | ConsumedService | ResourceId | ResourceName | ServiceInfo1 | ServiceInfo2 | AdditionalInfo | Tags | InvoiceSectionId | InvoiceSection | CostCenter | UnitOfMeasure | ResourceGroup | ReservationId | ReservationName | ProductOrderId | ProductOrderName | OfferId | IsAzureCreditEligible | Term | PublisherName | PlanName | ChargeType | Frequency | PublisherType | PayGPrice | PricingModel
received cols:
type | tags | billing_period_id | usage_start | usage_end | instance_name | instance_id | instance_location | currency | usage_quantity | pretax_cost | is_estimated | meter_id | subscription_guid | subscription_name | account_name | department_name | product | consumed_service | cost_center
The text was updated successfully, but these errors were encountered: