> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-eye/azure-ais/applications/apim-applications.md).

# APIM Applications

## Azure API Management

{% hint style="warning" %}

* To start scanning the applications, a schedule has to be created to scan the deployed API Management Instances - [Configure Code Scan Schedules](/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/code-scan-schedule-configuration.md)
  {% endhint %}

### What Is Scanned

For every API discovered in an API Management instance, the **`Azure API Management Analysis`** job collects the policy definitions at all four scopes and evaluates them together against the active **Azure API Management** quality profile:

| Scope         | File reported in issues                        | Description                                        |
| ------------- | ---------------------------------------------- | -------------------------------------------------- |
| **Global**    | `policy.xml`                                   | The service-level policy applied to all APIs       |
| **Product**   | `products/<product>/policy.xml`                | The policy of each product the API is published in |
| **API**       | `apis/<api>/policy.xml`                        | The policy of the API                              |
| **Operation** | `apis/<api>/operations/<operation>/policy.xml` | The policy of each operation of the API            |

Scopes without a policy are skipped. Issues are reported with the file path shown above and the line number inside that policy, so a rule such as *"API should have a rate-limit policy applied"* can be satisfied at any scope.

### To view all the APIs

1. Navigate to **`IZ Eye`** -> **`Azure`**-> **`Azure API Management`**. Overview includes

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F7hYVcAlYgiDUjlUyaVRQ%2Fazure_ais_apim_apps_1.png?alt=media&amp;token=01aa144d-5395-4a22-aa7b-df5ffb538405" alt=""><figcaption></figcaption></figure>

a. **`Name`** - Name of the API prefixed with Resource Group name

b. **`Organization`** - Subscription to which the API belongs to

c. **`Environment`** - Resource Group to which the API belongs to<br>

2. Click on the **`Plus`** icon to view all the versions of the API <br>

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FVFwgvG5Mgfeiux6Wv7eD%2Fazure_ais_apim_apps_2.png?alt=media&amp;token=4e325440-5269-4777-80b7-0e78bdbda77d" alt=""><figcaption></figcaption></figure>
3. Summary details include -
   1. **`Total Issues`** - Indicates total number of issues once the application is scanned
   2. **`Status`** - Indicated the status of class / trigger in Salesforce
   3. **`Last Scan`** - Time since the last scan was performed
4. Actions include -
   1. **`View Dashboard`** - Summary report of all the issues.
   2. **`View Issues`** - Detailed report of the issues with file names and line numbers.

### See Also

* [App Registration](/product-guides/integral-zone/iz-suite/iz-eye/azure-ais/app-registration.md)
* [Configure Code Scan Schedules](/product-guides/integral-zone/iz-suite/iz-pulse/configure-schedule.md)
* [Logic Apps](/product-guides/integral-zone/iz-suite/iz-eye/azure-ais/applications/logic-applications.md)
* [Function Apps](/product-guides/integral-zone/iz-suite/iz-eye/azure-ais/applications/function-applications.md)


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-eye/azure-ais/applications/apim-applications.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.