> 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/public-exposure/appsec-azure-196.md).

# Azure SignalR Service not Using Paid SKU for its SLA misconfiguration detected in code

## Azure SignalR Service not Using Paid SKU for its SLA misconfiguration detected in code

### Rule Details

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

### Impact

Azure SignalR Service is a managed service that allows for real-time communication using the SignalR library. The Service Level Agreement (SLA) is crucial for ensuring uptime and reliability for critical applications.

Using the "Free\_F1" SKU tier does not provide a business-level SLA, which can be a significant concern for applications requiring high availability and immediate support from Azure.

This rule ensures that SignalR Service instances do not use the free tier, hence ensuring a better SLA.

### How to Fix

*Resource:*

* azurerm\_signalr\_service

*Arguments:*

* sku \[source,go]

***

resource "azurerm\_signalr\_service" "example" { name = "example-signalr" location = azurerm\_resource\_group.example.location resource\_group\_name = azurerm\_resource\_group.example.name

* sku {
* name = "Standard\_S1" # or any other paid SKU
* capacity = 1
* }

## ... 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 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/public-exposure/appsec-azure-196.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.