'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Assign Send As Permission in Exchange Online PowerShell
Question details
The user needs to correctly assign Send As permissions to a shared mailbox using PowerShell in an Exchange Online environment.
- Product
- Exchange Online
- Device & OS
- not provided
- Scenario
- Administrating shared mailbox permissions in a hybrid Exchange setup.
- Observed behavior
- The standard Add-MailboxPermission cmdlet fails to assign Send As rights to the shared mailbox in Exchange Online, requiring a different command.
Ensure you are running PowerShell with administrative privileges and have connected to the ExchangeOnlineManagement module before executing these commands.
Use the Add-RecipientPermission Cmdlet
Execute the specific recipient permission cmdlet in PowerShell to accurately grant Send As rights to an Exchange Online mailbox.
In a hybrid Exchange environment, the standard Add-MailboxPermission cmdlet may not effectively assign Send As rights. Instead, the Add-RecipientPermission cmdlet must be used to modify recipient-level permissions in Exchange Online.
Open PowerShell as an Administrator and connect to Exchange Online by importing the ExchangeOnlineManagement module.
Type the following command: Add-RecipientPermission -Identity "SharedMailbox" -Trustee "User" -AccessRights SendAs. Replace 'SharedMailbox' with the actual identity of the shared mailbox, and 'User' with the delegate's account name.
If PowerShell prompts you to confirm the assignment, type 'Y' and press Enter to finalize the permission change.
Looking for a Lightweight and Compatible Office Suite?
While managing Exchange Online requires PowerShell expertise, handling your daily documents, spreadsheets, and emails should be effortless. WPS Office provides a free, lightweight, and highly compatible alternative to Microsoft Office, ensuring seamless workflow and migration.
- 1. Download the Installer: Visit the official WPS Office website to download the free installer for your operating system.
- 2. Install the Suite: Run the setup file and follow the quick installation prompts to set up WPS Office on your device.
- 3. Manage Your Files: Launch WPS Office and immediately start opening, editing, and saving your existing Microsoft Office files with full format retention.
Frequently Asked Questions
Why doesn't Add-MailboxPermission work for Send As rights in Exchange Online?
In hybrid and Exchange Online environments, Add-MailboxPermission is primarily used for assigning Full Access rights. For granting Send As capabilities, Exchange Online architecture specifically requires the Add-RecipientPermission cmdlet.
How can I verify that the Send As permission was successfully assigned?
You can verify the successful assignment by executing 'Get-RecipientPermission -Identity "SharedMailbox" -Trustee "User"' in your Exchange Online PowerShell session. It should list SendAs under the AccessRights column.
How do I remove the Send As permission if it's no longer needed?
To revoke the permission, you can use the corresponding removal cmdlet: Remove-RecipientPermission -Identity "SharedMailbox" -Trustee "User" -AccessRights SendAs.
