• Article for your preferred language does not exist. Below is international version of the article.

Article ID: 116292, created on Jun 18, 2013, last review on Sep 10, 2014

  • Applies to:
  • Operations Automation


A customer has POA-managed Hosted Exchange subscriptions with the service users and mailboxes like in the example below:

Your text to link here...

The key point - email address of one user (mbox1@customer.org) is the same as login name of another user.

If a customer try to grant the 'Send As' permission for the mailbox mbox1@customer.org on the mailbox johndoe@customer.org then POA task 'Grant send permissions for mailbox' fails with the following error message:

There are multiple users or groups matching the identity "mbox1@customer.org". Please specify a unique value.

See more detailed diagnostics in the example below:

Task name    Grant send permissions for mailbox 'johndoe' (id=273)
Last execution output
Provisioning request failed. Error in 'SW Managed Exchange.SetDeliveryPermissions'.
Exception calling "Execute" with "3" argument(s):
"There are multiple users or groups matching the identity "mbox1@customer.org". Please specify a unique value.


The reason of the problem is that there are two objects referencing the same value in Active Directory:

  • Service user #394 has login name mbox1@customer.org

  • Service user #395 has email address mbox1@customer.org

POA is using the Add-Permission Exchange cmdlet to grant permissions on the mailbox, the exact command looks like this:

Add-ADPermission -Identity "CN=johndoe,OU=S001000101,OU=Provider,OU=Hosting,DC=hosting,DC=local" -User "mbox1@customer.org" -ExtendedRights  Send-As -Confirm

The Exchange cmdlet Add-Permission found two target objects referencing mbox1@customer.org and fails to grant the Send-As permission.


Resolve conflict with two objects referencing the same value in AD, e.g. temporarily change login name of service user whose login is the same as email address of another service user, process failed POA task after that.

Additional information

This problem was fixed in scope of POA-65266 in 5.5 and in 5.4.14..

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF