Article ID: 127478, created on Nov 19, 2015, last review on Jan 18, 2016

  • Applies to:
  • Operations Automation

Table of Contents

Release Notes

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

Dependencies and Pre-Requisites

The Office 365 Application Package requires:

  • Operations Automation 6.0.6 or later
  • Business Automation 6.0.6 or later

Important: 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.

Fixed Issues

  • APSA-13484 Licenses get stuck in status "In provisioning" due to leftover event in WaitSubscription table.
  • APSA-13464 Task 'Unprovisioning "Tenant" for APS application Microsoft Office 365' fails with error 'You cannot remove the initial domain created for you in Office 365'.
  • APSA-13419 Office 365 4.17 is now requred for upgrading subscriptions from APS 1.2 to APS 2.
  • APSA-13400 Attempt to reset Microsoft Online Services Portal admin password is perfromed when tenant is not ready.
  • APSA-13331 Setting 'Show In Store' of Office 365 resource rates must be set to 'Yes'.
  • APSA-13321 Mass SKU switch UI does not work for large amount of subscriptions.
  • APSA-13172 Non-zero charges are applied to customers when their Office 365 subscriptions are upgraded from APS 1.2 to APS 2.
  • APSA-13143 [Upgrading Office 365 subscriptions from APS 1.2 to APS 2] Setting 'After Refund Period' must be set to 'Refund Prorated Recurring Fee' in subscription period of source service plan.
  • APSA-13132 Script upgradeAPS1ToAPS2.py skips Resource Types configured for 'Partner Access' add-on offers.
  • APSA-13421 Office 365 6.3 shows "Seats" instead of "GB" on "Adjust License Limit" screen in Customer Control Panel.
  • APSA-13417 Office 365 application package does not contain CSP Deployment Assistant tool.
  • APSA-13402 Lost French tooltip localization.
  • APSA-13344 Synchronization error: "Error: Value cannot be null. Parameter name: key".
  • APSA-13266 Task "Provisioning resource GUID of type 'migrations'" fails if length of string for property 'synchronization_results' is more than 4k symbols.
  • APSA-13204 There is no way to modify Office 365 add-on type parameters.
  • APSA-13407 Allow license assignment UI to use any of compatible parent licenses for add-on license.
  • APSA-13388 Synchronization of license assignments fails when multiple parent licenses of add-on license are present in one subscription.
  • APSA-13356 "Adjust License" window allows purchasing licenses of hidden resources.
  • APSA-12889 Office 365 tenant deletion must not fail if 'CSP customer Id' property is not specified.
  • APSA-12407 Office 365 subscriptions cannot be disabled due to missing '' section in callback requests.
  • APSA-9286 Account creation in Office 365 Gateway database should be performed in the same way as subscription creation.
  • APSA-13487 Provisioning "Migration" resource fails when subscriptions are imported from Microsoft cloud. 'The context is already tracking a different entity with the same resource Uri.' error appears.
  • APSA-13139 [Upgrading Office 365 subscriptions from APS 1.2 to APS 2] 'Billing Terms' settings must be identical in source and target service plans.
  • APSA-13556 Extra storage parameters of globals settings of application resource cannot be saved.

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

New Features and Changes

  • New and Discontinued Offers (Syndication Partner Scenario)
  • New Offers (Cloud Solution Partner Scenario)
  • Importing Tenant Subscriptions from Microsoft Cloud into Service Automation is Supported (Cloud Solution Provider Scenario)
  • Re-tested Synchronization Script from KB #122526

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.4 Release Notes here: http://download.pa.parallels.com/poa/Office365_APS2/doc/84699.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.

Installation

To install the 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 Office 365 Application.
  6. Starting provisioning Office 365 services.
  7. Configuring new offers.
  8. Processing discontinued offers.

