I have not seen any examples of using OWA parts in an iFrame.  However, I wrote such a sample recently and wanted to share it.

The full OWA UI in an iFrame is not supported and its expected that doing so may fail at any given point and at different points depending upon the service pack and hotfix rollup.  You can use OWA Parts (a URL reference to a folder which displays content) in an iFrame.  OWA parts have several options for outputting the contents of a folder, however they do not provide the full functionality of OWA.   OWA Parts work off a URL which takes parameters to output the desired view of a folders contents rather than using a direct url reference.

I have seen some customers get OWA to mostly work in an iFrame by modifying the .js files to redo frame targeting – however, this is very much not supported in any way and any sort of update to the server may overwrite the .js file changes;  further, if there are issues with OWA, you may be required to reverse all such changes before support can be provided.

As an example, this:

Would need to be written something like this:

Here are some starting articles which you should review around developing with OWA in an iFrame or usage of OWA Web parts:        

Hosting Outlook Web Access in an IFrame Is Not Supported

How to Use Outlook Web Access Web Parts

ConvertId operation

Below is a sample iFrame I put together - it loads views of different folders for a mailbox and public folder.  You will need to change the server part of the URLs to match your server and create a folder called “abc” in your inbox and a folder called “test”and a calendar folder called “test team calendar”  in your public folder to use it.

    <title>test iframe with owa web part</title>


<iframe src="" name="OwaPartsSample" align=center height="500" width="900" scrolling="Auto">


<div align=center>
  <b>Test Links</b>

  <!-- reference Inbox -->
  <a href="" target="OwaPartsSample">Inbox</A><BR>

  <!-- reference Inbox/abc -->
  <a href="" target="OwaPartsSample"> Inbox abc folder</A><BR>

  <!-- reference calendar -->
  <a href="" target="OwaPartsSample"> Calendar</A><BR>

  <!-- reference Public Folders/test -->
  <a href="" target="OwaPartsSample"> Public Folder test folder</A><BR>

  <!-- reference Public Folders/test team calendar -->
  <a href="" target="OwaPartsSample">Public Folder - Test Team Calendar</A><BR>

  <!-- reference Public Folders/test team calendar -->
  <a href="" target="OwaPartsSample"> Public Folder - Test Team Calendar - Weekly</A><BR>

  <!-- reference Public Folders/test team calendar -->
  <a href="" target="OwaPartsSample">Public Folder - Test Team Calendar - Monthly</A><BR>



Remember that OWA will need to authenticate you, so you should have integreated authentication enabled when you use these URLs othersie you could well get an error.

Some Limitations:

Please note that item URLs are not supported in an iFrame. The OWA URLs you can get from EWS for displaying individual items are only supported when opened in new browser windows.  Only the URLs as described in the following article are supported:

How to Use Outlook Web Access Web Parts

Please note that tasks webpart support not implemented in Exchange 2013.

OWA URLs and Identifiers:

It is extremely important to understand the different types of IDs which might appear in the URLs for OWA Web Parts.  These IDs are different for different versions of OWA.  Exchange 2013 uses EWS IDs for items and folders whereas 2010 and 2007 use their own version specific identifiers. You can use EWS's ConvertID method to convert between different identifiers - such as for converting from an EWS ID to a MAPI ID or an Exchange 2007/2010 OWA ID to an EWS ID.  Be sure to full read about ConvertID before doing any development with OWA URLs.  Be sure to note version specific information and particulars with public folders.

ConvertId operation

Converting EWS Identifiers in Exchange 2010

WebClientReadFormQueryString string and WebClientEditFormQueryString string return incorrect URLs in an Exchange Server 2013 environment
The format for OWA URLs changed in 2013; however, WebClientReadFormQueryString and WebClientEditFormQueryString don't reflect the change until you update to CU3 for 2013. 



Also see:

Microsoft support policy for the customization of Outlook Web Access for Exchange

OWA Single-sign-on support

Microsoft does not support using ISAPI extensions or filters to modify Outlook Web Access credentials on a server that is running Exchange Server

OWA Web Parts not working in 2013 - "This content cannot be displayed in a frame"

[MS-OXWSCORE]: Core Items Web Service Protocol

Exchange 2013 OWA URLs