Skip to main content

OWA Customization Example using Maps and StreetView with a Custom Contact Type and integrating EWS within OWA Custom Forms

For those brave souls who attended my MVP theatre talk on Friday here’s the OWA customization I demo'ed. The basics of creating custom forms are documented in the Exchange SDK . But putting this together can be a little tricky so let’s go though some of the basis’s step by step.

Firstly I wanted to create a custom form that would display a map of the contacts address information and also a Street-view of the same address information using Google’s new Streetview features that was recently released for Australia. For this I created some contact items with a Message class of IPM.Contact.Map.

To start the process of creating an OWA custom form for these items firstly you need to create a folder under the Forms directory on your CAS server. You should have a directory structure similar to this on your CAS server Program Files\Microsoft\Exchange Server\ClientAccess\Owa which represents the root of the OWA ASP.NET application. Under this directory is the Forms directory which is where you first need to create a folder to hold your customization e.g. I’ve created one called maps

Next there needs to be at least one file that goes in that directory which is the registry.xml file that contains the definition for your custom forms and what actions and pages to open. The actually content pages for your custom form can be located elsewhere but for my customization I’ve just used this folder which means that my pages are going to run as part of the OWA application and use the authentication from the OWAapplication pool. The Registry.XML for my OWA customization looks like

<ApplicationElement Name="Item"><ElementClass
Action="Open" Form="Map.aspx"/><Mapping
Action="Preview" Form="Map.aspx"/><Mapping
Action="Print" Form="Map.aspx"/></ElementClass>

This basically means that whenever anybody opens/Previews or trys to print items with a MessageClass of IPM.Contact.Map the file map.aspx will be used. At this stage you should pause and consider the application pool this custom form is going to be running under. Writing poorly performing code that runs under the OWA application pool is going to make OWA performance poor for everybody using the server. This is something you need to give serious consideration before putting any OWA customization into production.

Next comes the tricky part because I also wanted to use Exchange Web Service in my custom forms I had to have some way of loading the EWS proxy objects. Because I wasn’t creating a separate ASPX application for my pages and I didn’t want to put a class library containing the EWS proxy objects in the GAC I dropped a class library containing the proxy objects into the bin folder for the OWA application eg Microsoft\Exchange Server\ClientAccess\Owa\Bin. I used my EWSUtil.dll but you could create your own using WDSL.exe etc. Once I could now reference the EWS proxy objects in my ASPX code I could get on with the job of coding what I wanted my form to do.

But before that I had to address one final issue which was security because I was going to be making a request to EWS from within another webpage I need to ensure that the security context used to make this request was that of the users that was logged onto OWA. To do this impersonation needed to be set as per within the code behind file.

Okay so the final task now is just to copy the map.aspx and map.aspx.cs file into the map directory in the forms directory and then do an IISReset for Exchange to pick up the changes. If you want to see if Exchange has loaded you custom form check the application event log for an event

The code itself in the map.aspx.cs file does the following tasks firstly it takes the OWAid and Email address from the querystrings OWA passes to custom form. This information is then used to do a EWS convertID to convert that OWAid into a EWSid so that contact Item can be open in EWS using a GetItem call and the address properties can then be accessed. Next the address details are geocoded meaning it gets the longitude and latitude values for the address which are then used to send a request of to Google Maps for the Map and Street View of this address and then the result are display in couple of divs on the aspx page. The final result looks something like this to use Google Street View you need to register for you own API key (which is free) and change the following line

string gkGoogleKey = "abc123";

I’ve put a download of the aspx and registry.xml here the customization in action looks like this (for all those blues brothers fans)

Popular posts from this blog

Downloading a shared file from Onedrive for business using Powershell

I thought I'd quickly share this script I came up with to download a file that was shared using One Drive for Business (which is SharePoint under the covers) with Powershell. The following script takes a OneDrive for business URL which would look like This script is pretty simple it uses the SharePoint CSOM (Client side object Model) which it loads in the first line. It uses the URI object to separate the host and relative URL which the CSOM requires and also the SharePointOnlineCredentials object to handle the Office365 SharePoint online authentication. The following script is a function that take the OneDrive URL, Credentials for Office365 and path you want to download the file to and downloads the file. eg to run the script you would use something like ./spdownload.ps1 '

A walk-though using the Graph API Mailbox reports in Powershell

Quite recently the Reporting side of the Graph API has moved in GA from beta, there are quite a number of reports that can be run across various Office365 surfaces but in this post I'm going to focus on the Mailbox related ones. Accessing Office365 Reports using Powershell is nothing new and has been available in the previous reporting endpoint however from the end of January many of these cmdlets are now being depreciated in favour of the Graph API . Prerequisites  In comparison to using the Remote PowerShell cmdlets where only the correct Office365 Admin permissions where needed, to use the new Graph API reports endpoint you need to use OAuth for authentication so this requires an Application Registration  that is then given the correct oAuth Grants to use the Reports EndPoin

How to test SMTP using Opportunistic TLS with Powershell and grab the public certificate a SMTP server is using

Most email services these day employ Opportunistic TLS when trying to send Messages which means that wherever possible the Messages will be encrypted rather then the plain text legacy of SMTP.  This method was defined in RFC 3207 "SMTP Service Extension for Secure SMTP over Transport Layer Security" and  there's a quite a good explanation of Opportunistic TLS on Wikipedia .  This is used for both Server to Server (eg MTA to MTA) and Client to server (Eg a Message client like Outlook which acts as a MSA) the later being generally Authenticated. Basically it allows you to have a normal plain text SMTP conversation that is then upgraded to TLS using the STARTTLS verb. Not all servers will support this verb so if its not supported then a message is just sent as Plain text. TLS relies on PKI certificates and the administrative issue s that come around certificate management like expired certificates which is why I wrote th
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.