Add-RecipientPermission

 

Applies to: Exchange Online

This cmdlet is available only in the cloud-based service.

Use the Add-RecipientPermission cmdlet to add SendAs permission to users in a cloud-based organization.

For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax.

Add-RecipientPermission -Identity <RecipientIdParameter> -AccessRights <MultiValuedProperty> -Trustee <SecurityPrincipalIdParameter> [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]]

This example gives the user Ayla Kol SendAs permission for the mailbox Help Desk. Ayla can send messages that appear to come directly from the Help Desk mailbox.

Add-RecipientPermission "Help Desk" -AccessRights SendAs -Trustee "Ayla Kol"

When a user is assigned SendAs permission to a user or group, the user can send messages that appear to come from the other user or group.

You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Recipient provisioning permissions" section in the Recipients Permissions topic.

 

Parameter Required Type Description

AccessRights

Required

Microsoft.Exchange.Data.MultiValuedProperty

The AccessRights parameter specifies the permission.

Valid input for this parameter is SendAs.

Identity

Required

Microsoft.Exchange.Configuration.Tasks.RecipientIdParameter

The Identity parameter specifies the target recipient. The user or group specified by the Trustee parameter can operate on this recipient.

You can specify any type of recipient, for example:

  • Mailboxes

  • Mail users

  • External contacts

  • Distribution groups

  • Dynamic distribution groups

You can use any value that uniquely identifies the recipient.

For example:

  • Name

  • Display name

  • Alias

  • Distinguished name (DN)

  • Canonical DN

  • Email address

  • GUID

Trustee

Required

Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter

The Trustee parameter specifies the user or group to whom you're granting the permission. This allows the user or group to operate on the recipient specified by the Identity parameter.

You can specify the following types of users or groups:

  • Mailbox users

  • Mail users with a Microsoft account (formerly known as a Windows Live ID)

  • Security groups

You can use any value that uniquely identifies the user or group.

For example:

  • Name

  • Display name

  • Alias

  • Distinguished name (DN)

  • Canonical DN

  • <domain name>\<account name>

  • Email address

  • GUID

  • LegacyExchangeDN

  • SamAccountName

  • User ID or user principal name (UPN)

Confirm

Optional

System.Management.Automation.SwitchParameter

The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.

  • Destructive cmdlets (for example, Remove-* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.

  • Most other cmdlets (for example, New-* and Set-* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.

WhatIf

Optional

System.Management.Automation.SwitchParameter

The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

This parameter is reserved for internal Microsoft use.

To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.

 
Show: