For Microsoft 365 MSP and CSP teams

Turn TERRL data into owned work.

Analyze exported sender data, assign responsibility, compare routes, and define how each change will be verified. Your team stays in control; SenderOwner does not connect to the tenant or execute the migration.

No account. No Microsoft credentials. The probe analyzes each original CSV in your browser.

Actual local analyzer with three synthetic sender rows, an assigned sample owner and route review fields
Actual analyzer · synthetic sample data. Swipe the image to see every column. Inspect the example →

See the handoff

A sender row becomes
a piece of owned work.

The analyzer creates review fields. Your team supplies the judgment. This example was entered and exported from the real interface using fictional data.

From the built-in sample

billing@tenant-a.example

1,820 observed · Review
Rolling 24 hours

Synthetic source row
Owner
Billing operations (sample)
Route to review
Investigate — human confirmation required
Next action
Ask the application owner to review sending volume and recipient scope.
Verification required
Record an administrator-approved route and compare the next export.

The downloadable CSV repeats the built-in sample in both tenant slots. It demonstrates the output format; it is not evidence of two real tenants, a validated route or a completed migration.

Download the actual sample CSV ↓

A repeatable operator handoff

From export to a reviewable action plan

  1. 01

    Bring an export

    Select a supported CSV locally. The original file is not sent to a service.

  2. 02

    Name the owner

    Turn an unattributed sender row into a responsibility your team can follow up.

  3. 03

    Choose what to evaluate

    Mark a route for human review; the probe never approves it.

  4. 04

    Define the work

    Export a next step and verification requirement, not another usage chart.

  5. 05

    Repeat across tenants

    Use the same structure for a second client without rebuilding a spreadsheet.

Starts where reporting stops

Keep the source of truth. Add accountable work.

If you already use…Keep using it for…This probe adds…
EAC or Microsoft support scriptsLive state, estimates, sender attributionOwner, route, next step, verification plan
A reporting productMonitoring, reports, alertsA narrow remediation worksheet
A migration providerExecuting licensed migration workCustomer-side coordination and acceptance fields
A spreadsheet or ticket boardFlexible notes and general tasksConsistent fields across two client tenants

Data boundary

The original CSV is designed to stay on this device.

The probe does not request Microsoft, SMTP, or provider credentials. It does not connect to a tenant or execute an external change.

Read the architecture draft

PUBLIC PROBE · $0

Test the workflow here. Save it in a workspace.

The probe stays on this device. For saved tenant records, action history and export, start a no-card workspace trial or subscribe from your workspace.

See plans and the workspace trial

Try the method. Keep the work.

From a local draft
to a shared workspace.

Use the analyzer to inspect the workflow without an account. When you need saved tenant records and action history, start a workspace trial with no card.

Start workspace trial

Browser-local analyzer

Inspect and export

  • Two local tenant slots
  • Up to 5,000 rows per file
  • Editable owner, route and verification fields
  • CSV/JSON action-plan export

No saved workspace or account.

Saved workspace

Return to the work

  • Email sign-in and organization access
  • Saved tenant records and action history
  • Team, import and history limits by plan
  • No-card trial; no automatic conversion
See trial conditions and paid plans →

Before you bring a CSV

Know what stays
in your control.

Read the CSV field guide →
Does SenderOwner connect to Microsoft 365?

No. You bring an export you are authorized to process. SenderOwner does not request Microsoft credentials or make changes in a tenant.

Does a route choice approve a migration?

No. A route is a review decision for an authorized administrator. The sample is fictional and the analyzer is not the live TERRL counter.

Where is my data processed?

The public analyzer parses the original CSV locally. The saved workspace is a separate signed-in service that stores the records needed for saved work. Read Security and Privacy for those boundaries.

What are the import limits?

Every import has a 5,000-row safety limit. The local analyzer shows the first 50 rows for editing and exports all parsed rows. Paid plans do not remove the per-file safety limit.

Can I start without paying?

Yes. Use the local analyzer without an account, or start a no-card workspace trial. The trial does not convert automatically; Pricing lists its time, tenant and import limits.

Start with a reviewable result

Give the next sender a next step.

Try the built-in sample, inspect the fields, and download a draft before bringing a customer export.

Open the local analyzer