Scenario 1.1 – Assign Send As Permissions to user X on user Y Mailbox.

Scenario description

• Suzan is John personal assistant.
• We would like to assign Send As permissions to Suzan (the Trustee) on John’s mailbox so, she will be able to send an E-mail message using the John E-mail address.

Implementation

We will use the PowerShell command “Add-RecipientPermission”

Scenario 1.2 – Assign Send As Permissions to user X on all users Mailbox’s (Bulk Mode)

Scenario description

• We would like to grant the Send As Permissions to a user named John.
• The Send As permission will be assigned to a list of recipients.
• The Send As permission will be assigned separately, for each recipient on the list.
• The “recipient list”, will be defined as – all the existing Exchange Online recipients who classified as – users with a mailbox.

Implementation

Step 1: we will define a filter that will scan all the existing Exchange Online recipients and “pull out” only the Exchange recipient who defined as users with mailboxes.

The filter syntax that we use is-

Step 2: we will define a variable named $UserMailboxes, that will serve as a “container” for the output from a PowerShell filter that will fetch the required recipient list.

Step 3: we will pipe the information stored in the $UserMailboxes variable, to a second PowerShell command, which will assign the required Send As permissions to John (the Trustee) for each of the recipients the appears in the filtered list.

Using the confirm parameter

When we assign or remove Send As Permissions, the PowerShell command is configured to ask by default for approval, for any assignment or removal of Send As Permissions. In case that we want to avoid the need to approve the operation and let the command run freely without the need for approval, we can add the parameter -Confirm:$False

Scenario 1.3 – Assign Send As Permissions to user X on all the Exchange Online recipient type (Bulk Mode)

Scenario description

• We would like to grant the Send As Permissions to a user named John.
• The Send As permission will be assigned to a list of recipients.
• The Send As permission will be assigned separately, for each recipient on the list.
• Versus the former example, this time, we would like to grant John the Send As Permissions, on all the existing Exchange Online recipients, type such as – mailboxes, room mailbox, public folders and so on.

Implementation

Step 1- we will use the PowerShell command Get-Recipient , for “storing information” about all the Exchange Online recipients.

Step 2- we will pipe the information to the second PowerShell command.
The second PowerShell command will use the recipient list, and grant the Send As permissions to John for each of the recipients in the list (the recipients list from the previous PowerShell command).

Scenario 1.4 – Assign Send As Permissions to user X on multiple users by using a user list saved to a CSV file.

Scenario description

• We would like to grant the Send As Permissions to a user named John.
• The Send As permission will be assigned to a list of recipients.
• The Send As permission will be assigned separately, for each recipient on the list.
• The “recipient list”, will be defined as a – recipient list that is stored in a CSV (comma separated value) file.

Implementation

To be able to work with the information that stored as a CSV file, we will use the following procedure:

Step 1 – working with a CSV file

• We will prepare in advanced, a CSV file that will contain our recipient list. (You can download a sample of the CSV file).
• CSV file name – in our scenario, we will name the CSV file – csv.
  CSV file location – the CSV file, will be saved to a folder named Temp in C: drive.
• The information about the recipient list will be created “under” a column header
  named – alias

Technically speaking, a CSV file can contain multiple columns.

In the following screenshot, we can see an example of the CSV file content.

When using the option of CSV file, we will need to define a header name, for each of the existing columns.
Notice that although our CSV file contains multiple columns, we need to address only a particular column that stores our recipient list. The column header name of our specific column is – alias.

Regarding the column header name, technically we can choose any name whom we want.
The best practice is to define a simple column header name, using a single word, no spaces, etc.

Step 2 – we will use the PowerShell command that will import the information from the CSV file, into a temporary store in the RAM.

Step 3 – we will define a variable named $UserList, that will contain the output from a PowerShell command that imports the information from the CSV file.

Step 4 – using the PowerShell Foreach Loop operator

We will use the PowerShell Foreach Loop operator, for scanning (looping through) the information that was fetched from the CSV file (the information that is stored in the $UserList variable).

We will instruct the PowerShell Add-RecipientPermission command, to grant John; the send As permission separately, for each recipient’s name who appears “under” the alias column header.

When using the Foreach Loop operator, we need to define a variable that will serve as a “container”, for each recipient who appears on the list.

This variable will store the “first name” in the list, and after we finish the task of assigning John the required Send as permission, the recipient name will be “deleted” from the “variable store.”
Then the “next name” in the recipient list will be populated in the “variable storage”.

In our specific scenario, the variable that we use for referencing a “single recipient” from the recipient
list is – $user

We will “attach” to the $user variable the “alias” property from the CSV file.
For example – $user.alias

In this way, the $user variable will contain in the “first time”, the first recipient name who appears “under” the alias column header.
The next time, the $user variable, will contain the second recipient name who appears “under” the alias column header and so on, until the end of the recipient list.

Scenario 1.5 – Assign Send As Permissions to user X on multiple users by using Filter parameter | Filter by users the belong to a specific department.

Scenario description

• We would like to grant the Send As Permissions to a user named John.
• The Send As permission will be assigned to a list of recipients.
• The Send As permission will be assigned separately, for each recipient on the list.
• The “recipient list”, will be defined as – all the Exchange Online users who work in the marketing

Implementation

To be able to implement this requirement, we use a PowerShell command that consists of two parts:

Step 1 – filter a list of recipients

We will use the PowerShell cmdlets – Get-Recipient, for getting a list of all the existing Exchange Online recipients.

We will use the –Filter parameter to filter from the list only a specific recipient whom their department is marketing (we will use a PowerShell command that will “filter out” only Exchange Online recipient whom their department is equal to marketing).

An example of the filter syntax in our scenario is-

