> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.3/data-access/dam-supported-connectors/azure-synapse-analytics/data-access-audit.md).

# Data Access Audit

## Overview

The Data Access Audit tab provides a detailed trail of all actions performed within the Data Access module. It helps track changes across users, roles, permissions, and associated metadata objects. The audit log captures who performed an action, what was changed, when it happened, and the source of the change.

Audit entries support visibility and traceability, enabling compliance monitoring and operational transparency across the entire data access lifecycle.

The audit data appears across various levels, including instance, connector, users, groups, and permission entities (database, schema, and table).

## Instance-Level Audit

* **Date**: Timestamp of the action
* **Audit User:** The User who performed the action
* **Action**: Performed action (e.g., Add, Edit, Delete)
* **Description**: Summary of the change

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfcfqlrSC0dIY2pvadz-5DMsud8RcDCAGD54isunqJzQ2sfNJfqu7AWJph_TE3y2cgp7MnKEGstYfFnMWpkaCDzhF2D93D5oP1VYVcfsQfnT2OGdFhLnQnNEBC2zeFNKbtqNKTArA?key=0gA1DLHY-EdlMhKQwB4nSg" alt=""><figcaption></figcaption></figure>

## Connector-Level Audit

* **Date**: Timestamp of the action
* **Audit User**: The User who performed the action
* **Connection Name**: Name of the connector involved
* **Action**: Performed action
* **Description**: Summary of the change

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXekGvKNJYQ8GIVeB8mcPL5EZtWM2gM7pDHTwQXw1HokQuDMMGL3cRPEsBfH2fu_LW-E8PqzYAlsIfeqK8-zAfwjY3jm6YABXNWNsjfQ25tB30zzPVcpjh0GYv3RMN8A7mMEFdJxkA?key=0gA1DLHY-EdlMhKQwB4nSg" alt=""><figcaption></figcaption></figure>

## Azure Entra Users-Level Audit

* **Date**: Timestamp of the action
* **Azure Entra User**: Affected user from Azure Active Directory
* **Audit User:** The User who performed the action
* **Action**: Performed action
* **Source**: Origin of the change
* **Description**: Summary of the change

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcMgKZIlkMCqAJH1uyQNo9bypxOm_T7L49eis1KaRhz8iZkTDMoLlK5uQnpmsA2SgcxuqqZ36oFu3PoDC1etiYToxUgbuDNANYJqsVNkXLHj_3dFPGm5Df7J_ePj58YPF_5gzlm?key=0gA1DLHY-EdlMhKQwB4nSg" alt=""><figcaption></figcaption></figure>

## Azure Entra Groups-Level Audit

* **Date**: Timestamp of the action
* **Azure Entra Group**: Affected group from Azure Active Directory
* **Audit User**: The User who performed the action
* **Action**: Performed action
* **Source**: Origin of the change
* **Description**: Summary of the change

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeMMxOesXgsm66yQ5ZmxeIGV6Ee2Zjb_IvvbiPuPeOSD4jggsWmxnTMM2VSKKvW40WyT3H5WQywoEgkcaHPt14NQkIfQoGv92Elz6LfDyCy49bQ2DwaR3qzoaZG9sOOyVpzhz8gFA?key=0gA1DLHY-EdlMhKQwB4nSg" alt=""><figcaption></figcaption></figure>

## Database Roles-Level Audit

* **Date**: Timestamp of the action
* **Database Role**: Name of the role affected
* **Audit User**: The User who performed the action
* **Action**: Performed action
* **Source**: Origin of the change
* **Description**: Summary of the change

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeMWX6Dr0TPGvcItKauqB6XIrwY5327oHElq_y2L1hR3MsBDwnGRKeRHJZrqIGw53qcxG8NPajx8rkXd0lvj57nkKWhORYXy3KFxK5Fnz5VbPhsZmD62cTbYCEvn0DBJL_opxqfDw?key=0gA1DLHY-EdlMhKQwB4nSg" alt=""><figcaption></figcaption></figure>

## Database Users-Level Audit

* **Date**: Timestamp of the action
* **Database Users**: Name of the user affected
* **Audit User**: The User who performed the action
* **Action**: Performed action
* **Source**: Origin of the change
* **Description**: Summary of the change

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcEurg6A4oMDAgqZfwqvBd620ZScAAeeMwI2Muj56_gfDn4ruRag5qi5pix9elZN2-8GQsJAVYDC-jWca9dTlCJeBO3qTlVUBIVSuFwhY5Fqx3cHyx3yexNvlpjINV3w3ZA9sFiAw?key=0gA1DLHY-EdlMhKQwB4nSg" alt=""><figcaption></figcaption></figure>

## Database Permissions-Level Audit

* **Date**: Timestamp of the action
* **Connector**: The Connector associated with the action
* **Database**: Name of the database affected
* **Roles/Users**: Role or user impacted
* **Privileges**: Type of permission granted or revoked
* **Audit User**: The User who performed the action
* **Action**: Performed action
* **Source**: Origin of the change
* **Description**: Summary of the change

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfjZIc7AYiN53J-L73w9j-cbIVE7Rb_Pqw9oCHW5XCLuXKlSLCHCJNAKH85Et-rkblcG12ySPLAMcdvX43PTJbDAyTlmaHlcKH_jTOWXHFldgHwtt4TA836y2bGgVUgKkLOeW3N?key=0gA1DLHY-EdlMhKQwB4nSg" alt=""><figcaption></figcaption></figure>

## Schema Permissions-Level Audit

* **Date**: Timestamp of the action
* **Connector**: The Connector associated with the action
* **Schema**: Name of the schema affected
* **Roles/Users**: Role or user impacted
* **Privileges**: Type of permission granted or revoked
* **Audit User**: The User who performed the action
* **Action**: Performed action
* **Source**: Origin of the change
* **Description**: Summary of the change

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXepjBUdbqbT1U0fAD0CjSSu1iw7yKjlSWAdYK01KWAHNVKO3QyUVVO8X3vO-MlMyTSolPrHTlwChgTGNGuELUlr9jlX_GVl8ddM2MWr4xjngBDeMkrdxnnnKsatfjFjgxNFr9FqqQ?key=0gA1DLHY-EdlMhKQwB4nSg" alt=""><figcaption></figcaption></figure>

## Table Permissions-Level Audit

* **Date**: Timestamp of the action
* **Connector**: The Connector associated with the action
* **Schema**: Name of the schema containing the table
* **Table**: Name of the affected table
* **Roles/Users:** Role or user impacted
* **Privileges**: Type of permission granted or revoked
* **Audit User**: The User who performed the action
* **Action**: Performed action
* **Source**: Origin of the change
* **Description**: Summary of the change

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcuKZrpWLxdJOyOdlNrMVwNRrdq53hELgQdOXWm5K668hrirWZAf5ny3TVDpTrfpHtuPfSEmuFH0PJIOSd1Eyx-o5eLLJjxbq_cW-oLq9o-ll2my_DzqdLgZIpVeqDK_DEs_A9PuA?key=0gA1DLHY-EdlMhKQwB4nSg" alt=""><figcaption></figcaption></figure>

***

Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ovaledge.com/release8.3/data-access/dam-supported-connectors/azure-synapse-analytics/data-access-audit.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
