Search Engine: Elastic

Article ID: 131083, created on Jun 29, 2017, last review on Nov 21, 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.2 Release Notes here. Also, you can download the PDF version.

Dependencies and Pre-Requisites

The Office 365 application package requires:

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

Microsoft Cloud Germany is Supported

Now, Odin Automation service providers using the Office 365 app can sell Office 365 services of the national cloud Microsoft Cloud Germany (https://www.microsoft.com/en-us/trustcenter/cloudservices/nationalcloud).

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

Office 365 Operated by 21Vianet in China is Supported

Now, Odin Automation service providers using the Office 365 app can sell Office 365 services of the national cloud Office 365 operated by 21Vianet in China (https://www.microsoft.com/en-us/trustcenter/cloudservices/nationalcloud).

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

Fixed Issues

  • APSA-19112 Task 'Provisioning "subscription"' fails with "GRAPH API Error: One or more properties contains invalid values".
  • APSA-19075 Periodic task "Synchronize resource usage for APS application instance" fails with "Unrecognized Guid format".
  • APSA-18988 Synchronization of user: "String or binary data would be truncated" error appears if length of field "Job title" is more than 64 symbols.
  • APSA-18924 Application package Office 365 must not depend on platform library poaupdater.
  • APSA-18907 Country Jersey is not supported.
  • APSA-18902 Further provisioning actions are blocked after first unsuccessful provisioning action.
  • APSA-18729 Unclear error message is shown when subscription provisioning fails for reseller with wrong MPN ID.
  • APSA-18387 CSP migration task fails with error "An item with the same key has already been added".
  • APSA-18360 Unprovisioning task fails with error "Unable to deactivate Cloud subscription".
  • APSA-18214 During conversion from Syndication Partner Program to CSP Partner Program, promotions applied to syndication subscriptions are lost.
  • APSA-16155 Extra validation must be added for import scripts.
  • APSA-19091 Lower-case letters must be allowed in Provisioning ID.
  • APSA-19078 CCPv2: "Buy New License" button is still visible despite disabled option "Visibility of Billing Screens in CCP v2".
  • APSA-19073 Application endpoint does not update subscription limit in its database during reactivation if subscription is active in Microsoft cloud.
  • APSA-19039 Error "User duplicated in DB" appears during synchronization.
  • APSA-19003 Application endpoint error related to option 'Use an existing Microsoft account' is not handled in online store customization scripts.
  • APSA-18987 Error "JSON integer 2306867200 is too large or small for an Int32" appears when customer buys resource "Extra File Storage".
  • APSA-18923 Entry from ApsId2Id is not deleted when the last Office 365 subscription is removed from customer account.
  • APSA-18397 Unknown error appears on Office 365 screen when domain is activated.
  • APSA-17111 Office 365 subdomain form customization: "Add New Plan" wizard hangs when customer tries to add Office 365 service plan to existing sales order.
  • APSA-16631 Wizard "Buy More Licenses" displays HTML tags specified in descriptions of resource rates as plain text.
  • APSA-19081 completeMOSI2CSP.py: Unexpected error: Order instance has no attribute '__getitem__'.
  • APSA-19066 Unexpected error appears in Office 365 UI when license without target upgrade service plans is upgraded.
  • APSA-18891 Sales order fails if customer address is invalid.
  • APSA-18870 Incorrect password validation in Odin Automation affects Office 365 provisioning.
  • APSA-18599 Domains must not be removed from Microsoft cloud when subscriptions are removed.
  • APSA-18354 User language preferences are not propagated from Odin Automation to the Microsoft cloud.
  • APSA-18303 autoconf.py script cannot update "/possible_parents" collection.
  • APSA-17940 NL-nl localization issues in Office 365 16.8.3.
  • APSA-16706 Wrong error message is shown in CCP when app endpoint returns response with code 403.
  • APSA-16479 Translations of some keys are absent in nl_NL.po.
  • APSA-16026 'Skype P1 to Enterprise E1' upgrade task fails with error 'Subscription has multiple resources'.
  • APSA-19143 'Provisioning "Migration"' task fails with error 'The domain *** has already been added' due to duplicated APS resource 'Office365/Domain'.
  • APSA-18941 Office 365 task fails with error "Invalid partnerId: 0".

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.2 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.

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. Validating the format of the admin user's login in the application instance setting Administrator's login for connecting to Microsoft Online.
  3. Stopping provisioning Office 365 services.
  4. Upgrading the Office 365 application endpoint.
  5. Upgrading the Office 365 application.
  6. Updating the OA Billing control panel and online store customizations.
  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.1/17.1.1/17.1.2/17.1.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 >> 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. For each Office 365 application instance, validate the format of the admin user's login in the application instance setting Administrator's login for connecting to Microsoft Online:

    1. Log in to the control panel using the credentials of the provider account.
    2. Go to Services > Applications, select the Office 365 application and the necessary Office 365 application instance.
    3. Make sure that the login of the admin user is based on the onmicrosoft.com domain (for instance, partner.onmicrosoft.com). If it is not so, create a user whose login is based on the onmicrosoft.com domain in the Partner Center, set Assists your customers as to Admin agent for the user in the Partner Center, update the application instance settings Administrator's login for connecting to Microsoft Online and Administrator's password for connecting to Microsoft Online for the Office 365 application instance in the Odin Automation control panel.

      We recommend that you use the following user name and login for the admin user: Odin Automation and oa_account@<partnersubdomain>.onmicrosoft.com.

  3. 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.
  4. 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.
  5. 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.
  6. 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.

  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.

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. Creating native apps for Graph API access.

    Important: Do not perform further upgrade steps until you create and configure native apps for Graph API access (configuring includes the steps of the KB article Office 365 16.6.4 and Higher: Configuring Pre-consent for Graph API App).

  3. Validating the format of the admin user's login in the application instance setting Administrator's login for connecting to Microsoft Online.
  4. Stopping provisioning Office 365 services.
  5. Upgrading the Office 365 application endpoint.
  6. Upgrading the Office 365 application.

    Important: Before upgrading the Office 365 application and its instances, make sure that all native apps necessary for Graph API access are created and configured (configuring includes the steps of the KB article Office 365 16.6.4 and Higher: Configuring Pre-consent for Graph API App).

  7. Updating the OA Billing control panel and online store customizations.
  8. Specifying the application instance setting ID of Native Client for Azure AD Graph API.
  9. Checking allowed upgrade paths of Office 365 service plans.
  10. Performing post-upgrade validation.
  11. Starting provisioning Office 365 services.

Important:

  • The upgrade procedure is not reversible.
  • Upgrade steps 1-11 are mandatory.
  • Make sure the current version of the Office 365 application is 17.1/17.1.1/17.1.2/17.1.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:

  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. For each Office 365 application instance, create a native app for Graph API access.

    1. Log in to the Partner Center using the credentials of the partner account used by the Office 365 application instance.

      Note: Make sure that your user has full access to all administrative and Partner Center features (Manages your company as is set to Global admin in the Partner Center). Otherwise, you will not be able to perform further upgrade steps, such as step 2.2 and step 2.3.

    2. In the Partner Center, go to Account settings > App management.
    3. In the Partner Center, add a native app and write down its App ID (this native app will be used for access to the Graph API).
    4. Configure pre-consent for the native app using the instruction of the KB article https://kb.odin.com/en/126807.

    Important: Do not perform further upgrade steps until you create and configure native apps for Graph API access (configuring includes the steps of the KB article Office 365 16.6.4 and Higher: Configuring Pre-consent for Graph API App).

  3. For each Office 365 application instance, validate the format of the admin user's login in the application instance setting Administrator's login for connecting to Microsoft Online:

    1. Log in to the control panel using the credentials of the provider account.
    2. Go to Services > Applications, select the Office 365 application and the necessary Office 365 application instance.
    3. Make sure that the login of the admin user is based on the onmicrosoft.com domain (for instance, partner.onmicrosoft.com). If it is not so, create a user whose login is based on the onmicrosoft.com domain in the Partner Center, set Assists your customers as to Admin agent for the user in the Partner Center, update the application instance settings Administrator's login for connecting to Microsoft Online and Administrator's password for connecting to Microsoft Online for the Office 365 application instance in the Odin Automation control panel.

      We recommend that you use the following user name and login for the admin user: Odin Automation and oa_account@<partnersubdomain>.onmicrosoft.com.

  4. 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.
  5. 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.

  6. 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.

    Important: Before upgrading the Office 365 application and its instances, make sure that all native apps necessary for Graph API access are created and configured (configuring includes the steps of the KB article Office 365 16.6.4 and Higher: Configuring Pre-consent for Graph API App).

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

  8. For each Office 365 application instance, specify the setting ID of Native Client for Azure AD Graph API:

    1. Log in to the Odin Automation control panel using the credentials of the provider account.
    2. Go to Services > Applications, select the Office 365 application and the necessary Office 365 application instance.
    3. Specify the prepared App ID in the ID of Native Client for Azure AD Graph API setting.
    4. Make sure that the setting is correctly specified by clicking Test Connection.
  9. Check allowed upgrade paths of each Office 365 service plan:

    1. Obtain the CSP Deployment Assistant Tool from https://www.dropbox.com/sh/flvexj79k532lma/AADVZXXgraLg7DbQilkqYnf1a?dl=0 (use Office365DeploymentAssistant.2017.09.xlsx or newer).
    2. Make sure that the allowed upgrade paths of your Office 365 service plans are configured as specified in the CSP Deployment Assistant Tool.
  10. 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.
  11. Start provisioning Office 365 services. For example, activate the Office 365 service template in OA Operations.

Help Resources

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

Email subscription for changes to this article
Save as PDF