Overview of apps for Office 2013

Applies to: Office 2013, Office 365 ProPlus

Summary: Learn about apps for Office and how to obtain and manage apps for Office for users in your organization.

Audience: IT Professionals

The new apps for Office enable users to run the same solutions across applications, platforms, and devices, and provide an improved experience within Office applications by integrating rich content and services from the web. In this article, you can learn more about the types of apps for Office and the applications that support them. You can also learn how to make apps for Office available to users, how to manage them by using Group Policy settings or the registry, and how to monitor them by using Telemetry Dashboard.

In this article:

• What is apps for Office?

• Anatomy of an app for Office

• Types of apps for Office

• Supported applications for apps for Office

• Privacy and security for apps for Office

• Managing access to apps for Office

• Monitoring apps for Office

• Managing the performance of apps for Office

What is apps for Office?

Developers use apps for Office to create engaging new consumer and enterprise experiences that run within supported Office 2013 applications by using the power of the web and standard web technologies such as HTML5, XML, CSS3, JavaScript, and REST APIs.

An app for Office is basically a webpage that is hosted inside an Office client application. You can use apps to extend the functionality of a document, email message, meeting request, or appointment. Apps can run in multiple environments and clients. These include rich Office desktop clients, Office Online, mobile browsers, and also on-premises and in the cloud. Developers can publish apps to the Office Store or to an onsite catalog, where they can be available to users from their Office 2013 applications. As the IT Administrator of your organization, you can control how the apps for Office become available to users.

Anatomy of an app for Office

The basic components of an app for Office are an XML manifest file and a webpage. The manifest defines various settings and points to the webpage that implements the app UI and custom logic, as shown in the following figure.

Manifest + webpage = an app for Office

The manifest specifies settings and capabilities of the app, such as the following:

• The URL of the webpage that implements the app UI and programming logic.

• The app display name, description, ID, version, and default locale.

• Whether the app can be shown as a task pane, in line with document content, or started contextually in an email message, meeting request, or appointment.

• The kinds of client applications (including rich clients and Office Online) that an app supports.

• The permission level and data access requirements for the app.

Types of apps for Office

The three basic types of apps for Office are task pane, content, and mail apps for Outlook.

Task pane apps

Task pane apps enable users to see the app for Office side-by-side with an Office document, and provide app for Office developers with the opportunity to supply contextual information and functionality to enhance the document viewing and authoring experience. For example, a task pane app can look up and retrieve product information from a web service, based on the product name or part number that a user selects in a document. An example of a task pane app for Word 2013 that uses the Bing Translator service is shown in the following figure.

Task pane app

Content apps

Content apps integrate web-based features as content that can be shown in line with the document. Content apps enable users to integrate rich, web-based data visualizations, embedded media such as integrating a YouTube video player or a picture gallery as part of a document, and also other external content. The following figure shows an example of a content app for Excel 2013 that uses a web service to generate a geographical sales heat map.

Content app

Mail apps

Mail apps are displayed next to the currently viewed Outlook items: email message, meeting request, meeting response, meeting cancellation, or appointment. They can access contextual information from the item and use that data to access additional information about the server and from web services to create compelling user experiences. In most cases, a mail app runs without modification on the Outlook 2013 rich client and Outlook Web App for Exchange Server 2013. This user experience is seamless, whether on the desktop, the web, or on tablet and mobile devices.

The following figure shows an example of a mail app that uses the Bing Maps service.

Mail app

Supported applications for apps for Office

One big benefit of apps for Office is that they can be supported both on Office 2013 rich clients and some corresponding Office Online programs. To the developer, this means that, in many scenarios, they do not have to create separate apps for different environments or applications. To the user, it means a consistent user experience across the desktop and web browser. And for the IT Professional, it means that it’s easy to manage apps for Office across environments and applications.

For task pane apps, this means the same app can run on Excel 2013, Excel Online, Word 2013, and Project 2013. For apps for Outlook, it means that the same app can work for Outlook 2013 on the desktop, tablet, and mobile devices.

Supported app types

Privacy and security for apps for Office

Privacy and security for apps for Office are covered in the following two MSDN topics:

• Privacy and security for apps for Office

• Privacy and security for mail apps for Outlook

See Using Group Policy to manage how users can install and use apps for Office to learn more about the Group Policy settings that can help you manage privacy and security for apps for Office.

Managing access to apps for Office

As the IT Administrator of your organization, you can control how the apps for Office become available to users. You can choose the type of hosting option that's appropriate for your organization. For example, if you don’t want users to access apps for Office from the Office Store, you can disable that capability by using Group Policy. Then, you can make apps for Office available to users by hosting them internally in a SharePoint App Catalog, an Exchange catalog, or a file catalog share. These distribution methods are described in the following sections.

Supported distribution points for apps for Office

After an app for Office is created by a developer, the developer can decide how to publish it so that it is available to the users within your organization. In Office 2013, the following distribution points are supported for publishing apps for Office:

