Mail apps for Outlook evaluation criteria

Exchange

Find information about using mail apps for Outlook and Outlook Web App to develop against Exchange.

Last modified: March 31, 2014

Applies to: apps for Office | Exchange Online | Exchange Server 2013 | Office 365

In this article
Functional criteria for mail apps for Outlook
Development criteria for mail apps for Outlook
Security criteria for mail apps for Outlook
Deployment criteria for mail apps for Outlook
Additional resources

Mail apps provide a single interface and programming model that use web standards to create a custom experience for your users. Your mail app can be simple or complex, use data from an Exchange server or from any service on the web, and fully integrate with both Outlook Web App and Outlook 2013.

Note Note

"Outlook" in this article refers to the Outlook rich client, Outlook RT, Outlook Web App, and OWA for Devices.

The following table lists and describes the functional criteria for mail apps for Outlook. For descriptions of the functional criteria, see Functional criteria in the Exchange development technology evaluation criteria descriptions article.

Table 1:  Mail apps for Outlook functional criteria

Criterion

Description

Application function

Mail apps for Outlook are used to add content-specific extensions to the email reading experience. The mail app API provides tools to access Exchange Web Services (EWS), as well as information from third-party web services.

Availability

Mail apps for Outlook are included in Office 2013 and Exchange 2013.

Application architectures

Mail apps for Outlook run in an HTML5 frame inside the reading area of Outlook and Outlook Web App. There are no other restrictions on the client application architecture.

Remote usage

Mail apps for Outlook are designed to be used by remote email clients.

Major objects

Mail apps for Outlook provide objects for accessing information from email messages and appointments.

Data access model

Mail apps for Outlook use standard web protocols for sending and receiving data. JSON and XML documents are the primary data formats.

Threading models

Mail apps for Outlook support asynchronous methods using standard techniques in JavaScript programming.

Transactions

Mail apps for Outlook do not support transactions.

Management capabilities

Mail apps for Outlook can be installed by end users, or they can be installed by local administrators.

The following table lists and describes the development criteria for mail apps for Outlook. For descriptions of the development criteria, see Development criteria in the Exchange development technology evaluation criteria descriptions article.

Table 2:  Mail apps for Outlook development criteria

Criterion

Description

Languages and tools

Mail apps for Outlook use standard web technologies, including HTML5, XML and JavaScript. You can use any programming environment that supports these technologies to develop mail apps.

Managed implementation

The main mail apps for Outlook API is not a managed API. A managed API is provided for services that must validate a user identity token.

Scriptable

Mail apps for Outlook cannot be used in scripts.

Test/debug tools

No special debugging tools are required to debug mail apps for Outlook. For difficult issues, you can use debugging tools for standard web technologies.

Expert availability

Developers who have web development experience can easily create mail apps for Outlook. Because mail apps are new, it will be more difficult to find developers with specific experience with mail apps.

Available information

Standard web programming techniques are supported by many books and web sites. For information specific to mail apps for Outlook, see Apps for Office and SharePoint.

The following table lists and describes the security criteria for mail apps for Outlook. For descriptions of the security criteria, see Security criteria in the Exchange development technology evaluation criteria descriptions article.

Table 3:  Mail apps for Outlook security criteria

Criterion

Description

Design-time permissions

No specific permissions are required to develop a mail app for Outlook. If the mail app is using EWS to access information on the Exchange server, the email account that is used to connect to the Exchange server must have permission to use EWS, and the mail app must be specifically configured to make EWS requests.

Setup permissions

No specific permissions are required to set up a mail app for Outlook.

Run-time permissions

Outlook must connect to a valid domain user account on the Exchange server to use a mail app. If the mail app uses EWS, the mail app must be specifically configured to enable EWS access.

Built-in security features

All mail apps for Outlook must be served by using HTTPS. The mail app API includes a method to request a user identity token from the Exchange server; mail apps can send this token to third-party services to identify an email account on a particular Exchange server.

Security monitoring features

None.

The following table lists and describes the deployment criteria for mail apps for Outlook. For descriptions of the deployment criteria, see Deployment criteria in the Exchange development technology evaluation criteria descriptions article.

Table 4:  Mail app for Outlook deployment criteria

Criterion

Description

Server platform requirements

Mail apps for Outlook are supported by Exchange 2013.

Client platform requirements

Mail apps for Outlook are supported by Outlook 2013 and the version of Outlook Web App that ships with Exchange 2013.

Deployment methods

Mail apps for Outlook can be installed from a local directory, from an internal web server, or from the Apps for Office marketplace.

Deployment notes

None.

Show:
© 2014 Microsoft