Skip to main content

Looking for your questions on Exchange extensibility for MEC

This blog has been a little quiet over the last month as I've been putting all my efforts into my MEC Talk which is now only a week away, but I should have a number of new posts soon after that.

In addition to this talk I am going to be moderating the Experts Unplugged: Exchange Extensibility session at MEC. If your interested in Exchange extensibility in any way this should be a really good session to attend, as we will be able to discuss exchange extensibility as a whole across EWS, Transport, Apps and Powershell and not just the individual components. The Panel for this session is made up of Subject matter experts from Microsoft who are responsible for designing,building, and directing the future of extensibility in Exchange. So this will be great opportunity for the community to come together and discuss where we are at with extensibility, some of new exciting stuff in SP1 and where we are going in the future. More importantly its your opportunity if you are attending MEC to give some feedback to the panel.

If you aren't able to get to MEC or you can't get to this session and you have a really good question (or piece of feedback) or something you would really like to see in Exchange extensibility. Please Email me glenscales@yahoo.com or post your question as a comment on this blog entry and I'll try to include this in the discussion and get back to you with an answer of some sort. If you are going to attend this session and are a bit shy about asking questions you can also let me know your questions.

If you haven't heard already Exchange 2013 SP1 both (onPrem and Online) has been released bearing extensibility gifts, here are some pre reading links for some of the new SP1 bits and new Exchange Online bits that are worth reading on your way to MEC.

Compose Apps
EWS what's new in 2013 SP1 (and the new EWS Managed API 2.1)
(Exchange On-line and the new OData API)
Authentication and authorization using Common Consent Framework







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 Gr...
Read more

Exporting and Uploading Mailbox Items using Exchange Web Services using the new ExportItems and UploadItems operations in Exchange 2010 SP1

Two new EWS Operations ExportItems and UploadItems where introduced in Exchange 2010 SP1 that allowed you to do a number of useful things that where previously not possible using Exchange Web Services. Any object that Exchange stores is basically a collection of properties for example a message object is a collection of Message properties, Recipient properties and Attachment properties with a few meta properties that describe the underlying storage thrown in. Normally when using EWS you can access these properties in a number of a ways eg one example is using the strongly type objects such as emailmessage that presents the underlying properties in an intuitive way that's easy to use. Another way is using Extended Properties to access the underlying properties directly. However previously in EWS there was no method to access every property of a message hence there is no way to export or import an item and maintain full fidelity of every property on that item (you could export the...
Read more

EWS Create Mailbox folder Powershell module for Exchange and Office365 Mailboxes

This is a rollup post for a couple of scripts I've posted in the past for creating folders using EWS in an Exchange OnPremise or Exchange online Cloud mailbox. It can do the following Create a Folder in the Root of the Mailbox Create-Folder -Mailboxname mailbox@domain.com -NewFolderName test Create a Folder as a SubFolder of the Inbox Create-Folder -Mailboxname mailbox@domain.com -NewFolderName test -ParentFolder '\Inbox' Create a Folder as a SubFolder of the Inbox using EWS Impersonation Create-Folder -Mailboxname mailbox@domain.com -NewFolderName test -ParentFolder '\Inbox' -useImpersonation Create a new Contacts Folder as a SubFolder of the Mailboxes Contacts Folder Create-Folder -Mailboxname mailbox@domain.com -NewFolderName test -ParentFolder '\Contacts' -FolderClass IPF.Contact Create a new Calendar Folder as a SubFolder of the Mailboxes Calendar Folder Create-Folder -Mailboxname mailbox@domain.com -NewFolderName test -Parent...
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.