[This topic is in progress.]

Applies to: Exchange Server 2010 SP2

Topic Last Modified: 2011-05-03

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

Syntax

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

Detailed Description

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

Parameters

Parameter Required Type Description

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:

  • Alias

  • Distinguished name (DN)

  • GUID

  • Name

  • Display name

  • LegacyExchangeDN

  • E-mail address

AccessRights

Required

Microsoft.Exchange.Data.MultiValuedProperty

The AccessRights parameter specifies the permission.

Valid input for this parameter is SendAs.

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 Windows Live ID

  • Security groups

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

For example:

  • Alias

  • Distinguished name (DN)

  • GUID

  • Name

  • Display name

  • LegacyExchangeDN

  • E-mail address

Confirm

Optional

System.Management.Automation.SwitchParameter

The Confirm switch can be used to suppress the confirmation prompt that appears by default when this cmdlet is run. To suppress the confirmation prompt, use the syntax -Confirm:$False. You must include a colon ( : ) in the syntax.

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

This parameter is available for multi-tenant deployments. It isn't available for on-premises deployments. For more information about multi-tenant deployments, see Multi-Tenant Support.

The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain controller that writes this configuration change to Active Directory.

WhatIf

Optional

System.Management.Automation.SwitchParameter

The WhatIf switch instructs the command to simulate the actions that it would take on the object. By using the WhatIf switch, you can view what changes would occur without having to apply any of those changes. You don't have to specify a value with the WhatIf switch.

Input Types

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.

Return Types

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.

Errors

Error Description

 

Examples

EXAMPLE

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

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