Skip to content
iBlockSpam
Choosing a filter

What email security questions should you ask your MSP?

By iBlockSpam Team How we check our guides Updated 10 min read 8 sources
Short answer

Ask your MSP who holds admin access to your email and DNS and how it's protected, what filters inbound mail and whether it can be bypassed, whether SPF, DKIM and DMARC are enforced, how held mail is released, what's logged and for how long, how incidents are handled, and what you keep if you leave.

If a managed service provider (MSP) runs your IT, it probably also runs your email: the Microsoft 365 or Google Workspace tenant, the domain's DNS records, the spam filter and the response when someone clicks a bad link. That makes your MSP's own security part of yours.

These questions help a business owner or office manager find out what the MSP actually does for email, without needing to be a security specialist. Each comes with what a good answer sounds like.

Why ask your MSP about email security?

Because email is where most attacks start, and an MSP's admin access is a high-value target. In 2022, CISA, the NSA, the FBI and cyber agencies from four other countries published a joint advisory on threats to MSPs and their customers. It tells customers to "ensure their contractual arrangements specify that their MSP implements these measures and controls" and to "have a thorough understanding of the security services their MSP is providing" (CISA AA22-131A).

You don't need to audit your MSP. You need clear answers, in writing, to a short list of questions.

Who has admin access to our email, and how is it protected?

Start here. Admin accounts can read mailboxes, create forwarding rules and change routing.

  1. Which people at your company have admin rights to our tenant, and which roles do they hold? A good answer names roles, not "everyone on the help desk has global admin".
  2. Do you use GDAP for our Microsoft 365 tenant? GDAP, granular delegated admin privileges, gives partners "granular and time-bound access", and "customers must explicitly grant the least-privileged access" (Microsoft Learn).
  3. Is multifactor authentication required on every account you use to access us? CISA tells customers to require MFA "on all MSP accounts used to access customer environments".
  4. Do we keep our own admin account? Google recommends "more than one super administrator account, each managed by a separate individual", and separate everyday accounts for super admins (Google Workspace Admin Help).
  5. How would we remove your access? In Microsoft 365 the answer is Settings > Partner relationships > select the partner > Remove roles (Microsoft Learn). You can check that page yourself today.

Who controls our domain and DNS?

Whoever controls DNS controls where your mail goes.

  1. Is the registrar account in our company's name, with our recovery email? It should be. See our guide to registrar security and registry lock.
  2. Who can change our MX, SPF, DKIM and DMARC records, and how would we know if they changed? A good answer includes change alerts or a regular check.
  3. Where is our DMARC policy, and when do we reach enforcement? DMARC, defined in RFC 9989, tells receivers what to do with mail that fakes your domain. A policy of p=none only monitors. In our scan of the Tranco top 1,000 domains in October 2026, 38.3% didn't enforce DMARC, so don't assume yours does. Our DMARC rollout guide shows the path.

What filters our inbound mail, and can it be bypassed?

  1. What filters our inbound email: the built-in Microsoft or Google filtering, or a separate service? Either can be reasonable. Vague answers aren't. Our guide to what an email filtering service is explains the options.
  2. If mail goes through a filtering service first, can attackers send directly to Microsoft 365 and skip it? A good answer describes a locked-down connector. See blocking direct-to-tenant bypass.
  3. Who reviews quarantine, and how quickly is legitimate mail released? Ask whether users can release their own held mail or must open a ticket.
  4. Which attachment types and macros are blocked? Our guide to dangerous attachment types lists the usual candidates.

How do you detect and respond to email attacks?

  1. What do you get alerted on? Look for sign-ins from unusual places, new inbox forwarding rules and users restricted from sending. Our guide to malicious inbox rules explains why forwarding rules matter.
  2. How long are mail and audit logs kept, and who can search them? You'll need them after an incident.
  3. What happens in the first hour if one of our mailboxes is compromised? A good answer covers resetting the password, revoking sessions, removing rules and telling contacts. Compare it with our incident response plan guide.
  4. Is incident response in our contract, and what does it cost? CISA says contracts should "include incident response and recovery plans".

How do you measure and report on our email security?

  1. Do you check our tenant against a published baseline? CISA's SCuBA project publishes secure configuration baselines for Microsoft 365 and Google Workspace, with free assessment tools called ScubaGear and ScubaGoggles, and says "all organizations can use SCuBA" (CISA).
  2. What will you report to us each month? Ask for a sample.
  3. Do you run phishing awareness training or simulations? If so, ask how results are shared. See security awareness training for small businesses.

What happens if we leave?

  1. What do we keep, and how do you hand over? Admin accounts, registrar and DNS logins, filter configuration, documentation and backups should all stay with you. CISA tells customers to "disable MSP accounts that are no longer managing infrastructure".

What do good and bad answers look like?

Topic Good answer Red flag
Admin roles Named roles per task, time-limited GDAP "We all use one global admin login"
MFA Required on every MSP account, phishing-resistant for admins "Only for some staff"
Your own access You hold a separate admin account "You don't need admin access"
Registrar In your company's name In the MSP's account, or nobody knows
DMARC A current policy and a date for enforcement "We set up SPF, that covers it"
Filter bypass Direct delivery blocked or restricted "Spammers wouldn't know our tenant name"
Quarantine Users get digests and can release safe mail Every release needs a ticket
Incidents A written first-hour plan "We'd figure it out"
Reporting Monthly, in writing Only when something breaks
Exit Documented handover, access removed on day one Access stays "in case you need us"

