AegisAI Perspectives · 149

How do I run a proof of concept for an email security platform?

Run an email security PoC on your own mail: scope one read permission to a pilot group, write pass criteria with an end date, then revoke on that date. AegisAI starts read-only, and your admin grants access and can revoke it.

TL;DR
Answer
Run an email security proof of concept on your own mail: one read permission scoped to a pilot group, written pass criteria, an end date, and a revoke step on that date.
Who it's for
If you run IT for a company of 20 to 500 people on Microsoft 365 or Google Workspace, with a small IT or security team and no SOC.
Watch out for
Application Mail.Read reads every mailbox unless you pair it with a resource scope, and only direct members of the scoping group are in scope.
What AegisAI does
AegisAI connects to Microsoft 365 or Google Workspace through the API, judges every message by its intent, and removes what fails from every mailbox it reached.
Book a demo

See it on your own Google Workspace or Microsoft 365 tenant. No MX change.

Or get the Q3 2026 State of the AI Attack report (free, instant download)

Not ready for a demo? Check your domain.

How do I run a proof of concept for an email security platform?

Run an email security proof of concept on your own mail with one read permission scoped to a pilot group1, plus written pass criteria and an end date, then revoke the grant on that date. Exchange Online app permission changes take 30 minutes to 2 hours to apply4. AegisAI reads mail through the Microsoft 365 or Google Workspace API after delivery20. Its inbound email security page states how a deployment starts: "Starts read-only. Runs in monitoring mode first. Removal needs write access your admin grants and can revoke."23

If you run IT for a company of 20 to 500 people on Microsoft 365 or Google Workspace, with a small IT or security team and no SOC, this plan is written for you.

What you can do by the end

  • Run a seven-step PoC plan where every step has an owner and a time, plus a pass sign and a fail sign.
  • Grant one read permission scoped to a pilot group and prove the scope before day one counts.
  • Revoke the grant on the end date so the test app cannot read mail again.

Key takeaways

- Application Mail.Read reads email in all mailboxes unless you pair it with a resource scope21.

- Only direct members of a scoping group are in scope; nested group members are out3.

- Test-ServicePrincipalAuthorization shows InScope true or false per mailbox and bypasses the permission cache6.

- Export sign-in and audit logs before day seven on Entra ID Free; Entra ID P1 or P2 keeps them 30 days16.

- Revoking admin consent does not stop users from consenting again, so also stop dynamic consent14.

The short answer

QuestionAnswerSource
How do I run a proof of concept for an email security platform?Scope one read permission to a pilot group, write pass criteria and an end date, run the tool beside your current stack21, then revoke13.Microsoft Learn; aegisai.com
How do I prove the scope holds?Run Test-ServicePrincipalAuthorization: InScope must be true for pilot mailboxes and false for all others.Microsoft Learn
How long should it run?Run it beside your current stack for five days before you change anything. Export logs first: Entra ID Free keeps sign-in and audit logs for seven days16.aegisai.com; Microsoft Learn
How do I end it?Revoke admin consent and stop dynamic consent in Entra; delete the domain-wide delegation client in Google, which stops the app at once10.Microsoft Learn; Google Workspace Admin Help

Short on time? Watch the explainer, or book a demo.

How do you scope the email security PoC?

Give the app one read permission and nothing else: Application Mail.Read with a resource scope on Microsoft 365, or gmail.readonly on Google Workspace8. Prove the scope with Test-ServicePrincipalAuthorization before the first day counts. On Google, domain-wide delegation gives the app access to the data of all your users, so a pilot group does not limit it there27. The full permission setup, step by step, is in how to structure a read-only email security PoC.

What does a step-by-step PoC framework with scoring criteria look like?

Before anyone grants consent, write five items into the PoC agreement:

  1. The pilot group, with each pilot mailbox as a direct member.

  2. The pass criteria: what a finding must show to count.

  3. The run length: five days beside your current stack.

  4. The evidence to keep, exported before Entra ID Free drops sign-in and audit logs at seven days.

  5. The end date, when admin consent is revoked and dynamic consent stopped.

Then run the plan below. Each step has one owner and one time, plus a sign you can check.

