Skip to main content

Accessing the NON_IPM_Subtree folders in Exchange Web Services

One important and potentially frustrating point for anybody who wants to set permissions on the calendar folder in a mailbox with any Exchange API that allows you to modify the folder DACL’s is that you also need add the same ACE your adding (or modifying) to the FreeBusy Data folder which is one the NON_IPM_Subtree Root folders in a mailbox explained in this KB. Exchange Web Services is no exception to this rule and accessing the NON_IPM_Subtree folders isn’t as straight forward as normal mailbox folders but here’s a method for accessing the freebusy folder and modifying the DACL.

The highest level you can get to easily with EWS is the DistinguishedFolderIdNameType.msgfolderroot which in the basically the Root of the IPM_Subtree if you get the parentfolderID of this folder using a GetFolder Operation this will represent the Root of the NON_IPM_Subtree you can then use this ID in FindFolder operation to discover all the NON_IPM_Subtree folder in this case I’ve used a restriction to find the Free Busy folder based on the folderName. Then once you have the FolderID of the Free Busy folder you can Get and Set the ACL via the normal GetFolder and Update Folder operations.

Okay enough said I’ve put a download of the code here the code itself looks like

PermissionSetType fbPermissionSet = new PermissionSetType();
BaseFolderIdType[] bfBaseFolderArray = new BaseFolderIdType[1];
DistinguishedFolderIdType dfRootFolderID = new DistinguishedFolderIdType();
if (intebExchangeServiceBinding.ExchangeImpersonation == null)
{
EmailAddressType mbMailbox = new EmailAddressType();
mbMailbox.EmailAddress = emEmailAddress;
dfRootFolderID.Mailbox = mbMailbox;
}
dfRootFolderID.Id = DistinguishedFolderIdNameType.msgfolderroot;
bfBaseFolderArray[0] = dfRootFolderID;
ListrfRootFolder = GetFolder(bfBaseFolderArray);
BaseFolderIdType[] bfIdArray = new BaseFolderIdType[1];
bfIdArray[0] = rfRootFolder[0].ParentFolderId;
List fbFolder = FindFolder(bfIdArray, "Freebusy Data");
FolderResponseShapeType frFolderRShape = new FolderResponseShapeType();
frFolderRShape.BaseShape = DefaultShapeNamesType.AllProperties;
GetFolderType gfRequest = new GetFolderType();
gfRequest.FolderIds = new BaseFolderIdType[1] { fbFolder[0].FolderId };
intFreeBusyFolderID = fbFolder[0].FolderId;
gfRequest.FolderShape = frFolderRShape;
GetFolderResponseType gfGetFolderResponse = intebExchangeServiceBinding.GetFolder(gfRequest);
FolderType cfCurrentFolder = null;


if (gfGetFolderResponse.ResponseMessages.Items[0].ResponseClass == ResponseClassType.Success)
{
cfCurrentFolder = (FolderType)((FolderInfoResponseMessageType)gfGetFolderResponse.ResponseMessages.Items[0]).Folders[0];
fbPermissionSet = cfCurrentFolder.PermissionSet;
}

public List GetFolder(BaseFolderIdType[] biArray)
{
try
{
List rtReturnList = new List();
GetFolderType gfGetfolder = new GetFolderType();
FolderResponseShapeType fsFoldershape = new FolderResponseShapeType();
fsFoldershape.BaseShape = DefaultShapeNamesType.AllProperties;
DistinguishedFolderIdType rfRootFolder = new DistinguishedFolderIdType();
gfGetfolder.FolderIds = biArray;
gfGetfolder.FolderShape = fsFoldershape;
GetFolderResponseType fldResponse = intebExchangeServiceBinding.GetFolder(gfGetfolder);
ArrayOfResponseMessagesType aormt = fldResponse.ResponseMessages;
ResponseMessageType[] rmta = aormt.Items;
foreach (ResponseMessageType rmt in rmta)
{
if (rmt.ResponseClass == ResponseClassType.Success)
{
FolderInfoResponseMessageType firmt;
firmt = (rmt as FolderInfoResponseMessageType);
BaseFolderType[] rfFolders = firmt.Folders;
rtReturnList.Add(rfFolders[0]);
}
else
{
//Deal with Error
}

}
return rtReturnList;
}
catch (Exception exException)
{
Console.WriteLine(exException.ToString());
throw new GetFolderException("Get Folder Exception");
}

}
public List FindFolder(BaseFolderIdType[] biArray, String fnFolderName)
{
try
{
List rtReturnList = new List();
FindFolderType fiFindFolder = new FindFolderType();
fiFindFolder.Traversal = FolderQueryTraversalType.Shallow;
FolderResponseShapeType rsResponseShape = new FolderResponseShapeType();
rsResponseShape.BaseShape = DefaultShapeNamesType.AllProperties;
fiFindFolder.FolderShape = rsResponseShape;
fiFindFolder.ParentFolderIds = biArray;
RestrictionType ffRestriction = new RestrictionType();
IsEqualToType ieToType = new IsEqualToType();
PathToUnindexedFieldType fnFolderNameField = new PathToUnindexedFieldType();
fnFolderNameField.FieldURI = UnindexedFieldURIType.folderDisplayName;

FieldURIOrConstantType ciConstantType = new FieldURIOrConstantType();
ConstantValueType cvConstantValueType = new ConstantValueType();
cvConstantValueType.Value = fnFolderName;
ciConstantType.Item = cvConstantValueType;
ieToType.Item = fnFolderNameField;
ieToType.FieldURIOrConstant = ciConstantType;
ffRestriction.Item = ieToType;
fiFindFolder.Restriction = ffRestriction;

FindFolderResponseType findFolderResponse = intebExchangeServiceBinding.FindFolder(fiFindFolder);
ResponseMessageType[] rmta = findFolderResponse.ResponseMessages.Items;
foreach (ResponseMessageType rmt in rmta)
{
if (((FindFolderResponseMessageType)rmt).ResponseClass == ResponseClassType.Success)
{
FindFolderResponseMessageType ffResponse = (FindFolderResponseMessageType)rmt;
if (ffResponse.RootFolder.TotalItemsInView > 0)
{
foreach (BaseFolderType suSubFolder in ffResponse.RootFolder.Folders)
{
rtReturnList.Add(suSubFolder);
}

}
else
{
throw new FindFolderException("Find Folder Exception No Folder");
}
}
else
{
throw new FindFolderException("Find Folder Exception Seach Error");
}

}

return rtReturnList;
}
catch (Exception exException)
{
Console.WriteLine(exException.ToString());
throw new FindFolderException("Get Folder Exception");
}
}

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

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

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
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.