Screen shots of both messages as shown in the Outlook status bar follow.
Note This workaround requires the Office 365 administrator to use Windows PowerShell to change permissions to the Exchange Online mailboxes.
How to obtain explicit permissions to the secondary mailboxYour Exchange Online administrator must connect to the Office 365 environment by using Windows PowerShell to grant your user account explicit permission to the secondary or shared mailbox.
Important The administrator should use Run as administrator to start Windows PowerShell.
Although the symptom that is described in the "Symptoms" section is not caused by the AutoMapping feature, we recommend that AutoMapping be disabled when Outlook is used to connect to two or more Exchange Online accounts. To grant your user account explicit permissions to the secondary mailbox and at the same time to disable the AutoMapping feature, the administrator must follow these steps:
- Connect to Exchange Online by using Windows PowerShell:
- Click Start, and then click All Programs.
- Click Accessories, click Windows PowerShell, and then click Windows PowerShell.
- Run the following command:$LiveCred = Get-Credential
- In the Windows PowerShell Credential Request window that opens, type the credentials of an administrator account in your cloud-based organization. When you are finished, click OK.
- Run the following command:$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection
- To make sure that Windows PowerShell can run scripts, run the following command:Set-ExecutionPolicy RemoteSigned
- Run the following command:Import-PSSession $Session
Note A progress indicator appears that shows the importing of commands that are used in the cloud-based service into the client-side session of your local computer. When this process is complete, you can run the commands in the following steps.
- If the user does not have full access permissions to the secondary mailbox, go to step 3. If the user already has full access permissions to the secondary mailbox, follow these steps to remove full access permissions from the secondary mailbox:
- Run the following command:Remove-MailboxPermission -Identity <SecondaryMailbox> -User <PrimaryMailbox> -AccessRights FullAccessNote In this command, <SecondaryMailbox> represents the mailbox from which the primary mailbox user's permissions are being removed. For example, to remove Pedro Ruivo's full access permissions to John Smith's mailbox, use the following command:Remove-MailboxPermission -Identity firstname.lastname@example.org -User email@example.com -AccessRights FullAccess
- When you are prompted to confirm the action, type Y, and then press Enter.
- Run the following command:
- To grant full access permissions to the user for the mailbox, but not to enable AutoMapping, follow these steps:
- Run the following command:Add-MailboxPermission -Identity <SecondaryMailbox> -User <PrimaryMailbox> -AccessRights FullAccess -AutoMapping:$falseNote In this command, <SecondaryMailbox> represents the mailbox to which the primary mailbox user is being granted permissions. For example, to grant an administrator full access permissions to John Smith's mailbox, use the following command:Add-MailboxPermission -Identity firstname.lastname@example.org -User email@example.com -AccessRights FullAccess -AutoMapping:$false
- After you run this command, the following output is displayed:
Identity User Access Rights IsInherited Deny John Smith Contoso\johnsm Full access False False
- Run the following command:
- If the user also requires Send As permissions, run the following command:Add-RecipientPermission <SecondaryMailbox> -AccessRights SendAs -Trustee <PrimaryMailbox>Note In this command, <SecondaryMailbox> represents the mailbox for which the primary mailbox user is being granted Send As permission. For example, to grant an administrator Send As permissions on John Smith's mailbox, use the following command:Add-RecipientPermission "John Smith" -AccessRights SendAs -Trustee "Pedro Ruivo"
- Run the following command to disconnect the Windows PowerShell:Remove-PSSession $Session
How to remove credentials for the secondary mailbox from your local Windows workstationAfter the administrator grants your account explicit permissions to the secondary mailbox, you must remove any existing credentials that are stored on your local Windows workstation for the secondary mailbox. This forces Outlook to use your credentials to connect to both your own mailbox and to the shared mailbox.
Usually, when Outlook requires credentials to connect to a mailbox, a Windows Security dialog box appears. If you previously checked the Remember my credentials option, the credentials were saved on your workstation. To remove the credentials that were stored in Windows, follow these steps:
- Click Start, click Control Panel, and then click Credential Manager.
Note If View by is set to Category, click User Accounts first, and then click Credential Manager.
- Locate the set of credentials that are used to connect to *.outlook.com or to your Microsoft Office 365 domain.
- Expand the set of credentials, and then select Remove from Vault.
- Locate the set of credentials that are used to connect to the secondary mailbox.
- Expand the set of credentials, and then select Remove from Vault.Note If you are running Windows XP, run the User Accounts item in Control Panel. Click the Advanced tab, and then click the Manage Passwords button.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 2675986 - Last Review: Sep 5, 2013 - Revision: 1