Skip to main content

How to revoke recipient permission from shared mailbox in offic 365?

By
Today, I'd like to share how to revoke recipient permission from shared mailbox in office 365.

Powershell Syntax for this taks is as below,

Revoke Full Access permissions for Shared Mailbox
Remove-MailboxPermission <Shared Mailbox Name or Full e-mail address> -User  -AccessRights FullAccess

Revoke Send As permissions for Shared Mailbox
Remove-RecipientPermission  -AccessRights SendAs -Trustee  

For example, I want to revoke the Full & Send As permission from helpdesk@ictformyanmar.com that given from technical-support@ictformyanmar.com before.
Before revoke those permissions, I'll check effected permission on technical-support@ictformyanmar.com to ensure.
Use below powershell command to check the effected permission,


To display Full Access permissions for Shared Mailbox
Get-Mailboxpermission "Technical Support"
(or)
Get-Mailboxpermission technical-support@ictformyanmar.com

To display Send As permissions for Shared Mailbox
Get-RecipientPermission "Technical Support"
(or)
Get-RecipientPermission technical-support@ictformyanmar.com

After checked and ensured the granted permissions, I'm going to revoke the permissions by using following powershell commands,

Remove-MailboxPermission "Technical Support" -User "Help Desk" -AccessRights FullAccess
(or)
Remove-MailboxPermission technical-support@ictformyanmar.com -User helpdesk@ictformyanmar.com -AccessRights FullAccess

Press Enter to confirm changed effect if below promt come out,

 Confirm
Are you sure you want to perform this action?
Removing mailbox permission "Technical Support" for user "Help Desk" with access
rights "'FullAccess'".
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"):


Remove-RecipientPermission "Technical Support"  -AccessRights SendAs -Trustee  "Help Desk"
(or)
Remove-RecipientPermission technical-support@ictformyanmar.com -AccessRights SendAs -Trustee  helpdesk@ictformyanmar.com

Press Enter to confirm changed effect if below promt come out,

 Confirm
Are you sure you want to perform this action?
Removing recipient permission 'SendAs' for user or group 'Help Desk' from recipient
'Technical Support'.
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"):

To ensure revoke permission changed effect, please use below powershell commands.

To display Full Access permissions for Shared Mailbox
Get-Mailboxpermission "Technical Support"
(or)
Get-Mailboxpermission technical-support@ictformyanmar.com

To display Send As permissions for Shared Mailbox
Get-RecipientPermission "Technical Support"
(or)
Get-RecipientPermission technical-support@ictformyanmar.com

I've attached three sample photos in sequence (Before Revoke Permissions, Revoking Permissions and After Revoked Permissions) for your reference.





OK. That's the way to revoke the granted permission of shared permission from recipient.

I'll write about Inheritance Type that related with Group if I've time.

May you all be happy.
(Be knowledgeable, pass it on then)
Labels:

Comments

Post a Comment

Popular posts from this blog

Fortigate guide for Begineer - 6

By
I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a
Post a Comment
Read more

Why do we need network virtualization?

By
We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca
146 comments
Read more

Solving "WSUS administration console was unable to connect to the WSUS Server via the remote API" error

By
Today, I've got below when I try to connect my WSUS Server via WSUS Console. Below logs are display in Event Logs too. The WSUS administration console was unable to connect to the WSUS Server via the remote API.  Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 172.16.99.98:80 Source System Stack Trace:    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)    at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, S
7 comments
Read more