> 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/cortex-cloud-runtime-security/cortex-cloud-identity-security/enable-inactive-human-identity-logs-on-azure-in-cortex-cloud-identity-security.md).

# Enable inactive human identity logs on Azure in Cortex Cloud Identity Security

Configuration information for enabling inactive human identity logs on Azure.

To enable inactive human identity logs on the Microsoft Azure platform in Cortex Cloud Identity Security, you must first configure diagnostic settings for the **SignInLog** log types. These log types provide information regarding how long human identities have been signed in.

To configure the **SignInLog** log types, do the following:

1. Open the Azure console.
2. Navigate to the **Diagnostic settings** screen.
3. In the **Logs** area, under **Categories**, select the following categories that are related to sign-in logs:
   * **SigninLogs**
   * **NonInteractiveUserSigninLogs**
   * **ServicePrincipalSigninLogs**
   * **ManagedIdentitySigninLogs**
   * **ADFSSigninLogs**
4. Click **Save**.

{% hint style="info" %}

### Note

For more information, see [Ingest logs from Microsoft Azure Event Hub](/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/microsoft/azure-event-hub/ingest-logs-from-microsoft-azure-event-hub.md).
{% endhint %}


---

# 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/cortex-cloud-runtime-security/cortex-cloud-identity-security/enable-inactive-human-identity-logs-on-azure-in-cortex-cloud-identity-security.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.