When you run DMARC for client domains at an MSP, you are juggling domain approvals, third-party DNS credentials, and aggregate report feeds across separate companies.
Pick the guide for the job on your desk right now.
Onboard client domains
If you are onboarding a new client or absorbing an unfamiliar domain portfolio, start with Client domain onboarding for DMARC: the MSP intake record while the service scope is being agreed and evidence of access is being collected. You need to establish who authorizes policy changes, who holds production DNS credentials, who has permission to receive reports, and who signs off on emergency rollbacks.
The intake process separates destination-side DNS authorization from client approval and from report routing. You end up with a record the operations team can take over, including the domains still on hold and the people responsible for outstanding actions.
Prioritize policy changes across multiple clients
Once domain access is confirmed, you face the scheduling headache: tightening DMARC from p=none to p=quarantine or p=reject across clients without breaking delivery.
To stage these transitions safely, follow Multi-client DMARC rollout: ranking policy changes by risk. It builds a queue ordered by risk and readiness; each entry carries its own client approval, its evidence requirements and named people responsible for exceptions and rollback. The worked example tells apart changes that are ready, changes that are held and changes waiting for recovery staff. You end up with a queue that states the conditions for going ahead, for restoring a defined scope and for handing it over to ongoing support.
Hand off DMARC reporting during offboarding
Whether you are running client reviews or coordinating a client’s departure, this guide assumes domain intake and sending responsibilities are already documented.
Follow Transfer DMARC reporting to a new MSP: client handover to transition report streams cleanly, one client at a time, without interrupting monitoring for your remaining accounts. The process walks you through authorization, verification of receipt, acceptance by the successor and removal of the outgoing team’s access, with report evidence, change history and unresolved decisions kept in a register per client, so you finish with a handover record in which responsibilities have been accepted and every unfinished step has an owner.
Need help with other email authentication workflows? Browse all knowledge topics.


