Table of Contents
- Release Notes
- Dependencies and Pre-Requisites
- Fixed Issues
- Known Issues and Limitations
- Upgrade Procedure (Cloud Solution Provider Scenario)
- Help Resources
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.
- APSA-19485 Phone numbers in customer billing profiles must be formatted according to new Microsoft rules.
- APSA-19481 Support of private billing API method CustomerClassGet must be extended.
- APSA-19482 Switching Office 365 subscriptions does not work if 'Inc. Amount' is '0' in license resource rate of target service plans.
- APSA-19496 Office 365 synchronization fails with error "LinqToDB.Linq.LinqException: '_.Name.ToLowerInvariant()' cannot be converted to SQL".
- APSA-19502 If synchronization is started immediately after creation of user with Office 365 service, 'Office 365 User' APS resource of user is removed.
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.
- 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.
Contact your Odin Support account manager to obtain the new version of the Office 365 application package.
To install the Office 365 application, use the instructions provided in the Odin Automation Premium Office 365 Integration Provider's Guide.
The upgrade procedure consists of the following steps:
- Preparing necessary information for upgrading the Office 365 application endpoint (collecting Office 365 gateway site parameters).
- Stopping provisioning Office 365 services.
- Upgrading the Office 365 application endpoint.
- Upgrading the Office 365 application.
- Updating the OA Billing control panel and online store customizations.
- Performing post-upgrade validation.
- Starting provisioning Office 365 services.
- The upgrade procedure is not reversible.
- Upgrade steps 1-7 are mandatory.
- Make sure the current version of the Office 365 application is 17.3. 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:
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:
- Log in to Provider Control Panel.
- Go to Service > Applications and click the Office 365 application.
- Select the Instances tab and click the target application instance.
- Select the General tab.
- 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/.
- Write down the name of the directory from the URL. This is the name of the Office 365 gateway application.
- Write down the hostname from the URL. This is the hostname of the Office 365 gateway site.
- 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.
- Log on to the Office 365 Application Endpoint Host as Administrator via RDP.
- Open Internet Information Services (IIS) Manager.
- Go to the list of sites.
- From the list, select the site with the IP address obtained above.
- Write down the name of the site. This is the name of the Office 365 gateway site.
Stop provisioning Office 365 services:
- In OA Operations, go to Operations > Tasks and make sure all Office 365 tasks are processed.
- Stop provisioning Office 365 services. For example, deactivate the Office 365 service template in OA Operations.
Upgrade the Office 365 application endpoint:
- Upload the Office 365 application package to the Office 365 Application Endpoint Host.
- Unpack the application package.
- 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.
- Unpack the O365-Web.zip file.
- Start Windows PowerShell Console and go to the directory where the content of the O365-Web.zip file is placed.
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
- Run the
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.
Upgrade the Office 365 application:
- Import the Office 365 application package to Odin Automation. See Odin Automation Application Hosting Guide >> Application Hosting Configuration > Managing Applications > Importing Application for details.
- Upgrade existing Office 365 application instances. See Odin Automation Application Hosting Guide >> Application Hosting Configuration > Bulk Application Upgrades for details.
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.
Perform the following post-upgrade validation steps:
- In Task Manager, make sure that there are no unprocessed Office 365 tasks scheduled during the upgrade.
- 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.
- Start provisioning Office 365 services. For example, activate the Office 365 service template in OA Operations.