--- sourceDocument: Australia Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications Release : - australia ft:locale : - en-US ft:publication_title : - Australia Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # ServiceNow Remote Instance # ServiceNow Remote Instance {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of ServiceNow Remote Instance The ServiceNow Remote Instance connector provides read-only, real-time access to data residing in other ServiceNow instances without storing or replicating that data locally. It enables a central ServiceNow instance to query tables from one or more remote instances as if the data were local, supporting unified visibility and cross-instance workflows while maintaining data residency compliance. Show full answer Show less ## Key Features * **Zero Copy Connection:** A connection admin sets up a zero copy connection in the Zero Copy Connector Hub to a remote ServiceNow instance using a dedicated service account. * **Data Fabric Table Mapping:** Data stewards use the zero copy connection to create data fabric tables that map remote instance data, accessible via list views or GlideRecord scripts. * **Real-Time Data Retrieval:** Data is queried from the remote instance each time a user accesses the fabric table and is never stored locally; data is purged from memory after use. * **Service Account Security Model:** Access permissions are controlled on the remote instance through a dedicated service account with read-only access to specified tables and fields, ensuring secure and limited data exposure. * **Oracle Database Limitation:** The connector does not support remote ServiceNow instances running on Oracle databases. Queries to Oracle-backed instances will fail, but direct Oracle database connections can be made using the Oracle Connector. ## Practical Use Case A managed service provider operating multiple ServiceNow instances across different regions can designate one central instance for unified reporting and workflow orchestration. By using the Remote Instance connector, the central instance queries remote incident, change, and asset data in real time without moving or copying records, thus adhering to data residency regulations while enabling consolidated dashboards and cross-organizational workflows. ## Next Steps * Coordinate with the remote instance administrator to create a dedicated service account with appropriate read permissions. * Set up zero copy connections in the Zero Copy Connector Hub using service account credentials. * Have data stewards create and map data fabric tables to access remote data as needed. The ServiceNow Remote Instance connector provides read-only access to another ServiceNow instance. The ServiceNow Remote Instance connector enables you to query tables residing in remote ServiceNow instances and access that data as if it were stored locally. This connector is designed to allow a central instance to retrieve records from one or more remote instances in real time. A connection admin can set up a connection to a remote ServiceNow instance in the Zero Copy Connector Hub and grant data stewards access to this connection. Data stewards can then use the established connection to create a data fabric table and map data from the remote instance. This allows users to access remote ServiceNow data through the table list view or by using GlideRecord scripts. For details on creating data fabric tables and mapping data, see [Managing data fabric tables](https://www.servicenow.com/docs/vdLJlIcLw1vrKjAsL1R1Eg "Access data virtually from an external source or a local table on your instance using data fabric tables."). ## How the connector works {#servicenow-remote-instance-zcc__section_tg1_fjk_vgc} After a zero copy connection is established and a data steward creates a data fabric table with mapped data, the connector queries the remote instance each time users access the data fabric table. Records are retrieved in real time and displayed in lists and forms. They're never stored or persisted on your local instance. After users close the list or form, the retrieved data is purged from memory. This approach differs from other data synchronization methods like Instance Data Replication (IDR) or custom API integrations because no data transfer or storage occurs on the local instance. ## ServiceNow Connector --- Oracle instance limitation {#servicenow-remote-instance-zcc__section_oracle_limitation} When using the ServiceNow Connector with Workflow Data Fabric or Zero Copy Connectors, the remote ServiceNow instance must be running on a supported database platform. Connecting to a ServiceNow instance that uses Oracle as its underlying database is not supported. Queries that include tables from an Oracle-backed ServiceNow instance fail. Warning: This limitation applies specifically to ServiceNow to ServiceNow connectivity through the ServiceNow Connector. Workflow Data Fabric and Zero Copy Connectors support direct connections to external Oracle databases through the Oracle Connector. ## Service account security model {#servicenow-remote-instance-zcc__section_ogp_hxc_23c} Access to tables on the remote ServiceNow instance is controlled through a service account. The remote instance administrator creates this service account and grants it permissions to access only the specific tables required for the connection. When configuring the connection, the connection admin provides the service account credentials. The permissions assigned to the service account on the remote instance determine which tables and fields are available through the zero copy connection. This security model ensures that data stewards can only map data that the remote instance administrator has explicitly made accessible. Work with the remote instance administrator to perform the following tasks: * Create a dedicated service account for zero copy access. * Grant the service account read permissions to the required tables on the remote instance. * Document which tables and fields the service account can access. {#servicenow-remote-instance-zcc__ul_llk_txc_23c} ## Use case {#servicenow-remote-instance-zcc__section_dnb_yxc_23c} A managed service provider operates twelve ServiceNow instances for different business units, each containing incident, change, and asset data specific to that unit. Due to data residency regulations in multiple regions, records cannot be copied or moved between instances. The provider designates one instance as the central processing instance where cross-organizational workflows and dashboards are managed. Using the ServiceNow Remote Instance connector, the central instance establishes zero copy connections to each of the twelve remote instances. Data stewards create data fabric tables that map incident and asset fields from the remote instances. When an executive dashboard displays consolidated metrics, the central instance queries each remote instance and retrieves only the records needed for the current view. When a workflow requires a decision based on asset data from a specific region, the central instance looks up the relevant records without storing them. Throughout these operations, all data remains in its original instance, satisfying data residency requirements while providing the unified visibility the organization needs. **Related tasks** * [Create a ServiceNow Remote Instance connection](https://www.servicenow.com/docs/trhCrUxvp0hZjPhLc2n~gQ "Establish a zero copy connection to a remote ServiceNow instance in Zero Copy Connector Hub.")