Skip to main content

How to Like\Unlike an Item using EWS in Exchange Online

Likes and Mentions are a new feature in Exchange Online (in OWA) that was introduced late last year in First Release for Office365. With the focused Inbox now being rolled out to replace clutter these are some of the new social user curation type features that could change the user experience (hopefully for the better) in the coming years. While none of these features are new to those people using other Social platforms like facebook, twitter etc they do offer a world of new possibilities to those that have a little imagination.

In this post I'm going to look at how you can Like an item using Exchange Web Services eg

Currently there is no real documentation on the use of Likes in any API or how they are delivered in Exchange Online so care should be taken as this may mean the feature is subject to change in any of the future service updates.

Versioning your Requests

To use likes fully you need to make sure you version your EWS requests (which involves setting the ServerRequestVersion in the SOAP header) to V2015_10_05 or higher.  The Like information is returned by Exchange as a Strongly Type property in EWS (LikeType). If you look at a Response that includes the Like information in the SOAP response you should see both Like and LikePreview returned eg 

<t:Likes>
  <t:Like>
    <t:Id>150bb06c-1c9a-4ac2-8b55-8cf15854b555</t:Id>
    <t:CreatedBy>
      <t:Name>Glen Scales</t:Name>
      <t:EmailAddress>gscales@datarumble.com</t:EmailAddress>
      <t:ExternalObjectId>150bb06c-1c9a-4ac2-8b55-8cf15854b555</t:ExternalObjectId>
    </t:CreatedBy>
    <t:CreatedDateTime>2016-08-28T10:26:40.299Z</t:CreatedDateTime>
    <t:ServerCreatedDateTime>2016-08-28T10:26:40.299Z</t:ServerCreatedDateTime>
  </t:Like>
</t:Likes>
<t:LikesPreview>
  <t:LikeCount>1</t:LikeCount>
  <t:IsLiked>true</t:IsLiked>
  <t:Likers>
    <t:Name>Glen Scales</t:Name>
    <t:EmailAddress>gscales@datarumble.com</t:EmailAddress>
    <t:RoutingType>SMTP</t:RoutingType>
    <t:MailboxType>Mailbox</t:MailboxType>
    <t:ExternalObjectId>150bb06c-1c9a-4ac2-8b55-8cf15854b555</t:ExternalObjectId>
  </t:Likers>
</t:LikesPreview>
<t:AtAllMention>false</t:AtAllMention>

If you have the latest proxy objects from the Exchange Online WSDL then you should see the Likes and LikePreview property collections in the ItemType Class. In the latest EWS Managed API from github https://github.com/OfficeDev/ews-managed-api only the Likes class is currently available.

Liking an Item (Unsupported)

The EWS LikeItem operation currently has no definition in the Services.WSDL so liking an Item via EWS is currently unsupported. However you can still use the operation as long as you construct the request using Raw SOAP message eg a request to like or unlike and item using EWS look like

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
               xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types">
  <soap:Header>
    <t:RequestServerVersion Version="V2015_10_05"/>
  </soap:Header>
  <soap:Body xmlns="http://schemas.microsoft.com/exchange/services/2006/messages">
    <LikeItem>
      <ItemId Id="AAM.." ChangeKey="CQA.."/>
      <IsUnlike>false</IsUnlike>
 </LikeItem>
  </soap:Body>
</soap:Envelope>

As this is an unsupported operation if you do something like try to like the same item twice you will get a 500 error rather then a nice SOAP based error response. I've put together a scrip that allows you to search for an Item via subject and like or unlike it using EWS. I've put this up on GitHub here https://github.com/gscales/Powershell-Scripts/blob/master/EWSLIkeMessage.ps1
Labels:

Popular posts from this blog

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

If your getting an error such as Application is over its MailboxConcurrency limit while using the Microsoft Graph API this post may help you understand why. Background   The Mailbox  concurrency limit when your using the Graph API is 4 as per https://docs.microsoft.com/en-us/graph/throttling#outlook-service-limits . This is evaluated for each app ID and mailbox combination so this means you can have different apps running under the same credentials and the poor behavior of one won't cause the other to be throttled. If you compared that to EWS you could have up to 27 concurrent connections but they are shared across all apps on a first come first served basis. Batching Batching in the Graph API is a way of combining multiple requests into a single HTTP request. Batching in the Exchange Mail API's EWS and MAPI has been around for a long time and its common, for email Apps to process large numbers of smaller items for a variety of reasons.  Batching in the Graph is limited to a m
Read more

Sending a Message in Exchange Online via REST from an Arduino MKR1000

This is part 2 of my MKR1000 article, in this previous post  I looked at sending a Message via EWS using Basic Authentication.  In this Post I'll look at using the new Outlook REST API  which requires using OAuth authentication to get an Access Token. The prerequisites for this sketch are the same as in the other post with the addition of the ArduinoJson library  https://github.com/bblanchon/ArduinoJson  which is used to parse the Authentication Results to extract the Access Token. Also the SSL certificates for the login.windows.net  and outlook.office365.com need to be uploaded to the devices using the wifi101 Firmware updater. To use Token Authentication you need to register an Application in Azure https://msdn.microsoft.com/en-us/office/office365/howto/add-common-consent-manually  with the Mail.Send permission. The application should be a Native Client app that use the Out of Band Callback urn:ietf:wg:oauth:2.0:oob. You need to authorize it in you tenant (eg build a small ap
Read more

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  https://en.wikipedia.org/wiki/Opportunistic_TLS .  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
Read more
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.