# Request for review: 403 PERMISSION\_DENIED "project has been denied access" persists across 3 keys / 2 projects, 2FA enabled, billing shows Unavailable

**URL:** <https://discuss.ai.google.dev/t/request-for-review-403-permission-denied-project-has-been-denied-access-persists-across-3-keys-2-projects-2fa-enabled-billing-shows-unavailable/181152>\
**Category:** Gemini API\
**Tags:** billing\
**Created:** [September 7, 2026, 3:02am UTC](https://discuss.ai.google.dev/t/request-for-review-403-permission-denied-project-has-been-denied-access-persists-across-3-keys-2-projects-2fa-enabled-billing-shows-unavailable/181152 "2026-09-07T03:02:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ApexTrack](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/apextrack/32/147420_2.png) [@ApexTrack](https://discuss.ai.google.dev/u/ApexTrack)\
**Post date:** [September 7, 2026, 3:02am UTC](https://discuss.ai.google.dev/t/request-for-review-403-permission-denied-project-has-been-denied-access-persists-across-3-keys-2-projects-2fa-enabled-billing-shows-unavailable/181152/1 "2026-09-07T03:02:09Z")

</div>

I’m getting `403 PERMISSION_DENIED — "Your project has been denied access. Please contact support."` on every `generateContent` call to the Gemini API, and I’ve ruled out the usual causes:

- **Persists across multiple projects and keys.** Tried on the original project (`apextrack-507616`) and a brand-new project created directly through AI Studio’s “Create project” flow, with three separate API keys generated across them. Identical error every time.
- **Not a billing issue in the normal sense.** The Billing Tier for these projects shows “Set up billing — Unavailable,” and clicking “Set up billing” just spins indefinitely rather than loading Cloud Billing’s account-linking flow.
- **2-Step Verification is enabled** on the Google account, done specifically to try to clear this, per other threads here about account-level restrictions. No change after enabling it.
- **New project/key creation attempts are now themselves being blocked** with “Failed to create project, The request is suspicious. Please try again.” / “Failed to generate API key, The request is suspicious.”

This is a brand-new Google Cloud account (created today) being used to add a Gemini-powered chatbot to an ed-tech app for college recruiting students. Could someone from the team take a manual look at the account tied to this project ID and lift the restriction, or tell me what specifically triggered it?

Project ID: `apextrack-50761..`