Microsoft.Synapse workspaces/sqlPools/extendedAuditingSettings 2021-03-01

Template format

To create a Microsoft.Synapse/workspaces/sqlPools/extendedAuditingSettings resource, add the following JSON to the resources section of your template.

  "name": "string",
  "type": "Microsoft.Synapse/workspaces/sqlPools/extendedAuditingSettings",
  "apiVersion": "2021-03-01",
  "properties": {
    "predicateExpression": "string",
    "state": "string",
    "storageEndpoint": "string",
    "storageAccountAccessKey": "string",
    "retentionDays": "integer",
    "auditActionsAndGroups": [
    "storageAccountSubscriptionId": "string",
    "isStorageSecondaryKeyInUse": "boolean",
    "isAzureMonitorTargetEnabled": "boolean",
    "queueDelayMs": "integer"

Property values

The following tables describe the values you need to set in the schema.

Microsoft.Synapse/workspaces/sqlPools/extendedAuditingSettings object


In Bicep, type and apiVersion are specified in the first line of the resource declaration. Use the format <type>@<apiVersion>. Don't set those properties in the resource body.

Name Type Required Value
name string Yes The name of the blob auditing policy.
type enum Yes For JSON -extendedAuditingSettings

See Set name and type for child resources.
apiVersion enum Yes For JSON - 2021-03-01
properties object Yes Resource properties. - ExtendedSqlPoolBlobAuditingPolicyProperties object

ExtendedSqlPoolBlobAuditingPolicyProperties object

| Name | Type | Required | Value | | ---- | ---- | ---- | ---- | | predicateExpression | string | No | Specifies condition of where clause when creating an audit. | | state | enum | Yes | Specifies the state of the policy. If state is Enabled, storageEndpoint or isAzureMonitorTargetEnabled are required. - Enabled or Disabled | | storageEndpoint | string | No | Specifies the blob storage endpoint (e.g. If state is Enabled, storageEndpoint or isAzureMonitorTargetEnabled is required. | | storageAccountAccessKey | string | No | Specifies the identifier key of the auditing storage account. If state is Enabled and storageEndpoint is specified, not specifying the storageAccountAccessKey will use SQL server system-assigned managed identity to access the storage. Prerequisites for using managed identity authentication:

  1. Assign SQL Server a system-assigned managed identity in Azure Active Directory (AAD).
  2. Grant SQL Server identity access to the storage account by adding 'Storage Blob Data Contributor' RBAC role to the server identity. For more information, see Auditing to storage using Managed Identity authentication | | retentionDays | integer | No | Specifies the number of days to keep in the audit logs in the storage account. | | auditActionsAndGroups | array | No | Specifies the Actions-Groups and Actions to audit.

The recommended set of action groups to use is the following combination - this will audit all the queries and stored procedures executed against the database, as well as successful and failed logins:


This above combination is also the set that is configured by default when enabling auditing from the Azure portal.

The supported action groups to audit are (note: choose only specific groups that cover your auditing needs. Using unnecessary groups could lead to very large quantities of audit records):


These are groups that cover all sql statements and stored procedures executed against the database, and should not be used in combination with other groups as this will result in duplicate audit logs.

For more information, see Database-Level Audit Action Groups.

For Database auditing policy, specific Actions can also be specified (note that Actions cannot be specified for Server auditing policy). The supported actions to audit are: SELECT UPDATE INSERT DELETE EXECUTE RECEIVE REFERENCES

The general form for defining an action to be audited is: {action} ON {object} BY {principal}

Note that in the above format can refer to an object like a table, view, or stored procedure, or an entire database or schema. For the latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are used, respectively.

For example: SELECT on dbo.myTable by public SELECT on DATABASE::myDatabase by public SELECT on SCHEMA::mySchema by public

For more information, see Database-Level Audit Actions - string | | storageAccountSubscriptionId | string | No | Specifies the blob storage subscription Id. - globally unique identifier | | isStorageSecondaryKeyInUse | boolean | No | Specifies whether storageAccountAccessKey value is the storage's secondary key. | | isAzureMonitorTargetEnabled | boolean | No | Specifies whether audit events are sent to Azure Monitor. In order to send the events to Azure Monitor, specify 'state' as 'Enabled' and 'isAzureMonitorTargetEnabled' as true.

When using REST API to configure auditing, Diagnostic Settings with 'SQLSecurityAuditEvents' diagnostic logs category on the database should be also created. Note that for server level audit you should use the 'master' database as {databaseName}.

Diagnostic Settings URI format: PUT{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview

For more information, see Diagnostic Settings REST API or Diagnostic Settings PowerShell | | queueDelayMs | integer | No | Specifies the amount of time in milliseconds that can elapse before audit actions are forced to be processed. The default minimum value is 1000 (1 second). The maximum is 2,147,483,647. |