Assets that should be there are missing

You may notice that your Google Cloud assets that should be pulled through (e.g. VMs and Cloud DNS assets) are not appearing in the portal.

Why is this happening?

There are a few reasons for this, depending on the method of integration used,

If using OAuth for integration:

You may have connected to the wrong Google Account (for example, to a personal Google account rather than a work one)
You might have enabled an additional API after initial set-up (e.g. added Compute Engine API after a time where only Cloud DNS API enabled initially or vice versa)

If syncing individual projects:

The Service Account has been created for the wrong Google Cloud Project
The Service Account is missing permissions (missing Compute Network Viewer and/or DNS Reader)
The Service account was missing permissions initially, and the JSON key was exported before the needed permissions were added

Not to worry, these issues can generally be addressed by removing and re-adding your Google Cloud integration.

This will temporarily delete all of your Google Cloud targets, but don't worry, these will be restored as soon as the integration is re-added.

First up, double-check the enabled APIs on your project. To do so, head to APIs & Services:
That will open the following dashboard, where you can see enabled APIs:

We're looking for the following to be listed:
- Service Usage API
- Cloud Resource Manager API
- Cloud SQL Admin API
- Identity and Access Management (IAM) API
- API Keys API
- Access Approval API
- Essential Contacts API
- Cloud Key Management Service (KMS) API
- BigQuery API
- Cloud Logging API
- Cloud Asset API
- Compute Engine API
- Kubernetes Engine API
- Cloud DNS API
- Cloud Storage API
That will open the following dashboard, where you can see enabled APIs:

We're looking for the following to be listed:
- Service Usage API
- Cloud Resource Manager API
- Cloud SQL Admin API
- Identity and Access Management (IAM) API
- API Keys API
- Access Approval API
- Essential Contacts API
- Cloud Key Management Service (KMS) API
- BigQuery API
- Cloud Logging API
- Cloud Asset API
- Compute Engine API
- Kubernetes Engine API
- Cloud DNS API
- Cloud Storage API
If any are missing, head to the Library from the navigation panel on the left:
Here you can search for each and enable them:
Once done, you can then follow these steps in our Google Cloud integration article to re-add your integration.

There are a few more things to check here compared to using OAuth, but not to worry, the following steps should help get you sorted!

First up (as above), double-check the enabled APIs on your Google Cloud project. To do so, head to APIs & Services:
That will open the following dashboard, where you can see enabled APIs:

We're looking for the following to be listed:
- Service Usage API
- Cloud Resource Manager API
- Cloud SQL Admin API
- Identity and Access Management (IAM) API
- API Keys API
- Access Approval API
- Essential Contacts API
- Cloud Key Management Service (KMS) API
- BigQuery API
- Cloud Logging API
- Cloud Asset API
- Compute Engine API
- Kubernetes Engine API
- Cloud DNS API
- Cloud Storage API
If not, head to the Library from the navigation panel on the left:
Here you can search for each and enable them:
Beyond this, head to the Service Account you created (Welcome page > IAM & Admin > Service Accounts):
Here things do get a bit involved, but agai,n not to worry, click on the Service account of intere,st then head to Permissions and click View Access:
This will then open a pre-filled query builder, where you can click ANALYZE > Run query:
Which will then open this section, where you can review the current Roles here:
If any are missing, you can head back to the Service Account's Permission here:
Once done, you can then follow these steps in our Google Cloud integration article to re-add your integration.