Article ID: 128109, created on Jan 19, 2016, last review on Apr 25, 2016

  • Applies to:
  • Operations Automation

Table of Contents

Release Notes

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

Dependencies and Pre-Requisites

The Office 365 Application Package requires:

  • Odin Automation 6.0.7 or later
  • Odin Automation billing 6.0.7 or later

Important: Make sure that the instruction of the https://kb.odin.com/en/128704 KB article is performed on your installation.

Fixed Issues

  • APSA-15205 Office 365 subscription upgrade must be reenterable in respect of PlaceOrder failure.
  • APSA-15094 Office 365 provisioning task fails with 'Unexpected character encountered while parsing value: c. Path '', line 0, position 0.' error.
  • APSA-15022 GetMsSubscription should not set status of failed subscriptions in Office 365 application end-point database.
  • APSA-14823 Office 365 application instance with 90k subscriptions cannot be upgraded.
  • APSA-14816 APS 1.2 to APS 2 upgrade: new MX records are added to customer domains breaking existing mail flow.
  • APSA-14747 Task 'Provisioning "Tenant" for APS application Office 365' fails with error 'The INSERT statement conflicted with the FOREIGN KEY SAME TABLE'.
  • APSA-14686 readCSPAccounts.py fails if there are umlauts in customer information in the Microsoft cloud.
  • APSA-14507 Office 365 cannot be provided to customers from El Salvador.
  • APSA-15001 Upgrade from APS 1.2 to APS 2: list of post-upgrade activities is wrong.
  • APSA-14363 Add mention of "Allowed Networks" to requirements.
  • APSA-14042 Upgrade from APS 1.2 to APS 2: upgrade scripts do not handle situation when unit of measure of storage resource in Odin Automation billing is not KB.
  • APSA-13751 Incorrect Office 365 add-on property is specified in documentation.
  • APSA-15317 Upgrade from APS 1.2 to APS 2 (Office 365 6.4.1): prepareUpgradeAPS1ToAPS2.py fails.
  • APSA-14866 Task 'Provisioning "AsyncOperation" for APS application Office 365' fails with error 'InvalidOfferIdFault'.
  • APSA-14754 ReadCSPAccounts.py fails with error "A duplicated entry is found for the SA Customer".
  • APSA-14689 Import of existing customers fails to see service plans with unlimited resources.
  • APSA-14598 [Office 365 6.4] Importing CSP accounts does not work if service plan has more than one subscription period.
  • APSA-14590 Assigning licenses during synchronization must work in another way.
  • APSA-14552 [Office 365 6.4 (Syndication Partner Scenario)] Task "Unprovisioning Tenant" fails with error "The value in the parameter tenantId is null or empty".
  • APSA-14410 Wizard "Adjust Limits" sets new limit using information from Odin Automation instead of using information from Odin Automation billing.
  • APSA-14299 Value of property 'subdomain' does not match regular expression.
  • APSA-14110 Office 365 task fails with error "An item with the same key has already been added".
  • APSA-14006 Synchronization fails if user specifies country that is not in hard-coded list of countries in Utils.cs.
  • APSA-13990 upgradeAPS1ToAPS2.py fails with error "Subscription #50053800 is skipped because of error: 'NoneType' object has no attribute 'lower'".
  • APSA-13961 prepareUpgradeAPS1ToAPS2.py script does not work correctly if multiple source resource rates are specified.
  • APSA-13907 'Provisioning "AsyncOperation"' tasks cannot be completed. 'The transition is in progress: One or more errors occurred.' message is shown in task logs.
  • APSA-13893 Task 'Provisioning "Subscription" for APS application Office 365' fails with error 'Value cannot be null. Parameter name: masterTenant.Subdomain'.
  • APSA-13880 'INTUNE_A' has "isUserSpecific" set to 'false' in 'licensetypes.json', but this license can be assigned to user in Microfost Office 365 Portal.
  • APSA-13577 APS package "Office 365". Bunch of changes in German locale.
  • APSA-13570 Task 'Provisioning "Tenant" for APS application Microsoft Office 365' fails with error 'Culture de-DE is not supported in country BE'.
  • APSA-13564 Accounts cannot be created for customers from Serbia because error "Language sr is not supported in country RS" appears.
  • APSA-13387 Application endpoint must be protected from outdated PUT requests.
  • APSA-13179 Upgrade from APS 1.2 to APS 2: upgrade fails if APS 1.2 subscription was previously moved between accounts.
  • APSA-8562 Customers purchasing Office 365 subscriptions are asked to specify initial subdomains even if they do already have active Office 365 subscriptions.
  • APSA-15325 Workaround for resellers using delegated service plans must be removed from documentation.

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

