Skip to main content

How to setup automap feature in Shared Mailbox for group of user in Office 365?

Usually, we got to add manually for Shared Mailbox to each permission granted user's outlook client.
This is a bit OK for few users. But it will be problem if you have to add manually for many users.
So, I'd like to show you how to setup automap feature by using powershell command when you granting permission for each user to shared mailbox.

For this kind of task, I'll use below powershell syntax,

1) To create shared mailbox and generic e-mail address
New-Mailbox -Name "Shared Mailbox Name"  -Alias "Shared Mailbox Alias Name" –Shared   -PrimarySmtpAddress "External Contact Shared Mailbox e-mail address"

2) To Assign User to get Full and Send As permission with Automap Feature
Add-MailboxPermission "Shared Mailbox Name or Shared Mailbox e-mail address" -User "User Display Name or User e-mail address" -AccessRights FullAccess -InheritanceType all
Add-RecipientPermission "Shared Mailbox Name or Shared Mailbox e-mail address" -Trustee "User Display Name or User e-mail address" -AccessRights SendAs

For example, I want to shared mailbox of to salestaff1, salestaff2 and salestaff3 with Full Access, Send As Pemisssion and Automap it in their outlook client.

Just copy and paste below commands in Powershell Windows.

New-Mailbox -Name "Sales"  -Alias SNM –Shared   -PrimarySmtpAddress

Add-MailboxPermission "Sales" -User "Sale Staff 1" -AccessRights FullAccess -InheritanceType all
Add-MailboxPermission "Sales" -User "Sale Staff 2" -AccessRights FullAccess -InheritanceType all
Add-MailboxPermission "Sales" -User "Sale Staff 3" -AccessRights FullAccess -InheritanceType all

Add-RecipientPermission "Sales" -Trustee "Sale Staff 1" -AccessRights SendAs
Add-RecipientPermission "Sales" -Trustee "Sale Staff 2" -AccessRights SendAs
Add-RecipientPermission "Sales" -Trustee "Sale Staff 3" -AccessRights SendAs

Take note the highlighted area to modify for your requirement.
InheritanceType all is major point of Automap Feature.

Ok. I hope you guys will able to setup for automap now.

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


Popular posts from this blog

Fortigate guide for Begineer - 6

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

Solving the "A general system error occured:Invalid fault" error in vSphere 4

Below error was come out when you try to migrate VM to other host for some reason. Below error was come out when you try to edit VM setting. Below error was come out when you power on the VM. How to solve those error? Here is how I resolve the error! Login to the Host that errored VM exist by using Terminal or Direct Console. Enter below command and press enter. restart Wait until all VMware Services are restarted. After that try to Power On/Edit Settings or Migrate the errored VM and you will see all you can do without any error pop-up. This kind of errors can occur if you shutdown/restart VM unproperly or shutdown/restart the Host unproperly that VM exist. You can check log file deeply if you willing to know precisely on this. May you all be happy. (Be knowledgeable, pass it on then)

Link Aggregating with Synology NAS and Cisco Switch

I’d like to share how to setup Link Aggregating between Synology NAS and Cisco Switch. I’ve got one Synology NAS with 4 Network Ports and I’m going to use 2 of them. Both Network Port to be as one Logical Link, Fault Tolerance and Load Balancing. To do that, I need to configure Link Aggregating on Synology NAS and EtherChannel with LACP on Cisco Switch. Below is brief steps to do to meet with my requirements. - Get connected Synology NAS and Cisco Switch as shown in picture. - Bonding two Network Ports of Synology NAS and assign IP Address - Configure EtherChannel with LACP in Cisco Switch and add two physical ports as Member. OK. Let’s begin from Synology NAS. - Login to the Synology and go to Control Panel>Network>Create>Create Bond - Select IEEE 802.3ad to get Fault Tolerance and Load Balancing Featureyou’re your switch not support 802.3ad you can only select Fault Tolerance only feature). After that click “Next”. - Choose the network port f