Skip to content
exonaut

What exonaut is

Written for everyone - no software background required. If you just want to know what this is and why it exists, read this and stop.

The problem, with an analogy

Section titled “The problem, with an analogy”

Imagine a giant warehouse holding everything about your company’s email system - every mailbox, distribution list, spam rule, retention policy. Today the only way to operate it is to walk up to one terminal in the back and type cryptic commands, one at a time, in a language called PowerShell:

Connect-ExchangeOnline
Get-Mailbox -Identity jane@contoso.com | Format-List

That works for an expert at the terminal. It’s a terrible fit for the modern world, where you want your phone app, your company portal, or an automated assistant to look something up or make a change - none of which can “type at the terminal.” They speak the universal language of the web instead: simple, labelled requests over HTTPS.

Microsoft built a lovely web API for part of this - Microsoft Graph - but it covers only a slice (mostly email content and a handful of settings). The vast majority of day-to-day Exchange administration still lives only at that PowerShell terminal.

What this project is

Section titled “What this project is”

exonaut is the self-service web counter in front of that warehouse. Any app, in any language, sends a plain web request - “GET me the mailboxes” - and behind the scenes this service walks up to the PowerShell terminal, runs the right commands, cleans up the messy output, and hands back a tidy, predictable result. The app never has to know PowerShell exists.

Before: an expert admin types commands at a PowerShell terminal and apps cannot. After: any app sends a web request to exonaut, which runs the commands and returns clean JSON.Before: an expert admin types commands at a PowerShell terminal and apps cannot. After: any app sends a web request to exonaut, which runs the commands and returns clean JSON.

What it lets you do

Section titled “What it lets you do”
  • Look things up - “show me all the shared mailboxes”, “who’s in the Sales group”, “trace where this email went”. One web request each.
  • Make changes - create a distribution group, add a member, set an out-of-office, change a retention policy, recover a deleted mailbox.
  • Build on top of it - clean, stable data means you can power a help-desk tool, an internal portal, an onboarding automation, or a chatbot - without embedding PowerShell in any of them.

Is it safe?

Section titled “Is it safe?”

Yes, by design. Every request must prove who it is (a sign-in token), and callers are only allowed to do the specific things they’ve been granted - read mailboxes, say, but not change retention policy. There are 30 narrow permissions instead of one all-powerful key. The service itself signs into Exchange Online with modern, secret-free credentials in production.