> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/developer-tools/snyk-cli/scan-and-maintain-projects-using-the-cli/snyk-cli-for-iac/test-your-iac-files/arm-files.md).

# ARM files

How to test Azure ARM files with Snyk IaC using the CLI

With Snyk Infrastructure as Code, you can test your configuration files using the CLI.

Snyk Infrastructure as Code for Azure Resource Manager (ARM) supports scanning JSON format files. You can also scan Bicep format files by converting the configuration files to JSON using the Bicep CLI. Snyk supports the ARM `languageversion` 1.0.

## Test for an issue on specified JSON files

Enter the following Snyk CLI command:

```
snyk iac test deploy.json
```

You can also specify multiple files by appending the file names after each other, for example:

```
snyk iac test file-1.json file-2.json
```

## Test for an issue on specified Bicep files

Be sure you have the [Bicep CLI installed](https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/install).

After installing the Bicep CLI, **navigate** to the directory that contains your Bicep files and **convert** the relevant Bicep file to JSON by entering the following:

```
az bicep build -f deploy.bicep
```

You can then scan the newly created JSON file in the same way as any other file. Use the following Snyk CLI command:

```
snyk iac test deploy.json
```


---

# 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://docs.snyk.io/developer-tools/snyk-cli/scan-and-maintain-projects-using-the-cli/snyk-cli-for-iac/test-your-iac-files/arm-files.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.