Step 2 – we will pipe the output from the first command to an additional PowerShell command, which will grant the Send As permission to John, for each of the recipients named who appears on the list.

Scenario 1.6 – Assign Send As Permissions to each member of a distribution group to a specific user

Scenario description

• We would like to grant the Send As permissions, to each of the recipients who belongs to a distribution group named – marketing.
• We want to assign the Send As permissions on a recipient’s mailbox named – John

Implementation

As mentioned, we cannot directly grant Send As permissions to a distribution group on “other objects.”

The good news is that we can bypass the obstacle by use a little trick.

The trick that we use will “extract” each of the members of a particular distribution group, and will assign the Send As permission for each of the members separately.

Note – notice that this “trick”, will not apply to a new member in the marketing distribution group, that will be added to the group after we execute the PowerShell command.

Step 1 – we will use the PowerShell command Get-DistributionGroupMember, that will get the list of members in a specific distribution group (the marketing distribution group in our scenario).

Step 2 – we will use a variable named $Members who will “contain” the output, from a PowerShell command, that will “fetch” all the members in the marketing distribution group.

Step 3 – using the PowerShell Foreach Loop operator

We will use the PowerShell Foreach Loop operator, for scanning (looping through) the list of the distribution group members.

In our scenario, the Trustee identity will be replaced a couple of times for each of the members in the marketing distribution group.

A single member of the marketing distribution group (the Trustee) will define by the following combination of variable + property.

In our example, the variable is $Member and the property is – name.

The combination will look like – $Member.name

The PowerShell – Add-RecipientPermission , will “loop” through the member list and will assign each of the members the Send As permission on John’s mailbox.

Scenario description

• We would like to grant the Send As Permissions to a user named John.
• The Send As permission will be assigned to a list of recipients.
• The Send As permission will be assigned separately, for each recipient on the list.
• The “recipient list”, will be defined as – all the members of a distribution group named – marketing.

Implementation

Note – notice we will need to use the same “extract trick” because, we don’t want to grant John permission to the distribution group, but instead, grant the Send As permission for each of the group members separately.

Step 1 – we will use the PowerShell command Get-DistributionGroupMember, that will get the list of members in a specific distribution group (the marketing distribution group in our scenario).

Step 2 – we will use a variable named $Members who will “contain” the output, from a PowerShell command, that will “fetch” all the members in the marketing distribution group.

Step 3 – using the PowerShell Foreach Loop operator

We will use the PowerShell Foreach Loop operator, for scanning (looping through) the list of the distribution group members.

In this case, the Trustee is John.
We want to assign John; the Send as permission for each of the distribution group members.

The way that we relate to each element of the array (each of the group members) is, by using the variable with a combination of the property – name in the following way – $Member.name

Scenario 2.1 – Display information about recipients who have “Send As” permission on a specific user Mailbox.

Scenario description
In the following scenario, our goal is to:

• Display information about the recipient who has the Send As permission on John’s mailbox.

Implementation

We will demonstrate how to use the “simple version” of the PowerShell command, and also; we will provide a more “sophisticated PowerShell command” that will help us to remove an unnecessary information from the PowerShell command output.

In the following screenshot, we can see that we can see a list of recipients that have Send as permission to John’s mailbox, in addition, we can see
a “strange recipient” named – nt authority\self

The is the permission that John has for the purpose of sending email using his Email address(yes, I know it sounds strange).

If we want to display more “clean” output without the information about the permission that the user has to his mailbox, we can use a PowerShell syntax that will remove this no useful information.

Scenario 2.2 – Display information about All the recipients who have “Send As” permission on any user Mailbox.

Scenario description

In the following scenario, our goal is:

• Display information about all if our organization recipients, who have the Send As permission on other recipient mailboxes.

Implementation

Step 1- we will use the PowerShell command Get-Recipient, for “storing information” about all the Exchange Online recipients.

Step 2- we will pipe the information to the second PowerShell command, which will display on the screen, the Send As permissions that each recipient has on other recipients’ mailboxes.

Scenario 2.3 – Display information on the Send As permission that a specific recipient has on “other recipient”.

Scenario description

• John has Send As permission on many organization recipients. We need to get a clear information about who are these recipients.

Implementation

Step 1- we will use the PowerShell command Get-Recipient, for “storing information” about all the Exchange Online recipients.

Step 2- we will pipe the information to the second PowerShell command, which will display on the screen, the recipient that John has Send As permissions on their mailboxes.

Scenario 2.4 – Export information about Send As permission to TXT file.

Scenario description

• John has Send As permission on many organization recipients. We need to export the information about John Send As permission to a TXT file.

Implementation

The PowerShell parameter that we use for exporting information to a text file is – Out-File

We will need to provide the required path in which the text file created.
In our scenario, we wish to create a text file that will store in C: drive in a folder named – Temp.

In case that your Office 365 tenet uses characters set that include additional characters to the standard English characters, is recommended to add, an additional PowerShell
“format parameter” named – “Encoding UTF8,” which will enable PowerShell, to export non-English characters.

Scenario 2.5 – Export information about Send As permission to CSV file.

Scenario description

• John has Send As permission on many organization recipients. We need to export the information about John Send As permission to a CSV file.

Implementation

The PowerShell parameter that we use for exporting information to a text file is Export-CSV

We will need to provide the required path in which the text file created.
In our scenario, we wish to create a text file that will store in C: drive in a folder named – Temp.

When exporting information to a CSV file, a parameter that is recommended to
add is “-NoTypeInformation”

The purpose of this parameter is to omit the type information from the CSV file.
By default, the first line of the CSV file contains “#TYPE” followed by the fully-qualified name of the object type.