Per-user budget not limiting credit spent

[VincentPelletier1]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot Enterprise

Body

I have create a budget that is user wide across our enterprise that limits All AI Credit SKUs to a given sum per user per period (months). We've setup this budget a couple of periods ago. The budget never kicked in. Users could go a couple of hundred of dollars over the per user amount predefined by the budget (but never could go beyond the budget's max amount).

I initially thought that I did the budget wrong, but when I tried to create a "right" one, the platform promptly tells me that I already have another budget covering this kind of spending (which refers to my already existing one I talked about initially.

I also do not have a cost center nor do I think I need one. The only thing I want to do is for my users to have a fixed amount usage per period so that everyone has the same number of tokens per periods over the year.

I can provide further information if required, but it would be primordial that the feature works as it's a real hassle having to sync with a whole team trying to balance out token usage when nobody can predict how much they might use in a day.

I've seen the thread about this update and it is way too full of divergent conversation, which is why I'm opening a new ticket. Feel free to steer me in an already existing one if it exists, but I did not find any.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