Search Engine: Elastic

Article ID: 132374, created on Mar 14, 2018, last review on Mar 14, 2018

  • Applies to:
  • Operations Automation


The script may add to the Office 365 service template resource types, which are lnked to a wrong Office 365 application instance. For example, there are 2 Office 365 application instances:

  • 17 UK: Microsoft Office 365
  • 18 AU: Microsoft Office 365

and 2 corresponding service templates:

  • 5 UK: Office 365
  • 6 AU: Office 365

first time, the scipt is run with the wrong pair instanceID/prefix - 17/AU:

# python --license-types-json LicenseTypes.json --service-plans-json ServicePlans.json --o365-app-instance-id 17 --prefix AU

In case the file LicenseTypes.json contains the offer Office 365 Business Essentials, it creates a corresponding APS resource of type linked to the app instance #17. Next, the script creates the resource type AU: Office 365 Business Essentials referring to this license APS resource. On this first run the script will not add the resource AU: Office 365 Business Essentials to the service template AU: Office 365 as it cannot access this service template on behalf of the app instance #17.

However, on the next run of the script, with the correct parameters 18/AU, such resources will be added to the service template:

# python --license-types-json LicenseTypes.json --service-plans-json ServicePlans.json --o365-app-instance-id 18 --prefix AU

The script will try to create the resource type AU: Office 365 Business Essentials, find an existing one and include it into the the service template AU: Office 365. As a result, the service template AU: Office 365 will have resource types, which refer to the application instance #17 (UK).


When the script searches for existing resource types, it does not check which app instances those linked to. Such behaviour was recognized as a software issue APSA-19595.


Please contact your Technical Account Manager in order to clarify the current status of the issue.

Remove the incorrect resource types, created on the first run of the script. The full list of the created resource types can be found in the log file at /var/log/pa/csp. Created resource types can be found by the command like below:

# egrep "Creating RT | return {'status': 0, 'result': {'resource_type_id':" /var/log/pa/csp/csp_insta-2018-03-11_22-53-07.404.log

2018-03-08 21:21:03.533 [INFO] Creating RT AU: Office 365 Business Essentials
2018-03-08 21:21:03.822 [DEBUG] return {'status': 0, 'result': {'resource_type_id': 1000650}}

The line return {'status': 0, 'result': {'resource_type_id': 1000650}} shows, that the resource type AU: Office 365 Business Essentials was created with the ID 1000650, so it can be found and deleted.

Read more about in the Office 365 documentation (see the Automated Procedure section).

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF