Search Engine: Elastic

Article ID: 133528, created on Dec 18, 2018, last review on Feb 25, 2019

  • Applies to:
  • Operations Automation 7.2
  • Operations Automation 7.4

Symptoms

Office 365 users synchronization fails with the following output:

- user@example.onmicrosoft.com (Unable to process the ambiguous license assignment.)

The following string can be found in the Office 365 sitelog:

WARN sync: User with azure Ad-ObjectID '8facca47-xxxx-xxxx-xxxx-bc8600539bbd' (user id is 'edxxxx40-xxxx-xxxx-xxxx-cd0df075223a') has an ambiguous license assignment: unable to bind Provisioning IDs 'MCOPSTN2' to any customer subscriptions.

Cause

Microsoft does not differentiate subscriptions for the same offer in scope of user license assignment, but the Office 365 application does. This behavior will be improved in scope of request #APSA-19010.

Resolution

There are few possible cases with different ways to resolve the issue.

  1. Common Area Phone addon misconfiguration. To avoid the issue, it is required to find Common Area Phone license in the Office 365 instance settings and mark it as can be assigned to users. After that go to Add-on tab and add Common Area Phone license as parent for Domestic Calling add-on.

  2. Two subscriptions with the same offer on the Odin Automation side, but one is in disabled state. In order to fix the issue, need to destroy disabled subscription or re-activate it.

  3. Discrepancy between license quantity for the same subscription on the Odin Automation and Microsoft sides. Quantity for subscription on Microsoft side is bigger then in Odin Automation. In order to resolve the issue, buy additional licenses through the billing to make it equal to Microsoft.

  4. Customer has additional subscription for the same offer on Microsoft side but this subscription absent in Odin Automation. In this case, it is required to import this subscription to Odin Automation.

  5. Customer has additional subscription for the same offer purchased through another Microsoft Partner. There is no workaround for such case at the moment.

Contact your Technical Account Manager or Pooled Technical Associates to trace the status of the #APSA-19010.

31987597efff5a3a9ce779cc203bbe5e 8fc71f07abe5b233fea1ae0377cd5e3d 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 55fe109b4b4fe3fbb893f22dbb85a41a

Email subscription for changes to this article
Save as PDF