`az consumption budget create` failing

[letmaik]

Describe the bug

--resource-group-filter doesn't seem to work.

Related command

az consumption budget create --amount 1000 --budget-name ... --category cost --start-date 2024-09-22 --end-date 2025-09-22 --time-grain annually --resource-group-filter abc-rg def-rg --subscription ... --debug

Errors

{"error":{"code":"400","message":"Invalid budget configuration, please use filter interface with 2019-05-01-preview version (Request ID: f93d3dce-0a4b-4f28-b971-d347a23903eb)"}}

Issue script & Debug output

cli.azure.cli.core.sdk.policies: Request URL: 'https://management.azure.com/subscriptions/.../providers/Microsoft.Consumption/budgets/...?api-version=2023-05-01'
cli.azure.cli.core.sdk.policies: Request method: 'PUT'
cli.azure.cli.core.sdk.policies: Request headers:
cli.azure.cli.core.sdk.policies:     'Content-Type': 'application/json'
cli.azure.cli.core.sdk.policies:     'Accept': 'application/json'
cli.azure.cli.core.sdk.policies:     'Content-Length': '248'
cli.azure.cli.core.sdk.policies:     'x-ms-client-request-id': '3b7b38c9-7910-11ef-b199-f3f9b7eefc77'
cli.azure.cli.core.sdk.policies:     'CommandName': 'consumption budget create'
cli.azure.cli.core.sdk.policies:     'ParameterSetName': '--amount --budget-name --category --start-date --end-date --time-grain --resource-group-filter --subscription --debug'
cli.azure.cli.core.sdk.policies:     'User-Agent': 'AZURECLI/2.64.0 (DEB) azsdk-python-core/1.28.0 Python/3.11.8 (Linux-5.15.153.1-microsoft-standard-WSL2-x86_64-with-glibc2.35)'
cli.azure.cli.core.sdk.policies:     'Authorization': '*****'
cli.azure.cli.core.sdk.policies: Request body:
cli.azure.cli.core.sdk.policies: {"properties": {"amount": 1000.0, "category": "cost", "filters": {"resourceGroups": ["def-rg", "abc-rg"]}, "timeGrain": "annually", "timePeriod": {"endDate": "2025-09-21T23:00:00.000Z", "startDate": "2024-09-21T23:00:00.000Z"}}}

Expected behavior

No error.

Environment Summary

$ az version
{
"azure-cli": "2.64.0",
"azure-cli-core": "2.64.0",
"azure-cli-telemetry": "1.1.0",
"extensions": {
"ml": "2.30.1",
"ssh": "2.0.5",
"storage-preview": "1.0.0b4"
}
}

Additional context

No response

[yonzhan]

Thank you for opening this issue, we will look into it.

[hachi1030-Allen]

Hi Yong Zhang (@yonzhan) ,

I am from CSS team and I got one customer is hitting the same error as this one.

And I found the root cause of the issue is due to the request body error sent by Azure CLI cmdlet.

So if we use the --debug in the cmdlet, we saw the request body will be used is as below:

{
  "properties": {
    "amount": 900.0,
    "category": "cost",
    "filters": {},
    "timeGrain": "monthly",
    "timePeriod": {
      "endDate": "2035-01-01T00:00:00.000Z",
      "startDate": "2025-03-01T00:00:00.000Z"
    }
  }
}

If you see, it passed filters as the key their under properties.

However, I captured network trace from Portal, and Portal is using filter instead of filters in the request body.

So this is not Azure Cost Management API issue, but how Azure CLI passed the parameters in the request body.

Hope this makes sense and hope your team can fix the bug sooner.

Thanks and let me know if this helps.

[jacksorjacksor]

I have just run into the same error.

The below az cli command:

az consumption budget create --amount 300 --budget-name "AzCli-Dev-Test-Budget" --category cost --time-grain monthly --resource-group-filter "myRgName" --debug

generates a request body of:

{"properties": {"amount": 300.0, "category": "cost", "filters": {"resourceGroups": ["myRgName.poc"]}, "timeGrain": "monthly", "timePeriod": {"endDate": "2026-04-30T23:00:00.000Z", "startDate": "2025-04-30T23:00:00.000Z"}}}

which receives the same error message as described in the original post:

(400) Invalid budget configuration, please use filter interface with 2019-05-01-preview version

[TiloGit]

yes the REST API expects properties.filter see https://learn.microsoft.com/en-us/rest/api/consumption/budgets/create-or-update?view=rest-consumption-2023-05-01&tabs=HTTP

and based on DEBUG the azure cli sends filters:

{
    "properties": {
        "amount": 210.0,
        "category": "cost",
        "filters": {
        },
        "timeGrain": "monthly",
        "timePeriod": {
            "endDate": "2040-05-01T07:00:00.000Z",
            "startDate": "2025-05-08T07:00:00.000Z"
        }
    }
}

version of az

{
  "azure-cli": "2.72.0",
  "azure-cli-core": "2.72.0",
  "azure-cli-telemetry": "1.1.0",
  "extensions": {
    "account": "0.2.5",
    "aks-preview": "14.0.0b1",
    "containerapp": "1.0.0b1",
    "quota": "1.0.0",
    "resource-graph": "2.1.1",
    "ssh": "2.0.6"
  }
}

[TiloGit]

when I run the REST API call directly and fix the filters to filter it works:

# Invoke request
az rest --method PUT --url 'https://management.azure.com/subscriptions/a2czzzzzzzzzzz480d/providers/Microsoft.Consumption/budgets/VSEntMPN-zzz_BudgetAlert?api-version=2023-05-01' \
 --body '{"properties":{"amount":210.0,"category":"cost","filter":{},"timeGrain":"monthly","timePeriod":{"endDate":"2040-05-01T07:00:00.000Z","startDate":"2025-05-01T07:00:00.000Z"}}}'

[DavyJonesStockings]

Sorry if this is a naive question, but having just run into this issue myself, wouldn't the fix be as simple as finding wherever this api call is crafted and simply changing the key name from filters to filter? Unless it would cause issues when trying to use the command with multiple filters.

[TiloGit]

Evan Genske (@DavyJonesStockings) I agree. maybe 2027 will be the year we get a fix for that 🦖

[DavyJonesStockings]

Thankfully we have the power of open source software on our side. Cheers