A single red flag doesn't mean you should change provider. It means you should ask for a plan and a date.

How should you run the review with your MSP?

Treat this as a short, friendly review, not an interrogation. A good MSP will welcome it, because clear answers protect them too.

  1. Send the questions in writing first. Give your MSP a week or two to answer. Written answers are easier to compare and to keep.
  2. Book a 45-minute meeting to go through the answers you don't understand. Ask the MSP to show you the settings on screen where they can.
  3. Record each answer as done, planned or not offered. For anything planned, agree an owner and a date.
  4. Check what you can yourself using the steps in the next section.
  5. Put the important items in the contract. CISA's advisory recommends that contracts specify the security measures the MSP implements, including MFA and incident response.
  6. Repeat once a year, and after any security incident, staff change at the MSP, or move to a new mail platform.

If you're a regulated business, such as a medical, financial or legal practice, ask whether the MSP can provide the documentation your regulator or insurer expects. That's a question for your adviser as well as your MSP.

Which answers can you check yourself?

You don't have to take every answer on trust. A few take minutes to verify:

  1. Run the free Email Health Check on your domain to see your MX, SPF, DKIM and DMARC status.
  2. Use the MX Lookup to see which service actually receives your mail.
  3. Check the policy with the DMARC Checker; p=none means no enforcement yet.
  4. In Microsoft 365, open Settings > Partner relationships and review each partner's roles.
  5. Sign up for free Domain Watch to get an email when your public MX, SPF, DMARC or MTA-STS records change.

If your answers don't match what you were told, that's a good conversation to have.

How does iBlockSpam work with MSPs?

If your MSP uses iBlockSpam for inbound filtering, access is under your control. You grant the MSP full or read-only access to your account by invitation or partner code, and you can remove it any time. Partner staff must use two-factor authentication, and their actions appear in your activity log. Partners can't change your billing, plan, payment or security settings. Each business pays for its own domains, per domain rather than per mailbox; see iBlockSpam for small businesses. MSPs can read about the partner program.

Next steps

  • Send these 20 questions to your MSP and ask for written answers.
  • Check your domain with the Email Health Check before the conversation.
  • Review partner roles in your Microsoft 365 admin center today.
  • Make sure your company owns the registrar account.
  • If you're also choosing a filter, our email security RFP template covers the product questions. For a per-domain option your MSP can manage, see iBlockSpam for small businesses.

Browse more buying guides.

Frequently asked questions

What is GDAP, and why should I ask my MSP about it?

GDAP, granular delegated admin privileges, is how Microsoft partners get admin access to customer tenants. Microsoft describes it as granular, time-bound, least-privileged access that customers must explicitly grant. Ask your MSP which roles it holds and for how long, because broad, permanent partner access is a risk if the MSP itself is breached.

Should my MSP have Global Administrator rights in our Microsoft 365 tenant?

Usually not as a standing right. GDAP lets partners work with narrower roles, and Microsoft says Global Administrators have almost unlimited access and advises having as few as possible. Your MSP should explain which tasks need which roles. Keep at least one Global Administrator account that your own organization controls.

Who should own our domain registrar account, us or our MSP?

Your organization should own the registrar account and the domain, with the MSP added as a user or given delegated access. Whoever controls the registrar controls your DNS, and therefore your MX and DMARC records and where your mail goes. If an MSP relationship ends badly, owning the account avoids a dispute over your domain.

How often should an MSP report to us on email security?

Monthly is a sensible minimum for a small business. A useful report covers mail volumes and quarantine trends, any account compromises or suspicious sign-ins, changes to MX, SPF, DKIM or DMARC records, admin role changes, and progress on open recommendations. Ask for it in writing, not only in a meeting.

What should happen to MSP access when we change providers?

Remove it the day the contract ends. In Microsoft 365, go to Settings, then Partner relationships, select the partner and choose Remove roles. Disable or delete any accounts the MSP created, rotate shared passwords, and check registrar and DNS logins. CISA advises customers to disable MSP accounts no longer managing their systems.

Sources

  1. CISA, NSA, FBI and partners: Protecting Against Cyber Threats to Managed Service Providers and their Customers (AA22-131A)
  2. Microsoft Learn: Granular delegated admin privileges (GDAP) introduction
  3. Microsoft Learn: Manage Microsoft-certified solution provider partner relationships
  4. Microsoft Learn: Customer-led removal of a granular admin relationship
  5. Microsoft Learn: About administrator roles in the Microsoft 365 admin center
  6. Google Workspace Admin Help: Security best practices for administrator accounts
  7. CISA: Secure Cloud Business Applications (SCuBA) project
  8. RFC 9989: Domain-based Message Authentication, Reporting, and Conformance (DMARC)

See how your domain measures up

Run a free Email Health Check: MX, SPF, DKIM, DMARC and transport security in one scan, with the raw records shown. No sign-up.

Keep reading