is there a salesforce for outlook plugin for owa

Outlook uses a schema to validate manifests.

Even if your add-in manifest uses the element, it is still important to include the v1.1 manifest elements to allow your add-in to work with older clients that do not support.

This article will cover the requirements for a v1.1 manifest. This supports add-in commands and adds support for newer features, such as pinnable task panes and mobile add-ins. Supports later versions of the Office JavaScript API. For Outlook add-ins, this adds support for compose form. Supports version 1.1 of the Office JavaScript API and. For Outlook add-ins, this supports read form. Supports version 1.0 of the Office JavaScript API. The current versions of the schema are: Version This approach means that developers don't have to create multiple individual manifests, but rather keep everything defined in one file. However, if the version of Outlook doesn't support a certain version of, Outlook will ignore it and depend on the information in the rest of the manifest. This means that, whenever possible, Outlook will use what is in the section to set up the add-in. All elements defined inside will override the same element in the other part of the manifest. The element in the manifest is an example of this. Having schema versions lets developers build add-ins that are backwards compatible, using the newest features where they are available but still functioning on older versions. Not all Outlook clients support the latest features, and some Outlook users will have an older version of Outlook. In an actual valid manifest, these values would contain valid https web URLs. All URL values in the following sample begin with ''.

Is there a salesforce for outlook plugin for owa