Search Engine: Elastic

Article ID: 128658, created on Apr 12, 2016, last review on Apr 12, 2016

  • Applies to:
  • Operations Automation


Office365 user synchronization failed with the following error in synchronization log:

Unable to update following user(s) automatically:
    username@example.tld:         Resource type for offer set {['OFFER_NAME1', 'OFFER_NAME2'..]} cannot be found in subscription's Service Template. Either add new resource type with all required offers to the subscription or modify existing one, or adjust the offer set in MOP.

Offers mentioned in the error are services, not add-ons.

After that the subscription was marked as requires manual handling in synchronization log, and the corresponding user became not in sync. OA subscription has all necessary resources, and limits were not exceeded.


User has two or more different services assigned in MOP. In OA subscription corresponding offer IDs are set in activation parameters of different resource types.

By design in version 4.X of APS application Microsoft Office 365 synchronization will be successful if all necessary offers are set in activation parameters of one resource type. It means that if there is no resource type containing such services combination in OA subscription, then synchronization fails. This issue does not exist in version 5.X of application Microsoft Office 365.


Install Microsoft Office 365 package version 5.X or higher (the latest 6.X version is the most preferable). Then migrate existing O365 APS 1.2 subscriptions to APS 2.0. Details about the migration process can be found in the guide: Upgrading Office 365 Subscriptions from APS 1.2 to APS 2

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF