Search Engine: Elastic

Article ID: 130743, created on May 3, 2017, last review on Jul 14, 2018

  • Applies to:
  • Business Automation 7.0

Table of Contents

Release Notes

You can read the complete Azure Cloud Solution Provider Integration 4.1 Release Notes here: PDF version.

Dependencies and Pre-Requisites

The Azure Cloud Solution Provider application package requires:

  • Odin Automation 7.1 or later version.
  • Update from must be installed before Azure upgrade to prevent incorrect invoices

Integration with Office 365:

  • 16.8.5 on Odin Automation 7.1

Azure Cloud Solution Provider Integration Features

The following new features are supported in the Azure Cloud Solution Provider Integration version 4.1 for Odin Automation Premium 7.1:

  • CCP v2 support. Now CCP v2 is supported for all the features. CCP v1 is still supported in this new version 4.1 on feature parity with 3.2 version.
  • Reuse of tenant domains of Azure and Office 365 registered elsewhere. A customer can now create a subscription using a domain registered earlier in another provider.
  • Customer reconciliation report. The new report will help customers and their providers/resellers reconcile customer invoices received from provider/reseller (CCP v2 only).
  • Budget cap for customers. Customers can setup email alerts to be triggered if the set budget is overused (CCP v2 only).
  • Dynamic provisioning of Azure templates. The Azure package contains a set of pre-defined and auto-configured templates that customers can see and use in their control panel. Besides these templates, providers can create or customize their own templates and make them available for using by customers (CCP v2 only).


Contact your Odin support account manager to obtain the new versions of the Azure Cloud Solution Provider (Azure CSP) application package.


To install the Azure CSP application, use the instructions provided in the Azure Cloud Solution Provider Integration Provider's Guide.


Important: The upgrade to version 4.1 is supported from 3.2.4/3.2.5 package version only. See the full upgrade instruction in PDF version of the release notes.


  • Azure CSP Integration 3.2.4/3.2.5.
  • Odin Automation Premium 7.1.
  • There are no tasks for provisioning, unprovisioning, updating Azure subscriptions/resources (not only running tasks, but any tasks).
  • Upgrade will take additional disk space for temporary data (approximately): 3*N, where N is the original data size. It will be removed after upgrade.
  • The following identification information must be prepared before upgrade:

    • Partner Tenant Name
    • OAuth Client ID
    • OAuth Secret Key
    • ID of Native Client for Partner Center SDK
    • ID of Native Client for Azure Resource Management API
    • Partner Admin User Name
    • Partner Admin Password
    • Offer ID


  • Source endpoint node – old endpoint node on Windows with Azure CSP Integration version 3.2.4/3.2.5.
  • Target endpoint node – new endpoint node on Linux with Azure CSP Integration version 4.1.
  • export.ps1 – export script. It is run on the source endpoint node and exports all the data from the source endpoint node. The exported data is packed in a ZIP file. The export script performs the following actions:

    • Validation checks.
    • Stops the website for application instance, and disables its auto-start.
    • Exports database into CSV files.
    • Gathers additional data used by import and needed for resource schema changes.
    • Makes ZIP archive with exported data.
  • – import script. It imports all the exported data to the target endpoint node. It is run on management node. The import script performs the following actions:

    • Validation checks.
    • Extracts ZIP archive.
    • Imports data into new database.
    • Starts the APS application instance upgrade (through OA Operations task) and waits for completion.
    • Removes temporary database tables.

Upgrade Procedure

  1. Deploy the Azure application endpoint host following all steps in the section Azure CSP Integration 4.1 Provider's Guide >> Deploying and Configuring Azure CSP Integration > Deploying 'Azure' Application > Deploying Azure Application Endpoint.

    Downtime starts. Azure services downtime depends on hardware performance and is approximately 1-2 hours per 1000 subscriptions plus 10 minutes on manual operations.

  2. Export data.

    1. Copy the export script (export.ps1) to the source node. The script is located in the Azure 4.1 distribution package. (For example, you have copied it into c:).
    2. On the source node, run the script in the PowerShell console. The required parameters: name of the IIS website of the Azure Integration 3.2.4/3.2.5 endpoint node and path for the ZIP file with exported data.

      Important: Before running the script, once again check that there are no Azure-related tasks in Odin Automation.

      The example for the default instance:

      c:\export.ps1 -azureSiteName "Azure Cloud Solution Provider - Internal" -outputZipFile c:\
  3. Import data.

    Note: The import script has the -h option to print the usage help.

    1. Copy the ZIP file with the exported data from the source endpoint node to the target endpoint node (remember the path you copied it to, for example, /root/
    2. On management node, unzip the distribution package to the software root directory with files replace. For example:

      unzip -d /usr/local/ -o
    3. On management node, run the import script ( from the software root directory (default is /usr/local). The required parameters: service node ID, where the target endpoint is installed (provider control panel > Infrastructure > Service Nodes), Azure APS instance ID (In PCP, go to Services > Applications > > Instances tab) and path on the target endpoint node, where the ZIP file is copied to.

      The example:

      python azure/deployment/ --host=<NODE_ID> --instance=<INSTANCE_ID> --data=<PATH>
  4. Post upgrade configuration. Azure CSP Integration 4.1 requires additional global configuration because of the new functionality and changes in API for managing Microsoft Azure.

    1. In provider control panel, go to Services > Applications > > Instances tab.
    2. Click on the name of the migrated instance and then go to Configuration tab and click Edit.
    3. Enter the required information (refer to the Azure CSP Integration 4.1 Provider's Guide >> Deploying and Configuring Azure CSP Integration > Deploying 'Azure' Application > Creating 'Azure' Application Instance).

    Downtime ends.

  5. In Billing panel, remove the 'aps_defaults_azure' parameter in all Azure service templates. (Go to Products > Service Plans > Service Templates tab > > Service Parameters tab).
  6. In Billing panel, set the SHOW_APPLICATION_SERVICE_PARAMETERS of the 'Buy Azure CSP' screen to 'true'. (Go to Products > Online Store > Screens tab).
  7. In Billing panel, synchronize the online store. (Go to Products > Online Store and click Synchronize Now).


  1. Starting from Azure CSP Integration 4.1, several application instances may be served with the single endpoint website. The upgrade supports such configuration: you can import the data from multiple application instances of Azure CSP Integration 3.2.4/3.2.5. You do not need new nodes in this case, only do repeat steps for exporting, importing, and post configuration.

  2. Upgrade does not export/import Partner Admin Password. This is to avoid saving unencrypted sensitive data into ZIP file, and transferring it over unknown channels between source and target endpoint nodes. Provider must enter this password in the application instance configuration along with other additional sensitive settings.

  3. Keep the source node and ZIP file for a while, do not remove it. They keep original data and may be useful for upgrade troubleshooting. Remove them when no issues found for some time.

Help Resources

Azure Cloud Solution Provider Integration 4.1 guides are available here:

198398b282069eaf2d94a6af87dcb3ff 8fc71f07abe5b233fea1ae0377cd5e3d c0f836394088a28cc30dd0e5fe8b600e b2c3b33425dfc50c7d41a2efaa7f84f3

Email subscription for changes to this article
Save as PDF