Important:

  • The upgrade procedure is not reversible.
  • Upgrade steps 1-6 are mandatory. Upgrade steps 7-8 are optional but recommended.
  • Make sure the current version of the Office 365 Application is 6.3.x. Upgrading from versions that are lower than 6.3.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 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 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 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. Read the KB article https://kb.odin.com/en/127961 and apply the KB article on your Service Automation installation if necessary.
    2. Import the Office 365 Application Package to Service Automation. See Operations Automation Provider's Guide >> Application Hosting > Managing Applications > Importing Application for details.
    3. Upgrade existing 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. Configure the following new offers (optional but recommended):

    • Office 365 Enterprise E5 without PSTN Conferencing
    • Power BI Pro
    • Power BI Pro Trial
    • Skype for Business Cloud PBX
    • Skype for Business Plus CAL
    • Power BI Pro (Government Pricing) Trial

    Use the instructions of the https://kb.odin.com/en/127759 KB article.

  8. Stop selling the following discontinued offers (optional but recommended):

    • Office 365 Small Business
    • Office 365 Small Business Trial
    • Office 365 Small Business Premium
    • Office 365 Small Business Premium Trial
    • Skype for Business Online Phone Add-On
    • Office 365 Extra File Storage for Small Business
    • Office 365 Midsize Business
    • Office 365 Midsize Business Trial
    • Office 365 Enterprise E2
    • Office 365 Enterprise E4
    • Office 365 Enterprise E4 Trial
    • Office 365 Enterprise K2
    • Office Online with SharePoint Online (Plan 1)
    • Office Online with SharePoint Online (Plan 2)
    • SharePoint Online (Plan 1) with Yammer
    • SharePoint Online (Plan 2) with Yammer
    • Power BI for Office 365 with SharePoint Online (Plan 2) with Yammer
    • Power BI for Office 365 with SharePoint Online (Plan 2) with Yammer Trial
    • Power BI for Office 365 Add-On for SharePoint (Plan 2)
    • Power BI for Office 365 Add-On for E3/E4
    • SharePoint Online (Plan 2) with Yammer for Government
    • Power BI for Office 365 with SharePoint Online (Plan 2) with Yammer (Government Pricing)
    • Power BI for Office 365 with SharePoint Online (Plan 2) with Yammer (Government Pricing) Trial
    • Power BI for Office 365 Add-On for SharePoint (Plan 2) (Government Pricing)
    • Power BI for Office 365 Add-On for E3/E4 (Government Pricing)

    Use the instructions of the https://kb.odin.com/en/127761 KB article.

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.
  6. Validating the configuration of the Office 365 Application End-point.
  7. Configuring new offers.

Important:

  • The upgrade procedure is not reversible.
  • Upgrade steps 1-6 are mandatory. Upgrade step 7 is optional but recommended.
  • Make sure the current version of the Office 365 Application is 6.3.x. Upgrading from versions that are lower than 6.3.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 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 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. 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. Read the KB article https://kb.odin.com/en/127961 and apply the KB article on your Service Automation installation if necessary.
    2. Import the Office 365 Application Package to Service Automation. See Operations Automation Provider's Guide >> Application Hosting > Managing Applications > Importing Application for details.
    3. Upgrade existing Office 365 Application instances. See Operations Automation 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 Operations Automation.

  6. Validate the configuration of the Office 365 Application End-point. Make sure it belongs to the configuration described in the https://kb.odin.com/en/126224 KB article: the SeleniumServer service is stopped and disabled, Java SE Development Kit is installed, WildFly is installed, JAVA_HOME is set, the Office 365 CSP Component (csp-agent-war) is installed, the MOSI_FACTORY and SERVICE_PROVIDER_TYPE keys are updated in the Settings.config file, the global settings are updated.

  7. Configure the following new offers (optional but recommended):

    • Office 365 Enterprise E5 without PSTN Conferencing
    • OneDrive for Business (Plan 2)
    • Power BI Pro
    • Customer Lockbox
    • Delve Analytics
    • Office 365 Equivio Analytics for eDiscovery
    • Skype for Business Cloud PBX
    • Skype for Business Plus CAL
    • Microsoft Dynamics CRM Online Basic (Government Pricing)
    • Microsoft Dynamics CRM Online Essential (Government Pricing)
    • Microsoft Dynamics CRM Online Professional (Government Pricing)
    • Microsoft Dynamics CRM Online Professional Add-On to Office 365
    • Microsoft Dynamics CRM Online Professional Add-On to Office 365 (Government Pricing)
    • Microsoft Dynamics CRM Online Additional Non-Production Instance (Government Pricing)
    • Microsoft Dynamics CRM Online Additional Production Instance (Government Pricing)
    • Microsoft Dynamics CRM Online Additional Storage (Government Pricing)
    • Microsoft Social Engagement Additional 10K Posts (Government Pricing)
    • Office 365 Enterprise E5 without PSTN Conferencing (Government Pricing)
    • OneDrive for Business (Plan 2) (Government Pricing)
    • Power BI Pro (Government Pricing)
    • Customer Lockbox (Government Pricing)
    • Delve Analytics (Government Pricing)
    • Office 365 Equivio Analytics for eDiscovery (Government Pricing)
    • Skype for Business Cloud PBX (Government Pricing)
    • Skype for Business Plus CAL (Government Pricing)
    • Microsoft Dynamics CRM Online Professional
    • Microsoft Dynamics CRM Online Basic
    • Microsoft Dynamics CRM Online Essential
    • Microsoft Dynamics CRM Online Additional Storage
    • Microsoft Dynamics CRM Online Additional Production Instance
    • Microsoft Dynamics CRM Online Additional Non-Production Instance
    • Microsoft Social Engagement Additional 10K Posts

    Use the instructions of the https://kb.odin.com/en/126207 KB article.

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

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF