> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/ai-agents/software-management/unused-application-monitoring.md). # Unused Application Monitoring The Unused Application Monitoring agent automatically scans your Identity Provider (IdP) for applications that have gone unused, then creates tickets so your team can review and act on them. By surfacing stale apps on a regular basis, you reduce your attack surface, simplify your app portfolio, and keep your IdP clean without relying on manual audits. *** ### How It Works When the agent runs, it connects to your configured IdP sources and evaluates each application against the inactivity criteria you define. Any application that meets the unused threshold is flagged, and the agent automatically opens a ticket listing those applications so your team can investigate, reassign, or decommission them. The process follows these steps: 1. The agent scans the IdP sources and application groups you specify. 2. It evaluates each application against your configured detection threshold - based on last sign-in date or number of active users. 3. Applications that meet the unused criteria are collected into a report. 4. The agent creates a ticket containing the list of unused applications for your team to review and action. *** ### Configuring the Agent #### Detection Threshold You control what counts as "unused" by setting an inactivity threshold. You can base this on either: * **Last sign-in date** - Flag any application where no user has signed in within a defined number of days. * **Active user count** - Flag any application that falls below a minimum number of active users. Choose the criterion that best fits your organization's usage patterns. For example, a stricter last-sign-in window works well for high-frequency tools, while an active-user threshold may be more appropriate for applications with periodic but legitimate use. #### Scan Targets You can define exactly which parts of your IdP the agent scans on each run: * **IdP sources** - Select one or more IdP integrations (for example, Okta, Azure AD, or other connected providers) to include in the scan. * **Application groups** - Narrow the scope further by targeting specific groups or categories of applications within those sources. Limiting the scan to relevant targets keeps results focused and avoids noise from applications that are intentionally inactive or out of scope. *** ### Ticket Creation When the agent detects unused applications, it automatically creates a ticket that includes: * The list of applications identified as unused. * The relevant inactivity data for each application, based on your configured threshold. Your team can then use the ticket to coordinate review, reach out to application owners, or begin offboarding the unused apps. No manual report generation or scheduled exports are needed - the agent handles detection and notification end to end. *** ### Enabling the Agent To enable Unused Application Monitoring: 1. Navigate to **AI Agents** in your Harmony dashboard. 2. Locate the **Unused Application Monitoring** agent under the Software Management section. 3. Select your IdP source or sources to scan. 4. Configure your detection threshold - choose between last sign-in or active user count, and set the appropriate value. 5. Optionally, specify application groups to include or exclude from the scan. 6. Save your configuration and activate the agent. Once active, the agent will run according to your configured schedule and create tickets whenever unused applications are detected. *** ### Benefits * **Reduced security risk** - Unused applications are a common source of unnecessary access and credential exposure. Regular detection helps you close those gaps faster. * **Cleaner app portfolio** - Keeping your IdP free of stale apps makes administration easier and reduces confusion for end users and IT teams alike. * **Automated, consistent coverage** - Rather than relying on periodic manual reviews, the agent provides ongoing monitoring so nothing slips through between audit cycles. * **Actionable output** - Every detection run produces a ticket, giving your team a clear, trackable item to work from rather than a raw data export to sort through. --- # 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.harmony.io/ai-agents/software-management/unused-application-monitoring.md?ask=&goal= ``` `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.