Outlook Web Access
Outlook Web Access
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release. This topic provides information using Outlook Web Access to develop messaging applications.
Introduction
Microsoft® Outlook® Web Access provides a rich messaging environment for use with Exchange that can be accessed over the Internet. The components that make up the Outlook Web Access display can be reused in other applications, and new features can be added. In addition, you can create custom display and data entry forms by means of the Exchange Web forms registry.
Caveats
Support for customizing Outlook Web Access and reusing Outlook Web Access components is not available from Microsoft. Microsoft improves and adds features to Outlook Web Access with new releases of Exchange, and the Outlook Web Access internal workings and architecture may change without notice.
Functional Criteria
| Criteria | Outlook Web Access |
|---|---|
| Application Domain | Modifications to Outlook Web Access are typically minor stylistic or graphical modifications to the display theme. Major modifications to Outlook Web Access are not recommended or supported. Some customers reverse-engineer the URLs that Outlook Web Access uses to display mailbox and public folder information, such as Inbox data, Calendar, and Contacts. They then use those URLs inside other Web-based applications, consoles, or portals. This use of Outlook Web Access is also not recommended. |
| Major Objects | Outlook Web Access does not expose COM objects, or provide an object hierarchy. Instead, you can obtain the components of Outlook Web Access by using a URL; for example, https://mail.example.com/exchange/username/Inbox/?Cmd=contents |
| Data access model | Outlook Web Access returns data in various forms, including HTML and XML, depending on the capabilities of the client browser. |
| Threading Models | Not Applicable. |
| Application Architectures | Outlook Web Access is a Web client application. |
| Remote Usage | Outlook Web Access configured to use SSL/TLS and basic authentication can be used on an intranet as well as over the Internet. |
| Transactions | Outlook Web Access does not support transactions. |
| Management Capabilities | Outlook Web Access as a development technology does not provide any management features to the application. The Exchange administration and the individual user can access Outlook Web Access and other Outlook Web Access configurations. |
| Availability | Outlook Web Access is a core component of Microsoft Exchange Server 2003. However, Outlook Web Access features and internal architecture may change without notice. |
Development Criteria
| Criteria | Outlook Web Access |
|---|---|
| Languages and Tools | Outlook Web Access components are only available by means of the HTTPS GET and POST methods. |
| Managed Implementation | Outlook Web Access is not an API and does not provide components for use in a managed or unmanaged development environment. However, you can use the HTTPRequest and HTTPResponse managed classes to access Outlook Web Access programmatically. |
| Scriptable | It is not possible to directly access Outlook Web Access components by using a script. It is possible to use an HTTPRequest or similar object to retrieve information from Outlook Web Access. |
| Test/Debug Tools | No tools are available for debugging calls to Outlook Web Access, because the internal architecture is not available for debugging, and the URL calls required to access Outlook Web Access programmatically are not documented or supported. |
| Expert Availability | Outlook Web Access customization and component reuse is not supported by Microsoft. |
| Available Information | Little or no information is available about customizing Outlook Web Access or reusing Outlook Web Access components and commands. |
| Developer / Deployment Licensing | Outlook Web Access customization and component reuse is not supported by Microsoft. |
Security Criteria
| Criteria | Outlook Web Access |
|---|---|
| Design-Time Permissions | Outlook Web Access customization and component reuse is not supported by Microsoft. |
| Setup Permissions | Outlook Web Access customization and component reuse is not supported by Microsoft. |
| Run-Time Permissions | Outlook Web Access customization and component reuse is not supported by Microsoft. |
| Built-in Security Features | Outlook Web Access by default uses SSL/TLS and basic authentication. |
| Security Monitoring Features | None. |
Deployment Criteria
| Criteria | Outlook Web Access |
|---|---|
| Server Platform Requirements | Outlook Web Access customization and component reuse is not supported by Microsoft. |
| Client Platform Requirements | Outlook Web Access customization and component reuse is not supported by Microsoft. |
| Deployment Methods | Outlook Web Access customization and component reuse is not supported by Microsoft. |
| Deployment Notes |
Send us your feedback about the Microsoft Exchange Server 2003 SDK.
This topic last updated: June 2006
Build: June 2007 (2007.618.1)
© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.