-
Notifications
You must be signed in to change notification settings - Fork 21.1k
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
Resource group scope does not work as documented #38660
Comments
@AndrewGailer Thanks for the comment. This feedback has been shared with @bandersmsft for further review. |
I am also facing the same issue do we have any resolution on the above question ? |
I'm getting the same error when making a call to the Usage Details List with the 2019-10-01 API:
Results in the error:
Making the same call using the 2019-01-01 API is successful, but is not in line with the documentation and is missing fields (resourceGroup etc). Any resolution? |
@bandersmsft Are there any news on this issue? It still returns "Billing Period is not supported in (2019-11-01) API Version for Subscription Scope With Web Direct Offer. (Request ID: 69fda2f6-f14b-4202-8b6e-6f906a1d9a8b)" for subscription-based scopes. Even worse, the previously usable api-version "2019-01-01" started to return an empty array only. |
Same issue here : Billing Period is not supported in (2019-10-01) API Version for Subscription Scope. |
I got the same error with go-autorest for https://management.azure.com/subscriptions/XXXXXXXX/providers/Microsoft.Consumption/usageDetails?&api-version=2019-10-01:
I didn't provide any billing periods in the request. And how can I provide UsageStart and UsageEnd dates for usagedetails? |
It worked with the following query: The doc should be updated to mention the correct $filter spec for Web Direct Offer. |
@KrishnaG-MSFT This issue doesn't directly affect the article published to https://docs.microsoft.com/azure/cost-management-billing/manage/consumption-api-overview This appears to be a bug with https://docs.microsoft.com/rest/api/consumption/usagedetails/list and that's maintained by the engineering team. Can please reassign as a product bug, not a doc issue? Thanks. |
Hi @bandersmsft, is there a workaround or an ETA on the product bug fix? I am having a similar issue with the usageDetails endpoint, specifically i cannot filter on tags in the $filter parameter. Stack overflow question with the problem I'm having |
Unable to add @prkumarms-zz in assignees so tagging @prkumarms-zz for visibility, review and to help provide insights. |
Hello, I'm having the same error message with Az consumption usage list, I cannot pull any usage info |
@PcChip Hey, i found a workaround. If you check out the comment i made in my stack overflow post it may help: https://stackoverflow.com/questions/63125218/azure-usagedetails-rest-api-cannot-filter-on-tags |
apparently adding quotes in the filter fixes the issue not working: working: |
Still don´t working within newer api-versions. Just 2019-01-01 seems to acceppt the parameters. |
Having issues too, trying to use tags in combination with startDate/endDate does not work, giving always empty result
|
When using the Usage Details - List REST API, specifying a scope with a resource group returns a
404 - File or directory not found
error.The documentation says to specify the scope as
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}
but this returns the 404 error.As a workaround, you can specify the resource group in the filter like
$filter=properties/resourceGroup eq '{resourceGroupName}'
; however, this does not work with the latest version of the API (2019-05-01).If you specify the filter, the following error is returned:
Changing the API version to the previous stable release (2019-01-01) allows the filter to work.
This is an example of the full URI:
https://management.azure.com/subscriptions/00000000-0000-0000-0000-000000000000/providers/Microsoft.Consumption/usageDetails?api-version=2019-05-01&$filter=properties/resourceGroup eq 'dev-rg'
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 77db9ac7-6b1c-496b-36a3-24119c897546
Version Independent ID: 31fbb3ed-1eb8-ff0c-05d8-1e92ccc1519f
Content: Azure consumption API overview
Content Source: articles/billing/billing-consumption-api-overview.md
Service: billing
GitHub Login: @bandersmsft
Microsoft Alias: banders
The text was updated successfully, but these errors were encountered: