Search Engine: Elastic

Article ID: 129826, created on Nov 8, 2016, last review on May 22, 2017

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 6.0
  • Business Automation 7.0
  • Business Automation 6.0

Table of Contents

Release Notes

You can read the complete Office 365 16.6 Release Notes here: http://download.automation.odin.com/poa/Office365_APS2/doc/86178.htm. Also, you can download the PDF version.

New Features and Changes

Conversion from Syndication Partner Program to CSP Program is Supported

Conversion from Syndication Partner Program to CSP Program is now supported by the Office 365 application.

Conversion is performed on both the Microsoft side and the Odin Automation side.

Microsoft Side

Conversion on the Microsoft side is the transportation of financial information from a commercial system of the Syndication Partner Program to a commercial system of the CSP Program.

Key points of conversion:

  • Service data of customer tenants is not modified during the conversion of the customer tenants. Daily operations of end-users of the customer tenants are not affected.

  • The Office 365 admin center of the CSP Program is slightly different from the Office 365 admin center of the Syndication Partner Program.

  • The offer catalogue of the CSP Program and the offer catalogue of the Syndication Partner Program are different:

    • Both programs have a set of common offers and conversion is possible only within the set. This means that cloud subscriptions of other offers must be either replaced with cloud subscriptions of common offers or cancelled before conversion.

    • The CSP Program does not support trial offers. This means that trial cloud subscriptions cannot be converted. Trial cloud subscriptions must be either replaced with paid ones or cancelled before conversion.
  • The programs provide different APIs for managing customer tenants and cloud subscriptions. The Syndication Partner Program provides the MOSI API. The CSP Program provides the CREST API.

  • The CSP Program is globally divided into geographical regions (the regions can be seen at https://www.microsoft.com/en-us/licensing/licensing-programs/open-regional.aspx). CSP partners can sell Office 365 services only within their regions. For example, a CSP partner from the North America region can sell Office 365 services to customers only from the United States and Canada. This means that several CSP partner accounts might be required for a syndication partner who sells Office 365 services in various countries.

  • TIP partner accounts cannot be used to test conversion.

  • Before performing conversion, a partner must contact a Microsoft representative to discuss and approve the volume and schedule of conversion.

Odin Automation Side

Conversion on the Odin Automation side is the replacement of Office 365 syndication subscriptions with Office 365 CSP subscriptions.

Key points of conversion:

  • The Office 365 APS 1.2 and Office 365 APS 2 applications are supported.

  • A syndication partner might have several organization units for selling Office 365 services. This means that a separate CSP partner account is required for each organization unit.

  • Odin Automation supports the following configurations of Office 365 service plans:

    • Consolidated. All offers are available within an Office 365 service plan. A typical customer account has one subscription to such an Office 365 service plan.

    • Partitioned. All offers are partitioned into groups. A typical group contains one offer and its depended addon offers. Offers constituting a group are available only within a separate Office 365 service plan. A typical customer account has several subscriptions to such Office 365 service plans.

    It is possible to change one service plan configuration to another one during conversion.

  • Conversion is performed by using scripts shipped with the Office 365 application.

  • Customer accounts whose Office 365 subscriptions, customer tenants, and cloud subscriptions you need to convert must be split into groups. You must convert these groups one by one. This means that several groups must not be converted concurrently.

Limitations

Note the following limitations of the conversion scripts:

  • The scripts can automatically process Office 365 subscriptions including non-Office 365 resources only if the limits of the resources are zero.
  • The scripts do not automatically process Office 365 subscriptions whose 'DNS Hosting' resources are in use by domains.

    Note: Subdomains of the onmicrosoft.com domain are automatically processed by the scripts.

Odin Automation Premium Office 365 Integration Provider's Guide >> Conversion from Syndication Partner Program to CSP Program

Improved CSP Import Scripts

The following improvements were made in the CSP import scripts readCSPAccounts.py and importSubsCSP.py:

readCSPAccounts.py

  • Office 365 service plans with composite resources are now taken into account by the script.
  • Suspended cloud subscriptions are now taken into account by the script.

importSubsCSP.py

  • The input parameter o365APS2-app-instance-id was renamed to csp-app-instance-id.
  • The input parameter vendor-id is obsolete and ignored by the script.

Odin Automation Premium Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Importing Tenant Subscriptions from Microsoft Cloud into Odin Automation

Important: This section provides the list of new features and changes. To obtain the detailed description of a new feature or change, you must read the corresponding section of the complete release notes. You can read the complete Office 365 16.6 Release Notes here: http://download.automation.odin.com/poa/Office365_APS2/doc/86178.htm. Also, you can download the PDF version.

Fixed Issues

  • APSA-16926 Task 'Provisioning "Tenant" for APS application Vodafone Office 365' got stuck in 'Rescheduled' state.
  • APSA-16906 Tasks 'Provisioning "AsyncOperation" for APS application Office 365' failed.
  • APSA-16894 Import script fails with timeout error, but subscription created in Odin Automation is not rolled back.
  • APSA-16883 Task 'Provisioning "Subscription" for APS application Office 365' failed.

Important: This section provides the list of fixed issues. To obtain the detailed description of a fixed issue, you must read the corresponding section of the complete release notes. You can read the complete Office 365 16.6 Release Notes here: http://download.automation.odin.com/poa/Office365_APS2/doc/86178.htm. Also, you can download the PDF version.

Obtaining

Contact your Odin Support account manager to obtain the new versions of the Office 365 Application Package.

Dependencies and Pre-Requisites

The Office 365 Application Package requires Odin Automation 6.0.9 or later (including Odin Automation 7.0).

Installation

To install the Office 365 Application, use the instructions provided in the Odin Automation Office 365 Integration Provider's Guide.

Upgrade Procedure

Upgrade Procedure (Syndication Partner Scenario)

The upgrade procedure consists of the following steps:

  1. Preparing necessary information for upgrading the Office 365 Application End-point (collecting Office 365 Dispatcher Site parameters).
  2. Preparing necessary information for upgrading the Office 365 Application End-point (collecting Office 365 Gateway Site parameters).
  3. Stopping provisioning Office 365 services.
  4. Upgrading the Office 365 Application End-point.
  5. Upgrading the Office 365 Application.
  6. Starting provisioning Office 365 services.

Important:

  • The upgrade procedure is not reversible.
  • Upgrade steps 1-6 are mandatory.
  • Make sure the current version of the Office 365 Application is 16.6.1. Upgrading from versions that are lower than 16.6.1 is not supported.
  • Before upgrading the Office 365 application from one version to another one, make sure that you are going to follow the allowed upgrade paths. See the KB article https://kb.odin.com/en/130752 for details.
  • Make sure SQL Server logins of Office 365 Gateway Application Databases have the sysadmin server role. See Odin Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Deployment Architecture > Preparing SQL Server Databases for details.

To upgrade an existing installation of the Office 365 Application, perform the following steps:

  1. Prepare necessary information for upgrading the Office 365 Application End-point. You must prepare the name of the Office 365 Dispatcher Site, the name of the Office 365 Dispatcher Application, and the IP Address of the Office 365 Dispatcher Site. This can be done in the following way:

    1. Prepare the URL provided to Microsoft. This URL is structured in the following way: https://<Hostname_of_Office_365_Dispatcher_Site>/<Name_of_Office_365_Dispatcher_Application>/.
    2. Write down the name of the directory from the URL. This is the name of the Office 365 Dispatcher Application.
    3. Resolve the hostname from the URL into the IP address. This is the IP address of the Office 365 Dispatcher Site. Write down this IP address.
    4. Log on to the Office 365 Application End-point Host as Administrator via RDP.
    5. Open Internet Information Services (IIS) Manager.
    6. Go to the list of sites.
    7. From the list, select the site with the IP address obtained above.
    8. Write down the name of the site. This is the name of the Office 365 Dispatcher Site.
  2. Prepare necessary information for upgrading the Office 365 Application End-point. You must prepare the name of the Office 365 Gateway Site, the name of the Office 365 Gateway Application, the hostname of the Office 365 Gateway Site, and the IP Address of the Office 365 Gateway Site. This can be done in the following way:

    1. Log in to Provider Control Panel.
    2. Go to Service > Applications and click the Office 365 Application.
    3. Select the Instances tab and click the target Application Instance.
    4. Select the General tab.
    5. Obtain the value of the Application API end-point URI setting. This is a URL that is structured in the following way: https://<Hostname_of_Office_365_Gateway_Site>/<Name_of_Office_365_Gateway_Application>/aps/.
    6. Write down the name of the directory from the URL. This is the name of the Office 365 Gateway Application.
    7. Write down the hostname from the URL. This is the hostname of the Office 365 Gateway Site.
    8. Resolve the hostname from the URL into the IP address. This is the IP address of the Office 365 Gateway Site. Write down this IP address.
    9. Log on to the Office 365 Application End-point Host as Administrator via RDP.
    10. Open Internet Information Services (IIS) Manager.
    11. Go to the list of sites.
    12. From the list, select the site with the IP address obtained above.
    13. Write down the name of the site. This is the name of the Office 365 Gateway Site.
  3. Stop provisioning Office 365 services:

    1. In Odin Automation, go to Operations > Tasks and make sure all Office 365 tasks are processed.
    2. Stop provisioning Office 365 services. For example, deactivate the Office 365 Service Template in Odin Automation.
  4. Upgrade the Office 365 Application End-point:

    1. Upload the Office 365 Application Package to the Office 365 Application End-point Host.
    2. Unpack the Application Package.
    3. Unblock the content of the O365-Web.zip file. To do this, right-click the file in Windows Explorer, click Properties, click Unblock, click OK.
    4. Unpack the O365-Web.zip file.
    5. Start Windows PowerShell Console and go to the directory where the content of the O365-Web.zip file is placed.
    6. Run the .\setup.cmd -DispatcherSiteName <The name of the Office 365 Dispatcher Site> -DispatcherAppName <The name of the Office 365 Dispatcher Application> -DispatcherIPAddress <The IP address of the Office 365 Dispatcher Site> -GatewaySiteName <The name of the Office 365 Gateway Site> -GatewayAppName <The name of the Office 365 Gateway Application> -GatewayIPAddress <The IP address of the Office 365 Gateway Site> -GatewaySiteCertSubject <The hostname of the Office 365 Gateway Site> -Force command.

    Notes:

    • If you have several Office 365 Gateway Sites on the Office 365 Application End-point Host, use the provided above procedure to upgrade each Office 365 Gateway Site.
    • If you need to update your client Microsoft certificate, you can do this in the following way: upload the new client Microsoft certificate to the Office 365 Application End-point Host; add -MSCertPath <path to certificate> to the command provided above; run the command.
  5. Upgrade the Office 365 Application:

    1. Import the Office 365 Application Package to Odin Automation. See OA Operations Provider's Guide >> Application Hosting > Managing Applications > Importing Application for details.
    2. Upgrade existing Office 365 Application instances. See OA Operations Provider's Guide >> Application Hosting > Bulk Application Upgrades for details.
  6. Start provisioning Office 365 services. For example, activate the Office 365 Service Template in Odin Automation.

Upgrade Procedure (Cloud Solution Provider Scenario)

The upgrade procedure consists of the following steps:

  1. Preparing necessary information for upgrading the Office 365 Application End-point (collecting Office 365 Gateway Site parameters).
  2. Stopping provisioning Office 365 services.
  3. Upgrading the Office 365 Application End-point.
  4. Upgrading the Office 365 Application.
  5. Starting provisioning Office 365 services.

Important:

  • The upgrade procedure is not reversible.
  • Upgrade steps 1-5 are mandatory.
  • Make sure the current version of the Office 365 Application is 16.6.1. Upgrading from versions that are lower than 16.6.1 is not supported.
  • Before upgrading the Office 365 application from one version to another one, make sure that you are going to follow the allowed upgrade paths. See the KB article https://kb.odin.com/en/130752 for details.
  • Make sure SQL Server logins of Office 365 Gateway Application Databases have the sysadmin server role. See Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Deployment Architecture > Preparing SQL Server Databases for details.

To upgrade an existing installation of the Office 365 Application, perform the following steps:

  1. Prepare necessary information for upgrading the Office 365 Application End-point. You must prepare the name of the Office 365 Gateway Site, the name of the Office 365 Gateway Application, the hostname of the Office 365 Gateway Site, and the IP Address of the Office 365 Gateway Site. This can be done in the following way:

    1. Log in to Provider Control Panel.
    2. Go to Service > Applications and click the Office 365 Application.
    3. Select the Instances tab and click the target Application Instance.
    4. Select the General tab.
    5. Obtain the value of the Application API end-point URI setting. This is a URL that is structured in the following way: https://<Hostname_of_Office_365_Gateway_Site>/<Name_of_Office_365_Gateway_Application>/aps/.
    6. Write down the name of the directory from the URL. This is the name of the Office 365 Gateway Application.
    7. Write down the hostname from the URL. This is the hostname of the Office 365 Gateway Site.
    8. Resolve the hostname from the URL into the IP address. This is the IP address of the Office 365 Gateway Site. Write down this IP address.
    9. Log on to the Office 365 Application End-point Host as Administrator via RDP.
    10. Open Internet Information Services (IIS) Manager.
    11. Go to the list of sites.
    12. From the list, select the site with the IP address obtained above.
    13. Write down the name of the site. This is the name of the Office 365 Gateway Site.
  2. Stop provisioning Office 365 services:

    1. In Odin Automation, go to Operations > Tasks and make sure all Office 365 tasks are processed.
    2. Stop provisioning Office 365 services. For example, deactivate the Office 365 Service Template in Odin Automation.
  3. Upgrade the Office 365 Application End-point:

    1. Upload the Office 365 Application Package to the Office 365 Application End-point Host.
    2. Unpack the Application Package.
    3. Unblock the content of the O365-Web.zip file. To do this, right-click the file in Windows Explorer, click Properties, click Unblock, click OK.
    4. Unpack the O365-Web.zip file.
    5. Upgrade the Office 365 CSP Component (csp-agent-war) to the latest version using the instruction of the https://kb.odin.com/en/126003 KB Article.
    6. Start Windows PowerShell Console and go to the directory where the content of the O365-Web.zip file is placed.
    7. Run the .\setup.cmd -GatewaySiteName <The name of the Office 365 Gateway Site> -GatewayAppName <The name of the Office 365 Gateway Application> -GatewayIPAddress <The IP address of the Office 365 Gateway Site> -GatewaySiteCertSubject <The hostname of the Office 365 Gateway Site> -Force command.

    Note: If you have several Office 365 Gateway Sites on the Office 365 Application End-point Host, use the provided above procedure to upgrade each Office 365 Gateway Site.

  4. Upgrade the Office 365 Application:

    1. Import the Office 365 Application Package to Odin Automation. See OA Operations Provider's Guide >> Application Hosting > Managing Applications > Importing Application for details.
    2. Upgrade existing Office 365 Application instances. See OA Operations Provider's Guide >> Application Hosting > Bulk Application Upgrades for details.
  5. Start provisioning Office 365 services. For example, activate the Office 365 Service Template in Odin Automation.

Help Resources

Office 365 Integration Guides are available here: http://download.automation.odin.com/pa/.

All Office 365 Integration Release Notes

Supported APS Application Packages Versions in Odin Automation

Office 365 and Azure CSP Subdomain Form for OA Billing Control Panel (Customization Files)

Office 365 and Azure CSP Subdomain Form for OA Billing Online Store (Layout Template Customizations)

[Odin Automation Premium] [Office 365] Allowed Upgrade Paths

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 198398b282069eaf2d94a6af87dcb3ff 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328 c0f836394088a28cc30dd0e5fe8b600e b2c3b33425dfc50c7d41a2efaa7f84f3 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF