> 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/compute/appsec-azure-211.md).

# Azure App Service Plan is Not Suitable for Production misconfiguration detected in code

## Azure App Service Plan is Not Suitable for Production misconfiguration detected in code

### Rule Details

|                        |                                         |
| ---------------------- | --------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_211                      |
| Category - Subcategory | Compute - Unsanctioned Resource Or Type |
| Provider               | AZURE                                   |
| Severity               | LOW                                     |
| Framework              | Terraform, Terraform Plan               |

### Impact

Azure App Services offer various plans tailored to different requirements, including scalability, performance, and features. While some plans are ideal for testing and development purposes, they might not be equipped to handle production workloads effectively. Using plans not designed for production might expose applications to performance bottlenecks or lack of vital features.

The Free (F1), Shared (D1), and Basic (B1, B2, B3) plans serve well for limited testing and development but are not recommended for production environments. For production workloads, Azure recommends Standard and Premium plans, with PremiumV3 being the latest offering with advanced capabilities.

This rule checks and ensures that the App Service plan selected does not fall into the categories of Free, Shared, or Basic. Ensuring your App Service uses a production-ready plan enhances its reliability and performance.

### How to Fix

*Resource:*

* azurerm\_service\_plan

*Arguments:*

* sku\_name \[source,go]

***

resource "azurerm\_service\_plan" "example" { name = "example-service-plan"

## ... other configurations ...

* sku\_name = "P1v3" # Ensure you're using a production-suitable SKU like Standard or PremiumV3.

## ... 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/compute/appsec-azure-211.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.