SimpleOS Desk · Simple Intelligence Group

A help desk that shows its work.

Every ticket carries a priority, plus the client and the SLA policy you pick, and when you pick a policy the due time is frozen the moment the ticket is created. A Diagnose button matches the ticket against the common level-1 patterns, searches your own knowledge base, and proposes the Microsoft Graph or Intune fix with a confidence score and a reason. The fix runs in your tenant only when an administrator presses Execute. Every diagnosis and every run is written to an audit trail you can read on the ticket, so at the end of the month you can say what was proposed and what ran, instead of guessing.

One thing to remember: a help desk where every automated action is proposed to a person and kept on record.

Microsoft Entra sign-in first, with an emailed sign-in link for people without one. The fixes Desk runs happen in your own Microsoft tenant through Microsoft Graph and Intune.

The number nobody can show

What is SimpleOS Desk?

SimpleOS Desk is a help desk for firms on Microsoft 365 and the service providers who run desks for them, built so the answer to "what did the automation do to that account" is always on file. Every help desk now says its AI resolves tickets. Ask for the number and the room goes quiet, because the vendor's platform resolved it somewhere outside your tenant and the only record is a dashboard you cannot audit.

The cost is not the ticket. The cost is the day a client, an auditor or your own CFO asks what the AI did to that account and nobody can answer.

Desk is built so the answer is always on file.

See it in ninety seconds

Every clip is recorded on a fictional workspace (Ridgeline, with its made-up clients Acme Manufacturing and Lumen Bakehouse). Nothing you see is a real client.

SimpleOS Desk. Every ticket with a plan.

The clip is being recorded.

How it works, mechanically

How does a ticket get diagnosed, and who decides?

A person decides. Here is the whole path from a new ticket to a fix that ran, and what is written down at each step.

1

Intake with the client attached.

Your technicians create tickets in Desk, or an MCP client your administrator connects creates them. Each ticket carries a priority, the client you attach, and the SLA policy you pick; when you pick a policy, the due time is frozen at creation. Three queues show your technicians everything they may see, what they own, and what nobody has claimed, from one screen. Each client company has its own assets and its own recent tickets inside your workspace; one knowledge base serves all your clients.

2

Diagnose, then a person decides.

The Diagnose button runs a catalog of common level-1 patterns (password and lockout, license and seat, device and Intune) against the title and description, searches your published knowledge base for related articles, and writes a diagnosis with a confidence score and a reason. For the patterns it knows, it proposes the Microsoft Graph or Intune action that would fix the ticket. A model pass through Azure AI Foundry sits behind a switch your deployment turns on, and the panel says whether the catalog or the model wrote what you are reading. The proposal is where it stops.

3

Execution in your tenant, by an administrator's hand.

The proposed action runs only when an administrator presses Execute, the client has its Microsoft Entra tenant on file, and your deployment has execution switched on. It runs through Microsoft Graph and Intune in your own tenant, under the consent your administrator granted, never through a vendor's console.

4

An audit trail on every ticket.

Every diagnosis and every execution attempt is written to an audit trail. On the ticket you read what was proposed and what ran; on the workspace audit page an administrator reads who pressed it and when, filtered across the workspace. The trail is there from the first ticket, not from the day you ask for it.

The one thing to remember: a help desk where every automated action is proposed to a person and kept on record.

Governed like the rest of your Microsoft 365, dated

How does Desk fit Microsoft Agent 365 and Conditional Access?

As of May 1, 2026, Microsoft Agent 365 is generally available for the Commercial segment (Microsoft Learn, Microsoft Agent 365 overview, read November 2, 2026), and Conditional Access can target an agent identity when your tenant holds Microsoft 365 E7, or an Agent 365 license with Microsoft Entra ID P1 or Microsoft 365 E3 (Microsoft Learn, Conditional Access for agents, read November 2, 2026). Desk takes no agent identity of its own: your technicians sign in with Microsoft Entra ID, and the actions Desk proposes run through its Microsoft Graph application in your tenant under the consent your administrator granted, so the Agent 365 map stays the one map you govern. There is no vendor data lake behind the desk; what Desk keeps is the ticket, the diagnosis and the trail, in your workspace.

What will be working after two weeks

Tickets flowing in, each with a priority, and with a client and a due time on the ones you gave a client and an SLA policy. Your technicians working three queues from one screen. Diagnose proposing the fix on the patterns it knows, with a confidence score and a reason, and your first published knowledge base articles turning up as related articles on a ticket. The audit trail filling in from the first ticket.

What this does not do yet

Diagnose calls no language model until your deployment switches the model pass on; until then it is the pattern catalog and the knowledge base search. Desk does not draft replies to the requester yet; it proposes the fix. There is no permission setting per runbook yet: every execution is an administrator's press, and there is no four-setting row (may see, may draft, may do with approval, may do alone). Desk publishes no resolution rates yet. The Teams app and email intake are not switched on. The SLA clock marks a ticket as due soon, past due and escalated, and leaves an internal note on the ticket when it escalates. It can email the assigned technician and your administrators, but only where your deployment has that email switched on; until then your technicians see it in the queue. There is no message to your Teams channel and no on-call rota yet. The workspace export is a JSON download an administrator asks for by address; there is no export button yet. There is no per-client contract or billing yet, Desk does not couple to an RMM, and it does not replace a full PSA.

Why a firm picks it over a ticketing platform with an AI add-on

Why pick Desk over a ticketing platform with an AI add-on?

The audit trail on every diagnosis and every run, which a ticketing platform with an AI add-on does not give you. Execution through Microsoft Graph and Intune in your own tenant, by your administrator's hand, not through a vendor's console. Plans are per technician, with no per-resolution meter. And a service provider runs it for many clients from one workspace, each client with its own tickets and assets, and your own brand on the workspace.

You lose nothing by signing in: the audit trail is on every ticket from day one, and your records leave with you, as a JSON download an administrator asks for.

Where the fix runs

How does a fix run in our Microsoft tenant?

Through Microsoft Graph and Intune, in your own tenant, under the consent your administrator granted, and only after an administrator presses Execute on a proposal Desk wrote down. Desk holds the ticket, the diagnosis and the audit trail in your workspace; the account, the license and the device it acts on never leave Microsoft.

What you lose without it is the record: a reset that happened in a vendor's console is a reset you reconstruct from memory when the client asks, and a desk that cannot say what it did is a desk that pays for the question twice.

Questions buyers ask

Does Diagnose resolve tickets without a person?

No. Diagnose proposes the fix with a confidence score and a reason. It runs only when an administrator presses Execute, and every diagnosis and every run is written to the audit trail.

Where do our tickets live?

In your SimpleOS Desk workspace, isolated per workspace and attached to the client you pick, behind Microsoft Entra sign-in first and an emailed sign-in link for people without one. The fixes Desk runs happen in your own Microsoft tenant through Microsoft Graph and Intune.

Can we prove what Diagnose did?

Yes. Every diagnosis and every execution attempt is on the ticket's audit trail with what was proposed and what ran, and on the workspace audit page an administrator reads who pressed it and when, filtered across the workspace.

Is Desk a full PSA for MSPs?

Not yet. There is no per-client contract or billing yet, and Desk does not couple to an RMM.

Does Desk take tickets from Teams and email?

Not yet. Your technicians create tickets in Desk, or an MCP client your administrator connects creates them; the Teams app and email intake are not switched on.

A help desk where every automated action is proposed to a person and kept on record.

Sign in with the Microsoft account your firm already uses and open the first ticket. If you would rather talk first, a person answers.