---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# GCP Organization

# Google Cloud Platform (GCP) Organization discovery with Patterns {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

The ServiceNow
Discovery application uses the Discover Google Organization discovery pattern to find GCP Organization projects and resources. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.

## Request apps on the Store {#google-gcp-organization-discovery__section_sv2_vw5_5mb}

Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#google-gcp-organization-discovery__inline-send-to-store}

## Prerequisites {#google-gcp-organization-discovery__section_qqg_44v_5mb}

For details on system requirements and family compatibility, view the application listing on the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website.

GCP Organization structure
:   Verify that a GCP Organization resource is
    structured correctly, with projects underneath it in a miscellaneous hierarchy.
:   Ensure that all projects under the GCP Organization
    resource have the Compute Engine API enabled.

Service Account user settings
:   Check that Service Account users have access to the GCP Organization resource node.
:   Verify that Service Account users are members of all other projects located under the
    GCP Organization resource node.
:   Ensure that Service Account users have the following Cloud Identity and Access
    Management credentials for projects under the GCP Organization resource:

    * resourcemanager.folders.list
    * resourcemanager.organizations.get
    * resourcemanager.projects.get
    * resourcemanager.projects.list

Credentials for API elements
:   During the discovery, the pattern uses the following API elements. The user that was
    added to the credentials in the instance must have permissions to send these queries.

    * https://cloudresourcemanager.googleapis.com/v1/{name=organizations/\*}
    * https://cloudresourcemanager.googleapis.com/v1/projects
    * https://cloudresourcemanager.googleapis.com/v2/folders:search
    {#google-gcp-organization-discovery__ul_lnn_34t_wmb}

Credentials for creating a discovery schedule
:   Configure the following credentials:  
    1. Create GCP credentials.
    2. Create a GCP Service Account:
       1. Credentials: The GCP credentials.
       2. Account ID: The Google Service Account ID.
       3. Datacenter type: Select cmdb_ci_google_datacenter.
    3. Create a discovery schedule.
    {#google-gcp-organization-discovery__ol_exd_ljv_2hb}

(Optional) Create a serverless discovery schedule

:   Create a discovery schedule to perform targeted discovery of GCP Organization resources.

    1. Navigate to DiscoveryDiscovery Schedules.
    2. Click New and then fill in the form.  
       {#google-gcp-organization-discovery__table_ut3_sby_hhb__entry__2}

       | Field | Description |
       |-|-|
       | Name | Name for the Discovery schedule. For example, <kbd class="ph userinput">Discover GCP Organization</kbd>. |
       | Discover | Discover type. Select Serverless. |
       | MID Server | Name of the MID Server. |
       | Active | Option for enabling this schedule for discovery. Select this check box to enable discovery. |
       [Table 1. Discovery Schedule form]

       {#google-gcp-organization-discovery__table_ut3_sby_hhb}
    3. Right-click the header of the Discovery Schedule form and select Save.
    4. Click the Serverless Execution Patterns tab, click New, and then fill in the form.  

       {#google-gcp-organization-discovery__table_k3d_bzy_fhb__entry__2}

       | Field | Description |
       |-|-|
       | Name | Name for this Serverless Execution Pattern. For example, <kbd class="ph userinput">Discover GCP Organization</kbd>. |
       | Pattern | Name of the pattern to run: Discover Google Organization. |
       | Proxy Host | Fully qualified domain name of the machine on which you are installing the proxy server. Specify Global. |
       | Active | Option for enabling this schedule for discovery. Select this check box to enable discovery. |
       [Table 2. Serverless Execution Pattern form]

       {#google-gcp-organization-discovery__table_k3d_bzy_fhb}
    5. Under Discovery Pattern Launcher Parameters, configure the following parameters with the relevant values:{#google-gcp-organization-discovery__table_rqw_rkh_wnb__entry__2}

       | Parameter | Value |
       |-|-|
       | cloud_account_id | The Project ID within GCP. |
       | cloud_cred_id | The sysid of the GCP credentials. |
       | cloud_datacenter_type | <kbd class="ph userinput">cmdb_ci_google_datacenter</kbd> |
       [ ]

       {#google-gcp-organization-discovery__table_rqw_rkh_wnb}
    {#google-gcp-organization-discovery__ol_wb3_4by_hhb}

Customers with early access to the GCP Organization pattern
:   Verify that the Discover-GCP-SubAccounts scheduled job is not enabled in your
    instance.

    1. Navigate to System DefinitionScheduled Jobs.
    2. Click the Discover-GCP-SubAccounts scheduled job.
    3. Clear the Active check box, and then click Update.
    {#google-gcp-organization-discovery__ol_rf1_z45_4sb}
{#google-gcp-organization-discovery__ul_tb4_qjq_vmb}

## Data collected by Discovery during horizontal discovery {#google-gcp-organization-discovery__section_hm5_pvy_vmb}

{#google-gcp-organization-discovery__table_vk1_wvy_vmb__entry__2}

| Table and field | Description |
|-|-|
| Organization \[cmdb_ci_cloud_org\] ||
| name | The name of the organization resource. |
| object_id | The ID of the organization resource. |
| time | The time the organization resource was created in GCP. |
| operational_status | Current operational status. One of the following: * Operational * Non-Operational * Repair in Progress * DR Standby * Ready * Retired |
| Folder \[cmdb_ci_gcp_folder\] ||
| name | The name of the organization folder. |
| parent_id | The ID of the parent resource. |
| parent_type | The type of the parent resource. Can be <kbd class="ph userinput">organization</kbd> or <kbd class="ph userinput">folder</kbd>. |
| time | The time the resource was created in GCP. |
| status | The status of the folder according to the <kbd class="ph userinput">lifecycleState</kbd> status in GCP. |
| object_id | The ID of the organization folder. |
| Project \[cmdb_ci_gcp_project\] ||
| name | The name of the project. |
| project_id | The ID of the project. |
| parent_id | The ID of the parent folder resource. |
| parent_type | The type of the parent resource. Can be <kbd class="ph userinput">organization</kbd> or <kbd class="ph userinput">folder</kbd>. |
| time | The time the resource was created in GCP. |
| operational_status | The status of the folder according to the <kbd class="ph userinput">lifecycleState</kbd> status in GCP. |
| object_id | The ID of the project. |
| discovery_credentials | GCP account credentials. |
| Resource \[cmdb_key_value\] ||
| key | The key, or label, associated with the GCP project. For example, <kbd class="ph userinput">country</kbd>. |
| value | The project label value assigned to the GCP project. For example, <kbd class="ph userinput">ca</kbd>. |
| configuration_item | The URL or path of the CI. |
[ ]

{#google-gcp-organization-discovery__table_vk1_wvy_vmb}

## CI relationships {#google-gcp-organization-discovery__section_h2x_mqr_vmb}

{#google-gcp-organization-discovery__table_pfj_zqr_vmb__entry__3}

| CI | Relationship | CI |
|-|-|-|
| Cloud Organization \[cmdb_ci_cloud_org\] | Contained by::Contains | Google Project \[cmdb_ci_gcp_project\] |
| Cloud Organization \[cmdb_ci_cloud_org\] | Contained by::Contains | Service Account |
| Cloud Organization \[cmdb_ci_cloud_org\] | Contained by::Contains | Google Folder \[cmdb_ci_gcp_folder\] |
| Service Account | Owns::Owned by | Google Project \[cmdb_ci_gcp_project\] |
| Google Folder \[cmdb_ci_gcp_folder\] | Contained by::Contains | Google Project \[cmdb_ci_gcp_project\] |
| Google Folder \[cmdb_ci_gcp_folder\] | Contained by::Contains | Sub Google Folder |
| Sub Google Folder | Contained by::Contains | Google Project \[cmdb_ci_gcp_project\] |
[ ]

{#google-gcp-organization-discovery__table_pfj_zqr_vmb}

*[\>]: and then