Skip to content

Service Bus cost increase #10997

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

Open
simonness opened this issue Apr 13, 2025 · 0 comments
Open

Service Bus cost increase #10997

simonness opened this issue Apr 13, 2025 · 0 comments

Comments

@simonness
Copy link

Service Bus costs jumped 2000% on 11th March for a namespace we use in a production environment and 13th March for a namespace we use in a non-production environment. Both namespaces are solely used by Azure Function Service Bus triggers.

I'm confident this jump in cost is not down to a change made on our side. We made no relevant code changes, and always release to non-prod before prod. Furthermore the non-prod namespace is hardly used, certainly under 100 messages per month, indicating this cost is most likely from the Azure Function Service Bus trigger "at rest".

Has there been any change to Azure Functions on Microsoft's side that could have caused this change in cost? Is anyone else seeing this?

The cost analysis shows a consistent higher daily cost from the dates mentioned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant