> 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-209.md).

# Azure Cognitive Search Without SLA for Search Index Queries misconfiguration detected in code

## Azure Cognitive Search Without SLA for Search Index Queries misconfiguration detected in code

### Rule Details

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

### Impact

Azure Cognitive Search is a fully managed cloud search service that offers indexing and querying capabilities. Indexing is the process of loading content into the service to make it searchable, while querying is when a client searches for content by sending requests to the index. A crucial aspect of maintaining high performance and resilience for these processes is the configuration of multiple replicas. Replicas ensure that queries and index updates are load balanced across them, ensuring smooth operations and reduced latencies.

For maintaining consistent performance, especially in high-demand scenarios, and to uphold the Service Level Agreement (SLA) for search index queries, it's crucial to have an adequate number of replicas. Azure's SLA mandates a minimum of 2 replicas to guarantee the SLA for search index queries.

This rule validates that the Azure Cognitive Search service is configured with at least 2 replicas, ensuring the SLA for search index queries is met.

### 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 = 2

## ... 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-209.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.