Article ID: 128951, created on Jun 14, 2016, last review on Jul 1, 2016

  • Applies to:
  • Operations Automation 6.0

Table of Contents

Release Notes

You can read the complete Azure Cloud Solution Provider Integration 3.0 Release Notes here: Also, you can download the PDF version.

Dependencies and Pre-Requisites

The Azure Cloud Solution Provider application package requires:

  • Odin Automation 6.0.8 or later
  • Odin Automation billing 6.0.8 or later

Azure Cloud Solution Provider Integration Features

The following features are supported in the Azure Cloud Solution Provider Integration version 3.0:

  • Support of 2-Tier resellers and 1-Tier resellers’ accounts under provider. Registration by MPN ID is now optional and if it’s not set – end-customers are provisioned under partner’s account at Microsoft and a reseller doesn’t get any benefits from Microsoft in this case.
  • Integration with Office 365 application package (by Odin). Now it's possible to re-use an existing tenant for the customers who already have Office 365 subscription in Odin Automation. This functionality is available for Office 365 Integration version 16.5.
  • Synchronization of usage reports with billing time. By default, end-customers see their usage reports synced with the time on their local machines, which may differ from the reports they are billed with. It happens because billing system is located in a different timezone. By using synchronization settings, providers can let users see the real-time reports.
  • Number of decimals is increased for the Retail Markup setting – now 5 decimal places are available, which allows making the pricing adjustment more flexible.
  • Usage Reports selector behavior is improved.

Fixed Issues

APSA-15440 TenantsController.Delete finished by exception System.NullReferenceException: Object reference not set to an instance of an object

APSA-15159 Cannot create subscription with Azure CSP if previous provisioning task with Azure CSP failed

APSA-14891 Reseller L2 (under the L1) that cannot render the Reseller tab after modifying one of its L2's markup to -100%

Known Issues and Limitations

  • There is a delay in usage reporting from Microsoft side: the delivery of usage reports for some services may take from 3 to 48 hours till the information is updated on the dashboard in CCP and in the usage reports.
  • The creation of a subscription for the end-customer may take up to two hours due to the delay from Microsoft side.
  • The task "Synchronize resource usage for instances of APS applications" processes resource instances with counters in the order they were created. As a result, all resource instances belonging to resellers are processed before resource instances of their customers. This might delay the real usage of resellers.


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 3.0 is supported from 1.2 package version only.

  1. Unzip the application package The endpoint package ( file) contains 3 files:

    • install.bat
    • update.bat
  2. Copy them to the endpoint host. The upgrade is run by update.bat.
  3. To start the upgrade of the endpoint default instance, which was installed to the default location for the unnamed instance (“%ProgramFiles%\Odin\Azure CSP”) using “Integrated Security” to connect to the database, run this file without any arguments. After the finishing, the console window will stay open.
  4. Login to Odin Automation as a provider, import new Azure CSP package and upgrade the application instance.
  5. After the upgrade to Azure CSP 3.0, update Odin Automation billing online store and CP customizations with and

The upgrade script can be run with the following command line arguments:

Name Description Default Value
SILENT Run in the silent mode. If set to "Yes", the console window will close on finishing the upgrade. No
INSTANCENAME It allows to specify the name of the instance to be upgraded, if it is installed in the default location for the named instances ("%ProgramFiles%\Odin\Azure CSP` (%INSTANCENAME%"). Empty
TARGETDIR It allows to specify the target directory where the upgrading instance is installed. You can use this setting if an instance was installed to a non-default location. If this setting is specified in the command line, then “INSTANCENAME” setting is ignored. “%ProgramFiles%\Odin\Azure CSP” for the default instance and “%ProgramFiles%\Odin\Azure CSP (%INSTANCENAME%)” for a named instance (if “INSTANCENAME” is passed via the command line). “%ProgramFiles%\Odin\Azure CSP” for the default instance and “%ProgramFiles%\Odin\Azure CSP (%INSTANCENAME%)” for a named instance (if “INSTANCENAME” is passed via the command line).
DBLOGIN and DBPASSWORD Database administrator login and password. It allows to pass the login and password to access the database to make the upgrade of the database, if “Integrated security” is not used or a user running “update.bat” doesn’t have an administrative permissions to the database. "sa" for DBLOGIN and empty for DBPASSWORD, which means “use the integrated security”.

Note: If you have more than one instances of the back-end web site or the single instance is a non-default one, you have to upgrade each instance separately running update.bat with the proper value of the “INSTANCENAME” setting.

Help Resources

Azure Cloud Solution Provider Integration 3.0 guides are available here:

All Azure Cloud Solution Provider Integration Release Notes

Supported APS Application Packages Versions in Odin Automation

Office 365 and Azure CSP Subdomain Form for Odin Automation billing Control Panel (Customization Files)

Office 365 and Azure CSP Subdomain Form for Odin Automation billing Online Store (Layout Template Customizations)

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF