Integrating Outlook Web Access (OWA) and SharePoint 2013

SharePoint 2007 and SharePoint 2010 had a series of Web Parts dedicated to surfacing and interacting with an Exchange mail account directly from a page in SharePoint.

Overview of the Outlook Web Access Web Parts (for SharePoint 2007 and 2010)

If you are not familiar with the functionality here’s a quick overview (this info is taken from the official Microsoft help documentation

There are five Outlook Web Access Web Parts. These can be used with Microsoft Exchange Server version 2003 to 2007:

  • My Calendar
  • My Contacts
  • My Tasks
  • My Inbox
  • My Mail Folder

These Web Parts are most useful for your My Site, because only you (or someone who can log into your Exchange e-mail account) will be able to see the information from your folders. If you put one of these Web Parts on a shared site, other users will see the Outlook Web Access logon screen in the Web Part.

My Inbox Web Part on My Site

Each Web Part displays the information from a folder in your email account, so you can choose the information you want to show on your site. The Web Parts make it easy to show specific information, such as tasks, without showing all of your Outlook information. If you want to have full Outlook functionality on your SharePoint site, you can use a Page View Web Part linked to the URL for your Outlook Web Access server.

All of the Outlook Web Access Web Parts provide two-way communication with your Exchange Server e-mail account: Changes you make in a Web Part appear in Outlook.

What’s the Story with OWA integration in SharePoint 2013?

I was somewhat surprised when SharePoint 2013 arrived and all the Outlook Web Access web parts were missing. Had this been an oversight by Microsoft and they would reappear again in a cumulative update for SharePoint? It appears not.

On further digging Microsoft actually dropped support for the OWA web parts (in SharePoint 2010) if your mail was hosted in Exchange Online (Office 365). From the Exchange Online Service Description document:

Exchange Online supports Outlook Web App Web Parts via the PageViewer control in Microsoft SharePoint Online and Microsoft SharePoint Server, or via manually configured URLs. Built-in SharePoint OWA Web Part controls will not work against Exchange Online

The statement above alludes to an alternate method using the Page Viewer control (which to be honest I’d prefer to the OWA web parts which didn’t have the full functionality of the OWA interface). The idea behind using the Page Viewer web part is that OWA is just a web interface to your Exchange account served up at known URLs. So just wrap these in a iframe (Page Viewer web part) and you will have your full OWA interface embedded inside a SharePoint page. For a step by step guide of how to setup the Page View control to connect to Exchange Online (OWA) take a look at this article by Jesper_Osgaard.

So fast forward to SharePoint 2013, can we still use the Page Viewer web part technique? My experience so far has yielded mixed results.

More often than not the Page Viewer technique gets tripped up with security issues. I think the underlying issue is that an Internet Explorer session cannot handle authenticating with multiple domains at the same time and it just so happens SharePoint Online and Exchange Online reside in different domains.

This isn’t to say it flat out doesn’t work. Here’s a screenshot to prove it (no smoke and mirrors or Photoshop involved I promise). But I just didn’t find it stable enough to recommend it as a viable solution.



On reflection it would seem that Microsoft wasn’t able to iron out the complexities of integrating OWA content and SharePoint content in the same Internet Explorer session. If they could, then surely that would have provided better integration for the native SharePoint Site Mailboxes that were introduced in SharePoint 2013 (Exchange 2013). When a SharePoint Site Mailbox is provisioned, a mailbox is created in Exchange (for the SharePoint site) and a link is placed on the left navigation of the SharePoint site. When you click on the link you don’t get the mailbox content embedded in the SharePoint page (as you might expect and have hoped for!). Instead it launches a new Internet Explorer window (new IE session that can authenticate with a different domain) and opens the OWA URL directly to the mailbox. There’s essential no integration with the SharePoint UI other than a URL link.


About Cameron Dwyer

Architect and developer at OnePlace Solutions. Passionate about delivering compelling solutions on the Office 365/SharePoint platform. Addicted to coffee.

Posted on October 30, 2013, in Exchange, Office 365, Outlook, SharePoint and tagged , , , , , , . Bookmark the permalink. 15 Comments.

  1. Hi
    I just would like to let you know that you can have the outlook web parts

    do below steps:

    1) Go to Web part Gallery.

    2) On Web part Gallery page, Click Files-> New Document -> New in the ribbon.

    3) On New web part page(NewDWp.aspx), look for Microsoft.SharePoint.Portal.WebControls.OWAInboxPart , Select the web part and click on populate gallery.

    Now, you can go to your SharePoint page where you want to add web part, click on Add web part. Under Miscellaneous Category, you will see OWAInbox web part.

    Similarly, you can add OWA: Calendar, Task web parts etc.



  2. Dear Cameron,

    please, after using the owaInboxPart I have an error : This content cannot be displayed in a frame
    do you have any idea


  3. Dear Cameron,

    please, after using the owaInboxPart , How to bypass the authentication and open user inbox direct without entering username and password in sharepoint 2007 or any version ?

    I want to open my Inbox in sharepoint without entering username and password

    (I want to bypass entering of user information “username and password” as it is entered when I opened the Sharepoint site) for all the users.


    • Ensure the owa site is a trusted site in IE. Also ensure that the user has cached their credentials. You really need to get to the point that a user can go to the owa site directly in a browser and be logged in automatically. Then addressing via SharePoint should let the user to straight through. I always found that authentication and security issues plagued getting mail exposed on a SharePoint site. Now with Office 365 with a unified user identity across the SharePoint and Mail services the issue has largely been removed.


  4. Cameron,

    Excellent article. Very well organized content. Clean format.

    I have a bit different scenario- We have an on premise SharePoint 2013 farm. I need to send a column value from a list form to Exchange 2010 public calendar using SharePoint 2010/2013 workflow.

    I understand and am aware that public folders are going away but for now I do need to send list data to these Exchange 2010 public calendar.

    Any suggestions?


    • If I understand you correctly you need to create a calendar entry in an Exchange public calendar from a SharePoint workflow. I assume you are able to get a handle on the SharePoint item in the workflow and read the required column values and the main issue is how to create the calendar entry? Unfortunately this is not something I’ve tried to do in the past. I’m not aware of a way to simply send something to an address that will have the item appear in the calendar (although it may be possible). In my experience you could achieve what you are after using Exchange Web Services (EWS). Your workflow would need to programmatically call EWS and create the calendar entry.

      I hope this helps.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: