> 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/storage/appsec-azure-208.md).

# Azure Cognitive Search Without SLA Index Updates misconfiguration detected in code

## Azure Cognitive Search Without SLA Index Updates misconfiguration detected in code

### Rule Details

|                        |                                       |
| ---------------------- | ------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_208                    |
| Category - Subcategory | Public Exposure - Resource Health     |
| Provider               | AZURE                                 |
| Severity               | LOW                                   |
| Framework              | ARM, Bicep, Terraform, Terraform Plan |

### Impact

Azure Cognitive Search provides fully managed cloud search service capabilities, such as indexing and querying. Indexing involves loading content into the service to make it searchable, whereas querying is the process of searching for that content. The performance and resilience of these processes are enhanced by configuring multiple replicas. Replicas enable queries and index updates to be load balanced across different replicas, ensuring efficient performance and high availability.

To ensure consistent performance and high availability for search index updates, it's important to have an adequate number of replicas. According to Azure's Service Level Agreement (SLA), a minimum of 3 replicas is required to guarantee the SLA for search index updates.

This rule checks and ensures that the Azure Cognitive Search service has at least 3 replicas configured, guaranteeing that the SLA for search index updates is maintained.

### How to Fix

*Resource:*

* azurerm\_search\_service

*Arguments:*

* replica\_count \[source,go]

***

resource "azurerm\_search\_service" "example" { name = "example-search-service"

## ... other configurations ...

* replica\_count = 3

## ... other configurations ...

### }


---

# 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://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/storage/appsec-azure-208.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.