IT Reporting
Reports that tell you what is wrong, and what to do about it.
Most IT reports tell you something is wrong but not what to do about it. A dashboard reports a mailbox at 96%, and the only advice that follows is to delete things. A manager says their team is buried, and nobody has the numbers to check. We write jobs that read Microsoft 365 directly and report what they find in a form someone can act on.
How they work
What these reports do.
Demos
See each job run.
Full mailboxes
Two mailboxes can sit at nearly the same percentage for opposite reasons, and the admin center cannot tell them apart. A tool you run on demand reads Exchange and produces a printable document that says what each problem is, who fixes it, and how every figure was measured.
Mailbox workload
Ninety days of mail metadata, never contents, showing who carries the volume, who has no time away from email, and where incoming mail comes from, with an owner for each fix and a note on what the data cannot show.
Common questions
Before you book a walkthrough.
What runs these jobs?
Scripts that call Microsoft Graph and Exchange from your tenant when you need an answer. Nothing calls a third-party service and no data leaves your environment.
Does this read the contents of people’s email?
No. The workload job reads metadata only: when a message arrived or was sent, and how many. Subject lines and message bodies are never accessed.
Can this rank our staff by how hard they are working?
No. Message count shows how much mail someone handles, not how much they contribute. The report says so on screen, since a ranking like that would not hold up with an employee or HR.
Can these run against our systems?
Yes. Tell us what you want to know about your tenant and we will tell you whether it is worth automating.
What do you want to know about your tenant?
Tell us the question you keep having to answer by hand, and who needs to see the answer.