New Features and Changes

  • Upgrading 'P1 + P2' Subscriptions (Syndication Partner Scenario)
  • Reconciliation Reports are Supported
  • New Offers (Cloud Solution Partner Scenario)
  • Support of MPN_ID Attribute for Customer Accounts (Cloud Solution Partner Scenario)
  • Registering New Customers with Existing Microsoft Accounts (Cloud Solution Partner Scenario)

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.5 Release Notes here: http://download.pa.parallels.com/poa/Office365_APS2/doc/85277.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 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 6.4.x. Upgrading from versions that are lower than 6.4.x is not supported.
  • 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 Odin Automation Provider's Guide >> Application Hosting > Managing Applications > Importing Application for details.
    2. Upgrade existing Office 365 Application instances. See Odin 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 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. Updating the Odin Automation billing online store and control panel customizations.
  6. Starting provisioning Office 365 services.
  7. Validating license and add-on types.
  8. Configuring new offers.

Important:

  • The upgrade procedure is not reversible.
  • Upgrade steps 1-7 are mandatory. Upgrade step 8 is optional but recommended.
  • Make sure the current version of the Office 365 Application is 6.4.x. Upgrading from versions that are lower than 6.4.x is not supported.
  • 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 Odin Automation Provider's Guide >> Application Hosting > Managing Applications > Importing Application for details.
    2. Upgrade existing Office 365 Application instances. See Odin Automation Provider's Guide >> Application Hosting > Bulk Application Upgrades for details.
  5. Update the Odin Automation billing online store and control panel customizations on your installation. See Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Office 365 Subdomain Form for Odin Automation billing Online Store and Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Office 365 Subdomain Form for Odin Automation billing Control Panel for details.

    Important: Make sure that the instruction of the https://kb.odin.com/en/128704 KB article is performed on your installation.

  6. Start provisioning Office 365 services. For example, activate the Office 365 Service Template in Odin Automation.

  7. In Odin Automation, validate the license and add-on types listed below. Make sure the Can be assigned to users property is set in accordance with the list:

    • Office 365 Exchange Online ProtectionNo
    • OneDrive for Business (Plan 1)Yes
    • OneDrive for Business (Plan 2)Yes
    • Power BI ProYes
    • Exchange Online Archiving for Exchange OnlineYes
    • Exchange Online Advanced Threat ProtectionYes
    • Customer LockboxYes
    • Delve AnalyticsYes
    • Office 365 Equivio Analytics for eDiscoveryYes
    • Azure Active Directory BasicYes
    • Azure Active Directory PremiumYes
    • Azure Rights ManagementYes
    • OneDrive for Business (Plan 1) (Government Pricing)Yes
    • Power BI Pro (Government Pricing)Yes
    • Exchange Online Archiving for Exchange Online (Government Pricing)Yes
    • Exchange Online Advanced Threat Protection (Government Pricing)Yes
    • Customer Lockbox (Government Pricing)Yes
    • Delve Analytics (Government Pricing)Yes
    • Office 365 Equivio Analytics for eDiscovery (Government Pricing)Yes
    • Azure Active Directory Basic (Government Pricing)Yes
    • Azure Active Directory Premium (Government Pricing)Yes
    • Azure Rights Management (Government Pricing)Yes
  8. Configure the following new offers (optional but recommended):

    • Dynamics AX Additional Storage
    • Dynamics AX Device
    • Dynamics AX Enterprise
    • Dynamics AX Sandbox Tier 1: Developer & Test Instance
    • Dynamics AX Sandbox Tier 2: Standard Acceptance testing
    • Dynamics AX Sandbox Tier 3: Premier Acceptance testing
    • Dynamics AX Sandbox Tier 4: Standard Performance testing
    • Dynamics AX Sandbox Tier 5: Premier Performance testing
    • Dynamics AX Self Serve
    • Dynamics AX Task
    • Office 365 Education for faculty
    • Office 365 Education for students
    • Office 365 ProPlus for faculty
    • Office 365 ProPlus for students
    • Microsoft Azure Multi-Factor Authentication

    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 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)

Search Words

Pleasae upgrade CSP APS on Staging platform.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF