# Unable to show Exchange "Mailbox Send On Behalf" Permission

**URL:** <https://forums.powershell.org/t/unable-to-show-exchange-mailbox-send-on-behalf-permission/22160>\
**Category:** PowerShell Help\
**Created:** [April 18, 2023, 7:41pm UTC](https://forums.powershell.org/t/unable-to-show-exchange-mailbox-send-on-behalf-permission/22160 "2023-04-18T19:41:00Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![esainfra](https://avatars.discourse-cdn.com/v4/letter/e/65b543/32.png) [@esainfra](https://forums.powershell.org/u/esainfra)\
**Post date:** [April 18, 2023, 7:41pm UTC](https://forums.powershell.org/t/unable-to-show-exchange-mailbox-send-on-behalf-permission/22160/1 "2023-04-18T19:41:00Z")

</div>

I tried to use the following script to show which user has “Send On Behalf” permission to the mailbox of “myUserID” on Exchange 2012 environment, but the result does not show the users who actually have “Send On Behalf” permission to the mailbox of “myUserID” comparing to the results from “Exchange admin center” GUI. Please advise which command/parameter to use to show the results correctly. Thanks in advance.

`Get-ADUser -identity "myUserID" | %{Get-ADPermission -Identity $_.DistinguishedName | where {$_.ExtendedRights -like "*Send*"} | ft User,AccessRights -AutoSize}`  
Here is the result which does not show the users who actually have “Send On Behalf” permission to the mailbox of “myUserID” comparing to the results from “Exchange admin center” GUI

```auto
User AccessRights   
---- ------------   
NT AUTHORITY\SELF {ExtendedRight}

```

---

<div class="post-metadata">

**Author:** ![Olaf](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/olaf/32/992_2.png) [@Olaf](https://forums.powershell.org/u/Olaf)\
**Post date:** [April 18, 2023, 7:54pm UTC](https://forums.powershell.org/t/unable-to-show-exchange-mailbox-send-on-behalf-permission/22160/2 "2023-04-18T19:54:05Z")

</div>

I googled it for you … 😉

[https://www.google.com/search?q=powershell+exchange+GrantSendOnBehalf](https://www.google.com/search?q=powershell+exchange+GrantSendOnBehalf)

Here are some of the first hits:

> **[Manage permissions for recipients in Exchange Online](https://learn.microsoft.com/en-us/exchange/recipients-in-exchange-online/manage-permissions-for-recipients#use-exchange-online-powershell-to-assign-the-send-on-behalf-permission-to-mailboxes-and-groups)**
>
> Admins can learn how to assign Full Access, Send As, and Send on Behalf permissions to mailboxes and groups in Exchange Online.

> **[Grant Send on Behalf Permissions using Powershell](https://morgantechspace.com/2015/08/powershell-grant-send-on-behalf-permissions.html)**
>
> This article shares the Powershell script to grant or set send on behalf permissions for multiple mailbox users in Exchange Online/2016/2019.

> **[Send on Behalf Permissions With Powershell](https://activedirectorypro.com/send-on-behalf-permissions-with-powershell/)**
>
> This is a guide to managing send on behalf and send as permissions with PowerShell in Office 365. In this guide you'll learn: Tip #1 – A user delegated Send As permission is not allowed to open a…

> **[Find Users with Send On Behalf Permission](https://www.slipstick.com/exchange/find-users-send-behalf-permission/)**
>
> Use PowerShell to create a list of mailboxes with Send as permissions assigned.

And BTW:

> [@esainfra](#):
>
> Exchange 2012

Something like that does not exist. 😏

> **[Exchange Server build numbers and release dates](https://learn.microsoft.com/en-us/exchange/new-features/build-numbers-and-release-dates?view=exchserver-2019)**
>
> Summary: Learn about build numbers and release dates for current and past versions of Exchange Server.

---

<div class="post-metadata">

**Author:** ![esainfra](https://avatars.discourse-cdn.com/v4/letter/e/65b543/32.png) [@esainfra](https://forums.powershell.org/u/esainfra)\
**Post date:** [April 18, 2023, 8:21pm UTC](https://forums.powershell.org/t/unable-to-show-exchange-mailbox-send-on-behalf-permission/22160/3 "2023-04-18T20:21:40Z")

</div>

Thanks Olaf for your quick response with useful links. What command/parameter to use to show the “Send As” or “Send On Behalf” permission list of mailbox “myUserID” in Exchange 2012 environment?

---

<div class="post-metadata">

**Author:** ![tonyd](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/tonyd/32/1041_2.png) [@tonyd](https://forums.powershell.org/u/tonyd)\
**Post date:** [April 18, 2023, 8:27pm UTC](https://forums.powershell.org/t/unable-to-show-exchange-mailbox-send-on-behalf-permission/22160/4 "2023-04-18T20:27:27Z")

</div>

I do believe Olaf kindly pointed out there is no such build for Exchange Server 2012. I suspect what you are really referring to is the Server OS of 2012. If that is the case, you should really think about upgrading the server as it reaches end of life soon.

> **[Windows Server 2012 and 2012 R2 reaching end of support - Microsoft Lifecycle](https://learn.microsoft.com/en-us/lifecycle/announcements/windows-server-2012-r2-end-of-support)**
>
> Announcing end of support for Windows Server 2012 and 2012 R2.

---

<div class="post-metadata">

**Author:** ![esainfra](https://avatars.discourse-cdn.com/v4/letter/e/65b543/32.png) [@esainfra](https://forums.powershell.org/u/esainfra)\
**Post date:** [April 18, 2023, 8:31pm UTC](https://forums.powershell.org/t/unable-to-show-exchange-mailbox-send-on-behalf-permission/22160/5 "2023-04-18T20:31:41Z")

</div>

Sorry my bad. It’s Exchange 2013 version 15.0 (Build 1497.2) on Windows Server 2012.

---

<div class="post-metadata">

**Author:** ![Olaf](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/olaf/32/992_2.png) [@Olaf](https://forums.powershell.org/u/Olaf)\
**Post date:** [April 18, 2023, 9:04pm UTC](https://forums.powershell.org/t/unable-to-show-exchange-mailbox-send-on-behalf-permission/22160/6 "2023-04-18T21:04:47Z")

</div>

> [@esainfra](#):
>
> It’s Exchange 2013 version 15.0 (Build 1497.2)

That’s very very very outdated as well and you run your Exchange server for more than 2 years in an unsupported state.

> [@esainfra](#):
>
> What command/parameter to use to show the “Send As” or “Send On Behalf” permission list of mailbox “myUserID” in Exchange 2012 environment?

Are the links I posted not working for you? Did you read the help on the sites? Actually it is on the first link I posted. 🤷🏼‍♂️

---

<div class="post-metadata">

**Author:** ![esainfra](https://avatars.discourse-cdn.com/v4/letter/e/65b543/32.png) [@esainfra](https://forums.powershell.org/u/esainfra)\
**Post date:** [April 18, 2023, 9:14pm UTC](https://forums.powershell.org/t/unable-to-show-exchange-mailbox-send-on-behalf-permission/22160/7 "2023-04-18T21:14:45Z")

</div>

Thanks @Olaf, thanks all for your help.

---

<div class="post-metadata">

**Author:** ![Matt](https://avatars.discourse-cdn.com/v4/letter/m/a6a055/32.png) [@Matt](https://forums.powershell.org/u/Matt)\
**Post date:** [April 19, 2023, 4:17am UTC](https://forums.powershell.org/t/unable-to-show-exchange-mailbox-send-on-behalf-permission/22160/8 "2023-04-19T04:17:31Z")

</div>

First, not to beat the dead horse or to pile on about upgrading, but if you have any pull with your organization I also strongly encourage getting on a current Windows OS and version of Exchange. In addition to typical supportability and security issues, an often less thought of reason is documentation. It is going to get harder and harder to come by information and examples for the versions you are on. Also, people who have moved on, years ago, they are going start to forget stuff and be less able to help those still on old versions. No longer used knowledge is perishable.

A prime example of what I am getting at is the links googled for you, they mostly talk about newer versions of Exchange, primarily Exchange Online and not everything you can do there is possible with Exchange 2013/2016/2019. Fortunately, for now the answer to your “Send on Behalf” question is the same for Exchange 2013 as it is for Exchange online, so the links are still useful for your core question today.

You need to use Get-Mailbox

```auto
Get-Mailbox -Identity bugs.bunny | Format-List name,GrantSendOnBehalfTo

Name : Bugs Bunny
GrantSendOnBehalfTo : {contoso/UserTestAccounts/Elmer Fudd}

```

If you want to just check the occasional request, this is all you need. If you want a script that will check all mailboxes, this will get you started. Same for if you want to manipulate data into a more usable format for your needs.

As for the cmdlets you shared in your opening post. Why did it not work? First, for “send on behalf” it was the wrong cmdlets. What you posted is usable for finding “send as”, but how you approached it has some room for improvement.

First, while using Get-ADuser will work, it is not the best choice. Primary reason, what if the AD account is not mailbox enabled? It is still checked. So not efficient and wastes processing. A small AD with just a few hundred and a decent place to run the script, not a problem. But if you have 1000s in your AD, becomes a problem. Next, the return is the same regardless of not being mailbox enabled or simply having no delegate.

```auto
User AccessRights
---- ------------
NT AUTHORITY\SELF {ExtendedRight}

```

So unless you KNOW the ID being checked does have a mailbox, on the surface it would appear to failed. But it did not.

If there is a mailbox, and it has a delegate, you get a return like this. Still room for improvement because how can you be sure “ExtenedRight” is "SendAs ?

```auto
User AccessRights
---- ------------
NT AUTHORITY\SELF {ExtendedRight}
contoso\daffy.duck {ExtendedRight}

```

If you use Get-Mailbox, you are able to be more efficent and be sure you are only checking mailboxes.

```auto
Get-Mailbox -Identity bugs.bunny | Get-ADPermission | Where-Object { $_.ExtendedRights.rawidentity -like "*send*" } |ft user,extendedrights

```

Returns

```auto
User ExtendedRights
---- --------------
NT AUTHORITY\SELF {Send-As}
contoso\daffy.duck {Send-As}

```

More useful, more efficient. But not complete if you want to check more than one mailbox at a time.

The “Send As” is also an example of where things are going to slowly become harder to find if you have not learned how to find this already. The example for Exchange online use different cmdlets not available to Exchange on prem.

---

<div class="post-metadata">

**Author:** ![esainfra](https://avatars.discourse-cdn.com/v4/letter/e/65b543/32.png) [@esainfra](https://forums.powershell.org/u/esainfra)\
**Post date:** [April 19, 2023, 1:02pm UTC](https://forums.powershell.org/t/unable-to-show-exchange-mailbox-send-on-behalf-permission/22160/9 "2023-04-19T13:02:36Z")

</div>

Wow, thank you Matt. Deeply appreciate your insightful response. Thank every one for your help/response. I learn more than I expected when I posted my initial question. Thanks all.

---

<div class="post-metadata">

**Author:** ![dotnVo](https://avatars.discourse-cdn.com/v4/letter/d/4af34b/32.png) [@dotnVo](https://forums.powershell.org/u/dotnVo)\
**Post date:** [May 16, 2024, 8:14pm UTC](https://forums.powershell.org/t/unable-to-show-exchange-mailbox-send-on-behalf-permission/22160/10 "2024-05-16T20:14:58Z")

</div>


