With the preview release of "the new Outlook" on OWA, Office Add-ins are now buried in the drop down context menu in an email. Additionally, it appears they do not follow the same behavior of Outlook on the desktop, where Office Add-ins will show in the larger ribbon if used more frequently.

According to this article, Office Add-ins can be pinned if they are used frequently:

If you were using add-ins in the classic Outlook on the web experience, they will show up pinned next to mail actions or in the drop-down menu once you open an email in the new experience. You can also install more add-ins from the Office Store—simply open an email, click the drop-down menu, and select Get Add-ins. Once installed, add-ins will show up in the drop-down menu. You can also choose to pin frequently used add-ins.
While I can instruct users to pin this for themselves, it does not appear that Office Add-ins can be pinned by an administrator.

For this feature, it would be great for administrators to be able to customize which add-ins are immediately available to the user by pinning them. Office Add-ins being buried in the menu of OWA is not helpful in this regard.

Ok so I have a Blob file that I'm trying to save on local disk (the Blob is created locally from an ArrayBuffer). The problem I'm facing is that Outlook for macOS does not want to open a FileSaverDialog or something similar to let the user save the file.

My code is working perfectly in Outlook for Web (OWA) on all browsers (including Safari) and Outlook for Windows.

const blob = new Blob([body]); //body is an ArrayBuffer created locally
const link = document.createElement('a');
if (link.download !== undefined) {

const url = URL.createObjectURL(blob);

link.setAttribute('href', url);

link.setAttribute('download', fileName);

link.style.visibility = 'hidden';

document.body.appendChild(link);

link.click();

document.body.removeChild(link);

}

PS: I have tried using window.open(blob);, but Outlook for macOS throws an error in that situation: "There is no application set to open URL blob:https://..."

PS 2: I have also tried using Office.context.ui.displayDialogAsync(url, { height: 100, width: 100, requireHTTPS: true });,but still getting the same error.

How am I supposed to prompt a SaveFileDialog for the user ? Thank you in advance

i keep getting junk and these people keep using a auto response system, but they are lazy, what outlook needs is a first name @ blocker, so i keep getting two kinds of spam, one where they change the .com, and will either write dysfunctional names or coded numbers, so one is a blackmail scam, where they claim they will post videos of you wanking, and what they will do is saveyourself@4005.com or saveyourself@5564.com what outlook needs to develop is a (first name) @ blocker, and also sort numbers .com so just uploads loads of numbers 1 to billion, so then you can just add 1 to 1 billion.com on block and the is also another kind, where they will go Denovon@GR4jbg56jh4h.com or something like that, they need to develop a block all dysfunctional e-mail system, so you'd just click block dysfunctional, so if they word before the .com can't be pronounce they just get blocked. because these horrible people are corrupt and continuous.

We use Office.js to build an Outlook web add-in and we make use of the calls composeItem.to.getAsync where the compose Item is Office.context.mailbox.item. The call returns an array of recipients of Office.EmailAddressDetails objects and are as described in this documentation.

In the latest version(s) of Windows Outlook (16.0.11901.20204 and 16.0.11901.20070), we can observe a discrepancy in the resulting EmailAddressDetails.recipientType to the above call when it comes to Dynamic Distribution Groups. We observe that the recipientType used to be distributionList on a slightly older version of Windows Outlook (16.0.11328.20362). But now, the recipientType returns other for Dynamic Distribution Groups. This discrepancy affects clients that are on different Windows Outlook update cycles.

Is this change going to be permanent or will it be using a value something other than other?

This affects how we implement our web add-in because we're concerned with figuring out groups (distribution lists, DDGs, etc.) from users and expanding the groups. As it stands right now, we're unsure whether other is within the category of expandable groups or not as there is no documentation regarding the details of recipientType values.

Opening an url via displayDialogAsync even when redirecting to servers that do not honor "|" in query in parameters should work.

Current Behavior
Opening an URL via displayDialogAsync fails when opening AWS API Gateway URLs or similar such servers where "|" is not honored/configured to be used. Though it may be for the server to accept "|" the best practice may be to encode the URLs

Additional details:
Set up an AWS API Gateway + Lambda
Use Office API Office.context.ui.displayDialogAsync to open this URL.
The Office API adds a query parameter "hostinfo" with values similar to - outlook|web|16.01|en-us|6ed38bbe-e610-cf6a-b413-9491cdcef28a|isDialog|
The page fails to open with a 400 error.

FIX:
showDialog (line 8975) from https://appsforoffice.microsoft.com/lib/1.1/hosted/outlook-web-16.01.debug.js seems to include "|" in the constructing the query parameters. Can we please encode the query parameter component before calling window.open

There was a checkbox in 'the old' OWA which, when checked, ensured that the Compose form (new message, reply, forward) opened in a popup. Please bring that functionality back.

The problem is that my read-pane add-in has a timer which the user can start to record the time spent on writing the reply to a message. I want to record that time in my application. When the compose form opens, the read-pane add-in gets closed and hence we lose the time spent. When the compose form opens in a popup, the read-pane add-in stays in its place and the user can save the time in our application.

NOTE This is impacting our existing customers.

I am unable to unregister a previously registered event handler for ItemChanged event when the handler function is no more available in the page's scope. So there needs to be an ability to either:
- unregister the event handler by name only or
- unregister all the event handlers registered by the add-in

Use Case
My add-in has more than one web-pages and I have a navigation bar in it. So my web-pages unload when I navigate to another page. Because the Office.context.mailbox.removeHandlerAsync function requires the named handler to be a valid function, I can not unregister the handler in another web-page where the user has navigated to. And when I try to register the event handler again (for that web-page), it fails because more than one handlers are not supported.