Article ID: 126131, created on Jul 9, 2015, last review on Aug 10, 2016

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5

Table of Contents

Release Notes

You can read the complete Office 365 6.2 Release Notes here: http://download.pa.parallels.com/poa/Office365_APS2/doc/83978.htm. Also, you can download the PDF version.

Dependencies and Pre-Requisites

The Microsoft Office 365 Application Package requires:

  • Operations Automation 6.0.5 or later
  • Business Automation 6.0.5 + Business Automation 6.0.5 HOTFIX 126924 (https://kb.odin.com/en/126924) or later

Important:

  1. If Windows-based Branding Servers are used on your Service Automation installation, make sure the instructions of the https://kb.odin.com/en/122036 KB Article are performed.

  2. Powershell 3.0 should be installed on the endpoint host in order to use Graph API

Fixed Issues

  • APSA-10143 Empty administrative passwords are shown after upgrading Office 365 subscriptions from APS 1.2 to APS 2.
  • APSA-12393 It is not possible to switch Office 365 license because wizard hangs.
  • APSA-11884 Wrong alignment of prices in 'Upgrade License' popup.
  • APSA-11880 There is no hint in 'Upgrade License' popup that prices do not include taxes.
  • APSA-11022 License description link is shown even if description is empty.
  • APSA-12605 Subdomain availability checker does not work in Safari.
  • APSA-12550 Script fixLimitChangeSubscription.py (fix for APSA-12060) does not work with Operations Automation 5.5.8.
  • APSA-12508 Upgrading Office 365 subscriptions from APS 1.2 to APS 2: upgrade script rewrites subscription periods and sets up new wrong expiration dates.
  • APSA-12302 Microsoft Office 365 Application tries to change order status from 'OP' to 'OP'.
  • APSA-12133 Prices updated in 'Adjust limit' window are not updated in Office 365 subscription.
  • APSA-12060 Resources 'http://www.parallels.com/Office365/Subscription/' created till Microsoft Office 365 5.9 must be subscribed to event 'http://parallels.com/aps/events/pa/subscription/limits/changed'.
  • APSA-11857 Incorrect SPF record is generated for Exchange Online.
  • APSA-12647 Roll back changes of APSA-9852 (Create MX DNS records when domain gets verified).
  • APSA-11820 Changing user password in Customer Control Panel changes password in Microsoft Online Services Portal, but user is prompted to change password after login.
  • APSA-11821 Microsoft Office 365 application adds extra "." to end of SPF record target.
  • APSA-12406 Microsoft Office 365 (Cloud Solution Provider): 'Bill-to' information is not filled when customer is created in application.
  • APSA-12382 Upgrading license fails if target service plan contains more than one subscription period.
  • APSA-12664 Incorrect Romanian translations in Customer Control Panel.

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 6.2 Release Notes here: http://download.pa.parallels.com/poa/Office365_APS2/doc/83978.htm. Also, you can download the PDF version.

New Features and Changes

  • 'Can be assigned to users' Property is Added to License Types
  • Auto-Generating Names of Customer Default Subdomains is Supported
  • Transitions are Supported for Cloud Solution Provider Offers
  • Authorized Subscription Advisors are Supported
  • Windows Server 2012 R2 is Supported
  • Adjusting License Limits is Supported for Licenses Included into Composite Resources
  • Graph API is Used for Synchronizing Changes from Microsoft Online Services Portal to Service Automation
  • 'CSP over AET' Communication Means is no Longer Supported

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 6.2 Release Notes here: http://download.pa.parallels.com/poa/Office365_APS2/doc/83978.htm. Also, you can download the PDF version.

Obtaining

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

Installation

To install the Microsoft Office 365 Application, use the instructions provided in the Service 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 Microsoft Office 365 Application.
  6. Starting provisioning Office 365 services.
  7. Performing additional upgrade actions.

Important:

  • The upgrade procedure is not reversible.
  • Upgrade steps 1-7 are mandatory.
  • Make sure the current version of the Microsoft Office 365 Application is 6.1.x. Upgrading from versions that are lower than 6.1.x is not supported.
  • Make sure SQL Server logins of Office 365 Gateway Application Databases have the sysadmin server role. See Service 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 Microsoft 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 Microsoft 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 Operations 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 Operations Automation.
  4. Upgrade the Office 365 Application End-point:

    1. Upload the Microsoft 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 Microsoft Office 365 Application:

    1. Import the Microsoft Office 365 Application Package to Service Automation. See Operations Automation Provider's Guide >> Application Hosting > Managing Applications > Importing Application for details.
    2. Upgrade existing Microsoft Office 365 Application instances. See Operations Automation 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 Operations Automation.

  7. Perform the following additional upgrade actions:

    1. Perform the instruction of the https://kb.odin.com/en/126337 KB article.
    2. Update the configuration of the domain availability checker:

      1. In Provider Control Panel, go to Products > Online Store.
      2. Select the required Online Store for editing.
      3. Select the Layout Templates tab.
      4. In the list of Layout Templates, click on the provision Layout Template.
      5. Click Edit and update the Layout Template using the content provided in Service Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Configuring Office 365 Subdomain Form for Business Automation Online Store.
      6. Click Save.
      7. Go to Products > Online Store and click Synchronize Now.
      8. Make sure the domain availability checker works after updating.
    3. Reconfigure the Microsoft Office 365 Application to use Graph API for synchronizing changes from Microsoft Online Services Portal to Service Automation:

      1. Enable Graph API access and prepare necessary information (CLIENT ID/app key/your tenant identifier). Use the instruction provided in Service Automation Office 365 Integration Provider's Guide >> Syndication Partner Scenario > Deployment Architecture > Signing Syndication Agreement.
      2. In Operations Automation, set the following global settings of the required Office 365 Application Instance: Client ID (use the value of CLIENT ID), Client Secret Key (use the value of the app key), and Reseller tenant ID (use the tenant identifier of your syndication account).
    4. Update all existing Office 365 Service Templates:

      1. In Provider Control Panel, go to Products > Service Plans.
      2. Select the Service Templates tab.
      3. Click on the required Service Template.
      4. Click Edit.
      5. Set Destroy Service on Cancel to Yes (the checkbox is selected).
      6. Click Save.

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. Switching the Office 365 Application End-point from CSP over AET (the Selenium-based Advanced Emulation Technology is used to emulate CREST API methods) to CSP over CREST (CREST API methods are directly used by the application).
  4. Upgrading the Office 365 Application End-point.
  5. Upgrading the Microsoft Office 365 Application.
  6. Configuring offer transitions.
  7. Starting provisioning Office 365 services.
  8. Performing additional upgrade actions.

Important:

  • The upgrade procedure is not reversible.
  • Upgrade steps 1-8 are mandatory.
  • Make sure the current version of the Microsoft Office 365 Application is 6.1.x. Upgrading from versions that are lower than 6.1.x is not supported.
  • Make sure SQL Server logins of Office 365 Gateway Application Databases have the sysadmin server role. See Service 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 Microsoft 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 Microsoft 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 Operations 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 Operations Automation.
  3. Switch the Office 365 Application End-point from CSP over AET (the Selenium-based Advanced Emulation Technology is used to emulate CREST API methods) to CSP over CREST (CREST API methods are directly used by the application):

    1. In Partner Center, enable API access and write down the app registration information (App ID, Key, Account ID / Commerce ID). Use the instructions provided on the https://msdn.microsoft.com/en-us/library/partnercenter/mt267552.aspx page.

    2. On the Office 365 Application End-point Host, perform the following actions:

      1. Open Server Manager. Stop and disable the SeleniumServer service.
      2. Install Java SE Development Kit 8 (64-bit version) and WildFly 8.2.0.Final. See Service Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Deploying 'Microsoft Office 365' Application > Deploying Office 365 Application End-point > Preparing Office 365 Application End-point Host for details.
      3. Make sure the new value of the JAVA_HOME environment variable is set for Java SE Development Kit 8 (64-bit version).
      4. Install the latest version of the Office 365 CSP Component (csp-agent-war). See Service Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Deploying 'Microsoft Office 365' Application > Deploying Office 365 Application End-point > Installing Office 365 Application End-point for details.
      5. Open the Settings.config file of the required Office 365 Gateway Application and replace <add key="MOSI_FACTORY" value="AET" /> with <add key="MOSI_FACTORY" value="CSP" />. Save the changes.
      6. Open Internet Information Services (IIS) Manager. Restart the required Office 365 Gateway Site and the corresponding Application Pool.
    3. In Operations Automation, set the following global settings of the required Office 365 Application Instance:

      • Client ID - Use the value of App ID.
      • Client Secret Key - Use the value of Key.
      • Reseller tenant ID - Use the value of Account ID / Commerce ID.

    Notes:

    1. If CSP over CREST (CREST API methods are directly used by the application) is already enabled on the required Office 365 Gateway Site/Application, skip this step.
    2. If you have several Office 365 Gateway Sites/Applications on the Office 365 Application End-point Host, use the provided above procedure to switch each Office 365 Gateway Site/Application.
  4. Upgrade the Office 365 Application End-point:

    1. Upload the Microsoft 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.

  5. Upgrade the Microsoft Office 365 Application:

    1. Import the Microsoft Office 365 Application Package to Service Automation. See Operations Automation Provider's Guide >> Application Hosting > Managing Applications > Importing Application for details.
    2. Upgrade existing Microsoft Office 365 Application instances. See Operations Automation Provider's Guide >> Application Hosting > Bulk Application Upgrades for details.
  6. Configure offer transitions:

    1. Analyse your existing Office 365 Service Plans. Compare their names and their Resource Rates with the table provided in Service Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Useful Information > Examples of Office 365 Service Plans. Rename each existing Office 365 Service Plan in accordance with the table (if it is necessary).

      Examples:

      • You have the existing Office 365 Service Plan SharePoint Online (Plan 2) which includes the Resource Rates SharePoint Online (Plan 2) and Office 365 Extra File Storage. In this case you must rename the Office 365 Service Plan to SharePoint Online Plan 2 with Add-ons.
      • You have the existing Office 365 Service Plan Visio Pro for Office 365 which includes the Resource Rate Visio Pro for Office 365. In this case you must not rename the Office 365 Service Plan.
    2. Run the latest autoconf.py script. This script will create new Office 365 Service Plans. See Service Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Offers for details.
    3. Configure allowed upgrades for each Office 365 Service Plan using the table provided in Service Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Useful Information > Examples of Office 365 Service Plans.
    4. Configure the filtration of incompatible offers and reconfigure your firewall. See Service Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Filtration of Incompatible Offers and Service Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Firewall Requirements for details.
    5. Make sure all of your Office 365 Service Plans are configured in accordance with the table provided in Service Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Useful Information > Examples of Office 365 Service Plans.
  7. Start provisioning Office 365 services. For example, activate the Office 365 Service Template in Operations Automation.

  8. Perform the following additional upgrade actions:

    1. Perform the instruction of the https://kb.odin.com/en/126337 KB article.
    2. Update the configuration of the domain availability checker:

      1. In Provider Control Panel, go to Products > Online Store.
      2. Select the required Online Store for editing.
      3. Select the Layout Templates tab.
      4. In the list of Layout Templates, click on the provision Layout Template.
      5. Click Edit and update the Layout Template using the content provided in Service Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Office 365 Subdomain Form for Business Automation Online Store.
      6. Click Save.
      7. Go to Products > Online Store and click Synchronize Now.
      8. Log in to the Business Automation Application Server as root (for Linux) or Administrator (for Windows).
      9. Go to the /usr/local/bm/conf/html/o365 (for Linux) or C:\Program Files\Parallels\PBA\conf\html\o365 (for Windows) directory.
      10. Update the script.js file using the content provided in Service Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Office 365 Subdomain Form for Business Automation Control Panel.
      11. Make sure the domain availability checker works after updating.
    3. Perform the instructions of the https://kb.odin.com/en/126807 KB article.

    4. Update all existing Office 365 Service Templates:

      1. In Provider Control Panel, go to Products > Service Plans.
      2. Select the Service Templates tab.
      3. Click on the required Service Template.
      4. Click Edit.
      5. Set Destroy Service on Cancel to Yes (the checkbox is selected).
      6. Click Save.

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 Operations Automation

Search Words

new aps

update

"The identity of the calling application could not be establised"

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF