VaikoraVaikora

Vaikora › Blog › Product Updates

How Vaikora email security for Microsoft 365 works without an MX record change

Product Updates · Nov 18, 2026 · 3 min read

Most email security products require you to reroute your mail flow through their infrastructure. That means an MX record change, a redelivery hop, and a new dependency outside your environment. Vaikora's email security for Microsoft 365 takes a different path: it connects through Microsoft Graph, runs analysis on a virtual machine inside your own Azure subscription, and routes findings into your own Sentinel workspace.

Why the architecture choice matters

When analysis runs in a third-party cloud, your message content leaves your environment before it has been inspected. For organizations under HIPAA, PCI-DSS, or GDPR, that creates a data residency and compliance question before you have blocked a single threat.

Running the virtual machine inside the customer's Azure subscription means message data stays within the tenant boundary. The scanning infrastructure is yours to audit, yours to patch, and visible in your own cost and access logs.

How the connection works

Microsoft Graph provides API-level access to Exchange Online without touching your DNS configuration. Vaikora reads inbound mail through that API, routes each message to the analysis VM, and writes results back without altering the delivery path.

No MX record change means:

The connection uses your existing Azure identity controls. Access is governed by the Graph permissions you grant, not by a new external account with broad mailbox rights.

What detection looks like in practice

Consider a scenario where a supplier account has been compromised and is sending messages that pass SPF and DKIM checks because the attacker controls a legitimate sending account. Signature-based filters will not catch that. Vaikora analysis looks at behavioral signals in the message content, links, and attachment patterns rather than relying on the envelope alone.

Findings appear in your own Sentinel workspace. Because Vaikora integrates natively with Microsoft Sentinel, the same workspace where you track endpoint and identity alerts receives the email threat data. A SOC analyst investigating a lateral movement alert can correlate it against email activity in the same interface without pivoting to a separate vendor console.

The Sentinel reporting path

Vaikora pushes detections into Sentinel as native incidents rather than raw log entries. That means analysts see severity, affected mailboxes, and indicator data in a format that Sentinel already knows how to surface through its analytic rules and workbooks.

This matters for auditability. Every detection produces a record tied to the message, the analysis result, and the enforcement action taken. Compliance teams can produce a timestamped log of what was detected and what happened to it, which is what auditors actually ask for.

What you should check before deploying

Before deployment, confirm three things in your Azure environment.

If your team uses CrowdStrike Falcon or SentinelOne for endpoint detection, Vaikora's integrations with both platforms mean you can correlate a suspicious email against endpoint telemetry for the same user without manual indicator export.

What to do next

Pull up your current email security architecture and answer two questions: where does message analysis actually run, and who controls that infrastructure? If the answer to either is "a third-party data center," the residency and audit questions are worth working through explicitly before your next compliance review. The Microsoft Graph approach described here is one documented way to close that gap without a mail flow change.

See Vaikora enforce policy on your AI

Open-core AI runtime control. Self-host the MIT gateway free, or run the hosted Control Plane.

Get a demo Self-host the gateway

More from the Vaikora blog