outlook-web-addins

I'm creating an outlook add-in and use the OfficeJS API in React app. In there I want to load a specific set of features for the compose mode and another set of features for the read mode. So my question is, how to see in which mode I'm currently on? In the manifest.xml file you should have different ExtensionPoint for compose and read view as follow ... <ExtensionPoint xsi:type="MessageReadCommandSurface"> </ExtensionPoint> <ExtensionPoint xsi:type="MessageComposeCommandSurface"> </ExtensionPoint> Each of this sections have to have Action tag with ExecuteFunction or ShowTaskpane type. If you

Does the New OWA support on send? I have an addin that uses the on-send feature, it works fine in the old OWA but not the new OWA, do i have to do some extra configurations in order to get on-send to work in new OWA? onSend feature is currently not available on new OWA. We are currently working on it and should be available in the near future (no tentative date available). 来源： https://stackoverflow.com/questions/55510506/how-to-enable-on-send-feature-for-new-outlook-web-app

I'm working on an Outlook Web Add-In and I'm struggling with knowing what value to set for the X-Frame-Options: ALLOW-FROM header. As far as I know, users may access Outlook via three different domains ( office.com , office365.com and live.com ). Does anyone know how I can tell which site is making the request, so I can set the header appropriately? The add-in needs to be able to run in an iFrame in order to work in Outlook Web, thus X-Frame-Options header should not be included at all. ALLOW-FROM can't really be used because the number of domains to list is way more than 3 mentioned, and that

We're getting lots of Office JS API errors in Application Insights, but they don't have a stack trace. All that we have - The browser's same-origin policy prevents us from getting the details of this exception. Consider using 'crossorigin' attribute. . Note, we have set 'crossorigin' attribute to office.js in Add-In HTML: <script src="//appsforoffice.microsoft.com/lib/1.1/hosted/office.js" type="text/javascript" crossorigin="anonymous"></script> The issue is following: office.js injects additional scripts depending on environment and these scripts don't have crossorigin set. For example https:

I'm seeing an issue with my Outlook Add-in (running in Outlook 2016) where when I open a popup window using window.open , it sometimes opens in the user's default browser (e.g. Chrome) instead of the browser running the add-in (e.g. the IE11 web view embedded in Outlook 2016). This is a problem because it prevents the popup window from communicating with the add-in, which is necessary for clickjacking protection. Is there a way to force the popup window to be opened in the same browser that is running the add-in, without using the Dialog API? I would like to support requirement set 1.3.

I'm currently working with an Outlook Web Add-in with Office.js. In this project, we require sending mail merge emails to handle Distribution Lists and Groups. We use the ExpandDL call and our soap request looks like: <?xml version="1.0" encoding="UTF-8"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soap:Header>