AegisAI Perspectives · 149
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.
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.

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.
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.
| Question | Answer | Source |
|---|---|---|
| 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.
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.
Before anyone grants consent, write five items into the PoC agreement:
The pilot group, with each pilot mailbox as a direct member.
The pass criteria: what a finding must show to count.
The run length: five days beside your current stack.
The evidence to keep, exported before Entra ID Free drops sign-in and audit logs at seven days.
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.
| Step | Owner | Time | What to measure | Pass sign | Fail sign | Source |
|---|---|---|---|---|---|---|
| 1. Name a pilot group and write pass criteria | IT lead | Before consent | Group members, criteria, end date | Every pilot mailbox is a direct member | Pilot mailboxes sit in a nested group | 3 |
| 2. Grant one read permission | Microsoft admin, or Google super administrator | Day 1 | Role or scope granted | Application Mail.Read with a resource scope, or gmail.readonly | Mail.ReadWrite granted, or Mail.Read also held in Entra ID | 59 |
| 3. Prove the scope | Microsoft admin | Day 1, right after the grant; the test bypasses the 30 minute to 2 hour cache | InScope result per mailbox | True for pilot mailboxes, false for a mailbox outside the group | True for any mailbox outside the group | 46 |
| 4. Run in monitoring mode | Vendor and IT lead | Days 1 to 5 | Findings set against what your current tools caught | You can compare each finding with what your current tools caught | Findings you cannot compare with what your current tools caught | 22 |
| 5. Watch the app's access | Google super administrator | Daily | OAuth log events for the app's client ID | Only the grant you approved | A grant or scope you did not approve | 12 |
| 6. Export the evidence | IT lead | Before day 7 on Entra ID Free | Sign-in and audit logs, Google OAuth log events, findings list | Logs saved before they expire | Logs aged out before review | 1612 |
| 7. Decide, then revoke | Microsoft admin, or Google super administrator | End date | Grant removed, re-consent blocked | Consent revoked on the Entra Admin consent tab and dynamic consent stopped; delegation client deleted | The app still holds a grant after the end date | 131410 |
Copy this table into your PoC agreement and fill in the names and dates.
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.
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.
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.
Track three numbers, each from a place you can open.
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.
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.
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.
No. An API connection reads mail after delivery, with no MX record change. In monitoring mode, nothing is removed until you grant write access.
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.
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.