This version of the application reached its end of life. We recommend that you upgrade to the latest supported version of the application. To obtain the latest supported version, see this article.

Table of Contents

Release Notes

You can read the complete Office 365 18.1 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 7.0 Release Notes >> Changes > Core > New Branding Implementation for details). This change affects the Office 365 application (see Odin Automation 7.0 Upgrade Workflow Guide >> Pre-Upgrade Actions > Branding Configuration Restrictions > Back Up Branding Customizations and Odin Automation 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.

Fixed Issues

  • APSA-19580 Office 365 endpoint deployment/upgrade scripts must support SQL Server databases configured for high availability.
  • APSA-19616 Attempt to process more than 50,000 users during synchronization leads to error "System.Data.SqlClient.SqlException (0x80131904): Timeout expired.".
  • APSA-19533 Domain synchronization fails with error "Domain name conflicts with existing domain '__domain_name__'".
  • APSA-19360 Reconciliation report generation fails with "timeout" error under provider account because bottom threshold for OrderByStatusListGet_API is not set.
  • APSA-19581 Unclear Office 365 upgrade documentation (configuring "Native App for Graph API").
  • APSA-19539 readCSPAccounts.py script does not support non-Office 365 resources.
  • APSA-19480 Only *.onmicrosoft.com subdomains must be used with account-default-domain parameter.
  • APSA-19467 Documentation improvement request regarding reconciliation reports.
  • APSA-19463 Upgrade instructions of Office 365 customizations contain outdated paths.
  • APSA-19449 account-default-domain parameter is not mentioned in Odin Automation Office 365 Integration Provider's Guide.
  • APSA-19508 'Not found SKU for user xxx@xxx.onmicrosoft.com matching offer WIN10_VDA_E3' error.
  • APSA-19492 Administrative users cannot select domains when assigning Office 365 service to themselves in CCP v2.
  • APSA-19037 Multi-offer Office 365 subscriptions: licenses are shown in CCP v2 despite zero limits.
  • APSA-18306 Different price formats on different screens.
  • APSA-18279 It is not possible to buy add-on to existing license on Office 365 tab.
  • APSA-19627 In CCP v2, 'Reassign User Licenses' button works incorrectly when billing menu items are disabled (error is shown, though licenses are reassigned).
  • APSA-19622 Azure AD GRAPH API Error: 'DeltaLink older than 30 days is not supported.'.
  • APSA-19618 Task 'Provisioning "AsyncOperation"' fails with error 'Sequence contains more than one matching element.'.
  • APSA-19589 Task 'Provisioning "Subscription" for APS application Office 365' fails with error "Domain name '__domain__' is reserved by domain part of existing service user".
  • APSA-19525 UTC time is used by synchronization, whereas local time is used by tasks that start synchronization. That causes synchronization to produce huge sitelog.
  • APSA-19503 Property 'is_activated' of 'Office 365 tenant' APS resource is 'activating' whereas all provisioning tasks are successfully completed.
  • APSA-19458 'Office 365 tenant' APS resource with 'aps:unprovisioning' status is not checked when new sales order is placed.
  • APSA-19457 'BillingPeriod' property is not taken into account when subscription is reactivated.
  • APSA-19104 autoconf.py error: "poaupdater.openapi.OpenAPIError: Table Screen doesn't contain row with id ... ".
  • APSA-19093 'Add-on Type Edit' screen does not store all possible parents.
  • APSA-18782 Script autoconf.py should allow specifying input files for sales categories and resource categories.
  • APSA-18167 Ability to correct SubscriptionStartDate in subscriptions created by Office 365 import script is required.
  • APSA-19641 Office 365 documentation contains description of disabled functionality.
  • APSA-19662 Sales order fails with error "Language es is not supported in country AD.".
  • APSA-19588 Unclear error message is shown in 'Use an existing Microsoft account' scenario.
  • APSA-19579 Incorrect translations in nl_NL.json.
  • APSA-19233 autoconf.py does not work if HTTP authentication is enabled for XMLRPC API.
  • APSA-18296 Import script readCSPAccounts.py tries to use non-published service plans.
  • APSA-19238 Canceled periodic tasks of uninstalled Office 365 application instances are rescheduled when Office 365 is upgraded.
  • APSA-19279 Unexpected behavior of "Synchronization with Office 365 Portal" periodic tasks.
  • APSA-19658 Property 'friendly name' should be set during cloud subscription provisioning.
  • APSA-19705 autoconf.py does not work if HTTP authentication is enabled for XMLRPC API.
  • APSA-18860 Improvements of column names in reconciliation reports.

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

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

Marketplace of UX1 for Customers is Supported

Now, the Office 365 application supports the Marketplace of UX1 for Customers, which provides customers with a convenient way of buying Office 365 services directly from their control panel.

Ability to Turn Off Auto-linking of Domains to Office 365 Organizations

The auto-linking of domains to Office 365 organizations is a feature of the Office 365 application. It is responsible for automatically linking customer domains to Office 365 organizations when customers buy Office 365 services (existing domains and domains bought with Office 365 services are taken into account).

In previous versions of the Office 365 application, auto-linking is constantly turned on and cannot be turned off. Since Office 365 18.1, service providers can turn auto-linking off using the application global setting Automatically add domains to Office 365 organizations (Yes/No).

Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Deploying 'Office 365' Application > Creating 'Office 365' Application Instance

Odin Automation Office 365 Integration Subscriber's Guide >> Managing Office 365 Domains

Support for Multi-level Offer Model

Microsoft switched its offer model from two-level (offers can have child add-on offers) to multi-level (offers can have child add-on offers, which, in turn, can also have child add-on offers, and so on).

Now, the Office 365 application supports the multi-level offer model, as well as add-on offers of the second and deeper levels. This allows you to provide your customers with new Office 365 services.

When configuring offers, take into account the parent-child relations of the offers:

  • An add-on offer has parent offers, which, in turn, may have their own parent offers, and so on, up to top-level offers; a customer tenant can be subscribed to an add-on offer only if the customer tenant has subscriptions to all necessary ancestor offers of the add-on offer, starting from a parent offer and ending with a top-level offer.

  • If you need to provide your customers with an add-on offer, you must create not only an add-on type for the add-on offer but also license and add-on types for all necessary ancestor offers of the add-on offer.

  • If you need to provide your customers with an add-on offer within an 'Office 365' service plan, you must create not only a resource rate for the 'Office 365 Add-on' resource of the add-on offer but also resource rates for 'Office 365 License' and 'Office 365 Add-on' resources of all necessary ancestor offers of the add-on offer.

Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Offers > Creating License Types

Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Offers > Creating Add-on Types

Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Configuring Offers > Creating 'Office 365' Service Plans

New Offers are Supported

Now, the Office 365 application supports the following new offers:

  • Domestic Calling Plan (120 min)
  • Domestic Calling Plan (120 min) for faculty
  • Domestic Calling Plan (120 min) for students
  • Common Area Phone
  • Common Area Phone for faculty
  • Common Area Phone for students
  • Azure Advanced Threat Protection for Users
  • Azure Advanced Threat Protection for Users (Government Pricing)
  • Azure Advanced Threat Protection for Users for Faculty
  • Azure Advanced Threat Protection for Users for Students
  • Minecraft: Education Edition (per user)
  • Microsoft 365 A1
  • Exchange Online Advanced Threat Protection (Nonprofit Staff Pricing)
  • Microsoft 365 Business (Nonprofit Staff Pricing)
  • Microsoft 365 Business (Nonprofit Staff Pricing) Trial
  • Microsoft 365 E3 (Nonprofit Staff Pricing)
  • Microsoft Stream Plan 2 for Office 365 Add-On (Nonprofit Staff Pricing)
  • Microsoft Stream Storage Add-On (500 GB) (Nonprofit Staff Pricing)
  • Office 365 Business Essentials (Nonprofit Staff Pricing)
  • Office 365 Business Premium (Nonprofit Staff Pricing)
  • Office 365 Business Premium (Nonprofit Staff Pricing) Trial
  • Office 365 Enterprise E1 (Nonprofit Staff Pricing)
  • Office 365 Enterprise E3 (Nonprofit Staff Pricing)
  • Office 365 Enterprise E5 (Nonprofit Staff Pricing)
  • Office 365 Enterprise E5 (Nonprofit Staff Pricing) Trial
  • Office 365 Extra File Storage (Nonprofit Staff Pricing)
  • Office 365 ProPlus (Nonprofit Staff Pricing)
  • Project Online Essentials (Nonprofit Staff Pricing)
  • Project Online Premium (Nonprofit Staff Pricing)
  • Project Online Professional (Nonprofit Staff Pricing)
  • Visio Online Plan 1 (Nonprofit Staff Pricing)
  • Visio Online Plan 1 (Nonprofit Staff Pricing) Trial
  • Visio Online Plan 2 (Nonprofit Staff Pricing)
  • Exchange Online Archiving for Exchange Online (Nonprofit Staff Pricing)
  • Microsoft 365 F1 (Nonprofit Staff Pricing)
  • Office 365 Advanced Compliance (Nonprofit Staff Pricing)
  • Office 365 Cloud App Security (Nonprofit Staff Pricing)
  • Office 365 Enterprise E3 (Nonprofit Staff Pricing) Trial
  • Office 365 ProPlus (Nonprofit Staff Pricing) Trial
  • Office 365 Threat Intelligence (Nonprofit Staff Pricing)
  • Phone System (Nonprofit Staff Pricing)
  • Skype for Business Online (Plan 2) (Nonprofit Staff Pricing)
  • Visio Online Plan 2 (Nonprofit Staff Pricing) Trial
  • Windows 10 Enterprise E3 (local only) (Nonprofit Staff Pricing)
  • Windows 10 Enterprise E3 (Nonprofit Staff Pricing)
  • Windows 10 Enterprise E5 (Nonprofit Staff Pricing)

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

Nonprofit offers are offers intended for nonprofit organizations. To be able to subscribe to such offers, nonprofit organizations have to meet certain requirements, which can be viewed at https://www.microsoft.com/en-us/nonprofits/eligibility.

The application processes subscriptions to nonprofit offers in a special way: When a customer places an order to subscribe to a service plan including a nonprofit offer, the application checks if the customer tenant of the customer is eligible for the offer. If so, the order is processed as usual. If not, the processing of the order is stopped so that no subscription is created on the Microsoft side. Such an order can be resubmitted for further processing as soon as the customer tenant of the customer becomes eligible. You can see more details about this in Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Useful Information > Processing Orders of Nonprofit Offers.

Compression of sitelog is Turned On

Now, the sitelog files of Office 365 application endpoints, which contain log records of the endpoints and are rotated on a daily basis, are compressed after their rotation. This will help service providers reduce the consumption of disk space on their Office 365 application endpoint hosts.

On new installations of the application, the compression of sitelog is turned on by default. On existing installations of the application, the compression of sitelog is automatically turned on after upgrading to Office 365 18.1.

If necessary, you can turn off the compressions of sitelog for an endpoint. To do this, in web.config of the endpoint, comment the line <appender name="RollingLogFileAppender" type="Parallels.Office365.Gateway.Log.ZipRollingFileAppender"> and uncomment the line <appender name="RollingLogFileAppender" type="log4net.Appender.RollingFileAppender">. Then, execute the iisreset command.

Odin Automation Office 365 Integration Provider's Guide >> Cloud Solution Provider Scenario > Useful Information > Viewing and Configuring Endpoint Logs

Ingram Micro Federation is Supported

Now, the Office 365 application supports Ingram Micro Federation (http://www.ingrammicrocloud.com/federation/).

Ingram Micro Federation provides a new way of selling cloud services, including Office 365 services.

The key points of selling Office 365 services with Ingram Micro Federation:

  • Ingram Micro Federation is available to a service provider that uses Odin Automation.
  • The service provider does not need to have a contract with Microsoft to sell Office 365 services; it is enough to be an Ingram Micro Federation partner.
  • The service provider must have a federated subscription. The subscription defines which Office 365 services the service provider can sell to customers.
  • The service provider must have an Indirect CSP Reseller account in the Microsoft Partner Center.
  • The Indirect CSP Reseller account of the service provider must be connected with an Indirect CSP Provider account of Ingram Micro.
  • Ingram Micro Federation requires installation and configuration that are performed on both sides: The Office 365 application is installed and configured within the Odin Automation system of the service provider. Additional components necessary for Ingram Micro Federation are installed and configured both on the side of the service provider and on the side of Ingram Micro.

Odin Automation Office 365 Integration Provider's Guide >> Ingram Micro Federation

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

Contact your Ingram Micro 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 Office 365 Integration Provider's Guide.

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 new 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.3/17.3.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 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 contents 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.

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

  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. Configure the following new offers:

    • Domestic Calling Plan (120 min)
    • Domestic Calling Plan (120 min) for faculty
    • Domestic Calling Plan (120 min) for students
    • Common Area Phone
    • Common Area Phone for faculty
    • Common Area Phone for students
    • Azure Advanced Threat Protection for Users
    • Azure Advanced Threat Protection for Users (Government Pricing)
    • Azure Advanced Threat Protection for Users for Faculty
    • Azure Advanced Threat Protection for Users for Students
    • Minecraft: Education Edition (per user)
    • Microsoft 365 A1
    • Exchange Online Advanced Threat Protection (Nonprofit Staff Pricing)
    • Microsoft 365 Business (Nonprofit Staff Pricing)
    • Microsoft 365 Business (Nonprofit Staff Pricing) Trial
    • Microsoft 365 E3 (Nonprofit Staff Pricing)
    • Microsoft Stream Plan 2 for Office 365 Add-On (Nonprofit Staff Pricing)
    • Microsoft Stream Storage Add-On (500 GB) (Nonprofit Staff Pricing)
    • Office 365 Business Essentials (Nonprofit Staff Pricing)
    • Office 365 Business Premium (Nonprofit Staff Pricing)
    • Office 365 Business Premium (Nonprofit Staff Pricing) Trial
    • Office 365 Enterprise E1 (Nonprofit Staff Pricing)
    • Office 365 Enterprise E3 (Nonprofit Staff Pricing)
    • Office 365 Enterprise E5 (Nonprofit Staff Pricing)
    • Office 365 Enterprise E5 (Nonprofit Staff Pricing) Trial
    • Office 365 Extra File Storage (Nonprofit Staff Pricing)
    • Office 365 ProPlus (Nonprofit Staff Pricing)
    • Project Online Essentials (Nonprofit Staff Pricing)
    • Project Online Premium (Nonprofit Staff Pricing)
    • Project Online Professional (Nonprofit Staff Pricing)
    • Visio Online Plan 1 (Nonprofit Staff Pricing)
    • Visio Online Plan 1 (Nonprofit Staff Pricing) Trial
    • Visio Online Plan 2 (Nonprofit Staff Pricing)
    • Exchange Online Archiving for Exchange Online (Nonprofit Staff Pricing)
    • Microsoft 365 F1 (Nonprofit Staff Pricing)
    • Office 365 Advanced Compliance (Nonprofit Staff Pricing)
    • Office 365 Cloud App Security (Nonprofit Staff Pricing)
    • Office 365 Enterprise E3 (Nonprofit Staff Pricing) Trial
    • Office 365 ProPlus (Nonprofit Staff Pricing) Trial
    • Office 365 Threat Intelligence (Nonprofit Staff Pricing)
    • Phone System (Nonprofit Staff Pricing)
    • Skype for Business Online (Plan 2) (Nonprofit Staff Pricing)
    • Visio Online Plan 2 (Nonprofit Staff Pricing) Trial
    • Windows 10 Enterprise E3 (local only) (Nonprofit Staff Pricing)
    • Windows 10 Enterprise E3 (Nonprofit Staff Pricing)
    • Windows 10 Enterprise E5 (Nonprofit Staff Pricing)

  8. To configure the offers, you can use the instructions provided in KB article #126207.

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

Help Resources

Internal content

Link on internal Article