Microsoft Direct Delivery permissions
What the mail permission on Microsoft's consent screen allows, what Hook actually does in your mailboxes, and what it never touches, including the email already in them.
Microsoft writes the text on its consent screen, and it's the same for every app that asks for the same permission. That text describes the most the permission could allow. It doesn't describe what Hook does with it. This page covers what Hook does in your mailboxes, when it does it, and what it never does.
To set up Microsoft Direct Delivery itself, see Set up Microsoft Direct Delivery.
The short version
- Hook places phishing simulations in the inboxes of the people in a campaign's audience. Nobody else's mailbox receives anything.
- Hook never opens, reads, or searches your email. The only mail it ever looks for is a simulation it placed itself.
- Hook never sends email as your people, and it never moves, changes, or deletes anything already in a mailbox.
- You can limit Hook to a group of mailboxes in Exchange Online.
What the permission is for
Microsoft Direct Delivery uses its own Hook app, separate from directory sync, and asks for one permission: Read and write mail in all mailboxes. Microsoft may also list Sign in and read user profile, which lets the admin granting consent sign in to approve the request. When you approve, Microsoft only tells Hook your tenant ID and that consent was granted.
Hook uses the mail permission for three things, and nothing else:
| What Hook does | When | What it touches |
|---|---|---|
| Places a simulation in a person's inbox | When a campaign delivers to that person | One new, unread message in that person's inbox |
| Checks whether it already placed a simulation | Before retrying a delivery that may have gone through | A search for its own message by a hidden marker it added. Microsoft returns only the message ID. |
| Checks that it can reach a mailbox | When you click Check access during setup, and when a delivery is refused | The ID of the inbox folder in the mailbox you entered. No messages. |
What Hook can't do
The permission doesn't cover any of the following, so Hook has no way to do them:
- Send email as your people. That needs a separate permission, which Hook doesn't request. A simulation is placed directly in the inbox, so it never appears in anyone's sent mail.
- Read OneDrive or SharePoint files, Teams chats, or calendars
- Read your directory, passwords, or sign-in logs
- Change mailbox settings, rules, or forwarding
What Hook doesn't do, even though it could
Microsoft's mail permission covers every message in every mailbox, and Microsoft doesn't offer a narrower version for adding messages only. Hook limits what it does on its own side.
Does Hook read our email?
No. Hook never opens a message, reads message content, or lists what's in a mailbox. The one search it runs looks for a simulation Hook placed itself, using a hidden marker on that message, and it asks Microsoft for that message's ID and nothing else.
Does Hook delete or move mail?
No. Hook never deletes, moves, or edits any message, including its own simulations after delivery. What a person does with a simulation stays in their mailbox.
Which mailboxes does Hook put simulations in?
Only those of the people in a campaign's audience. Hook doesn't touch any other mailbox, apart from the inbox check described above. Test emails you send from a template don't go through Microsoft Direct Delivery.
How does Hook know if someone clicks or reports a simulation?
From the simulation itself, not from your mailbox. Links in a simulation record a click when someone opens them, and the Hook Report button tells Hook when someone reports one. Hook doesn't read the mailbox to find out.
Can we limit Hook to certain mailboxes?
Yes. Exchange Online lets you restrict an app to a group of mailboxes, with RBAC for Applications or an application access policy. Keep these in mind:
- The mailbox you entered under Mailbox to check must stay in scope. Hook uses it to tell a single blocked mailbox apart from a connection that stopped working. If it falls out of scope, Hook treats the connection as lost and stops delivering.
- Simulations to people outside the scope fail for those people only. The rest of the campaign still delivers.
- Exchange can take up to a couple of hours to apply a scope change to every mailbox.
Does this permission let Hook sync our directory?
No. Directory sync is a separate Hook app with its own consent and its own read-only directory permissions. Microsoft Direct Delivery can't read your users or groups.
How do we revoke Hook's access?
Disconnecting in Hook stops deliveries, but your consent stays in place in Microsoft. To remove Hook's mailbox access entirely, go to Enterprise applications in the Microsoft Entra admin center, find Hook's direct delivery app, and delete it or remove its permissions. Hook then can't reach any mailbox. See Disconnect and revoke access.