StepOwnerTimeWhat to measurePass signFail signSource
1. Name a pilot group and write pass criteriaIT leadBefore consentGroup members, criteria, end dateEvery pilot mailbox is a direct memberPilot mailboxes sit in a nested group3
2. Grant one read permissionMicrosoft admin, or Google super administratorDay 1Role or scope grantedApplication Mail.Read with a resource scope, or gmail.readonlyMail.ReadWrite granted, or Mail.Read also held in Entra ID59
3. Prove the scopeMicrosoft adminDay 1, right after the grant; the test bypasses the 30 minute to 2 hour cacheInScope result per mailboxTrue for pilot mailboxes, false for a mailbox outside the groupTrue for any mailbox outside the group46
4. Run in monitoring modeVendor and IT leadDays 1 to 5Findings set against what your current tools caughtYou can compare each finding with what your current tools caughtFindings you cannot compare with what your current tools caught22
5. Watch the app's accessGoogle super administratorDailyOAuth log events for the app's client IDOnly the grant you approvedA grant or scope you did not approve12
6. Export the evidenceIT leadBefore day 7 on Entra ID FreeSign-in and audit logs, Google OAuth log events, findings listLogs saved before they expireLogs aged out before review1612
7. Decide, then revokeMicrosoft admin, or Google super administratorEnd dateGrant removed, re-consent blockedConsent revoked on the Entra Admin consent tab and dynamic consent stopped; delegation client deletedThe app still holds a grant after the end date131410

Copy this table into your PoC agreement and fill in the names and dates.

What compliance documentation should regulated industries keep from a PoC?

Keep four records: the written pass criteria, the scope test output, the exported sign-in and audit logs, and the revocation record. Entra ID keeps those logs for 30 days with P1 or P2 and seven days on the Free tier16. On Google Workspace, OAuth log events record the client ID for each grant and each revocation12. File all four with the PoC agreement on the end date.

How AegisAI handles this

AegisAI connects to Microsoft 365 or Google Workspace through the API, judges every message by its intent, and removes what fails from every mailbox it reached19. Nothing is removed until you grant write access. Run it beside your current stack for five days before you change anything.

Book a demoSee inbound email security

See your own records: Check your domain.

What does a five-day PoC run look like?

A five-day run goes in this order: grant and test the scope on day one, run in monitoring mode through day five, then export the logs, score the findings and revoke.

Illustrative example, figures are fictional: Harbor Row Dental (fictional) has 85 people on Microsoft 365 and one IT admin. Monday: the admin scopes Application Mail.Read to a 20-mailbox pilot group. The scope test then reads true for the office manager and false for the owner. Tuesday to Friday: the tool runs in monitoring mode. It flags 6 messages; the admin opens each one, and 4 were already in Junk. Friday: the admin exports the sign-in logs and scores the results against the written criteria. Then the admin revokes consent and stops dynamic consent.

In this fictional week, the scope test on day one is what made the rest countable. Write your own five-day schedule in the same order.

How to measure it in 30 days

Track three numbers, each from a place you can open.

  • Messages the PoC flagged that your current filters delivered, from the monitoring mode findings and the message in the pilot mailbox.
  • Pilot mailboxes that tested InScope true and others that tested false, from Test-ServicePrincipalAuthorization.
  • Grants still active after the end date, from the Entra Admin consent tab and Google OAuth log events.

AegisAI reports in its post Half of AI phishing reaches the inbox, last updated October 30, 2026, that, in its analysis of more than 20,000 phishing emails, AI-generated phishing got past Gmail and Microsoft tier-1 filters 50.3 percent of the time26. For catch rate and false positive math, use how to measure email security efficacy. To test on your own tenant, ask for a read-only trial run.

Questions people ask

How do I run a proof of concept for an email security platform?

Scope one read permission to a pilot group and write pass criteria with an end date. Connect a tenant in monitoring mode and compare what AegisAI finds with what your current tools caught. Run it beside your current stack for five days before you change anything. Revoke the grant on the end date.

How long should an email security proof of concept run?

Five days beside your current stack is the run length the platform page sets. Export sign-in and audit logs before they expire: seven days on Entra ID Free, 30 days with Entra ID P1 or P2.

Does an email security proof of concept change mail flow?

No. An API connection reads mail after delivery, with no MX record change. In monitoring mode, nothing is removed until you grant write access.

How do I end the PoC cleanly?

Revoke admin consent in the Microsoft Entra admin center and stop dynamic consent, or users can consent again. In Google Workspace, delete the domain-wide delegation client; apps that depend on it stop working at once.

How does an AegisAI proof of concept run?

AegisAI connects to Microsoft 365 or Google Workspace by API, with no MX change, and starts read-only. It gives one verdict per email, so you can review them on your own mail. Your admin grants access and can revoke it.

Sources

  1. RBAC for Applications in Exchange Online, Microsoft Learn
  2. Choose Gmail API scopes, Google for Developers
  3. Control API access with domain-wide delegation, Google Workspace Admin Help
  4. OAuth log events, Google Workspace Admin Help
  5. Review and manage permissions granted to applications, Microsoft Learn
  6. Microsoft Entra data retention, Microsoft Learn
  7. AegisAI platform
  8. AegisAI inbound email security
  9. Half of AI phishing reaches the inbox, AegisAI

Recent posts

Every email, investigated.