This version of the application reached its end of life. We recommend that you upgrade to the latest supported version of the application. To obtain the latest supported version, see this article.

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

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.

CSP Program: CREST API is Replaced with Partner Center API

Microsoft plans to replace the CREST API with the Partner Center API (see https://msdn.microsoft.com/en-us/library/partnercenter/mt791651.aspx for details and the schedule). As a result, the Office 365 application starts using the Partner Center API for managing customer tenants and cloud subscriptions in the Microsoft cloud. On new application installations, the Partner Center API will be used by default. On existing application installations, the application will be switched from the CREST API to the Partner Center API during the upgrade of the application.

Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario

Obtaining

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

Dependencies and Pre-Requisites

The Office 365 Application Package requires:

  • Odin Automation 6.0.9 or a later 6.0.x version

Important: After upgrading Odin Automation from 6.0.x to 7.0.x, the Office 365 app must be immediately upgraded from 16.6.x to 16.8.x (see the allowed upgrade paths for the app in the KB article at https://kb.cloudblue.com/en/130752).

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.3. Upgrading from versions that are lower than 16.6.3 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.cloudblue.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.
  5. 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.
  6. 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.
  7. 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. Switching the Office 365 application from the CREST API to the Partner Center API.
  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.3. Upgrading from versions that are lower than 16.6.3 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.cloudblue.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.
  • Since version 16.6.4, as well as further 16.6.x versions, the Office 365 application does not use WildFly and Java installed on the Office 365 Application Endpoint Host. After upgrading to version 16.6.4, consider uninstalling them in order to release the hardware resources of the Office 365 Application Endpoint Host.

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. 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 -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.
  4. 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.

  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. Switch the Office 365 application from the CREST API to the Partner Center API:

    1. Create a native app in the Partner Center:

      1. Log in to the Partner Center.
      2. Go to Account setting > App management and click Add new native app.
      3. Write down App ID of the native app.
    2. Specify App ID of the native app in the ID of Native Client for Partner Center SDK setting of your Office 365 application instance:

      1. Log in to the Provider Control Panel.
      2. Go to Services > Applications and click on the Office 365 application. Then, click on your Office 365 application instance.
      3. Click Edit.
      4. Specify App ID of the native app in the ID of Native Client for Partner Center SDK setting. Then, click Save.
  7. Note: If your Odin Automation system has several Office 365 application instances, you must perform this step for each of them.

  8. 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

Internal content

Link on internal Article