---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Discover datacenters only for new cloud accounts

# Discover datacenters only for new cloud accounts {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

If you have multiple cloud accounts and datacenters in AWS and Azure, you can discover datacenters for new cloud accounts only, instead of refreshing the entire list.

## Vorbereitungen

* Verify that you're using at least Zurich Patch 2.
* Verify that the glide.discovery.cdu.auto_refresh_sub_accounts_and_ldcs system property is set to true. For more information, see [Create discovery schedules for cloud resources](https://servicenow-prod.fluidtopics.net/3IDBT71oapHdBE_T6JFg8A#discovery-manager "Create schedules for discovering cloud resources based on the cloud discovery method you choose; that is, service accounts or IP ranges.").
{#discover-datacenter-only-new-account__ul_f35_lkd_pgc}

Role required: discovery_admin

## Prozedur

1. Navigate to AllSystem PropertiesAll Properties.
2. In the Name column, search for <kbd class="ph userinput">cloud.discovery.refresh_datacenter_for_new_member_account</kbd>.
3. Select the cloud.discovery.refresh_datacenter_for_new_member_account property.
4. In the Value field, enter true.
5. Select Update.
{#discover-datacenter-only-new-account__steps_tbs_qkd_pgc}

## Nächste Maßnahme

Either execute discovery immediately or wait until the predefined schedule triggers the discovery. For more information, see [Create a discovery schedule in Cloud Discovery Workspace](https://servicenow-prod.fluidtopics.net/5ehVc~2tght_73SbCZDybw "Create schedules for discovering cloud resources based on the discovery method that you choose: service accounts or IP ranges. The discovery schedule defines the various settings for the cloud discovery.").
**Vorheriges Thema:** [Activate a disabled pattern](https://servicenow-prod.fluidtopics.net/QY18rrI8lbM7yX~7g5cjTw "If you want to use a pattern for discovery that's disabled by default, activate it manually.")  
**Nächstes Thema:** [Improved query performance with direct field population in CI tables](https://servicenow-prod.fluidtopics.net/fv_6mvxBkpH9GnKa1~2XMQ "The Populate Service Account and LDC IN CMDB scheduled job populates the Service Account and Logical Datacenter fields in cloud configuration item (CI) tables, and the Virtual Machine Object field in the Hardware [cmdb_ci_hardware] table. This direct population reduces query complexity and improves query performance.")  
**Zugehörige Verweise**   

* [AWS discovery using patterns](https://servicenow-prod.fluidtopics.net/VRVjHOLBToHiwjz2ZRkbUg "Discovery and Service Mapping Patterns uses patterns to discover components of the Amazon AWS Cloud deployment during horizontal discovery. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.")
* [Microsoft Azure Cloud discovery using patterns](https://servicenow-prod.fluidtopics.net/21n1k1oqQLa8pJAwiICsIg "Discovery uses multiple patterns to discover components of the Microsoft Azure Cloud deployment during horizontal discovery. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.")