• Office Store Hosted and regulated by Microsoft, the Office Store is where developers around the world can publish and sell their custom Office solutions. End users and IT professionals can download these custom Office solutions for personal or corporate use. Office Store handles the consumer download experience from discovery to purchase, upgrades, and updates.

• SharePoint App Catalog   For task pane and content apps, IT departments can deploy private app catalogs to provide the same app acquisition experience that the Office Store provides. This new catalog and development platform enables IT departments to use a streamlined method to distribute apps for Office and SharePoint to managed users from a central location.

  App Catalog is available to all SharePoint customers (including Office 365 and SharePoint on-premises). App Catalog enables publishing and administration of both internally created apps and apps that are available in the Office Store and licensed for corporate use. For more information, see Manage the App Catalog in SharePoint 2013.

• Exchange catalog   This is a private catalog that is managed by an Exchange administrator for mail apps that are available to users of the Exchange Server on which it resides. It enables publication and administration of corporate mail apps, such as internally created apps and apps that are available in the Office Store and licensed for corporate use.

• File-based app catalog   IT departments and developers can deploy task pane and content apps to a central file share, where the manifest files will be stored and managed. Users can then obtain apps by specifying this file share as a trusted catalog, or an IT administrator can configure this file share as a trusted catalog by using Group Policy.

Using Group Policy to manage how users can install and use apps for Office

You can manage and enforce apps for Office settings by using Group Policy settings that are available in the Office 2013 Administrative Template files (ADMX/ADML) and Office Customization Tool. The settings are found under User Configuration\Administrative Templates\Microsoft Office 2013\Security Settings\Trust Center\Trusted Catalogs. The OCT settings are in corresponding locations on the Modify user settings page of the OCT.

The following table describes the Group Policy settings that manage apps for Office.

Group Policy settings for apps for Office

Using Group Policy and Exchange admin center to manage how users can install and use apps for Outlook

You can prevent users from downloading apps for Outlook from the Office Store and, for Outlook that comes with an Office 365 subscription, remove the Store button from the Home tab.

To prevent users from downloading apps for Outlook from the Office Store, remove the My marketplace apps user role from the user policy in the Exchange Administration Center (EAC). To do this,

1. In EAC, select Permissions > User roles.

2. Select the policy and Edit.

3. Under Other roles, clear the My marketplace apps check box.

4. Select Save.

To remove the Office Store button from the Home tab in the version of Outlook that comes with an Office 365 subscription, use the Outlook Group Policy setting Hide the Office Store button, shown in the following table. In Group Policy, the setting is found under User Configuration\Administrative Templates\Microsoft Outlook 2013\Outlook Options\Other.

Monitoring apps for Office

Telemetry Dashboard helps IT professionals monitor client computers to learn what Office solutions, add-ins, and documents are being used in an organization. You can use Telemetry Dashboard to monitor loads and load failures for apps for Office in Word, Excel, and Outlook. This information will tell you which apps for Office are frequently used in your organization and which apps for Office are experiencing errors. For more information, see Deploy Telemetry Dashboard.

Managing the performance of apps for Office

You can control the performance of apps for Office by adding or changing performance-related threshold registry settings.

There are three ways for an administrator to set these registry keys, listed in the following tables. The following is the order that a host application checks for the existence of these keys:

1. If the host application supports group policy for app resource usage, the host application first looks for a group policy key.

2. In the absence of a group policy key, the host application looks for an application-specific registry key.

3. If an application-specific key is absent, the host application looks for a global registry key.

4. If the host application does not find a global registry key, the host application uses the corresponding default value.

For apps for Office, the settings in the following table can be added or changed in the registry. You can add these registry keys in the general Office hive under HKLM:

• HKEY_LOCAL_MACHINE\Software\Microsoft\Office\15.0\WEF, for Windows Installer-based (MSI) versions of Office, such as the volume licensed version of Office Professional Plus 2013.

• HKLM\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Wow6432Node\Microsoft\Office\15.0\WEF, for Click-to-Run versions of Office, such as Office 365 ProPlus.

The global registry keys in the following table apply to all apps for Office, running on any Office rich client that supports apps for Office on the local computer.

These registry keys are not present by default in the Windows registry. Administrators create them initially if they want to fine-tune the performance of apps for Office. You can configure application specific settings by creating a key under WEF, such as HKEY_LOCAL_MACHINE\Software\Microsoft\Office\15.0\WEF\Excel for Excel. Also, users must restart the corresponding host application for that application to recognize such settings.

Performance-related registry settings for apps for Office

Outlook 2013 provides Group Policy settings to help you manage mail apps for Outlook. You can find them under User Configuration\Administrative Templates\Microsoft Outlook 2013\Security\Trust Center. If you are using the Windows based-installer (MSI) delivery format of Office 2013, you can use the OCT to set default settings that users can later change. OCT settings are in corresponding locations on the Modify user settings page of the OCT.

Performance-related Group Policy settings for mail apps

The following table describes the Group Policy settings that manage mail apps for Outlook. The term "web extension" in the policy setting name refers to mail apps for Outlook.

Performance-related Group Policy settings for mail apps