Article ID: 128853, created on May 22, 2016, last review on May 22, 2016

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5
  • Operations Automation 5.4


Office365 subscription synchronization fails with the following error:

Error: Object with id = xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx not found


Subscription (or customer account) was never provisioned to Microsoft, and it is absent in MOSI database.


In case the application under the subscription in question is in Waiting for the default subdomain to be specified status, please apply the instructions described in the following chapter of the documentation (step 3): Configuring Office 365 Subscription > Installing Application

Otherwise, check unprocessed or cancelled tasks, related to this subscription to identify the reason why it has not been provisioned yet.

Search Words

Object with id = ... not found

Subscription not synchronized from MOP

Object with

Application configuration script reported errors: ' error id "validation-error", setting id "Configuration": Method lock_customer calling failed. Reason:Object with id = b3b9bef8-d4f4-4d22-9818-0d8aac9716eb not found'

provisioning Office 365 accounts on staging environment

Reason:Object with id = 7c4eae5f-f635-4b22-b5a4-fddab75a5020 not found'

The provisioning tasks fail.

ac82ce33439a9c1feec4ff4f2f638899 caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 5b048d9bddf8048a00aba7e0bdadef37

Email subscription for changes to this article
Save as PDF