Fix There is No Existing Permission Entry Found for User Error
Write-ErrorMessage : ||There is no existing permission entry found for user:.
Error Message
Write-ErrorMessage : |Microsoft.Exchange.Management.StoreTasks.UserNotFoundInPermissionEntryException|There is no existing permission entry found for user:'UserDisplayName'.
Root Cause Analysis
This error appears when you use the ‘Set-MailboxFolderPermission’ cmdlet to grant a mailbox folder permission to users or groups for the first time.
Note: ‘Set-MailboxFolderPermission’ cmdlet is used exclusively to modify mailbox folder permissions once it is assigned.
How to Fix There is No Existing Permission Entry Found for User Error
Solution - Via Exchange Online PowerShell
3 mins
Admin Permission Required
Use the ‘Add-MailboxFolderPermission’ cmdlet to assign folder permissions to users or groups for the first time.
-
The Exchange admin center (EAC) doesn’t provide a straightforward option to specifically manage mailbox folder permissions.
-
It primarily allows you to manage mailbox delegations, such as Full Access, Send As, and Send-on-behalf permission.
Add Exchange Online Mailbox Folder Permissions Using PowerShell
Follow the steps below to add the mailbox folder permissions using Exchange Online PowerShell.
-
Connect to Exchange Online PowerShell as an administrator.
-
Since the calendar (Bruce's folder) hasn’t been assigned already to a user (Saansui), you need to execute the below cmdlet to add the Exchange Online mailbox calendar permission.
-
Windows PowerShell
Add-MailboxFolderPermission -Identity <MailboxUserUPN>:\<FolderName> -User <DelegatedUserUPN> -AccessRights <RolesOrPermissions> #You can specify multiple permissions and roles separated by commas. -
Check whether the mailbox folder permission for the Bruce's mailbox has been assigned to a user (Saansui) by executing the below.
-
Windows PowerShell
Get-MailboxFolderPermission -Identity <MailboxUserUPN>:\FolderName -
Points to Remember
-
Ensure appropriate folder permissions are assigned to the delegated user to avoid overexposure of sensitive information.
-
When you assign the same permission that is already set, you will see the following warning message:
-
WARNING: The command completed successfully but no permissions of Identity:'********-****-****-****-************:\calendar' have been modified.
Still Need Help?
If these solutions don’t resolve your issue, feel free to leave a comment in the below ‘Discussion section’. We’ll assist you to the best of our ability. However, if none of the solutions worked, you may need to contact Microsoft Support for additional help.