- What it does
- When to use it
- How to activate it
- How to use it
- Settings and controls
- Behind the scenes
- Limits
- If something goes wrong
What it does
General Settings › Integrations connects Threats to Microsoft Defender and your tools. On Microsoft 365, it links Microsoft Defender to send user-reported emails to Microsoft for analysis, and lets LibraCyber block senders in your Microsoft 365 tenant. On any email platform, it can call your system whenever a user reports an email and refers to the Public API that reads your threats.
Admins set this up once, with help from your Microsoft 365 admin for the Microsoft parts. End users never see it.
General Settings › Integrations on a Microsoft 365 company: the three tabs, with both Microsoft consents granted. ① API and Webhooks ② Microsoft Defender ③ Defender Block Senders · 2026-11
When to use it
- Block phishing senders in Microsoft 365, not just in the console. Enable Defender Block Senders: a Block policy set in Threats is written to your Microsoft Defender block list.
- Have Microsoft Defender analyze what users report and share your team's verdict with it. The Microsoft Defender tab is used to send user-reported emails to Microsoft, followed by any verdict you give in Threats. This is available on request: ask LibraCyber support if it can be enabled for your company.
- Open a ticket in your SOC, SIEM, or ticketing tool when a user reports an email. Set up a webhook: your system is called within seconds of a report, then reads the details via the Public API.
- Create your own reports on reported emails. Read your threats, their verdicts, and their AI analysis via the Public API.
Not for: deciding which senders are blocked or allowed: that's Threats › Sender policies. Choosing who receives the threat alert email: that's Threats › Setup. Granting Smart Banners access to Microsoft 365: see Setup › How do I check the access was granted?
How to activate it
Each integration is activated separately in General Settings › Integrations. Microsoft Defender and Defender Block Senders only appear for companies on Microsoft 365. API and Webhooks appears for every company.
Prerequisites
- In the console: an admin with both General Settings and Threats permissions (General Settings › Admins). Without Threats, the tabs show errors instead of settings.
- To send to Microsoft Defender: available on request. Ask LibraCyber support if it can be enabled for your company.
- For the two Microsoft consents: a Microsoft Global Administrator account to accept the permissions requested by LibraCyber.
- For Defender Block Senders: someone with the Microsoft 365 Global Administrator or Exchange Administrator role to run a PowerShell step in Azure Cloud Shell from the Azure portal. A computer with PowerShell 5.1 or later also works.
- For the webhook: an address on your side that accepts calls from the internet.
How do I send reported emails to Microsoft Defender?
Ask LibraCyber support if sending can be enabled for your company. Once enabled, grant consent in the Microsoft Defender tab: the Office Defender Submission switch will turn on automatically.
Until LibraCyber has enabled it for your company, the tab can be activated but no emails will be sent to Microsoft.
- Ask LibraCyber support if sending can be enabled for your company and wait for their confirmation.
- Open General Settings and select the Integrations tab. → The Microsoft Defender tab says Allow LibraCyber to submit threats to Microsoft Defender. and shows Not granted yet.
- Select Grant Threat Submission to Microsoft Defender Consent to LibraCyber. → Warning: Granting Consent opens: You must use a Microsoft Global admin account to grant consent to LibraCyber.
- Select Grant Consent, sign in with a Microsoft Global admin account, and accept the permissions. → A new tab says Consent successfully granted. You can close this window.
- Close that tab and reload the Integrations tab. → The tab shows Already granted and Office Defender Submission is enabled.
The Microsoft Defender tab after consent: Already granted, sending enabled. ① Already granted ② the switch · 2026-11
If you manage the company from a partner or group account, the window won't have the Grant Consent button: select Copy link and send the link to the company's Microsoft Global admin.
How to turn it off: turn off Office Defender Submission. New reports will no longer be sent and verdicts will no longer be shared with Microsoft. Emails already sent remain in Microsoft Defender. You can turn it back on at any time. Consent remains granted: to revoke it, remove the Threats Submission app from Enterprise applications in the Microsoft Entra admin center. After that, the console will still show Already granted.
LibraCyber's submission app in the Microsoft Entra admin center: Enterprise applications › Threats Submission › Permissions. ① the app to remove ② its only permission, threat submissions · 2026-04
How do I let LibraCyber block senders in Microsoft Defender?
Four steps in the Defender Block Senders tab: grant consent, have your IT run the PowerShell module, enable Automatic Sender Blocking, and wait for the tab to confirm permissions. From then on, every Block policy in Threats is written to your Microsoft Defender Tenant Allow/Block List.
- In General Settings › Integrations, select Grant Defender Block Senders Consent to LibraCyber, then Grant Consent, and accept the permissions with a Microsoft Global admin account. → The new tab says Consent successfully granted. You can close this window.
- Reload the Integrations tab. → The tab shows Already granted, the PowerShell instructions, and the Automatic Sender Blocking switch, which is off.
- In the Azure portal, open Enterprise applications, search for Mantra Block Threats, and open Mantra Block Threats (production), LibraCyber's sender blocking app. Copy its Object ID. The ScribeHow Documentation link in the tab shows these steps with images.
- Paste it into Application Object ID. → The command in the gray box now includes it. LibraCyber's App ID and your tenant are already filled in.
The Defender Block Senders tab configured: Application Object ID filled in, both commands, blocking enabled and permissions verified. ① Application Object ID ② the commands to run ③ the switch · 2026-11
- Your Microsoft 365 admin logs into the Azure portal and opens Cloud Shell in PowerShell. Paste the first line from the gray box, which installs the MantraBlockSenders module. Then paste the rest, starting with Connect-MantraBlockSenders, and sign in with the same admin when Microsoft prompts. → PowerShell runs five steps, from [1/5] Checking Exchange module... to [5/5] Assigning permissions....
PowerShell in Azure Cloud Shell running the module: Mantra Threats Block - Configuration, steps 1 to 5. ① the five steps · 2026-10
- To check the connection, type Test-MantraBlockSendersConnection. → It shows Exchange Online connection: OK. This checks the admin's own connection to Exchange Online; the tab itself confirms that LibraCyber can block (next step).
- Back in the tab, turn on Automatic Sender Blocking. → You'll see Automatic sender blocking enabled and the text below the switch says Senders and domains can be blocked in Defender directly from the console. The tab then shows Starting the verification of your Microsoft 365 tenant...
- Wait for verification. → The tab shows Verifying the permissions in your Microsoft 365 tenant. This can take up to 2 hours after running the PowerShell module., then Permissions verified: blocked senders are synchronized with Microsoft Defender. You can leave the page in the meantime.
If the tab shows LibraCyber cannot manage blocked senders in your tenant, the PowerShell step is missing or incomplete: run it again (step 5), then turn Automatic Sender Blocking off and on again to retry the check.
If the command shows yourtenant.onmicrosoft.com, replace it with your tenant's onmicrosoft.com domain or its ID: the module won't accept anything else.
Blocks set before Permissions verified appears are kept and sent once permissions are verified. If verification fails, LibraCyber checks again about once a day: to check immediately, turn Automatic Sender Blocking off and on again.
What the PowerShell step grants. It registers LibraCyber's sender blocking app in Exchange Online and assigns it a single role, Tenant AllowBlockList Manager, in a role group created for it. That role only manages the Tenant Allow/Block List: LibraCyber can't read or modify mailboxes with it.
How to turn it off: turn off Automatic Sender Blocking. Blocks and unblocks made in Threats will no longer reach Microsoft Defender and the hourly check stops. Senders already blocked remain in Microsoft Defender: remove them there if you want to delete them. To also revoke permissions, delete Mantra Block Threats (production) in the Azure portal under Enterprise applications: this removes all LibraCyber permissions. The role group created by the module remains in the Exchange admin center, unused: you can remove it from there too.
How do I set up a webhook?
Enter your address in Webhook URL in the API and Webhooks tab: it's saved automatically for the Threat reported event.
- In General Settings › Integrations, find the Webhooks section of the API and Webhooks tab.
- Enter your endpoint address in Webhook URL, for example
https://soc.example.com/threats-hook. → A second after you stop typing, Webhook saved appears.The API and Webhooks tab with a webhook address saved, Threat reported event, and the Webhook saved message. ① Public API ② Webhook URL ③ Events · 2026-11
- Leave Events set to Threat reported, the only event.
The address must start with http:// or https:// and point to a public server. Local and private addresses are rejected, with the reason shown in the message. Each company has only one webhook address.
How to turn it off: clear the Webhook URL. → Webhook saved appears and calls stop.
How to use it
General Settings › Integrations. Once set up, integrations work automatically: this section explains what each one sends and how to check it.
What does Microsoft Defender receive and what happens to its verdict?
Microsoft Defender receives every email sent as possible phishing, then the verdict you give in Threats. Microsoft's verdict is not shown in the console.
- What gets sent: the entire reported email, for the mailbox of the user who reported it, a few seconds after it's reported. Sending does not block or remove anything from the mailbox.
- What does not get sent: Smart Banner alerts, the same reported email again from the same mailbox, and phishing simulation emails.
- Your outcome: when an admin resolves a submitted email in Threats › Threats, Microsoft is notified: Safe as not spam, Spam as junk, Suspicious and Unsafe as phishing. Changing the outcome later sends the new one.
- Microsoft's outcome: LibraCyber collects it, but does not display it in the console, exports, or the Public API.
How do I check that blocking reaches Microsoft Defender?
Search for the sender in your Tenant Allow/Block List: in the Microsoft Defender portal, open Policies & rules › Threat policies › Tenant Allow/Block Lists, then go to the Domains & addresses tab.
- Every sender or domain blocked by Threats is listed as a block, with no expiration date and a note added by LibraCyber.
- Unblocking in Threats removes the entry.
- Microsoft Defender remains the source of truth: about once an hour, LibraCyber reads this list and updates Threats › Sender policies, including senders blocked directly in Microsoft Defender. What a block does and how this check changes things in the console is described in Sender policies › What does Block do in Microsoft 365?
What does the webhook send?
A call every time a user reports a new email to Threats. The call says a threat was reported and where to find it, but never what the email contains.
- The call: an HTTP POST with a small JSON body, sent a few seconds after the report.
- What it contains: the threat ID, the date and time of the report, a link to the threat in the console, and the event, threat reported.
- What it never contains: the sender, recipient, subject, content, or attachments. Read these through the Public API, using the threat ID.
- When it's sent: for every new report, no matter the channel (forwarding, Microsoft Report button, LibraCyber add-in, Report email in a banner). Not for banner alerts, not for the same email reported again from the same mailbox, and not for phishing simulation emails. Two users reporting the same email generate two calls.
- Your response: respond within 10 seconds with a success code (2xx). Otherwise, the call is retried once immediately, then dropped: it will not be sent again later.
- The link: opens the threat in a previous view of the Threats list, not in Threats › Threats. To work on the threat, open Threats › Threats and paste the ID into the Threat ID filter.
How do I secure the webhook?
The call contains no password, token, or signature, which is why it contains nothing sensitive: treat it only as a signal. To verify a threat is real, read it through the Public API with your credentials: a threat the API does not return was not reported in your company.
- Use an
https://address so the call is encrypted. - Your endpoint only needs to accept the call and read the ID.
Can I read threats through an API?
Yes, through the Public API, read-only. It returns threats for your company, their outcomes, and their AI analysis; it cannot change an outcome, delete a threat, or create one.
- What you can read: the list of threats, whether still awaiting an outcome or already resolved. For each threat: headers, body, list of attachments, SPF, DKIM, and DMARC results, the original email, and AI analysis when available.
- How the list works: most recent report first, up to 100 threats per page. There is no date filter: scroll through pages until you reach a threat you've already seen. Read both lists, pending and resolved, to see everything.
- Credentials: not created in the console. Ask LibraCyber support for API credentials for your company: they only give access to your company's threats.
- Documentation: the Public API link in the API and Webhooks tab.
Can I send every report to my SIEM or SOC?
Yes, using the webhook and Public API together: the webhook tells your system a threat was reported, and the API provides the details. There is no built-in connector for a specific SIEM. Another option is the threat alert email, sent to your security team for every report: see Threats › Setup.
Settings and controls
Each setting applies to the whole company and can be changed by an admin with General Settings and Threats permissions.
| Setting / control | Default | Effect | Who can change it |
|---|---|---|---|
| Grant Threat Submission to Microsoft Defender Consent to LibraCyber (Microsoft 365) | Not granted yet | Gives LibraCyber's submission app access to your tenant and enables Office Defender Submission. | Admin, with a Microsoft Global admin account |
| Office Defender Submission | On once consent is granted | On: sends new reports to Microsoft Defender, followed by your outcomes, once LibraCyber has enabled sending for your company. Off: nothing is sent to Microsoft. | Admin |
| Activation of sending to Microsoft Defender | Not activated | Allows Office Defender Submission to send emails to Microsoft. Not activated: nothing is sent, even if the switch is on. | LibraCyber support, on request |
| Grant Defender Block Senders Consent to LibraCyber (Microsoft 365) | Not granted yet | Gives LibraCyber's sender blocking app access to your tenant and shows the PowerShell step and the Automatic Sender Blocking switch. | Admin, with a Microsoft Global admin account |
| Application Object ID | Empty | Fills in the PowerShell command. Not saved: re-enter if you reload the page. | Admin |
| Automatic Sender Blocking | Off | On: LibraCyber checks its permissions in your tenant and shows the result below the switch; then Block policies are written to your Microsoft Defender Tenant Allow/Block List and Microsoft Defender is checked every hour. Off: nothing is sent to Microsoft Defender. | Admin |
| Webhook URL | Empty | The address called for every new reported threat. Empty: no calls. | Admin |
| Events | Threat reported | The event that triggers the webhook. It's the only one. | Admin |
| Public API credentials | None | Provide read-only access to your company's threats via the Public API. | LibraCyber support, on request |
Behind the scenes
Every integration starts from a report or an outcome, never from a schedule you set.
- A user reports an email → the webhook is called within seconds; on Microsoft 365, sending to Microsoft Defender also starts from the report, once enabled for your company.
- An admin gives an outcome → it's sent to Microsoft Defender, if that email was submitted.
- An admin blocks or unblocks a sender → the change is sent to your Tenant Allow/Block List in the background, as soon as it's saved.
- Every hour → LibraCyber reads your Tenant Allow/Block List and updates Threats › Sender policies.
Data updates: consent status is read when you open the tab. After granting consent, reload the tab to see Already granted.
Microsoft 365 and Google Workspace: on Google Workspace, only the API and Webhooks tab is shown. Reported emails are not sent anywhere and Block is not available in Sender policies; Allow works through Smart Banners.
Limits
- Microsoft Defender and Defender Block Senders only work on Microsoft 365 (as of 11/03/2026).
- Sending to Microsoft Defender only works after LibraCyber has enabled it for your company (as of 11/03/2026).
- The Microsoft Defender outcome for a submitted email is not shown in the console, exports, or the Public API (as of 11/03/2026).
- Banner alerts are not sent to Microsoft Defender or the webhook (as of 11/03/2026).
- Only one webhook address per company and only one event, Threat reported. There is no event when a threat is resolved (as of 11/03/2026).
- A webhook call that fails twice is not sent again and the console does not show failed calls (as of 11/03/2026).
- The Public API is read-only, with no date filter. API credentials are not managed in the console (as of 11/03/2026).
- Removing consent in Microsoft Entra is not shown in the console: it continues to show Already granted (as of 11/03/2026).
If something doesn't work
| Symptom | Likely Cause | What You Can Do | When to Contact Support |
|---|---|---|---|
| The Microsoft Defender and Defender Block Senders tabs are missing | Your company is not set up on Microsoft 365: these tabs are only available for Microsoft 365. | Check in LibraCyber which email platform your company uses. | If your company is on Microsoft 365 and the tabs are still missing. |
| The tabs show An error occurred or Failed to load… | Your admin account does not have the Threats permission. | Ask an administrator to assign you the Threats permission. | If the errors persist even with both permissions. |
| The tab still shows Not granted yet after giving consent | The status is checked when the tab opens. | Reload the Integrations tab. | If it still says Not granted yet after a successful consent page. |
| The consent window does not have the Grant Consent button | You manage this company from a partner or group account. | Select Copy link and send it to the company's Global admin. | — |
| The consent page says The Administrator consent has failed | The account is not a Microsoft Global admin, permissions were denied, or the link has expired. | Start again from the tab using a Microsoft Global admin account. | If it fails with a Global admin account. |
| Reported emails never reach Microsoft Defender even though the switch is on | Sending has not been enabled for your company. | Ask LibraCyber support if it can be enabled for your company. | If it has been enabled and emails still do not reach Microsoft Defender. |
| The tab says LibraCyber cannot manage blocked senders in your tenant | The PowerShell step was not run, failed, or the wrong Object ID or tenant was used. | Run the PowerShell step again, then turn Automatic Sender Blocking off and on. | If the message returns after a successful PowerShell step: send the error code shown to support. |
| The PowerShell step fails with an access or permissions error | The account used is not a Global Administrator or Exchange Administrator. | Run it again, signing in as a Global Administrator or Exchange Administrator. | If it fails with one of these roles: send the error text to support. |
| The PowerShell step says You are signed in to another tenant | The administrator is signed in to a Microsoft 365 tenant different from the one specified in the command. | Run the command again and sign in with an admin account for your tenant. | — |
| The PowerShell step says The Object ID belongs to another application | The Object ID entered in the tab is not for Mantra Block Threats (production). | Copy the Object ID for Mantra Block Threats (production) from Enterprise applications, paste it into the tab, then run the command again. | — |
| The PowerShell step says the existing role group does not have the 'Tenant AllowBlockList Manager' role | Your Exchange Online already has a role group with the same name, but without that role. | Add the role to that role group, or delete it, then run the command again. | — |
| The PowerShell step rejects the organization | The command still contains yourtenant.onmicrosoft.com. | Replace it with your onmicrosoft.com domain or the tenant ID. | — |
| Blocks set in Threats never appear in the Microsoft Defender Tenant Allow/Block List | Permissions have not yet been verified: the tab does not show Permissions verified. | Wait for Permissions verified, up to 2 hours. If the tab shows an error, run the PowerShell step, then turn Automatic Sender Blocking off and on. | If blocks are still missing an hour after Permissions verified. |
| Saving the webhook shows an error | The address is not http or https, or it points to a local or private server. | Use a public address that starts with https://. |
— |
| Webhook calls are not received | Your endpoint did not respond with a success code within 10 seconds, twice. | Make sure your endpoint responds within 10 seconds with a 2xx code. | If your endpoint was active: send support the time of the report and the address. |
| Some reported emails do not trigger any webhook call | They are banner alerts, simulation emails, or emails already reported from the same mailbox or already marked there by a banner alert. | No action needed: only new user reports trigger the webhook. | If a new user report did not trigger any call. |
| The link in a webhook call opens a previous version of the Threats list | The link points to the previous Threats list. | Paste the identifier into the Threat ID filter in Threats › Threats. | — |
| The Microsoft Defender result for a reported email is not shown anywhere in the console | The console does not display it. | No action needed: LibraCyber does not show Microsoft's result. | — |