entra-stale-accounts
A read-only CLI that flags inactive Microsoft Entra ID (Azure AD) accounts past a configurable threshold. Point it at your own tenant, get a table or CSV of accounts that haven't signed in for N days — including accounts that have never signed in.
It never modifies anything: the only Microsoft Graph call it makes is a read of the user list. When Graph throttles (429), it waits out the Retry-After interval and retries instead of failing.
Install
pip install entra-stale-accounts
On macOS (or any system where Python blocks global pip installs), use pipx instead — it installs the CLI in its own isolated environment and puts the command on your PATH:
brew install pipx
pipx ensurepath
pipx install entra-stale-accounts
Usage
# Every enabled account with no sign-in in 90+ days
entra-stale-accounts check --days 90
# Same, as CSV — redirect to a file to hand to a manager or import elsewhere
entra-stale-accounts check --days 90 --output csv > stale.csv
# Also include already-disabled accounts, for a fuller audit
entra-stale-accounts check --days 90 --include-disabled
# Add a column of each account's license SKUs — which stale accounts
# are still holding paid licenses you could reclaim?
entra-stale-accounts check --days 90 --licenses
$ entra-stale-accounts check --help
Usage: entra-stale-accounts check [OPTIONS]
List enabled Entra ID accounts with no sign-in activity in the last N days.
Options:
--days INTEGER Inactivity threshold in days [default: 90]
--output [table|csv] Output format [default: table]
--include-disabled Also show already-disabled accounts
--env-file TEXT Path to a .env file with tenant credentials
--help Show this message and exit.
Accounts that have never signed in are always flagged — no activity at all is at least as noteworthy as an old sign-in — and sort to the top of the results.
Setup
The tool authenticates with your own Entra ID app registration via client credentials. Nothing is hardcoded — any tenant works.
1. Create an app registration
In Entra admin center → App registrations → New registration. No redirect URI needed.
Grant these application permissions under Microsoft Graph, then click Grant admin consent:
| Permission | Why |
|---|---|
User.Read.All |
Read the user list |
AuditLog.Read.All |
Read the signInActivity field |
Organization.Read.All |
Optional — lets --licenses show your tenant's own SKU names |
Without Organization.Read.All, --licenses still works: common SKUs resolve
through a built-in table and anything unknown shows as its raw GUID.
Create a client secret under Certificates & secrets.
2. Configure credentials
Copy .env.example to .env and fill in your values:
ENTRA_TENANT_ID=your-tenant-id
ENTRA_CLIENT_ID=your-app-client-id
ENTRA_CLIENT_SECRET=your-client-secret
Plain environment variables work too, and take precedence over the .env file.
3. The licensing requirement (read this)
The Graph field this tool depends on — signInActivity — requires a Microsoft Entra ID P1 or P2 license on the tenant, not just API permissions. Without it, the field comes back empty or the request is denied — that's a licensing wall, not a bug. P1 is included in Microsoft 365 Business Premium (not Basic) and is also available standalone.
Accounts whose signInActivity is missing are reported as never signed in — if every account shows never, suspect the license, not your users.
Example output
USER PRINCIPAL NAME DISPLAY NAME ENABLED LAST SIGN-IN DAYS
----------------------------- ------------ ------- ------------ -----
nina@contoso.onmicrosoft.com Never Nina true never never
sam@contoso.onmicrosoft.com Stale Sam true 2026-01-01 229
2 stale account(s) past a 90-day threshold.
Troubleshooting
"blocked by your organization's Device Guard policy" on Windows. Smart App
Control (and enterprise App Control/WDAC policies) block the unsigned
entra-stale-accounts.exe launcher that pip generates. The tool itself still
runs fine through the signed Python interpreter — substitute the command name
and keep every flag the same:
python -m entra_stale_accounts.cli check --days 90
CSV opens in Excel as one mangled column. In Windows PowerShell, > writes
UTF-16, which Excel mis-detects. Redirect through Out-File instead:
entra-stale-accounts check --days 90 --output csv | Out-File stale.csv -Encoding utf8
A .env in the current directory is ignored. Fixed in 0.1.4 — upgrade with
pip install --upgrade entra-stale-accounts, or pass --env-file .env
explicitly on older versions.
Every account shows never. Almost always the licensing wall described in
Setup, not a bug.
Development
git clone https://github.com/pobrienDev/entra-stale-accounts
cd entra-stale-accounts
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
pytest
The test suite mocks every Graph call — it runs in milliseconds and never needs real credentials or a live tenant.
Origin
Generalized from account-lifecycle automation built for a production Microsoft 365 environment: while automating provisioning, I kept needing to check for stale accounts, so the pattern became a standalone, general-purpose tool any admin can install.
License
Metadata
Release files for entra-stale-accounts 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| entra_stale_accounts-0.2.1.tar.gz | 21.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| entra_stale_accounts-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.2 kB
Release files / entra_stale_accounts-0.2.1.tar.gz
| Download URL | entra_stale_accounts-0.2.1.tar.gz |
|---|---|
| Size | 21.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d70cbbe0f294f2751d2625e6ee9d6f186cb52f686faf808eee620473b898881a
|
|
BLAKE2b-256 checksum How to use checksums |
0b0a9df7631d177c51e7f188f20ba6de19381eb4c5f8ba1824a9503a226b450a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 28, 2026.
Transparency logRelease files / entra_stale_accounts-0.2.1-py3-none-any.whl
| Download URL | entra_stale_accounts-0.2.1-py3-none-any.whl |
|---|---|
| Size | 15.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f9a861d450ef60f39f011f48625178ab129d5c74af39e1381d8224c512053656
|
|
BLAKE2b-256 checksum How to use checksums |
c78b5db3694d20e6928b246617f4e925c217df32dd7482d1e920a9122b1337ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 28, 2026.
Transparency log