> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/logging/appsec-azure-156.md).

# Azure SQL Server does not have default auditing policy configured misconfiguration detected in code

## Rule Details

|                        |                               |
| ---------------------- | ----------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_156            |
| Category - Subcategory | Logging - Disabled or missing |
| Provider               | AZURE                         |
| Severity               | LOW                           |
| Framework              | Terraform                     |

## Impact

Configuring a default auditing policy for your Azure SQL Server can help improve the security and management of your database. Auditing allows you to keep a record of events and activities that have occurred on your database, such as user logins, data changes, and other actions.

*Runtime - Buildtime*

## How to Fix

*Resource:* azurerm\_function\_app

* *Arguments:* enable\_builtin\_logging \[source,go]

***

resource "azurerm\_function\_app" "pass2" { name = "test-azure-functions" location = azurerm\_resource\_group.example.location resource\_group\_name = azurerm\_resource\_group.example.name app\_service\_plan\_id = azurerm\_app\_service\_plan.example.id storage\_account\_name = azurerm\_storage\_account.example.name storage\_account\_access\_key = azurerm\_storage\_account.example.primary\_access\_key https\_only = false enable\_builtin\_logging = true

## site\_config { dotnet\_framework\_version = "v4.0" scm\_type = "LocalGit" min\_tls\_version = 1.1 ftps\_state = "AllAllowed" http2\_enabled = false cors { allowed\_origins = \["\*"] } } }


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/logging/appsec-azure-156.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.