- Quick checks
- The report button
- Reports that don't reach Threats
- Emails users receive
- Notifications to administrators
- Reviewing and resolving threats
- AI analysis and settings
- Blocking and allowing senders
- Microsoft Defender integration
- Webhook
- The Dashboard
- Threats is slow or unavailable
- What to send to support
Start with the quick checks—they solve most problems. If those aren't enough, find your situation below. Each table shows the likely cause and the first thing to do, along with the page and section containing the full solution.
Quick checks
Do these five checks before anything else—they solve most Threats issues.
- The user's address is registered in your company's LibraCyber account, under General Settings › User management. Reports from any other address, like a personal mailbox or an alias, are ignored without any message.
-
The user reported the right way. With the Microsoft button, Report phishing, not Report junk. With forwarding, a regular forward to
report@app.mantra.ms, not as an attachment. Each method, mail app by mail app: Reporting a suspicious email › Which reporting method works in my mail app? - You refreshed the list and checked Archived. Threats › Threats doesn't update automatically, and a sender policy with auto-resolve moves a report straight to Archived.
- The email wasn't a phishing simulation, and it's smaller than about 7.5 MB. A reported simulation counts for the simulation and never appears in Threats; emails larger than this can't be reported.
- Your admin role has the Threats permission, granted in General Settings › Admins. Without it, integration tabs show errors and Threats settings can't be opened.
For one-line answers to the most common customer questions, see Quick answers.
The report button
Most often, the add-in hasn't reached the user yet, the user's Outlook is too old, or the add-in can't sign the user in. Forwarding to report@app.mantra.ms always works in the meantime.
| Symptom | Why | What to do |
|---|---|---|
| The Report phishing to LibraCyber button isn't in Outlook | The add-in hasn't reached this user yet, the user is outside the deployment, or no received email is open. | Forward the email to report@app.mantra.ms, then check the deployment → The report button is missing in Outlook: what should I check?, below |
| The add-in opens a new email instead of reporting | The add-in couldn't sign the user in, read the email, or reach LibraCyber, or the user's address isn't registered. In a shared mailbox, the causes are the same. | Select Send in the new email opened by the add-in → Reporting a suspicious email › If something goes wrong |
| The add-in says The report button is currently unavailable. | The add-in couldn't report or open a new email. | Forward the email to report@app.mantra.ms → Reporting a suspicious email › If something goes wrong |
| The add-in says Outlook version not supported | This Outlook is too old for the add-in, like some Outlook 2016 and 2019 installations. | Select Forward this email, or use Outlook on the web → Reporting a suspicious email › If something goes wrong |
| The add-in says The message is too big to be reported. | The email is larger than the size limit. | Let your IT department know about the email another way → Reporting a suspicious email › If something goes wrong |
| The add-in panel keeps spinning, stays on Loading... or stays blank | The add-in can't reach LibraCyber from this computer or network, or Outlook is still signing the user in. | Meanwhile, forward the email to report@app.mantra.ms → Reporting a suspicious email › If something goes wrong |
| Integrated apps rejects the add-in because it's already deployed | The add-in, maybe under a previous name, is already deployed in your tenant. | Open the deployed add-in in Integrated apps and update it → Setup › Troubleshooting setup issues |
| The Microsoft 365 admin center shows another error during add-in deployment | Microsoft rejected the deployment for a reason not listed on this page. | Take a screenshot of the error, then contact LibraCyber support → What to send to support, below |
| Users still see an old name or icon on the report button | The add-in was deployed before May 2026 and has never been updated. | Update the add-in in Integrated apps with the current link → Setup › Troubleshooting setup issues |
| Users see two report buttons in Outlook | Both the add-in and Microsoft's Report button are shown. | Select Use a non-Microsoft add-in button in User reported settings → Setup › Troubleshooting setup issues |
| Microsoft rejects the report mailbox | It's a distribution list, which Microsoft no longer accepts. | Use a shared mailbox as the report mailbox → Setup › Troubleshooting setup issues |
The report button is missing in Outlook: what should I check?
Forward the email to report@app.mantra.ms, then check the deployment. Forwarding works from any mail app while you look for the cause.
- Make sure a received email is open or selected. The button doesn't appear in drafts or emails being composed.
- Check the mail app. The add-in works in classic Outlook for Windows (recent Microsoft 365 versions), the new Outlook, Outlook for Mac, Outlook on the web, and Outlook for iPhone and Android, with a Microsoft 365 mailbox. Outlook that's too old, like some Outlook 2016 and 2019 installations, shows Outlook version not supported and suggests forwarding the email. In Gmail, users report with the LibraCyber add-on for Gmail, if your company has installed it. Other mail apps don't have a LibraCyber button: users forward the email, or use Report email in a Smart Banners banner.
- Look in the right place. In Outlook for Windows and Mac, the button is in the ribbon, under the Report Phishing group. In the new Outlook and Outlook on the web, it may be under Apps or …. On a phone, it's in the email's … menu.
- Check the deployment. After deployment, the add-in can take up to 72 hours to appear in Outlook: wait, then restart Outlook. Make sure the user is included in the add-in assignment in Integrated apps. For solutions to any deployment issue: Setup › Troubleshooting setup issues.
- If the button is deployed to the user and still missing after three days, or if it's there but disabled or unresponsive, contact support with the info in What to send to support, below. Include the Outlook app and its version.
Reports that don't reach Threats
Most often, the user's address isn't registered, the email was reported with Report junk, it was a phishing simulation, or the list wasn't refreshed. Reports from unregistered addresses are ignored without any message.
| Symptom | Why | What to do |
|---|---|---|
| No reported emails reach Threats for any user | The reporting addresses aren't registered, the tests were phishing simulations, or Threats is disabled for your company. | Forward a harmless email to report@app.mantra.ms from your address → No reported email reaches Threats: what should I check?, below |
| A user reported an email, but it's not in Threats | The user's address isn't registered, Report junk by Microsoft was used, the email is too large, or it was a phishing simulation. | Check that the user's address is registered in your LibraCyber account → Reporting a suspicious email › If something goes wrong |
| An email reported by a user isn't in User Reports | The list wasn't refreshed, or a sender policy with auto-resolve already resolved it and moved it to Archived. | Refresh the page, then check Archived → Threats list › If something goes wrong |
| A user reported with Microsoft's Report junk and nothing reached the security team | Junk mail reports aren't sent to LibraCyber. | Forward it from the Junk folder to report@app.mantra.ms → Reporting a suspicious email › If something goes wrong |
| A test report isn't in Threats, no matter how it's sent | The reporting address isn't registered, the test email was a phishing simulation, or Threats is disabled for your company. | Check the reporting address in General Settings › User management → Setup › Troubleshooting setup issues |
| A forwarded email isn't in Threats | The forward came from an unregistered address, like a shared mailbox or alias, or it was blocked on the way out. | Forward it again from the user's registered address → Setup › Troubleshooting setup issues |
| Reports with Microsoft's Report button reach the report mailbox but not Threats | The mailbox isn't forwarding to report-hook@app.mantra.ms: wrong address, automatic forwarding blocked by outbound anti-spam policy, or a data loss prevention rule. |
Check that the forwarding address is report-hook@app.mantra.ms → Setup › Troubleshooting setup issues
|
No reported email reaches Threats: what should I check?
Forward a harmless email to report@app.mantra.ms from your address, then run the checks below. Use a regular email from outside your company, never a phishing simulation: a reported simulation counts for the simulation and doesn't go to Threats.
- Refresh Threats › Threats and check User Reports, then Archived.
- Check that your address, and the addresses your users report from, are registered in General Settings › User management. Reports from unregistered addresses are ignored without any message.
- If one reporting method works and another doesn't, find that method in The report button above, or in this table.
- If your address is registered and nothing arrives after a few minutes, contact support with the info in What to send to support, below. Threats may be disabled for your company: only LibraCyber, or your partner if you have one managing your LibraCyber account, can reactivate it.
Emails users receive
Users receive a confirmation email only after forwarding or using the Microsoft button, and only while User feedback is enabled; the add-in, Gmail add-on, and banner display confirmation on screen. Reporting the same email twice in the same way results in only one report in Threats; reporting it in two different ways may result in two reports. An outcome email may also reach a user who didn't report anything, when a banner alert is resolved by an admin or through auto-resolve.
| Symptom | Why | What to do |
|---|---|---|
| Users don't receive any confirmation email after reporting | User feedback is disabled, the user reported using the add-in or a banner, or the email was a phishing simulation. | Check that User feedback is enabled in Threats › Setup → AI Analysis and Notifications › If something goes wrong |
| User feedback turned itself off after I changed another setting | A known issue: the first saved change on this screen can also disable User feedback. | Re-enable User feedback → AI Analysis and Notifications › If something goes wrong |
| A user received two confirmation emails for a single email | The email was reported twice, or through two different channels. | No action needed: each report is confirmed → Report a Suspicious Email › If something goes wrong |
| Users receive an outcome email for an email they never reported | An admin resolved a banner alert: its recipient gets the outcome, and this email can't be disabled (as of 11/03/2026). | Explain to the user that it's related to a warning banner they received → Threat List › If something goes wrong |
| After enabling auto-resolve, users get outcome emails for emails they never reported | Auto-resolve also resolves banner alerts from that sender: each mailbox owner receives the outcome. | Disable auto-resolve for that sender or domain → Sender Policies › If something goes wrong |
Notifications to Administrators
Every admin in your company receives the New threat alert, once for each new threat, unless they've clicked Unsubscribe from Threat alerts. Only LibraCyber support can add, remove, or restore a recipient.
| Symptom | Why | What to do |
|---|---|---|
| An admin doesn't receive the New threat alert | They clicked Unsubscribe from Threat alerts, are not an admin, or the threat was a banner alert or a repeated report. | Ask LibraCyber support to restore alerts for this admin → AI Analysis and Notifications › If something goes wrong |
| Admins who don't manage threats receive the New threat alert | Every admin receives alerts, regardless of their permissions. | Ask each one to click Unsubscribe from Threat alerts → AI Analysis and Notifications › If something goes wrong |
| No admin receives the New threat alert anymore | Your mail system rejected our alerts, so LibraCyber stopped sending to those addresses; or Threats is disabled for your company. | Allow no-reply@notify.libracyber.com in your mail security, then contact LibraCyber support → AI Analysis and Notifications › If something goes wrong |
| An alert arrived, but the threat isn't in Threats › Threats | The list wasn't refreshed, a sender policy already resolved the threat and moved it to Archived, or the console is showing another of your companies. | Refresh Threats › Threats, then check Archived → AI Analysis and Notifications › If something goes wrong |
| The alert button opens an empty list | The threat was already resolved and is in Archived, or the console is showing another of your companies. | Open the Archived tab: the threat ID remains in the filter → AI Analysis and Notifications › If something goes wrong |
| The alert doesn't show the sender or subject | Show threat details in the alert is disabled. | Enable Show threat details in the alert in Threats › Setup → AI Analysis and Notifications › If something goes wrong |
| The alert doesn't have the .eml attachment | The option is disabled, the reported email was too large to attach in time, or your mail security removed it. | Enable Include the threat as .eml attachment in threat alert notifications → AI Analysis and Notifications › If something goes wrong |
| Our mail security blocks or quarantines the alert | The attached .eml is the actual phishing email. | Allow no-reply@notify.libracyber.com, or disable the .eml attachment option → AI Analysis and Notifications › If something goes wrong |
| Our mail rule doesn't catch every alert | The subject line is translated into each recipient's language. | Filter by sender no-reply@notify.libracyber.com instead of by subject → AI Analysis and Notifications › If something goes wrong |
Reviewing and Resolving Threats
Most issues here are caused by a missing requirement to block or allow, or by a sender rule that couldn't be saved. Hover over a disabled option to see why. When a sender already has a Block or Allow policy, check the box again before clicking Resolve: if left unchecked, Resolve will revert that policy to Monitoring.
| Symptom | Why | What to do |
|---|---|---|
| The Banner alerts tab says Banner logging is off | Log banner emails in Threats is disabled in Smart Banners. | Enable Log banner emails in Threats in Smart Banners › Setup → Threat List › If something goes wrong |
| Block future emails or Deactivate banners on future emails is disabled | A requirement is missing: Microsoft Defender consent for blocking, Smart Banners for allowing. Blocking isn't available on Google Workspace. | Hover over the box and fix the reason shown → Threat List › If something goes wrong |
| The message Failed to resolve threat appears | The sender rule wasn't saved, so the threat wasn't resolved. | Wait a minute, then click Resolve again → Threat List › If something goes wrong |
| Emails from a blocked sender come through again, or an allowed sender gets banners again, after I resolved a threat from them | Resolve was clicked with Block future emails or Deactivate banners on future emails unchecked, so the sender's policy reverted to Monitoring. | Block or allow the sender again in Threats › Sender policies → Threat List › If something goes wrong |
| No policy was created when resolving a threat | The sender doesn't have a valid email address, only a display name. | No action needed: the threat is resolved → Sender Policies › If something goes wrong |
| I resolved several threats but only one sender was blocked | The sender rule is created only for the sender of the first selected threat. | Resolve threats from other senders separately, one sender at a time → Threat List › If something goes wrong |
| Images are missing in the email | Images are hidden by default. | Enable Display images above the email → Threat List › If something goes wrong |
| SPF, DKIM, or DMARC shows Error or Unknown for a legitimate email | A gateway or forwarding service between the sender and your mailbox changed the authentication results, or the email doesn't include them. | Check the authentication headers in the Headers tab → Threat List › If something goes wrong |
| CSV export is empty | The current tab and filters don't show any threats, or the list hadn't finished loading. The file will then be empty, without even column names. | Make sure the tab and filters show threats, then export again → Threat List › If something goes wrong |
| Export to CSV ends with An error occurred | Some part of the list couldn't be read, so no file was produced. | Wait a minute, then export again → Threat List › If something goes wrong |
| The list is empty after I resolved or deleted threats | You were on a later page: when its threats leave the tab, the list stays on that page, now empty. | Go back to the first page, or refresh the page → Threat List › If something goes wrong |
| I deleted a threat by mistake | Deletion is permanent. | Ask the user to report the email again → Threat List › If something goes wrong |
| Export to CSV finishes but no file is downloaded | The file is saved only after reading every page of the list, so the browser may treat it as an automatic download and block it or ask for confirmation. Closing or refreshing the tab during export will lose the file. | Allow downloads from the console in your browser, then export again → Threat List › If something goes wrong |
| Emails sent by LibraCyber appear in Threats, like a New threat alert, an outcome email, or a confirmation | A user reported them. Threats only excludes phishing simulations, regardless of sender: any other reported email becomes a threat. | Delete them in Threats › Threats, and explain to users what they are → Threat List › If something goes wrong |
AI Analysis and Settings
AI analysis is performed only once, when the email is reported, if AI Smart Analysis is enabled at that time, in the language selected then. Banner alerts are not analyzed.
| Symptom | Why | What to do |
|---|---|---|
| The AI Analysis tab is missing | AI Smart Analysis was disabled when the email was reported, or the threat is a banner alert, including an email reported after a banner alert flagged it in that mailbox. | Check that AI Smart Analysis is enabled in Threats › Setup → Threat List › If something goes wrong |
| The AI label says Safe for a phishing email | The AI analysis is a suggestion and can make mistakes. When the sender doesn't have a tag, the label dropdown preselects the AI label. | Select the correct Label in Threat resolution, then click Resolve → Threat List › If something goes wrong |
| The AI summary is in the wrong language | Analysis language was set differently when the email was reported: existing analyses are not translated. | Select the language in Analysis language: new reports will use it → AI Analysis and notifications › If something goes wrong |
| A change shows Failed to update settings or Failed to update AI Smart Analysis settings | A temporary error, or your admin account can't change Threats settings. | Reload the page after a moment and try again → AI Analysis and notifications › If something goes wrong |
Blocking and Allowing Senders
Block only works on Microsoft 365, once the Defender Block Senders integration is complete; Allow requires Smart Banners. The most specific policy wins, so a sender's policy can override their domain's policy.
| Symptom | Why | What to do |
|---|---|---|
| A sender is Blocked, but their emails are still delivered | The Defender Block Senders integration isn't complete, so the block hasn't reached Microsoft Defender yet. | Finish setting up Defender Block Senders in General Settings › Integrations → Sender policies › If something goes wrong |
| Block is disabled | Your company isn't on Microsoft 365, or Microsoft Defender consent hasn't been granted. | Grant consent in Defender Block Senders, General Settings › Integrations → Sender policies › If something goes wrong |
| Allow is disabled | Smart Banners isn't enabled for your company. | Ask your LibraCyber contact about Smart Banners: Allow requires it → Sender policies › If something goes wrong |
| A sender or domain that's allowed still gets a banner | A more specific policy is blocking it, the domain is still Monitoring or Undefined, or the email has a second sender address. | Check the sender's row in Senders and the domain status → Sender policies › If something goes wrong |
| A Blocked policy disappeared from the list | Microsoft Defender no longer lists the block: it was removed there, or it never reached Microsoft Defender. | Check the sender in the Microsoft Defender Tenant Allow/Block List → Sender policies › If something goes wrong |
| A Blocked policy appeared that no one created here | The sender was blocked directly in Microsoft Defender. | Manage that block in Microsoft Defender, or change the policy here → Sender policies › If something goes wrong |
| The tag for a blocked sender changed to Dangerous | The hourly check with Microsoft Defender assigns the Dangerous tag to every blocked sender and disables auto-resolve for them. | No action needed: the block remains → Sender policies › If something goes wrong |
| Auto-resolve is enabled for a domain, but reports for one of its senders are still pending | That sender has its own policy without auto-resolve, which takes precedence; or the domain is Undefined. | Enable Auto-resolve on the sender's row in Senders → Sender policies › If something goes wrong |
| Reports received before auto-resolve was enabled are still pending | Auto-resolve only applies to new reports. | Resolve pending reports with Remediate in Threats › Threats → Sender policies › If something goes wrong |
| Failed to update policy after choosing Block domain or Allow domain in Edit Sender Policy | The domain already has its own policy. | Change the domain's policy in the Domains tab → Sender policies › If something goes wrong |
| A domain policy reverted to Monitoring on its own | A sender from that domain was added with Add Sender, which resets the domain's policy. | Set the domain policy again in the Domains tab → Sender policies › If something goes wrong |
Microsoft Defender Integration
Microsoft Defender tabs only exist for companies on Microsoft 365, and granting consent requires a Microsoft Global admin. Blocking senders also requires a PowerShell step, performed by your IT, then Automatic Sender Blocking enabled: the tab confirms permissions within 2 hours. Sending reported emails is available on request: ask LibraCyber support if it can be enabled for your company.
| Symptom | Why | What to do |
|---|---|---|
| The Microsoft Defender and Defender Block Senders tabs are missing | Your company isn't set up on Microsoft 365: these tabs only exist for Microsoft 365. | Check which email platform your company uses in LibraCyber → Integrations › If something goes wrong |
| The tabs show An error occurred or Failed to load… | Your admin account doesn't have the Threats permission. | Ask an admin to give you the Threats permission → Integrations › If something goes wrong |
| The tab still shows Not granted yet after consent | Status is read when the tab is opened. | Reload the Integrations tab → Integrations › If something goes wrong |
| The consent window doesn't 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 → Integrations › If something goes wrong |
| The consent page says The Administrator consent has failed | The account isn't a Microsoft Global admin, permissions were denied, or the link has expired. | Start again from the tab with a Microsoft Global admin account → Integrations › If something goes wrong |
| Reported emails never reach Microsoft Defender even though the switch is on | Sending hasn't been enabled for your company. | Ask LibraCyber support if it can be enabled for your company → Integrations › If something goes wrong |
| The tab says LibraCyber cannot manage blocked senders in your tenant | The PowerShell step wasn't run, failed, or used the wrong Object ID or tenant. | Run the PowerShell step again → Integrations › If something goes wrong |
| The PowerShell step fails with an access or permissions error | The signed-in account isn't a Global Administrator or Exchange Administrator. | Run it again, signed in as a Global or Exchange Administrator → Integrations › If something goes wrong |
| The PowerShell step says You are signed in to another tenant | The admin signed in to a Microsoft 365 tenant different from the one in the command. | Sign in with an admin account for your tenant → Integrations › If something goes wrong |
| The PowerShell step says The Object ID belongs to another application | The Object ID entered in the tab isn't for Mantra Block Threats (production). | Copy the Object ID for Mantra Block Threats (production) from Enterprise applications → Integrations › If something goes wrong |
| 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 → Integrations › If something goes wrong |
| The PowerShell step rejects the organization | The command still contains yourtenant.onmicrosoft.com. | Replace it with your onmicrosoft.com domain or your tenant ID → Integrations › If something goes wrong |
| Blocks set in Threats never appear in the Microsoft Defender Tenant Allow/Block List | Permissions haven't been verified yet: the tab doesn't show Permissions verified. | Wait for Permissions verified, up to 2 hours → Integrations › If something goes wrong |
| The Microsoft Defender result for a reported email isn't shown anywhere in the console | The console doesn't display it. | No action needed: LibraCyber doesn't show Microsoft's result → Integrations › If something goes wrong |
Webhook
The webhook is called once for each new user report. If your endpoint doesn't respond in time, the call is retried once, then dropped: it won't be resent later.
| Symptom | Why | What to do |
|---|---|---|
| Saving the webhook shows an error | The address isn't http or https, or it points to a local or private server. | Use a public address that starts with https:// → Integrations › If something goes wrong
|
| Webhook calls aren't coming through | Your endpoint didn't respond with a success code within 10 seconds, twice. | Make sure your endpoint responds within 10 seconds with a 2xx code → Integrations › If something goes wrong |
| Some reported emails don't trigger a webhook call | They're banner alerts, simulation emails, or emails already reported from the same mailbox or already reported there by a banner alert. | No action needed: only new user reports trigger the webhook → Integrations › If something goes wrong |
| The link in a webhook call opens a previous version of the Threats list | The link points to the previous Threats list. | Paste the ID into the Threat ID filter in Threats › Threats → Integrations › If something goes wrong |
The Dashboard
Threat landscape works for every company. Most issues with Targeting your company come from an Email Security account not linked to your console: only LibraCyber support can link it.
| Symptom | Why | What to do |
|---|---|---|
| The Dashboard shows Failed to load the brand impersonation dashboard. | A service issue on our end. | Reload the page, then contact LibraCyber support if the issue persists → Dashboard › If something goes wrong |
| Targeting our company shows Not included, but we use Email Security | Your Email Security account hasn't been linked to your console yet. | Ask LibraCyber support to link your Email Security account → Dashboard › If something goes wrong |
| A branch office can't see its own data | Each company in the console only shows the Email Security account linked to it. | Ask LibraCyber support to link the branch's Email Security account → Dashboard › If something goes wrong |
| Targeting our company shows No brand impersonation detected against followed by our company name | Email Security hasn't detected any brand impersonation for your company during the selected period, or the account was only recently linked. | Select a longer period, like 3 mo or 1 yr → Dashboard › If something goes wrong |
| The variation column shows - | There isn't any data for the previous period yet. | No action needed: variations appear when there is data for a full previous period → Dashboard › If something goes wrong |
| Contact us shows Failed to send request. Please try again later. | The request couldn't be sent. | Try again later, or contact your account manager directly → Dashboard › If something goes wrong |
Threats is slow or unavailable
The list doesn't update automatically: reload it to see new reports. Threats doesn't filter, quarantine, or ever delete emails, so if it's unavailable your mail is still delivered as usual.
| Symptom | Why | What to do |
|---|---|---|
| Reports, alerts, or blocks seem delayed | The list hasn't been reloaded, or the step that seems delayed has its own schedule, like blocks in Microsoft Defender or Dashboard data. | Reload Threats › Threats: the list doesn't update automatically → Reports, alerts, or blocks seem delayed: what should I check?, below |
| Threats won't load, or every action fails for every admin | A service outage on our end. | Wait a few minutes, reload the page, and try again → Threats is unavailable: what should I do?, below |
Reports, alerts, or blocks seem delayed: what should I check?
Reload Threats › Threats: the list doesn't update automatically. How long each step takes, from reporting to the outcome email: Overview › How it works.
- The report: if a user's report is missing after reloading, see Reports that don't reach Threats, above.
- AI analysis is added shortly after the report, but only if AI Smart Analysis was active at that time. It is never added later.
- The New threat alert is sent once for each new threat, when a user reports it for the first time: repeated reports or a banner alert won't send another. See AI Analysis and notifications › When is an alert sent?
- Blocks in Microsoft Defender are sent when the tab shows Permissions verified, up to 2 hours after the PowerShell step. If verification fails, LibraCyber checks again about once a day: turn Automatic Sender Blocking off and on to check immediately. See Integrations › How do I let LibraCyber block senders in Microsoft Defender?
- Dashboard data stops at yesterday: today's detections will appear tomorrow. See Dashboard › How often is the data refreshed?
- If reports take more than a few minutes to appear for every user, contact support with two or three examples and the time each email was reported.
Threats is unavailable: what should I do?
Wait a few minutes, reload the page, and try again. Threats works on copies of emails reported by your users: an outage never blocks, delays, or deletes your mail.
- If the add-in says The report button is currently unavailable., users can forward the email to
report@app.mantra.msin the meantime. - If Threats › Threats, Threats › Setup, or Threats › Sender policies still won't load, or every action ends with an error for every admin, contact support. Send the information listed in What to send to support, below.
What to send to support
To get an answer instead of a follow-up question, please include:
- Your company and your email platform: Microsoft 365, Google Workspace, or another system.
- For a report: the reporting user's address and how they reported it: LibraCyber add-in, Microsoft's Report phishing, forwarding, or Report email in a banner. Add the date and time, sender and subject of the email, and its approximate size.
- For a threat in the list: its Threat ID, shown in the page address when the threat is open. The original email can be downloaded from the threat with Download EML.
- For the report button: the Outlook app and version, and a screenshot of the button, the message shown by the add-in, or the error in the Microsoft 365 admin center.
- For an error message: a screenshot with the exact text. For the PowerShell step, the printed error text.
- For an integration: the webhook address and the time of the report; for a block, the sender and whether they appear in the Microsoft Defender Tenant Allow/Block List.
- When it started, and what changed during that time: a new add-in deployment, a consent removed in Microsoft Entra, users or mailboxes added or removed.