Skip to main content

How to convert user mailbox into shared mailbox in office 365?

By
I'd like to share how to convert user mailbox into shared mailbox in office 365 today.

But before going through, let me explain briefly what is shared mailbox and what can we use it for.

A shared mailbox is a mailbox that multiple users can open to read and send e-mail messages. Shared mailboxes allow a group of users to view and send e-mail from a common mailbox. They also allow users to share a common calendar, so they can schedule and view vacation time or work shifts. Why set up a shared mailbox?


• It can provide a generic e-mail address, such as technical-support@ictformyanmar.com or info@ictformyanmar.com, which customers can use to inquire about your company.
• It allows staff in departments that provide centralized services to employees, such as the technical support, help desk, human resources, or printing services, to respond to employee questions.
• It allows multiple users to monitor and reply to e-mail sent to an e-mail address, such as a Technical Support , Help Desk, Customer Support.
• In a school environment, it provides students and parents with an entry point to different school departments, such as academic departments, library services, or financial aid.
Shared mailboxes in Microsoft Office 365
In Office 365, shared mailboxes don’t require a license. However, each user who accesses a shared mailbox must have a user subscription license. Users with Exchange Online Kiosk subscriptions can’t access shared mailboxes. Also, shared mailboxes can’t be used to archive e-mail, except for the messages that are actually sent to or received from the shared mailbox.

Shared Mailbox Size can be 2GB to 5GB as shown in below link
http://technet.microsoft.com/en-us/library/dn133593.aspx

But Office 365 recently upgraded and I was noticed that Shared Mailbox size become 25GB.

OK. Now I assume you guys know about Shared Mailbox in brief.

Let's start to convert user mailbox into shared mailbox now.

For example, I'll use below steps to do.
- First, convert regular mailbox of technical-support@ictformyanmar.com into shared mailbox.
- Second, grant access permission (Full and Send As) to shared mailbox for technicalsupport1@ictformyanmar.com
- Last, revoke the subscription license of technical-support@ictformyanmar.com.

First, Run Powershell as Administrator and login to Exchange Online.
Copy and Paste following command line by line into Powershell window.

Set-Mailbox -Identity "Technical Support" -Type “Shared”  
(OR)
Set-Mailbox -Identity technical-support@ictformyanmar.com -Type “Shared”  - (To convert Technical Support Mailbox from Regular Mailbox into Shared Mailbox)


Second,
Add-MailboxPermission "Technical Support" -User "Tech Support 1" -AccessRights FullAccess
(OR)
Add-MailboxPermission technical-support@ictformyanmar.com -User techsupport1@ictformyanmar.com -AccessRights FullAccess - (Giving Full Access Permission to Tech Support 1 to access Shared Mailbox)

Add-RecipientPermission "Technical Support" -Trustee "Tech Support 1" -AccessRights SendAs 
(OR)
Add-RecipientPermission technical-support@ictformyanmar.com -Trustee techsupport1@ictformyanmar.com -AccessRights SendAs - (Giving Send As Permission to Tech Support 1 for Shared Mailbox)

Just press Enter when you see below prompt.
Confirm
Are you sure you want to perform this action?
Adding recipient permission 'SendAs' for user or group 'Tech Support 1' on recipient 'Technical Support'.
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"):

Last,
Login to Office 365 Portal. Go to Users and Groups>Active Users.
Choose Technical Support and Revoke subscription license.

That's it. Converting Regular Mailbox into Shared Mailbox is done.

In above example, you can modify highlighted text as your requirement. Text can use Display Name or Full Email Address.
Take note the doube quote of highlighted text. Double Quote is no need if your text is without space.



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