Synchronizing Changes from the Microsoft 365 Portal

Changes which are directly made by customers in the Microsoft 365 Portal are automatically synchronized from the portal to CloudBlue Commerce. Synchronization is performed by periodic tasks Synchronization with Office 365 Portal, which are executed every 15 minutes.

Note the following:

  • The number of Synchronization with Office 365 Portal tasks depends on how many application instances exist on your installation. Each application instance has its own Synchronization with Office 365 Portal task.
  • A Synchronization with Office 365 Portal task takes into account customer tenants that were never synchronized or were synchronized more than 12 hours before.
  • A Synchronization with Office 365 Portal task has a limit of 100 customer tenants. In other words, when such a task is run, it can process no more than 100 customer tenants.
  • Customers can manually start synchronization from the Customer Control Panel (both CCP v1 and UX1 for Customers). For CCP v1, synchronous calls are used instead of tasks. For UX1 for Customers, a separate task is scheduled.
  • Users' phone numbers are not synchronized.
  • Synchronization takes into account all licenses of Microsoft accounts of customers, including licenses that belong to cloud subscriptions obtained outside of CloudBlue Commerce.

The following changes are synchronized from the portal and reflected in CloudBlue Commerce:

  • A new user is added, modified, or removed.
  • A license is assigned or unassigned.
  • A domain is added or removed.

To monitor the status of synchronization, perform the following actions:

  1. Log in to the Provider Control Panel.
  2. Go to Operations > Tasks, and then select the Periodic tab.
  3. Click the Synchronization with Office 365 Portal task that you need.
  4. See task logs in the Last task execution results area.

Note that if a problem appears during synchronization, the respective Synchronization with Office 365 Portal task does not fail and continues its execution. To find detailed information on the problem, see the task's logs.