Skip to main content

How To Series Sample 7 : Reverse Delegate Permissions and Rights Report

The script expands on part 5 of the how to series and produces a reverse permission report of the delegates of all Mailboxes on a server or within a Exchange Org or Exchange Online tenant. This is to help show for a particular delegate what mailboxes that they have been given delegate rights to and if they can see private Items and do they receive Meeting forwards. This script is designed to be run from within a Remote Powershell session that is already connected to your Exchange 2010 org (or from a Exchange Online/Office365 remote Powershell session).


 It uses Get-Mailbox to get all the mailboxes in your org and then it uses the EWS Managed API to connect to each mailbox and query the delegates. It then produces a CSV file that looks like



If you want to understand how it works have a read of the How To Series posts and hopefully you should be able to work out how to customize it if you need to for your own environment. The Script as posted uses EWS Impersonation

If you want to customize which mailboxes it reports on then just change the Get-Mailbox line

Get-Mailbox -ResultSize Unlimited | ForEach-Object{  

eg if you want to limit to only checking one server you could use

Get-Mailbox -ResultSize Unlimited -Server servernameblah | ForEach-Object{

You could do similar with other filter properties such as Database or OU

I've posted a downloadable copy of the script here the script itself look like

  1. ## EWS Managed API Connect Module Script written by Glen Scales  
  2. ## Requires the EWS Managed API and Powershell V2.0 or greator  
  3. $rptArray = New-Object System.Collections.ArrayList  
  4. ## Load Managed API dll  
  5. Add-Type -Path "C:\Program Files\Microsoft\Exchange\Web Services\1.1\Microsoft.Exchange.WebServices.dll"  
  6.   
  7. ## Set Exchange Version  
  8. $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP1  
  9.   
  10. ## Create Exchange Service Object  
  11. $service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)  
  12.   
  13. ## Set Credentials to use two options are availible Option1 to use explict credentials or Option 2 use the Default (logged On) credentials  
  14.   
  15. #Credentials Option 1 using UPN for the windows Account  
  16. $psCred = Get-Credential  
  17. $creds = New-Object System.Net.NetworkCredential($psCred.UserName.ToString(),$psCred.GetNetworkCredential().password.ToString())  
  18. $service.Credentials = $creds      
  19.   
  20. #Credentials Option 2  
  21. #service.UseDefaultCredentials = $true  
  22.   
  23. ## Choose to ignore any SSL Warning issues caused by Self Signed Certificates  
  24.   
  25. [System.Net.ServicePointManager]::ServerCertificateValidationCallback = {$true}  
  26.   
  27.   
  28.   
  29. function CovertBitValue($String){  
  30.     $numItempattern = '(?=\().*(?=bytes)'  
  31.     $matchedItemsNumber = [regex]::matches($String$numItempattern)   
  32.     $Mb = [INT64]$matchedItemsNumber[0].Value.Replace("(","").Replace(",","")  
  33.     return [math]::round($Mb/1048576,0)  
  34. }  
  35.   
  36.   
  37. Get-Mailbox -ResultSize Unlimited | ForEach-Object{   
  38.     $MailboxName = $_.PrimarySMTPAddress.ToString()  
  39.     "Processing Mailbox : " + $MailboxName  
  40.     if($service.url -eq $null){  
  41.         ## Set the URL of the CAS (Client Access Server) to use two options are availbe to use Autodiscover to find the CAS URL or Hardcode the CAS to use  
  42.   
  43.         #CAS URL Option 1 Autodiscover  
  44.         $service.AutodiscoverUrl($MailboxName,{$true})  
  45.         "Using CAS Server : " + $Service.url   
  46.           
  47.         #CAS URL Option 2 Hardcoded  
  48.         #$uri=[system.URI] "https://casservername/ews/exchange.asmx"  
  49.         #$service.Url = $uri    
  50.     }  
  51.   
  52.     $service.ImpersonatedUserId = new-object Microsoft.Exchange.WebServices.Data.ImpersonatedUserId([Microsoft.Exchange.WebServices.Data.ConnectingIdType]::SmtpAddress, $MailboxName)  
  53.     $delegates = $service.getdelegates($MailboxName,$true)    
  54.     foreach($Delegate in $delegates.DelegateUserResponses){    
  55.         $rptObj = "" | select Delegate,Mailbox,Inbox,Calendar,Contacts,Tasks,Notes,Journal,MeetingMessages,ViewPrivateItems    
  56.         $rptObj.Mailbox = $MailboxName  
  57.         $rptObj.Delegate = $Delegate.DelegateUser.UserId.PrimarySmtpAddress    
  58.         $rptObj.Inbox = $Delegate.DelegateUser.Permissions.InboxFolderPermissionLevel    
  59.         $rptObj.Calendar = $Delegate.DelegateUser.Permissions.CalendarFolderPermissionLevel    
  60.         $rptObj.Contacts = $Delegate.DelegateUser.Permissions.ContactsFolderPermissionLevel    
  61.         $rptObj.Tasks = $Delegate.DelegateUser.Permissions.TasksFolderPermissionLevel    
  62.         $rptObj.Notes = $Delegate.DelegateUser.Permissions.NotesFolderPermissionLevel    
  63.         $rptObj.Journal = $Delegate.DelegateUser.Permissions.JournalFolderPermissionLevel    
  64.         $rptObj.ViewPrivateItems = $Delegate.DelegateUser.ViewPrivateItems    
  65.         $rptObj.MeetingMessages = $Delegate.DelegateUser.ReceiveCopiesOfMeetingMessages   
  66.         [Void]$rptArray.Add($rptObj)  
  67.             
  68.     }    
  69. }  
  70. $rptArray | Sort-Object Delegate | Export-Csv -Path c:\temp\ReverseDelegateReport.csv -NoTypeInformation  


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

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

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