> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/getting-started/entitlement-data-discovery/credentials-discovery/microsoft-azure-credentials.md).

# Microsoft Azure: Credentials

### **Overview**

BalkanID supports discovery and governance of credentials within Microsoft Azure(AWS) as part of **IGA for Non-Human Identities (NHI)**.

All credentials are normalized into the BalkanID data model and surfaced in the **Credentials tab**, along with their associated identities, access relationships, and risk insights.

The associated Credentials can also be seen under the specific application integration(Azure) page.

<figure><img src="/files/A7h22f3EdXgEusoDuzAg" alt=""><figcaption></figcaption></figure>

### **Credential Types Supported**

BalkanID tracks the following AWS credential types:

{% hint style="info" %}
**Note:** The credential types listed below are examples and do not represent the full set of supported Azure credentials.
{% endhint %}

* Federated Identity Credentials
* Key Credentials
* Client Secret

Common risks associated with Azure credentials include:

* Long-lived client secrets not rotated
* Expired or soon-to-expire credentials
* Over-privileged service principals
* Unused or orphaned application credentials

BalkanID highlights these risks through insights for credentials and enables organizaiond to;

* Discover all application and service principal credentials
* Map credentials to identities, roles, and resources
* Identify stale, unused, or high-risk credentials
* Understand access paths and privilege levels


---

# 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://docs.balkan.id/getting-started/entitlement-data-discovery/credentials-discovery/microsoft-azure-credentials.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.