404 on Vertex AI Models - Suspected Cloud Org Identity Mismatch After Domain Change

Google Cloud Build with AI Generative AI & Foundational Models
,
1

Hello,

We are facing a critical access issue with Vertex AI publisher models and believe it’s caused by an identity synchronization issue after a Google Workspace domain change.

The Problem:

  • API calls to any Vertex AI publisher model (e.g., a gemini-2.5-preview model) fail with a 404 Publisher Model not found error.

  • However, we can successfully use the same models in the same project via the web-based Vertex AI Studio.

This proves the issue is not with our user’s IAM permissions but with the programmatic authentication context.

Root Cause Analysis:

We recently changed our primary Google Workspace domain from [OLD-DOMAIN].dev to [NEW-DOMAIN].ngo.

Our investigation shows that our Google Cloud Organization is still identified by the old domain ([OLD-DOMAIN].dev), while our users and Workspace account are correctly configured with the new domain. We believe this identity mismatch is causing the authorization failure for API calls, especially for preview models that are allowlisted at the organization level.

Our Request:

We have confirmed our client-side and Workspace configurations are correct. The issue appears to be a backend synchronization problem between Workspace and Google Cloud Identity.

Could a Google staff member investigate this? We need our Google Cloud Organization’s identity to be updated to reflect our new primary domain.

I can provide the exact Project ID, Organization ID, and domain names in a private message upon request.

Thank you.