Hi @aljoscha.s,
Thank you for asking such an important and insightful question about the dependency of the onSend feature on Exchange Server. You are absolutely right in identifying onSend as an Outlook client-side API (Office.js), but the role of the server in enabling it is crucial.
Here’s a detailed explanation of how the server affects this feature and how you can diagnose it:
- The Role of Exchange Server in the onSend Feature
The onSend feature is not just a local function on the Outlook Desktop client. It is a compliance-driven capability designed to ensure that email content adheres to organizational policies before the message is sent.
- How to Diagnose onSend Support from Exchange Server
To determine whether your Exchange Server supports and has enabled the onSend feature, an Exchange Administrator needs to perform the following steps:
Diagnostic Method: Check the Mailbox Policy
The most direct way is to inspect the OWA Mailbox Policy applied to the target user’s mailbox using PowerShell in the Exchange Management Shell (EMS):
- Retrieve the current policy: The administrator should identify which OWA policy is applied to the mailbox.
Get-CASMailbox -Identity "<Email Address>" | Select-Object OwaMailboxPolicy
- Check the onSend flag: Once the policy name is known (e.g., OWAOnSendAddinAllUserPolicy), check the status of the onSend flag:
Get-OwaMailboxPolicy -Identity "OWAOnSendAddinAllUserPolicy" | Select-Object OnSendAddinsEnabled
Diagnostic Results
- If the result is True: This confirms that the Exchange Server has enabled the feature via policy. If the add-in still doesn’t work, the issue likely lies in incompatibility or deployment errors in your Outlook 2021 (perpetual license) or specific Exchange Server SE environment.
- If the result is False: The onSend feature is disabled at the server level. The administrator must enable it using the following command:
Set-OwaMailboxPolicy -Identity "OWAOnSendAddinAllUserPolicy" -OnSendAddinsEnabled:$true
The onSend feature has a dual dependency: it requires both the Mailbox API 1.8+ on the Outlook client and the OnSendAddinsEnabled flag to be turned on in Exchange Server.
You should coordinate with your Exchange Administration team to perform this check. If the flag is confirmed to be enabled but the feature still fails, it is almost certainly due to incompatibility with perpetual license products in an on-premises environment.
To obtain more accurate information, you may consider visiting the following forum:
Microsoft 365 and Office Development Office JavaScript API - Microsoft Q&A
We apologize for redirecting you to another community, as most members in this category primarily focus on Microsoft 365 users and have limited knowledge about APIs. Therefore, to receive faster and more effective support, allow me to guide you in the right direction.
We are more than happy to assist you, but we’re concerned that providing inaccurate information may not be beneficial to you. We sincerely hope you’ll find the perfect solution with support from experienced experts and community members. We also welcome any community member to share ideas regarding your situation if they have relevant experience.
If you have any updates regarding the issue, or if you have any other questions, please feel free to share them with me. I will support you to the best of my ability.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.