Setup Guide
Sentaro Setup Guide
Sentaro is EU-sovereign AI email security for Microsoft 365 and Google Workspace. It lives inside the tenant, scores mail and app grants before people interact with them, and acts according to your policy.
Best for teams that still see business-email compromise, invoice fraud, and unverified OAuth apps after native filters. Start at join.sentaro.com/skowers.
Start Sentaro Read More On The Tool PageWhat It Solves
Most successful attacks still start with a person and an inbox. Native spam tools catch noisy phishing. They miss quieter asks: a CFO “reply” with no thread, a supplier invoice with new bank details, or a document viewer that wants to read all mail.
- AI analysis of who is asking, from where, and whether the ask fits the relationship.
- Actions before interaction: deliver, flag inline, quarantine, or block.
- Visibility into OAuth grants and unverified apps that already touch the tenant.
- EU hosting in Sweden for teams that must evidence data location under GDPR, DORA, and NIS2.
How To Get Started
- Open Sentaro from the Skowers join link and choose Microsoft 365 or Google Workspace.
- Connect the tenant with an admin account. Setup is designed to finish in about four minutes.
- Review the API scopes Sentaro requests and what it does not ask for before you approve.
- Do not change MX records, DNS, or endpoint agents. Mail stays in the existing tenant path.
- Start with a pilot group (finance, executives, or anyone who approves payments) before org-wide policy.
Policy To Set First
- Map detections to actions per group: block, quarantine, tag inline, force re-auth, or revoke access.
- Keep finance and leadership on stricter actions than general staff during the first week.
- Decide who can release quarantined mail and how quickly they must review it.
- Tell staff that a Sentaro label in the mailbox is a verdict, not a suggestion to ignore.
What To Review In Security
Permissions
Which admin API scopes are used, and which mailbox or file scopes are deliberately not requested.
Data location
Models trained and served in Sweden. Confirm this matches your DPA, sector rules, and board evidence pack.
Message coverage
Email (and connected collaboration surfaces the product supports) scored before the user interacts.
App coverage
OAuth grants, unused integrations, and unverified publishers that can still read mail or files.
Roadmap vectors
Identity (leaks, lookalike domains) and behavioral (forwarding rules, off-hours sessions) are listed for Q4 2026. Do not buy as if they are live today.
Retention and subprocessors
Ask Sentaro for the security pack: encryption, retention, and subprocessors a reviewer will request.
Suggested First Tests
Invoice and bank-detail fraud: Use a realistic internal test message that asks finance to change payment details with no prior thread. Confirm it is held or blocked.
Executive impersonation: Send a lookalike-from test (only in a controlled exercise) and check whether Sentaro flags missing conversation history.
Risky app consent: Review existing OAuth grants. Identify unused or over-scoped apps and confirm Sentaro surfaces them.
False-positive check: Watch a week of real supplier and customer mail. Legitimate threads should still arrive without extra steps for most users.
Clickthrough Links
How To Evaluate The Trial
- Confirm connect time, missing MX/DNS work, and that mail still flows through Microsoft or Google.
- Count blocked or quarantined BEC-style messages versus tickets created for false positives.
- Have security sign off on permissions, data location, and retention before expanding past the pilot group.
- Keep Bitdefender or similar endpoint protection in place. Sentaro covers inbox and app grants, not laptops.