Being charged for Secret Protection while I don't have it enabled

[snandam]

🏷️ Discussion Type

Bug

Body

Hello - Our org (teams plan) is being charged every day for "Secret Protection" that we have disabled in settings/security_products. I have a rule that has this feature disabled and not using the default GitHub rule. However, I'm still being charged everyday. I opened a support ticket last week and no response for that either. Could someone help please.

[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. ⭐

[syedsafeer]

This usually happens because GitHub Advanced Security (GHAS) billing is based on unique committers within a 90-day window. If the feature was recently active, those committers might still be "active seats" on your bill even after you've toggled the setting to off.

A few things to double-check:

1. Repository Overrides: Check if any specific repository has an individual override or a Ruleset that is keeping Secret Protection active despite the Organization-level setting.

2.. Billing Breakdown: Go to Settings -> Billing and plans -> Plans and usage and look for the "GitHub Advanced Security" section. It should show you a list of exactly which repositories are currently consuming seats.

If the "active seats" list is empty but you're still being charged, then it's definitely a billing sync error that only Support can fix, but the 90-day rule is the most common culprit.

[snandam]

Thank you.

1. Repository Overrides: Check if any specific repository has an individual override or a Ruleset that is keeping Secret Protection active despite the Organization-level setting.

Checked the individual repositories and it's disabled as well

2.. Billing Breakdown: Go to Settings -> Billing and plans -> Plans and usage and look for the "GitHub Advanced Security" section. It should show you a list of exactly which repositories are currently consuming seats.

I downloaded the csv report from Billing and Licensing -> Licensing, "Download CSV report, Secret Protection" and it's empty.

I also downloaded usage report from Billing and Licensing -> Usage "Get Usage Report" that shows 'ghas_secret_protection_licenses` against our users but no repositories tied to those line items.

Really confused why I'm unable to stop this usage billing. Appreciate looking into it.

[syedsafeer]

the $76 charge for 4 seats while showing 0 licenses is a clear sync issue. This usually happens because of the 90-day committer rule: GitHub keeps charging for anyone who committed while the feature was active for 90 days, even after you disable it.

Check one more place: Organization Settings -> Billing and plans -> View active committers. If you see 4 names there, that’s the reason for the charge. If that list is also empty, then your billing status is stuck in the backend and only a Support agent can manually refresh it for you

[snandam]

https://docs.github.com/en/billing/concepts/product-billing/github-advanced-security

[snandam]

Trying to get to a support agent is the biggest struggle here. I opened a support ticket and not a single response. This is really bad customer service

[syedsafeer]

That screenshot is perfect proof of the discrepancy. Since it clearly shows '0 licenses' in use but you're still being charged $76, it's definitely a backend sync error on GitHub’s side.
I recommend updating your existing support ticket with this exact screenshot. Make sure the ticket is categorized under 'Billing -> Incorrect Charge' these usually get prioritized. Unfortunately, only a billing agent can manually refresh this 'stuck' state. Hope they resolve it for you soon!

[facundotorraca]

hey, any update on this? We are on a similar case here!

[moza369]

what this discussion about ?