Pro-Tip: Use our Office 365 reports to see which users have full access to particular mailboxes! Create a Security Group which will contain your Admin accounts. Log in to the Microsoft Office 365 Portal. Click Distribution Groups under Manage Outlook and Exchange Settings. Click the New button. Add a shared mailbox to Outlook. After your admin has added you as a member of a shared mailbox, close and then restart Outlook. The shared mailbox should automatically display in your Folder pane in Outlook. What if it didn't work? If your admin only recently added you to a shared mailbox, it may take a few minutes before the shared mailbox appears.
A shared mailbox is accessible by multiple users, all of whom are granted specific access permissions. Every member is able to read and send email messages to and from the shared mailbox itself. Shared mailboxes are widely used.
They permit performing a wide range of coordinated activities with a team. Essentially, a shared mailbox acts as a centralized service allowing many people to work in a synchronized manner. Among the most common advantages of using shared mailboxes include these abilities:.
Monitor and send email from a centralized account: For example, [email protected], [email protected]. Handle customer email inquiries: Numerous users within the organization can share the responsibility for monitoring the mailbox and answering queries. Share Outlook calendar information: Multiple users can plan and view work shifts and/or holiday time. In this article, you will learn how to configure a shared mailbox in Outlook and what to do if the shared mailbox is not synchronizing properly.
Add an Additional Shared Mailbox in Outlook Once your shared mailbox account is ready (created either on Active Directory on-premises or on Azure Active Directory) you can proceed by adding it to your Outlook profile. You should keep in mind, however, that there are different methods to do this. Depending on the infrastructure Office 365 is relying on, a shared mailbox added using a different method than the one shown below might not work as expected, or might produce error messages.
![Open shared mailbox outlook mac Open shared mailbox outlook mac](/uploads/1/2/5/4/125485119/208877156.png)
In Outlook, go to File Account Settings Account Settings. Select your profile and click on Change. Click on More Settings. On the Advanced tab, click Add. Type the email address or name of the shared mailbox, then click OK. Once configured, the shared mailbox will be automatically available in the left folder pane in Outlook. Delegate Access to Shared Mailbox for another User With the exception of the mailbox owner, anyone else who needs to access the additional mailbox (and configure it on his Outlook profile) must be granted the correct permissions.
There are two main actions the mailbox owner will need to take in order to provide another user with access to the shared mailbox. Please consider, however, that once the process below is completed, permissions might not be available in real time to the user, since permission replication over the whole infrastructure might take a while. Action 1: Delegate Access In Outlook, go to File.
Click on Account Settings Delegate Access. Select the user who will work with the shared mailbox (use Ctrl-click to select multiple names) and click on Add OK. Select the permission level you want to assign for each section: Calendar, Tasks, Inbox, Contacts, Notes. Select Editor permissions (which will provide full access) and click OK. Action 2: Set granular permissions over a shared mailbox for the targeted user Start Outlook, go to “Mail”, then right-click on the Shared Mailbox. Click on Data File Properties.
Select the Permissions Tab from the menu. Under Permission Level, select Full Details All Folder Visible, as below. Click the Add button. Enter the name or fully-qualified email address of the target user and click on Go. Select the name from the list, and click Add OK. Select Editor. Under Read, select Full Details.
Select the permission level—Editor permissions will provide full access—and click OK. Troubleshooting Shared Mailbox Synchronization Shared mailboxes might suffer from a wide range of technical and configuration issues. See below for help on how to proceed if the shared mailbox is not syncing. 1) Disconnect/Reconnect the Shared Mailbox. This quick action could actually bring the shared mailbox back in sync again. Try to disconnect and connect back the Shared Mailbox to your Outlook profile. Close Outlook.
Go to Start Control Panel (View by Large Icons) Click on Mail. The Mail Setup window will pop up.
Click on Email Accounts. Select your profile and click on Change. Select More Settings. On the Advanced tab, select the Shared Mailbox and click Remove.
Open Outlook again and reconnect the shared mailbox following the process listed for step number 1 (How to add an additional shared mailbox on Outlook). See if the issue persists. 2) Rename the Offline Outlook Data File (.ost) Office 365 keeps your mailboxes (shared or individual) on a server called Microsoft Exchange. However, Outlook locally caches all folders to which you have access (also for shared mailboxes) in a file called Offline Outlook Data File (.ost).
The Offline Outlook Data File (.ost) is a synchronized local copy of your mailbox saved on your computer, and is stored in the following default location (which might vary depending on the client version and the Outlook account type): C: Users AppData Local Microsoft Outlook The Offline Outlook Data File, however, can get corrupted or become unreadable from within Outlook. Reasons for this could include a data storage device failure (bad sectors on the hard disk); networking connection failure (if the network connection has a problem, then the synchronization process will be aborted and the OST file is likely to get corrupted); incorrect file system recovery; or viruses. When this happens either the shared mailbox or your main Inbox might stop syncing.
Very often mailbox synchronization issues with Outlook are due to.ost file corruption and can be resolved simply by renaming the.ost file or by creating a new Outlook profile, which will create a new Offline Outlook Data File (.ost) for Outlook to cache data. Navigate to: C: Users AppData Local Microsoft Outlook, select the Offline Outlook Data File and rename it (for example, by adding “.old” to the end.) Restart Outlook and check if the issue persists. Outlook should create a new Offline Outlook Data File, which will start to synchronize again with the Mailbox on the Exchange Server. Of course, full synchronization might take a while, and some data (emails) might be available on Outlook (especially older items) only a few hours later. 3) Enable/Disable Cached Exchange Mode The feature Cached Exchange Mode is set up by default when you are using an Exchange account. It works by keeping a copy of your mailbox locally saved (cached) on your computer.
Accessing a local copy allows access to your data to be much quicker, and allows you to work on Outlook while offline. Using Cached Exchange Mode, you can read and respond to your cached messages while offline, and any new messages or updates to your mailbox on the server will be automatically sent/received once Outlook (specifically the.ost file) gets connected again. If the shared mailbox is not synchronizing, you might try to disable, restart Outlook, and re-enable again Cached Exchange Mode on the advanced profile configuration settings of your Outlook profile. Click File Account Settings Account Settings. Highlight the Exchange account, and then click Change.
Go to More Settings. On the Advanced tab, under Cached Exchange Mode Settings, uncheck the option Cached Exchange Mode.
Restart Outlook, re-enable the checkbox and see if the issue persists. 4) Enable “Download shared Folders” and “Public folders favorites” When Cached Exchange Mode is turned on, shared folders—the folders available in your shared mailbox—are downloaded (in the.ost file) to the local computer.
To make sure that shared folders are properly downloaded to the Offline Outlook Data File when Cached Exchange Mode is turned on, you will proceed as follows: Click File Account Settings Account Settings. Click the Exchange account, and then click Change More Settings. On the Advanced tab, under Cached Exchange Mode Settings, make sure the checkboxes “Download shared Folders” and “Public folders favorites” are selected. 5) Link a Shared Mailbox to a new Outlook Profile One more check is to see if the shared mailbox is showing the same connectivity problem on a new Outlook profile. Close Outlook. Go to Start Control Panel (View by Large Icons) Click on Mail.
The Mail Setup window will pop up. Click on Show Profiles. Click on the Add Button.
Choose the name for the new profile, and click OK. The Autodiscover service should be able to create the Outlook profile automatically: Click on Next. And then click Finish. Go again to the Mail Configuration window and select the option: ”Always use this profile”. Next time Outlook opens up, it will automatically load your new profile. To add the Shared Mailbox to the new Outlook profile, follow the step above: “How to add an additional shared mailbox in Outlook“. Check if the Shared Mailbox is synchronizing properly on the new Outlook profile.
6) Check Shared Mailbox Accessibility via the Outlook Web App If the syncing problem still persists with the new Outlook profile, then the problem might be elsewhere. The network infrastructure might have some problem, permissions might not have properly replicated across the infrastructure after the shared mailbox owner granted the target user with permissions and many others. Check if you are able to access the shared mailbox on the cloud-hosted service Outlook Web App, which is the Microsoft Exchange Web-based email client. The user experience is similar to Microsoft Outlook but it doesn’t need the client software (Outlook) to be installed on the PC. This allows us to access e-mail, calendars, contacts, tasks, and other mailbox content when something is wrong with Outlook. Just go to provide your credentials (Outlook email address and password) and log in. Click on the upper right user icon, and select “Open another Mailbox”.
Insert the shared mailbox email address. Click on Open. If the Mailbox is available and properly synchronizing via Outlook Web App, this means that the issue is local, with Microsoft Outlook, and you will need to investigate further. If the shared mailbox is neither accessible nor properly synchronizing on the web app, the problem most likely needs to be fixed at the server level. In this case, you should contact your system administrator.
Shared mailboxes within an Exchange/Office 365 hybrid environment are now fully functional using Full Access permissions. This has been a limitation for some customers migrating to Office 365 up until now.
With this restriction removed, customers can now fully support a long term migration process or even a permanent hybrid choice for their company. In on-premises Exchange deployments, users can be granted a variety of permissions to other user’s mailboxes. This is called delegated mailbox permissions and it is useful when someone needs to manage some part of another user’s mailbox; for example, managing an executive's calendar, or if multiple users have access to a shared repository mailbox. Some of these permissions can be used in Exchange hybrid deployments. Exchange hybrid deployments support the use of the Full Access mailbox permission between mailboxes located in an on-premises Exchange organization and mailboxes located in Office 365.
A mailbox on an on-premises Exchange server can be granted the Full Access permission to an Office 365 mailbox, and vice versa. Note: Users might receive additional credential prompts when they first access a mailbox that is in the other realm and add it to their own Outlook profile. While Exchange hybrid configurations do support the use of the Send-As, Receive-As, or Send on behalf of mailbox permissions, these permissions are only available when both the mailbox granting the permissions, and the mailbox receiving the permissions, are in the same realm.
Any mailboxes that receive these permissions from another mailbox need to be moved at the same time as that mailbox. If a mailbox receives permissions from multiple mailboxes, that mailbox, and all of the mailboxes granting permissions to it, need to be moved at the same time and exist in the same realm of either on premises or Office 365 Exchange organizations.
In addition to these permissions, the Auto Mapping feature is unsupported when used between mailboxes in the on-premises Exchange and Office 365 organizations. Over the last few months of helping customers, I have seen where this shared mailbox access topic has been a limitation. I am happy to be able to post this material and be able to update customers that this issue has a resolution. For further reading, visit the page for additional knowledge. I have an issue at one of my accounts where we are migrating from an existing Exchange 2010 Org to a new Exchange 2013/O365 Hybrid as the business is splitting from another business.
The Shared Mailboxes are remaining on the Exchange 2010 Org during the migration period (using Quest Tools for Mailbox Migration) but we need the users to connect to O365 Mailbox and then also connect back to old Org for Shared Mailbox using Outlook 2016. When we connect the first Shared Mailbox we use the Exchange 2010 AutoDiscover Name and this works ok but if connect further Shared mailboxes the same way the one that was already connected automatically redirects to the Office 365 copy and then the new shared mailbox connection goes back to the Exchange 2010 legacy Org. So it seems we can only point back one Shared Mailbox Have you seen this before?
To clarify the ‘Send As’ permission.it seems from this posting that in order for a user to ‘send as’ for a shared mailbox, both the user and the shared mailbox need to be on-prem OR both moved to O365 is that correct? A) shared mailbox exists on-prem b) user moved to O365 and Outlook 2016 – granted full control over shared mailbox c) user gets error: You do not have permissions to send the message on behalf of the specified user So if I move the shared mailbox to O365, that user SHOULD be able to ‘send as’ the shared mailbox? Thanks very much. That’s great news!
This is the last issue we need resolved before we begin migrating to Exchange online. However we cant get this working When trying to add an Office 365 user to the full access permission on a on-prem 2013 shared mailbox the list of users available to choose from are only on-prem users, all office 365 users are excluded from the list and you cannot manually add a user no on the list. Maybe I’ve miss-configured something? We are running Exchange 2013 CU 16 on Server 2012 R2. Do we need CU 17 for this to work or was this change in exchange online?
Can you clarify this point from the technet article. “If a mailbox receives permissions from multiple mailboxes, that mailbox, and all of the mailboxes granting permissions to it, need to be moved at the same time.” Does this point only apply to permissions other than full access or all permissions? Or is it simply referring to maintaining permissions during the migration of a mailbox as in if both mailboxes aren’t moved simultaneously then permissions between those mailboxes will need to be recreated post migration, or is it saying that any user can only be delegated permissions to one cross premises shared mailbox and vice versa?