The Cyberdise report button normally authenticates against Microsoft Entra ID (Azure AD). Organisations that run Exchange on premises, or that do not want to register an application in Entra ID, can now deploy the same button in an Exchange / On-premises (EWS) mode that needs no Azure registration at all.
Choosing the connection type
- As a realm operator, go to Advanced → Settings → Integrations → O365 Plugin. As a tenant operator, go to **Realms → *realm name* → Integrations → O365 Plugin**.
- Set Connection Type to Exchange / On-premises (EWS).
The two connection types expect different things from you:
| Connection Type | What it needs |
|---|---|
| Microsoft 365 / Azure AD | Azure applications registered in Entra ID, with a Reply URL — see the Azure setup guide |
| Exchange / On-premises (EWS) | Nothing in Entra ID. The Azure Applications and Reply Url fields disappear from the page |
Everything below the connection type — report delivery, post-report action, report routing and the feedback messages — is configured the same way in both modes.
Configuring and deploying
- Choose how reports reach Cyberdise:
- Enable Web Delivery with an HTTP Destination, and/or
- Enable Mail Delivery with a Mail Destination (internal and external addresses).
- Set Post Report Action — what happens to the reported message in the user's mailbox: *None*, *Move to Spam* or *Delete from Inbox*.
- Save the settings, then select Download Manifest.
- Deploy the manifest to your users:
- Exchange on premises — Exchange admin center → *Organization → Add-ins*, or per user in OWA under *Manage add-ins*.
- Microsoft 365 without an Azure app registration — Microsoft 365 admin center → *Integrated apps → Upload custom app*.
- Restart Outlook and confirm the button appears on the ribbon.
Limits to be aware of
- Large messages. The add-in hands the original message to Cyberdise as MIME, and
that transfer is capped at roughly 700 KB. A reported message above the cap — typically one with large attachments — is still reported and still counted in the campaign, but without the full original MIME attached.
- Mailbox permissions. EWS mode acts in the context of the signed-in mailbox.
Reporting from a shared mailbox requires the user to have access to that mailbox in Outlook.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| The task pane stays blank or white | The page is blocked from being framed by Office | Reload the task pane once or twice; if it persists, check the framing policy on the reverse proxy in front of Cyberdise — X-Frame-Options: SAMEORIGIN prevents Office from rendering the add-in |
| The button appears but reporting fails | The HTTP destination is not reachable from the client | Open the realm system domain in the user's browser and confirm the certificate is trusted |
| The add-in asks for a Microsoft sign-in | Connection Type is still *Microsoft 365 / Azure AD* | Switch it to *Exchange / On-premises (EWS)*, save, and download the manifest again |
Comments
0 comments
Article is closed for comments.