Configure
Skype for Business
for the
Connect
service

You can configure your environment to work with

Skype for Business

If your environment uses multiple

Skype for Business

on-premises servers using trusted application mode or non-trusted application mode, have the

Skype for Business

servers load balanced with a load balance server. For more information about load balancing requirements, visit https://docs.microsoft.com/en-us/skypeforbusiness/plan-your-deployment/network-requirements/load-balancing.

If your environment uses

Skype for Business

in non-trusted application mode, verify that you completed the prerequisite for the LyncDiscoverInternal DNS record. For more information about preinstallation requirements, see "BlackBerry Connect and BlackBerry Presence" in the BEMS installation content.

If your environment uses

Skype for Business

in non-trusted application mode, import the certificate chain trust into the

BEMS

Java

keystore to trust the HTTPS connections to LyncDiscoverInternal.example.com and the

Skype

Front End pool. For instructions on how to import the certificate chain, see "Import the CA certificate into the Java certificate store" in the BEMS-Core configuration content.

In the

BlackBerry Enterprise Mobility Server Dashboard

, under

BlackBerry Services Configuration

, click

Connect

Click

Service Account

, enter the

BEMS

service account credentials, and click

Save

Click

Skype for Business

. The system queries the instant messaging server to verify that the appropriate

BEMS

instant messaging server topology is added. This can take a few moments.

Complete one of the following tasks:

Instant messaging server in environment	Tasks
Skype for Business on-premises using trusted application mode Using this configuration, the Connect service is trusted by Skype for Business and can impersonate a user. End user authentication is not required on the device to access BlackBerry Connect .	Select the Skype for Business On-Premises check box. Select Trusted Application Mode . Beside the Application ID dropdown list, click Browse . This step can take up to a minute to complete. In the Application ID drop-down list, select the app ID. For example, <`appid_connect.mycompany.com`> . If the drop-down list is empty, either the BEMS <`instant messaging server type`> topology is not set up correctly or the service account does not have permissions to query these settings. If you enable persistent chat in your Skype for Business 2015 environment, in the Persistent Chat Default Category field, enter the default category. For more information on enabling persistent chat, see the BlackBerry Connect Administration content.
Skype for Business on-premises using non-trusted application mode Using this configuration, the Connect service is not trusted by Skype for Business and cannot impersonate a user. End user authentication on the device is required to access BlackBerry Connect .	Select the Skype for Business On-Premises check box. Select Non-trusted Application Mode . Complete one or both of the following actions: Select the Auto discover servers checkbox for BEMS to use the existing DNS records of LyncDiscoverInternal to discover the Skype for Business servers in the environment. For more information about preinstallation requirements, see "BlackBerry Connect and BlackBerry Presence" in the BEMS installation content. Enter the default Skype for Business on-premises FQDN or the complete URL to the Skype for Business server for BEMS to use if autodiscovery is not enabled or fails. For example, http(s)://<`FQDN_of_the Skype_front_end_pool`>/Autodiscover/AutodiscoverService.svc/root/oauth/user. The certificate chain trust must be imported into the BEMS Java keystore to trust the HTTPS connections to LyncDiscoverInternal.example.com and the Skype Front End pool. For instructions on how to import the certificate chain, see "Import the CA certificate into the Java certificate store" in the BEMS-Core configuration content.

Instant messaging server in environment

Tasks

Skype for Business

on-premises using trusted application mode

Using this configuration, the

Connect

service is trusted by

Skype for Business

and can impersonate a user. End user authentication is not required on the device to access

BlackBerry Connect

Select the

Skype for Business On-Premises

check box.

Select

Trusted Application Mode

Beside the

Application ID

dropdown list, click

Browse

. This step can take up to a minute to complete.

In the

Application ID

drop-down list, select the app ID. For example,

<appid_connect.mycompany.com>

If the drop-down list is empty, either the

BEMS

<instant messaging server type> topology is not set up correctly or the service account does not have permissions to query these settings.

If you enable persistent chat in your

Skype for Business

2015 environment, in the

Persistent Chat Default Category

field, enter the default category. For more information on enabling persistent chat, see the BlackBerry Connect Administration content.

Skype for Business

on-premises using non-trusted application mode

Using this configuration, the

Connect

service is not trusted by

Skype for Business

and cannot impersonate a user. End user authentication on the device is required to access

BlackBerry Connect

Select the

Skype for Business On-Premises

check box.

Select

Non-trusted Application Mode

Complete one or both of the following actions:

Select the

Auto discover servers

checkbox for

BEMS

to use the existing DNS records of LyncDiscoverInternal to discover the

Skype for Business

servers in the environment. For more information about preinstallation requirements, see "BlackBerry Connect and BlackBerry Presence" in the BEMS installation content.

Enter the default

Skype for Business

on-premises FQDN or the complete URL to the

Skype for Business

server for

BEMS

to use if autodiscovery is not enabled or fails. For example, http(s)://<FQDN_of_the Skype_front_end_pool>/Autodiscover/AutodiscoverService.svc/root/oauth/user.

The certificate chain trust must be imported into the

BEMS

Java

keystore to trust the HTTPS connections to LyncDiscoverInternal.example.com and the

Skype

Front End pool. For instructions on how to import the certificate chain, see "Import the CA certificate into the Java certificate store" in the BEMS-Core configuration content.

Verify that the

Azure

information is accurate and log in to the user account:

If you configure the environment to use

Skype for Business

On-Premises using non-trusted application mode

Click

Test

Enter a user email address and password.

Click

Test

Click

Save

For more information about available settings in the

BEMS-Connect

configuration files, see Appendix: Understanding the BEMS-Connect configuration file.

Section:

Configuring the Connect service in the BEMS dashboard

Configure Skype for Business for the Connect service

Configure
Skype for Business
for the
Connect
service