How To Setup Office 365 “Send As”

On 27/05/2012, in Office 365, by Cromby

This perplexing subject has a lot of bits and pieces all over the web but no body’s blog’s or help’s or comments on the subject spelled out how this is done well enough for the general public or even tech savvy geek to understand how to do it. So after having researched and accomplished it I decided it should be spelled out here so that there is somewhere to get it all in one place. I admit that I’m not that good at explaining things but I’ll give it my best effort.

The purpose of this article is to explain how to setup the “Send As” feature in Microsoft’s Office 365 web services. This is for when you would like an employee to be able to send an email for you so that it is as if you sent it yourself. You would of course only allow this kind of privilege only to someone you trust to act on your behalf in sending email for you. Anyone who replies to one of these emails sent on your behalf would be sending it directly to your email address and not the trustee because to the original recipient, they don’t know that you didn’t really send it and that your trustee did. This is different than “Send on behalf of” where you would know that the trustee sent it.

Step 1:
To start, you need to have Windows PowerShell installed. Preferably 2.0 but version 1.0 works as well. If you have Windows 7 or 2008 Server R2 then you should already have it. If not, then get it.

Step 2:
Open PowerShell with the Administrator account by going to the main menu. The path to it is “All Programs\Accessories\Windows PowerShell\Windows PowerShell (x86) or Windows PowerShell. It doesn’t matter which one. Right Click it and select “Run As Administrator”.
At the command line type or paste: (right click to paste in the command line shell)
press enter to execute. It should say “RemoteSigned”. If not then type or paste:
set-executionpolicy remotesigned
and press enter. It will show the following;

Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose
you to the security risks described in the about_Execution_Policies help topic. Do you want to change the execution
[Y] Yes [N] No [S] Suspend [?] Help (default is "Y"):

Type “Y” and press enter to change the Execution Policy to RemoteSigned.
This makes changes to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell in the registry.
Now we’re ready for the good stuff.

Step 3:
In the command line type or paste:
$LiveCred = Get-Credential

This will open a logon dialog “Windows PowerShell Credential Request”. Enter the email address of a user account that is an administrator for your Office 365 account and its password. This stores these credentials for doing the “Send As’ setup.
$LiveCred dialog window

Step 4:
Type or paste this in the command line
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri -Credential $LiveCred -Authentication Basic -AllowRedirection

Step 5:
(If you installed the “Microsoft Online Services Module” then you can skip this step. If you’re not sure then do it anyhow.)
Type or paste in the command line
Import-PSSession $Session

This downloads the scripts for administrating Office 365 from PowerShell.

Step 6:
Now to set your permissions for a specific user. Type the folowing but substitute your “Send As” account and the trustee account.
Add-RecipientPermission -AccessRights SendAs -Trustee
Like this:
Add-RecipientPermission -AccessRights SendAs -Trustee

Step 7:
When your done you can end the session by typing or pasting
Remove-PSSession $Session

Also these commands are useful
View Send As permissions :
Get-RecipientPermission - Trustee

View Send As permission on a specific recipient :

View all Send As permissions you’ve configured in your organization :
Get-RecipientPermission | where {($_.Trustee -ne 'nt authority\self') -and ($_.Trustee -ne 'null sid')}

Revoke Send As permission :
Remove-RecipientPermission -AccessRights SendAs -Trustee

For more detail see the following:
Single Sign-on :


Leave a Reply