Search Engine: Elastic

Article ID: 128993, created on Jun 22, 2016, last review on Jun 22, 2016

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


Office365 executing configuration script task failed with the following error:

Method add_user calling failed. Reason:SubscriptionOutOfSeatFault Method: SetUserSubscriptions


Office 365 subscription is not synced with MOP. It means that most probably customer created users and assigned licenses to them directly in MOP. As a result, OA does not know anything about this and 'thinks' that there are still unassigned licenses.


Method SetUserSubscriptions means that OA tries to assign license to the user and fails. How to troubleshoot such situation:

  1. Check MOP side and OA side - compare users having assigned/unassigned licenses and try to manually sync subscription with MOP by deleting/unassigning license from users in MOP

  2. Check if there are 'Deleted' users in MOP with licenses assigned. Users, marked as 'Deleted' do not take part in synchronization process

  3. Try to run synchronization script (cancel failed 'executing' task and corresponding 'finalizing' task before you start).

Real life example:

  • license was assigned to user A in MOP, license limit is 1 in the subscription
  • sync was not done yet, and the same license was assigned to user B via OA CCP
  • task for assigning license to the user B failed with SubscriptionOutOfSeatFault

The solution for such case will be to deassign license from user A via MOP.

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

Email subscription for changes to this article
Save as PDF