Evaluating a Valimail mailbox connector
Check the current connector architecture, permissions and data handling before approving access.
Mailbox reporting can add context to a DMARC programme, but the Microsoft and Google integrations should not be presented as one unchanging design. Valimail’s current documentation describes different deployment and package prerequisites. A prospect’s evaluation should identify the exact connector being proposed and review its access and operating requirements.
Mailbox integration review
SC-FL-06 · REV A · 2026.07
01Identify
version and package
02Inspect
permissions and data
03Approve
security and cost owners
04Operate
monitor and disconnect
The current Microsoft and Google integrations have different prerequisites.
What mailbox reports add to sender investigations
Aggregate DMARC reports describe observed authentication activity. A mailbox integration can add visibility into mail received by the connected environment and support investigation of unknown services. This does not make either source a complete inventory. Agree which questions the additional reporting is expected to answer and test them with representative traffic.
Microsoft 365: review the tenant-hosted component
Valimail’s current Microsoft connector guidance describes a component installed in the organisation’s Azure tenant that scans email header information. It lists an Azure subscription and tenant-wide administrator consent among the prerequisites. Review the permissions shown during installation, the deployment’s operating responsibility and who owns Azure charges. Confirm how this differs from any Classic connector already in use.
Google Workspace: confirm package and access
The Google Workspace setup article says the integration works with Sender Owner Insights, available for Enterprise packages, and requires Workspace administrator access. Review the API scopes presented by the current setup, the accounts and domains covered, and the means of removing access. Do not infer the exact permission boundary from a general description such as metadata only.
Confirm data handling and how to disconnect the integration
Record data fields, processing locations, retention, support access and deletion or disconnection steps. Metadata and email addresses may still have data-protection implications. A security certification is useful evidence within its scope, not automatic APPI compliance for a particular deployment. Get the prospect’s security and data owners to approve the actual integration design.
// Key Takeaways
What to remember
- Identify the connector and version being evaluated.
- Review administrator consent and ongoing operating responsibility.
- Confirm data handling and removal before granting access.
// FAQ
Frequently asked questions
Are the Microsoft and Google connectors configured the same way?
No. Current vendor documentation gives them different deployment and package prerequisites. Review the exact integration and any existing Classic connector before planning rollout.
Does a connector’s security certification remove the need for privacy review?
No. Assess the data fields, permission scopes, processing and retention arrangements for the actual customer deployment. Certification evidence has a defined scope.
Last updated:
Plan local support for Microsoft 365 and Google Workspace connectors.
StrategyCore works with your product team and the prospect’s administrators to confirm the proposed connector, permissions, tenant or subscription requirements and data handling. We agree installation, administrator approval and post-sales technical support responsibilities before licensing.
