[ Operations & automation ]
MSP, APIs and integrations
Multi-tenant operations for MSPs and MSSPs, plus APIs and integrations with your security stack.
42 guides
[ Core guides ]
[ All guides ]
Article
What are the Major Benefits of Managed Services Provider with EmailAuth and DMARC
A Managed Services Provider or MSP offers dedicated services to your company within the context of the app or product you purchase.
Guide
Alert routing by tenant, domain owner and business impact
Route authentication findings through verified tenant and service ownership, with explicit handling for unknown owners and critical impact.
Guide
API authentication and scoped access to domain data
Grant report access by tenant and operation, then test denials as carefully as successful reads.
Guide
Application integration failure: separate data ingestion from email delivery
Diagnose integration failures by separating provider mail handling from webhook or API ingestion, storage and dashboard processing.
Guide
Authentication API evaluation: scope, provenance and rate limits
Evaluate an authentication reporting API by testing its contract, provenance and failure behavior before committing a workflow.
Guide
Autotask workflow requirements for authentication incidents
Map authentication incidents into Autotask with active tenant-specific values, durable correlation and verified resolution.
Guide
Build an MSP service catalogue around the work customers actually need
Describe an MSP authentication service as concrete work, customer dependencies and acceptance evidence.
Guide
Create tickets from authentication findings without flooding the service desk
Create one accountable incident per meaningful authentication episode, with a destination map and a tested closure rule.
Guide
Customer handover from implementation to steady-state monitoring
Transfer ownership with an accepted baseline, a tested escalation path and explicit limits on what monitoring can prove.
Guide
Customer notifications through Microsoft Teams, Slack or email
Choose a notification channel and prove the difference between attempted send, platform acceptance, receipt and human acknowledgment.
Guide
Customer-specific approval and escalation responsibilities
Assign each customer a real approval path and escalation clock before the next authentication incident.
Guide
Define a meaningful service-level agreement for authentication operations
Write authentication service commitments that can be timed, evidenced and assigned to an accountable owner.
Guide
Design a ConnectWise authentication incident workflow
Specify a ConnectWise PSA incident handoff with customer mapping, evidence access, retry reconciliation and closure gates, without claiming an integration exists.
Guide
Design a HaloPSA authentication incident workflow
Plan a HaloPSA authentication event lifecycle with tenant mapping, action visibility, permission boundaries and retry evidence while keeping integration claims unverified.
Guide
Design a traceable authentication API evidence trail
Design an API evidence trail that preserves contract versions, collection completeness, retry outcomes and human decisions without retaining credentials.
Guide
Design integration tests away from production DNS
Design offline fixtures and a separately approved environment stage that test integration behavior without treating production DNS as a sandbox.
Guide
Design Microsoft Sentinel ingestion for authentication evidence
Build a bounded report pipeline into Azure Monitor before treating authentication data as usable Sentinel evidence.
Guide
Design Splunk ingestion for authentication evidence
Map normalized authentication observations to Splunk HEC while preserving counts, isolation and replay evidence.
Guide
Evaluate DNS integration access before connecting
Evaluate a proposed DNS connection by its exact operations, zone scope, data exposure and withdrawal plan before granting persistent access.
Guide
Incremental export and reliable report synchronisation
Synchronize report evidence with replay-safe identities, durable checkpoints and an explicit policy for late or corrected data.
Guide
Interpret bulk domain scans without overstating coverage
Plan a bounded domain scan with a clear inventory, distinct error states and honest coverage before turning configuration findings into customer actions.
Guide
Launch one MSP customer with a repeatable authentication onboarding process
Onboard an MSP customer with explicit authority, sender coverage, acceptance tests and a usable exit plan.
Guide
Monthly MSP reporting with accountable next actions
Turn aggregate report evidence into a bounded monthly account of coverage, unresolved risk and named next actions.
Guide
Offboard an MSP customer and return its configuration and evidence
Return a verified operating record and preserve reporting continuity before retiring MSP access or dependencies.
Guide
Pagination, filtering and time windows in report exports
Export every intended report once by defining timestamp semantics, continuation rules and independently checkable boundaries.
Guide
Preserve tenant boundaries when exporting data to shared analytics
Preserve customer isolation across export selection, transformation, redaction and shared analytics destination access.
Guide
Price an MSP authentication service using real operating effort
Build service pricing from measured work and explicit assumptions rather than domain count alone.
Guide
PSA integration requirements for an MSP authentication service
Specify the customer lifecycle, data boundary and acceptance evidence before choosing a PSA integration.
Guide
Reconcile domain and customer inventories across billing and operations
Reconcile billing and operational domain inventories using explicit metric definitions, stable mappings, raw totals and coverage-aware sender drill-downs.
Guide
Role-based access for customer staff, analysts and administrators
Give customer staff, analysts and administrators only the actions and tenant scope their responsibilities require.
Guide
SAML and SSO requirements for an authentication platform
Define SAML and SSO acceptance around tenant binding, authorization, user changes and active-session behavior rather than a successful login alone.
Guide
SCIM and user lifecycle requirements for an authentication platform
Specify SCIM lifecycle requirements with stable identifiers, tenant-bound operations and separate evidence for disablement, roles and session revocation.
Guide
Send authentication findings to a SIEM with useful context
Map authentication findings into Microsoft Sentinel with tenant context, evidence links and a deliberate incident lifecycle.
Guide
Separate domain health from message authentication
Distinguish configuration observations, receiver authentication results and monitoring coverage before deciding what an email-health alert means.
Guide
Service accounts and API-key rotation for authentication integrations
Define integration credential lifecycle requirements around tenant scope, complete consumer migration and separately verified revocation.
Guide
Tenant isolation in an MSP authentication service
Test tenant isolation across reads, exports, writes and background work rather than relying on a hidden user-interface filter.
Guide
Use provider delivery events alongside DMARC aggregate reports
Combine provider delivery events and DMARC aggregates using explicit time windows, source coverage and defensible linkage granularity.
Guide
Validate domain ownership before granting a customer access
Verify scoped domain authority without confusing a public record, login or DNS challenge with legal ownership.
Guide
Webhook authentication, signatures and replay protection
Verify webhook bytes before trusting the payload, then control replay with a provider-specific delivery identity and retention policy.
Guide
Webhook retries, idempotency and duplicate events
Acknowledge durable acceptance promptly and make retries safe across duplicate delivery, partial failure and restart.
Guide
WHMCS provisioning requirements for authentication services
Design WHMCS provisioning around service identity, repeat-safe operations and an explicit boundary between billing and DNS changes.
Enterprise provenance
Why top financial institutions and governments retired their email security dashboards.
Traditional email authentication platforms sell you a dashboard and ask your engineers to do the labour. In high-stakes environments, manual oversight means delayed enforcement, configuration drift and unmonitored shadow domains.
EmailAuth is the agentic email provenance platform. Our agents enforce p=reject, keep third-party senders aligned and move your domains to full RFC 9989 compliance, the new DMARC standard,, with human-in-the-loop auditability.
SaaS · Dedicated tenancy · Air-gapped on-prem · BYOK encryption
[ More in Operations & automation ]