With more persistence testing so many different scenarios, I've narrowed it down to: This also triggered Outlook to keep prompting to enterįixed it. This time without adding another account but then I logged in to Office App Account - found in File > Account > User Information. But when I added another account, everytime the user logs in and starts Outlook, it prompts to enter password.Ģnd round of test creating a new profile using the same account. I did a test creating a new profile using the same account which works fine on its own.
I have tried all suggestions from all places in the forums - clearing Password cache, Windows Credentials, Registry key fixes and Autodiscover to no avail. This only happens to users withĪdditional account - i.e. It would be OK after signing in for the entire session but upon logout and logging back in, it keeps asking for password. Problem is Outlook started asking for password when we added another email account of the same domain. Email is hosted by Office 365 and not on-prem. This is a new deployment so it's a fresh clean RDS with new profiles. C:\>Get-ADUser -Filter -Properties msExchDelegateListLink | Select -ExpandProperty msExchDelegateListLinkĬN=Bruce.Thillainayagam,OU=Users,OU=Head Office,OU=Company,DC=exchangeserverpro,DC=netĬN=Alex.We have Office ProPlus 2019 VL Outlook version 0.20017 圆4 running on RDS. For example, to view the list of auto-mapped users for a mailbox named Payroll, we can run the following command. The property that stores this information is named msExchDelegateListLink, and it can be queried using Get-ADUser. However, for on-premises mailboxes you can query the Active Directory user object properties to determine who will be auto-mapped to a mailbox. If the user needs to access the mailbox for anything, they must add it to their profile, or open it via the Outlook File menu.Īs a side note, there’s nothing in the Get-MailboxPermission output that will tell you whether a user who has access to a mailbox will be auto-mapped. When Outlook receives the updated Autodiscover response, it will remove the auto-mapped mailbox from the user’s Outlook profile. The change will not immediately be obvious to the end user, because there is a delay before their Outlook client picks up the change via Autodiscover. C:\>Add-MailboxPermission -Identity SharedOnPremMailbox -User Adam.Wally -AccessRights FullAccess -AutoMapping:$false Yes Yes to All No No to All Help (default is "Y"): yįinally, re-add the mailbox permission by running Add-MailboxPermission, this time using the -AutoMapping parameter to disable auto-mapping. Removing mailbox permission "SharedOnPremMailbox" for user "Adam.Wally" with access rights "'FullAccess'". C:\>Remove-MailboxPermission -Identity SharedOnPremMailbox -User Adam.Wally -AccessRights FullAccessĪre you sure you want to perform this action? Next, use Remove-MailboxPermission to remove the mailbox permission for the user. Identity : /Company/Head Office/Shared/SharedOnPremMailbox C:\>Get-MailboxPermission -Identity SharedOnPremMailbox -User Adam.Wally | fl Using the example from the screenshot above, the user in question is Adam Wally, and the shared mailbox is named ShareOnPremMailbox. Use Get-MailboxPermission to check that the permissions have been granted as mailbox permissions. First, for an on-premises mailbox open the Exchange Management Shell, or for a cloud mailbox connect to Exchange Online. To remove and re-add a user’s mailbox permissions using PowerShell, we can use the following steps. Also, this will need to be performed using PowerShell, because the Exchange Admin Center doesn’t expose the option to enable or disable auto-mapping when configuring mailbox permissions. If you want to remove auto-mapping for a user’s access to a shared mailbox, then you must remove their mailbox permissions and then re-add the permissions again. The auto-mapping option can only be configured at the time the permissions are granted. When auto-mapping is enabled, Outlook receives extra information in the Autodiscover response that tells it to open the additional mailbox. The reason that the shared mailbox appears in Outlook, but does not appear in the Outlook account settings, is that auto-mapping is enabled by default when a user is granted access to a shared mailbox or to another user’s mailbox. In the Outlook account settings for the user, the shared mailbox does not appear as an additional mailbox. This can occur for on-premises Exchange Server and cloud-hosted mailboxes in Exchange Online. Although this case was for shared mailboxes, the cause and solution apply equally to user mailboxes. In this case they were shared mailboxes and appeared in the left pane of Outlook. A customer asked about a situation in which they’re unable to remove mailboxes from users’ Outlook profiles.