Search Engine: Elastic

Article ID: 131851, created on Dec 4, 2017, last review on Dec 22, 2017

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1
  • Operations Automation 7.2
  • Business Automation 7.0
  • Business Automation 7.1
  • Business Automation 7.2

Table of Contents

Release Notes

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

Dependencies and Pre-Requisites

The Office 365 application package requires:

  • Odin Automation 7.3.0 or a later 7.3.x version
  • Odin Automation 7.2.0 or a later 7.2.x version
  • Odin Automation 7.1.0 or a later 7.1.x version
  • Odin Automation 7.0.1_hf130748 or a later 7.0.x version

Important: Starting with Odin Automation 7.0.0, the new branding implementation is used (see Odin Automation Premium 7.0 Release Notes >> Changes > Core > New Branding Implementation for details). This change affects the Office 365 application (see Odin Automation Premium 7.0 Upgrade Workflow Guide >> Pre-Upgrade Actions > Branding Configuration Restrictions > Back Up Branding Customizations and Odin Automation Premium 7.0 Upgrade Workflow Guide >> Post-Upgrade Actions > Configuring Branding for details). You must back up and restore the respective Office 365 data when migrating brands.

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

Support of Trial Offers (Cloud Solution Provider Scenario)

Now, the Office 365 application supports trial offers. Odin Automation service providers using the application on their installations can now provide their customers with the ability to evaluate Office 365 services for free before buying them.

The following offers can be provided as trial offers:

  • Office 365 Business Premium
  • Office 365 Enterprise E3
  • Office 365 Enterprise E5
  • Office 365 Enterprise E5 without Audio Conferencing
  • Microsoft 365 Business
  • Enterprise Mobility + Security E5
  • Dynamics 365 for Finance and Operations Business Edition
  • Dynamics 365 Customer Engagement Plan Enterprise Edition

For new installations of the application, trial offers are configured by default during the deployment of the application. For existing installations of the application, trial offers are configured during the upgrade of the application to version 17.3 (see Upgrade Procedure (Cloud Solution Provider Scenario) for details).

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

Support of Localization Add-ons

Now, localization add-ons can be used for the localization of the Office 365 application. This allows Odin Automation service providers using the application on their installations to add languages that are not supported by default. To learn more about localization add-ons, refer to https://doc.apsstandard.org/7.2/concepts/i18n/add-on/#.

Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Useful Information > Adding New Language

Fixed Issues

  • APSA-16504 Offer configuration script autoconf.py does not copy some necessary properties from template service plan to new service plans.
  • APSA-19287 OA Billing customizations of Office 365: BM_ProvisioningParams.xml can contain customizations of other apps.
  • APSA-19294 Office 365 upgrade procedure: issue about permissions of partner tenant user necessary for upgrade.
  • APSA-18305 Creation of reconciliation report fails with error "ID cannot be empty".
  • APSA-19340 Password of partner tenant's admin user must not be shown in PCP.
  • APSA-19333 Synchronization must skip cloud users with the following properties: (1) usageLocation is empty and provisioningErrors is not empty; (2) usageLocation and assignedLicenses are empty.
  • APSA-19329 Implement workaround for APS-43697.
  • APSA-19319 Reconciliation report cannot be generated when order detail does not have Unit Price (Unit Price = NULL).
  • APSA-19292 "Activate Office 365" pop-up behavior: focus of input fields is changed while password is entered.
  • APSA-19219 Synchronization starts failing after upgrading to Office 365 17.2.
  • APSA-19021 Only one copy of "Office 365 License" resource type should exist in Office 365 service template.
  • APSA-18407 "Synchronize now" functionality does not work if HTTP authentication is enabled for OA Operations XMLRPC API.

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

Known Issues and Limitations

  • Office 365 and Azure CSP resources cannot be sold in the same service template/service plan. You must use separate service templates/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 CCP v2.
  • In CCP v2 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

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

Installation

To install the Office 365 application, use the instructions provided in the Odin Automation Premium 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 endpoint (collecting Office 365 gateway site parameters).
  2. Stopping provisioning Office 365 services.
  3. Upgrading the Office 365 application endpoint.
  4. Upgrading the Office 365 application.
  5. Updating the OA Billing control panel and online store customizations.
  6. Performing post-upgrade validation.
  7. Starting 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 17.2/17.2.1. Upgrading from other versions 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 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 Premium Office 365 Integration Provider's Guide >> Syndication Partner 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, return 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 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 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 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. In OA Operations, 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 OA Operations.
  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 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 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.

    Notes:

    • 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.
    • 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 Endpoint Host; add -MSCertPath <path to certificate> to the command provided above; run the command.
  4. Upgrade the Office 365 application:

    1. Import the Office 365 application package to Odin Automation. See Odin Automation Application Hosting Guide >> Application Hosting Configuration > Managing Applications > Importing Application for details.
    2. Upgrade existing Office 365 application instances. See Odin Automation 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 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 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.

Upgrade Procedure (Cloud Solution Provider Scenario)

The upgrade procedure consists of the following steps:

  1. Preparing necessary information for upgrading the Office 365 application endpoint (collecting Office 365 gateway site parameters).
  2. Stopping provisioning Office 365 services.
  3. Upgrading the Office 365 application endpoint.
  4. Upgrading the Office 365 application.
  5. Updating the OA Billing control panel and online store customizations.
  6. Configuring trial offers.
  7. Performing post-upgrade validation.
  8. Starting provisioning Office 365 services.

Important:

  • The upgrade procedure is not reversible.
  • Upgrade steps 1-8 are mandatory.
  • Make sure the current version of the Office 365 application is 17.2/17.2.1. Upgrading from other versions 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 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 Premium 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, return 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 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 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 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. In OA Operations, 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 OA Operations.
  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 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 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 Odin Automation Application Hosting Guide >> Application Hosting Configuration > Managing Applications > Importing Application for details.
    2. Upgrade existing Office 365 application instances. See Odin Automation 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 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 find necessary customizations and update instructions.

  6. Configure the following trial offers:

    • Office 365 Business Premium
    • Office 365 Enterprise E3
    • Office 365 Enterprise E5
    • Office 365 Enterprise E5 without Audio Conferencing
    • Microsoft 365 Business
    • Enterprise Mobility + Security E5
    • Dynamics 365 for Finance and Operations Business Edition
    • Dynamics 365 Customer Engagement Plan Enterprise Edition

    To configure the offers, you can use the instructions provided at https://kb.odin.com/en/126207.

  7. 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.
  8. Start provisioning Office 365 services. For example, activate the Office 365 service template in OA Operations.

Help Resources

c0f836394088a28cc30dd0e5fe8b600e caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 198398b282069eaf2d94a6af87dcb3ff b2c3b33425dfc50c7d41a2efaa7f84f3 ef171e3fccb12bd8e09076a7b49212c0 7c0b495571a6c1bec50e4f324a20ec14 0871c0b47b3b86ae3b1af4c2942cd0ce 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 31987597efff5a3a9ce779cc203bbe5e 8c199f0ee4305da1a577740620df4a51

Email subscription for changes to this article
Save as PDF