AI agents for your Microsoft 365 tenant. Run locally, approved by you.
OpenAdminOS is an open-source desktop app for Intune and Entra admins. Agents investigate your tenant with local models, and every Graph change waits for your confirmation.
Pending signing.
Free and open-source. MIT licensed. github.com/OpenAdminOS/OpenAdminOS
46
GitHub stars
14
Community agents
203
Agent installs
MIT
Licensed, open source
How it works
Install an agent, run it locally, approve what changes.
01
Install from an open registry.
Each agent's manifest lists its Microsoft Graph scopes, read or write mode, and model requirements before you install it. Enterprises can point the app at a private registry; the rules do not change.
Browse the registry02
Run it against your tenant.
ollama serveThe app signs in with MSAL and reads tenant data through Microsoft Graph. With a local model like Ollama, prompts and tenant data stay on this device. Hosted providers are optional and labeled before anything leaves.
Investigate · Explain · Prioritize · Prepare changes
Compare model providers03
Approve every change.
Read-only agents run autonomously. Write agents stop at a diff of the proposed Graph change, and destructive operations require typed confirmation. There is no trust-this-agent bypass.
Diff confirmation
Retire inactive devices
This will retire 47 devices. Type RETIRE 47 DEVICES to confirm.
Human in the loop
Changes wait for your approval.
Read-only agents can run autonomously. Any change shows a diff first, and destructive actions require typed confirmation. There is no trust-this-agent bypass.
Review the trust modelOpen source
No vendor-owned agent runtime.
The app, runtime, agents, and registry contract are open from day one. Audit them, change them, or point OpenAdminOS at your own curated registry.
MIT
Commercial-friendly license
Open runtime
Agents, desktop app, registry, and SDK
Forkable registry
Point enterprises at their own curated agents
No tenant telemetry
Tenant content does not leave by default
Common questions
Questions admins usually ask first.
These answers summarize the product boundary: desktop app, Microsoft Graph, local-first model choice, declared agent permissions, and write confirmation.
What is OpenAdminOS?
OpenAdminOS is a local-first agent runtime and open-source desktop app for Microsoft 365, Intune, and Entra administrators. It connects to a tenant through MSAL, reads tenant data through Microsoft Graph, and runs declared agent workflows from the admin's machine. Local LLM providers keep prompts and tenant context on-device; hosted providers remain optional and are labeled before data leaves the workstation.
Does OpenAdminOS send Microsoft 365 tenant data to the cloud?
Not when a local provider is selected. With Ollama or another local provider, tenant data, prompts, and run results stay on the device. If an admin chooses a hosted provider such as OpenAI, Anthropic, or Azure OpenAI, the app labels that tenant context will be sent to that provider.
Which Microsoft 365 services does it work with?
The product is built around Microsoft Graph and initially focuses on Intune and Entra administration: devices, users, groups, sign-ins, Conditional Access, compliance posture, app assignments, audit logs, and related tenant signals.
What Microsoft Graph permissions do agents need?
Each agent declares its required Graph scopes in its manifest. OpenAdminOS shows those scopes before install and before consent, so admins can see what an agent can read or propose changing before it runs. Enterprises can point the app at a private registry; the same scope declaration and write-confirmation rules still apply.
What happens before a write agent changes my tenant?
Write agents always pause at a diff confirmation screen. Destructive operations require typed confirmation. There is no trust-this-agent bypass and no skip toggle for write operations.
Is OpenAdminOS affiliated with Microsoft?
No. OpenAdminOS is an independent open-source project. Microsoft 365, Intune, Entra, and Microsoft Graph are Microsoft trademarks and are referenced only to describe compatibility and administration targets.
Run tenant agents on your terms.
Use local models by default, hosted models by choice, and approve every Graph change.