Skip to content

Publish main to live, Friday 10:30AM PDT, 10/04 #12151

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Oct 4, 2024
Merged

Publish main to live, Friday 10:30AM PDT, 10/04 #12151

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
0257791
added a note
v-mathavale Oct 3, 2024
38a1f24
Update Get-RecipientPermission.md
chrisda Oct 3, 2024
dec2c47
Merge branch 'main' into v-mathavale-9407123
chrisda Oct 3, 2024
a052278
Merge pull request #12148 from MicrosoftDocs/v-mathavale-9407123
Stacyrch140 Oct 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions exchange/exchange-ps/exchange/Get-RecipientPermission.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,9 @@ Get-RecipientPermission [[-Identity] <RecipientIdParameter>]
## DESCRIPTION
When a user is given SendAs permission to another user or group, the user can send messages that appear to come from the other user or group.

> [!NOTE]
> This cmdlet doesn't return expected results when the recipient specified by the Trustee parameter has multiple `SecurityPrincipalIdParameter` (Sid) values. When you use the Trustee parameter, the command compares the Sid of the specified Trustee with the recipient's access control list (ACL) record. If some of the recipient's Sid values have changed, there's a mismatch. The workaround is to not to use the user principal name (UPN) value, to use all Sids including the one for history.

You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).

## EXAMPLES
Expand Down