Setup overview

Before connecting a data source to Data Access, configure the underlying data source with the necessary permissions to allow Data Access to synchronize the required information.

Data Access requires broader permissions than standard Data Catalog ingestion because it actively reads, creates, and updates access controls.

To bridge Data Access and your underlying data source, create a connection from an Edge site to the data source.

Data Access requires specific connection types for certain data sources. It does not support standard JDBC connection types, which are typically used for Data Catalog ingestion. For example, for Databricks and Snowflake, you must use the dedicated Data Access connection types, Databricks Account and Snowflake, respectively. However, for BigQuery and Microsoft Entra ID, you can reuse the existing connection types, GCP connection and Azure connection, respectively.

Once your Edge connection is ready, add the data source to Data Access and link it to the Edge connection. This is when you set the sync schedule to pull the existing entities from your underlying data source.

Data Access does not require you to create an Edge capability; it automatically creates one when a sync is triggered. This Edge capability acts as the connector, running the sync instructions sent from Data Access to your underlying data source. If the capability is manually deleted from Edge, Data Access simply recreates it during the next sync.