Creating an Office 365 Application Instance

To be able to use the Office 365 application, first you need to create a new application instance.

  1. In the Provider Control Panel, go to Services > Applications. Then, select the APS Connectors tab and click the Office 365 application.
  2. Select the Instances tab and click Add Instance.

  3. Specify the following parameters:

    • Application Version: Select the required version of the application.
    • Application API end-point URI: The application API endpoint URI, which is constructed in the following way: https://<Office_365_Gateway_Site_Hostname>/<Office_365_Gateway_Application_Name>/aps/. For example: https://office365gateway01.hosting.local/Office365GatewayApplication01/aps/.
    • Authentication Type: Select Certificate.
    • Network Access: Select Backnet.

    Select the Accept the impersonation level checkbox and click Next.

    Important:

    1. The hostname specified in Office_365_Gateway_Site_Name must be resolved from the OA Operations Management Node into the BackNet IP address of the Office 365 Application Endpoint Host.

    2. Each Office 365 gateway site requires a separate BackNet IP address.

  4. Specify the following application instance settings:

    • Instance Name: The name of the application instance.
    • URL for Microsoft Online Services Portal: The URL of the Office 365 admin center.
    • Homepage: (Optional) The URL of your website. If it is specified, this URL is displayed in the Customer Control Panel. For example: https://provider.com.

    • OA Billing OpenAPI URL: The OA Billing Public API URL. For example: https://bss-public-api.hosting.local:5224/RPC2.

      Important: On your Office 365 Application Endpoint Host, make sure that the host name specified in this URL is resolved to the BackNet IP address of the OA Billing Application Server.

    • User name for connecting to OA Billing API: The name of the prepared user used to connect to the OA Billing Public API.
    • User password for connecting to OA Billing API: The password of the prepared user used to connect to the OA Billing Public API. Note that the setting is not displayed in view mode.
    • Reseller tenant ID: Specify the Microsoft ID of your CSP partner account that you prepared (see Preparing a CSP Account for details).

    • Customer Deactivation Behavior: Choose how to handle Microsoft accounts of customers when the corresponding Odin Automation subscriptions are canceled in Odin Automation. The following options are available:

      • Production Account. When an Odin Automation subscription is canceled in Odin Automation, the corresponding Microsoft account and subscriptions are disabled. The corresponding Microsoft users are removed. Use this option for production environments. This option is selected by default.
      • TIP (Test In Production) Account. When an Odin Automation subscription is canceled in Odin Automation, the corresponding Microsoft account, users, and subscriptions are removed. Use this option for test environments only.
    • Confirm Deactivation Behavior: Confirm the TIP (Test In Production) Account customer deactivation behavior by selecting the I do understand the difference between TIP and Production accounts and my account is a TIP account option.
    • Federated Credentials Provider Application Instance: Leave the default value.
    • "Secondary E-mail" is a mandatory Service User's details field: Leave the default value. This global setting is reserved for future use.
    • Welcome Message Templates Download URL: If you need to send welcome messages to newly created Office 365 users, specify the prepared URL.
    • Format Phone Numbers: Make sure it is set to No (the checkbox needs to be clear).

    • Prefix for Naming Subscriptions: A prefix for generating names of customer initial domains. The following options are available:

      • If this parameter is not specified, names of customer initial domains must be manually specified in the online store or Customer Control Panel.
      • If this parameter is specified and names of customer initial domains are not manually specified, Odin Automation automatically generates these names using the value of the parameter and subscription identifiers. For example, if the value of the parameter and a subscription identifier are companyabc and 1000000, the name of the customer initial domain will be companyabc1000000.onmicrosoft.com (for Microsoft Cloud) or companyabc1000000.partner.onmschina.cn (for Office 365 operated by 21Vianet in China). Note that you must use only the following symbols for this parameter: a-z, A-Z, 0-9.
    • Reseller Mode: Select either Direct CSP Provider or Indirect CSP Provider depending on the type of the CSP account you create the application instance for.

    • OA Operations OpenAPI URL: The OA Operations Public API URL. For example: https://oss-public-api.hosting.local:8440/.

      Important: On your Office 365 Application Endpoint Host, make sure that the host name specified in the URL is resolved to the BackNet IP address of the OA Operations Management Node.

    • User name for connecting to OA Operations API: The login of the prepared user used to connect to the OA Operations Public API.
    • User password for connecting to OA Operations API: The password of the prepared user used to connect to the OA Operations Public API. Note that this setting is not displayed in view mode.

    • Cloud Type: Select the type of the cloud that the application instance is intended for (Microsoft Cloud or Office 365 operated by 21Vianet in China).

      Important: You will not be able to change this setting after you create the application instance.

    • Automatically add domains to Office 365 organizations: Specify whether the auto-linking of customer domains to Office 365 organizations is turned on. The following options are available:

      • Yes. When a customer buys Office 365 services, existing domains of the customer account as well as domains bought with the Office 365 services are automatically added to the Office 365 organization of the customer. Also, the Exchange and Lync services are enabled for these customer domains.

        Notes:

        1. Domains that already have MX DNS records are excluded from auto-linking.

        2. Up to 10 domains can be auto-linked. If a customer account has more domains, the remaining domains are not auto-linked.

      • No. The auto-linking of customer domains is turned off.
    • Invitation URL for indirect resellers: The URL of a page on which Indirect CSP Resellers can connect their CSP partner accounts with CSP partner accounts of Indirect CSP Providers. Leave the default value of this setting.

    Click Next.

  5. Check the parameters carefully and click Finish.

© 2021 Ingram Micro, Inc. All Rights Reserved. Privacy Policy, Terms of Use and Legal