Microsoft support policy for the customization of Outlook Web App for Exchange Server 2010

Unsupported Customizations

You may want to change OWA features or the user interface to better suit the needs or your organization. Many OWA source files can be edited or changed on the server. Therefore, it is possible to modify the default functionality of OWA. However, Microsoft CSS only supports customizing OWA in ways that are documented as part of Microsoft's Exchange or OWA documentation on the Microsoft Developer Network (MSDN) or TechNet websites. Any other customizations are not supported or recommended by Microsoft. All OWA source files should be treated as regular source code files unless there is Microsoft documentation that describes how the files should be customized.

Microsoft CSS cannot help you with any undocumented customizations. If you want to customize OWA, the following limitations and considerations apply:

• Microsoft CSS does not provide assistance with customizing OWA components.

• If you contact Microsoft CSS about an OWA issue for a server on which OWA is customized, you may have to replace the customized files with the original versions of the files and verify that you can reproduce the issue by using the original versions of the files. If the issue occurs only with the customized versions of the files, and you cannot reproduce the issue with the original versions of the files, Microsoft CSS cannot help you troubleshoot the issue.

• If you install an Exchange service pack, rollup, or hotfix that updates OWA files, any customized files may be overwritten. If you do not want to lose the customizations that you created, create a backup of the customized files, and then restore the files after you install the service pack, rollup, or hotfix. You should review any Exchange release notes before you install service packs, hotfixes, and hotfix rollups to find instructions about how to handle overwrites to customizations.

The following OWA feature areas are common requests for customization, but are not supported by Microsoft CSS:

• Custom user authentication logic and the default user interface.

• The custom logoff button.

• Modifying the user interface on any page other than the logon page.

• Using an ISAPI filter to modify OWA. You can use an ISAPI filter to monitor OWA.

• Using the full OWA user interface in a custom iFrame HTML tag. Instead, you can consider whether using an OWA web part in an iFrame tag may suit your needs. For more information, visit the following Microsoft TechNet website:

Exchange 2010: Using Outlook Web App Web Parts

Peer-to-Peer Assistance

Microsoft public forums provide peer-to-peer support for the Exchange developer community. To view the Exchange Development forum, visit the following Microsoft website:

Exchange Development forum

Supported Customizations

Support for customizing OWA varies, depending on the version of Microsoft Exchange that is used. However, all versions of OWA allow you to create custom web forms for custom item types. Web forms must be registered for custom message classes. Customizing the built-in item types is not supported.

The following is a summary of the documented and supported features for customizing OWA.