> For the complete documentation index, see [llms.txt](https://docs.bsure.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsure.io/user-guides/applications/application-overview.md).

# Application Overview

This report will show you how many users that have signed into the specific application, and also if the application have been signed into by a service principal or a managed identity.

The report will help you find applications in use and also the applications not in use.

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

**Slicer menu:**

* Applications: number of applications based on you filter choices
* Microsoft App: Gives you the opportunity to filter between Microsoft apps and third party apps
* Enabled: If application is enabled for users to sign-in
* App In Use: If neither used by end-users nor service principal/Managed identity or have SCIM configured = No, else Yes
* User Sign-In: If used by End-users or not
* Latest User Sign-In: To filter on a specific period when end-users signed into the applications
* System Sign-in: If used by Service Principal or Managed Identity or not
* Application Owner: If an application owner is set on the the application in customer settings - applictions
* Type: Service principals has different types, like Application, Managed Identity, Social ldp and Legacy, ref <https://learn.microsoft.com/en-us/entra/identity-platform/app-objects-and-service-principals?tabs=browser#service-principal-object>

Use report to find application usage and track Service Principals.


---

# 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.bsure.io/user-guides/applications/application-overview.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.