![user mapped user mapped](https://draft.io/assets/site/examples/en/full/example-user-story-mapping-01db983e7f754ab3264484de00312bbf.png)
#User mapped full
Scenario 1: Permissions are in place before the user or mailbox is being moved to the cloudĮxample: John has full access permissions to the Sales mailbox. In some hybrid scenarios, additional steps are required for auto-mapping to work. For more information about the AutoMapping parameter, see Add-MailboxPermission. You can disable auto-mapping by using the AutoMapping parameter of Add-MailboxPermission. These properties are not displayed as attributes by using Exchange PowerShell cmdlets. These properties can be viewed on-premises by using an Active Directory tool such as LDP or Active Directory Service Interfaces Editor (ADSI Edit). The user who is being granted permissions: msExchDelegateListBL The mailbox that is permissioned: msExchDelegateListLink
![user mapped user mapped](https://18f.gsa.gov/assets/blog/digital-acquisition-accelerator/example-user-story.png)
When these permissions are added, one value is added to the user and another to the mailbox to link the objects. In a non-hybrid deployment, auto-mapping is automatically enabled when a user is granted Full Access permissions to a mailbox by using the Add-MailboxPermission cmdlet or by using Exchange Admin Center (EAC). Note The auto-mapping feature is available only for Microsoft Exchange Online users. Values don’t exist for the Active Directory (AD) attributes to enable auto-mapping.
![user mapped user mapped](http://cdn.businessnews.com.au/articles-2019-09/Tianqi_Lithium-AM-03.jpg)
User is running an older version of Outlook. In Microsoft Office 365, mailboxes aren’t automatically mapped together with their Microsoft Outlook profile after a mailbox is moved to another forest in a hybrid deployment.