Search Engine: Elastic

Article ID: 133660, created on Jan 29, 2019, last review on Mar 7, 2019

  • Applies to:
  • Operations Automation 8.0
  • Operations Automation 7.4

Table of Contents

Release Notes

You can read the complete Office 365 19.1 Release Notes here. Also, you can download the PDF version.

Prerequisites

The Office 365 application package requires:

  • Odin Automation

    • 8.0.0 or a later 8.0.x version
    • 7.4.0 or a later 7.4.x version
    • 7.3.0 or a later 7.3.x version
    • 7.2.0 or a later 7.2.x version
  • UX1 Marketplace (optional)

    • 1.4

Note: For information about UX1 Marketplace, please refer to the guide at https://docs.cloudblue.com/oa/8.0/premium/content/UX1-Marketplace/Introduction.htm.

Fixed Issues

  • APSA-20942 A provisioning task failed with the error 'Value cannot be null.\r\nParameter name: stringToEscape'.
  • APSA-20830 autoconf.py set Max Amount to 100 for resources that are measured in GBs.
  • APSA-20905 A 'Provisioning "Migration"' task failed with the 'An item with the same key has already been added' error.
  • APSA-20902 It was not possible to activate a user in UX1 for Customers.
  • APSA-16048 Tax details were missing for resources.
  • APSA-20919 User synchronization failed with the 'Object reference not set to an instance of an object' error.
  • APSA-20884 Microsoft Cloud Agreement (MCA) information was not saved when a subscription was purchased.
  • APSA-20912 The cache of license objects was initialized incorrectly.
  • APSA-20887 Default admins were not created properly in the UX1 for Customers Marketplace.
  • APSA-20885 The "Test Connection" button verified only the Graph API's access token but not the Partner Center API's access token.
  • APSA-19820 In UX1 for Customers in the 'Change Password' dialog window, password complexity requirements were shown only if a weak password was entered.
  • APSA-20731 An 'Initiating operation' task failed with the "'No result detected' while 'accessing result set field by name'" error.
  • APSA-20972 Reconciliation report generation ended with the 'Object reference not set to an instance of an object' error.

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 19.1 Release Notes here. Also, you can download the PDF version.

New Features and Changes

Customer Acceptance of the Microsoft Cloud Agreement is Now Mandatory

As of this version of the application, customers must accept the Microsoft Cloud Agreement (MCA) and provide acceptance information when they purchase Office 365 services. To view details on the MCA, refer to the article at https://docs.microsoft.com/en-us/partner-center/confirm-consent-faq.

Support for the UX1 for Resellers Marketplace

The application now supports the UX1 for Resellers Marketplace, which enables resellers to sell Office 365 services to their customers through UX1 for Resellers. To learn more about UX1 for Resellers, please refer to the related documentation at https://docs.cloudblue.com/oa/8.0/premium/content/home.htm.

Office 365 Activation has been Improved for UX1 for Customers

In UX1 for Customers, the procedure of Office 365 activation is now improved. During Office 365 activation, a customer can now not only create a new Microsoft account but also use an existing Microsoft account.

Known Issues and Limitations

  • Office 365 and Azure CSP resources cannot be sold in the same service template and service plan. You must use separate service templates and service plans for selling Office 365 and Azure CSP resources.
  • Upgrading trial Office 365 subscriptions from trial service plans to paid service plans does not work in CCP v1. To work around this issue, you can switch customers with trial Office 365 subscriptions from CCP v1 to UX1 for Customers.
  • In UX1 for Customers of Odin Automation 7.2, adding trial Office 365 services to users does not work on the Users screen. To work around this issue, customers can use the Office 365 screen.

Obtaining the 'Office 365' Package

Contact your Ingram Micro Support account manager to obtain the new version of the Office 365 application package.

Installation Procedure

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

Upgrade Procedure

The upgrade procedure consists of the following steps:

  1. Prepare the necessary information for upgrading the Office 365 application endpoint (collect Office 365 gateway site parameters).
  2. Stop provisioning Office 365 services.
  3. Upgrade the Office 365 application endpoint.
  4. Upgrade the Office 365 application.
  5. Update the OA Billing control panel and online store customizations.
  6. Perform post-upgrade validation.
  7. Start provisioning Office 365 services.

Important:

  • The upgrade procedure is not reversible.
  • Upgrade steps 1-7 are mandatory.
  • Make sure the current version of the Office 365 application is 18.4.1. Upgrading from other versions is not supported.
  • Before upgrading the Office 365 application from one version to another, make sure that you are going to follow the allowed upgrade paths. See KB article #130752 for details.
  • If a non-LocalDB edition of SQL Server is used by your Office 365 application endpoint, make sure all 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.
  • The names of the Office 365 gateway sites must not be changed after the installation of the Office 365 application endpoint. If you have changed them, reinstate the original names before upgrading the Office 365 application endpoint.

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

  1. Prepare the necessary information for upgrading the Office 365 application endpoint. 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 the 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 and write down the hostname from the URL into the IP address. This is the IP address of the Office 365 gateway site.
    9. Log on to the Office 365 Application Endpoint 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. Stop provisioning Office 365 services. For example, deactivate the Office 365 service template in OA Operations.
    2. In OA Operations, go to Operations > Tasks and make sure all Office 365 tasks are processed.
  3. Upgrade the Office 365 application endpoint:

    1. Upload the Office 365 application package to the Office 365 Application Endpoint Host.
    2. Unpack the application package.
    3. Unblock the contents of the O365-Web.zip file. To do this, right-click the file in Windows Explorer, click Properties, click Unblock, and click OK.
    4. Unpack the O365-Web.zip file.
    5. Start Windows PowerShell Console and go to the directory where the contents of the O365-Web.zip file are located.
    6. Run the following command:

      .\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
      
    7. Run the iisreset command.

    Note: If you have several Office 365 gateway sites on the Office 365 Application Endpoint Host, use the procedure provided above to upgrade each Office 365 gateway site.

  4. Upgrade the Office 365 application:

    1. Import the Office 365 application package to Odin Automation. See APS Application Hosting Guide >> Application Hosting Configuration > Managing Applications > Importing Application for details.
    2. Upgrade existing Office 365 application instances. See APS Application Hosting Guide >> Application Hosting Configuration > Bulk Application Upgrades for details.
  5. Update the installed OA Billing control panel and online store customizations. Use KB article #130232 to find the necessary customizations and update instructions.

    Important: After upgrading Odin Automation, make sure the installed OA Billing control panel and online store customizations belong to the current version of Odin Automation. If necessary, update them. Use KB article #130232 to the find necessary customizations and update instructions.

  6. Perform the following post-upgrade validation steps:

    1. In Task Manager, make sure that there are no unprocessed Office 365 tasks scheduled during the upgrade.
    2. For each Office 365 application instance, make sure that all settings are correctly specified and all necessary Microsoft APIs are accessible. To do this, select the application instance you need to check and click Test Connection.
  7. Start provisioning Office 365 services. For example, activate the Office 365 service template in OA Operations.

Helpful Resources

5356b422f65bdad1c3e9edca5d74a1ae 8fc71f07abe5b233fea1ae0377cd5e3d 55fe109b4b4fe3fbb893f22dbb85a41a 1941880841f714e458ae4dc3d9f3062d adc6deaa66054d8a194d131ba07f2785 aab95f5cf9bcfa920cc1dda8487f084a

Email subscription for changes to this article
Save as PDF