SMS Connector Installation Step-by-Step Guide

Introduction

Use this guide as an overview to help you configure SMS services using the SMS Connector App and Unified Connector App—collectively referred to as SMS Connectors. It outlines the key setup steps and provides direct links to related articles for detailed instructions and configuration guidance.

IMPORTANT UPDATE
To simplify deployment and ongoing management, we are consolidating four separate connector applications into a single Unified Connector App.
This approach reduces complexity for both enterprise administrators and end users by eliminating the need to install, configure, and manage multiple Microsoft Teams applications. With the Unified Connector App, organizations benefit from a single installation that supports PBX, SMS, Call, and Chat services, resulting in a more streamlined setup experience, fewer configuration points, and a more consistent user interface.
Additional benefits of this consolidation include simplified updates and version control, improved reliability through shared services, reduced administrative overhead, and a clearer support and troubleshooting model.

Recommendation
The CallApp and Chat services are now available exclusively through the Unified Connector App.
New enterprise deployments are therefore strongly encouraged to use the Unified Connector App for PBX and SMS, rather than relying on standalone connector apps.
The end of life date for PBX and SMS Connector Apps will be announced soon.

The SMS Connectors

Setting Up an SMS Connector for an Enterprise

Setting up an SMS Connector involves the collaboration of the Service Provider and the Enterprise Admin with Global Admin role in Teams Admin Center. Some tasks can be delegated to non-Global Admins, but due to Microsoft’s security policies there is no way to complete setup without the Global Administrator’s initial involvement.

Instructions for the Service Provider

Carry out the following steps in the ConnecttoTeams Service Portal.

Configure the enterprise for SMS service.
For a new enterprise: create the enterprise with SMS service included. In the Registered Email ID field, supply the Microsoft Global Administrator’s email address. The Global Admin will receive the invitation email which contains instruction with a with a link to start the set-up process.
- For an existing enterprise: edit the enterprise to add “SMS” to the Service field.
Optionally, review your app template.
If you want to make changes that apply to all enterprises, update your Reseller-level default app template:
- If your enterprises are using the new Unified Connector app, follow this guide: Build Unified App Template.
- If your enterprises are using the legacy SMS Connector app, follow this guide: Build SMS App Template.
To customize settings for a specific enterprises.
This prepares the app for the deployment by the Global Admin, which is included in the steps presented in the next section.
- If the enterprise uses the Unified Connector App, check this guide: Customize and Deploy Unified Connector App for an Enterprise
- If the enterprise uses the legacy SMS Connector App, check this guide: Customize and Deploy SMS App for an Enterprise.
Configure SMS Carrier Profiles and assign applicable profile/s to the enterprise.
If the underlying SMS provider is one of these SMS providers - Netsapiens, RingLogix, United Cloud, Viirtue - configure the SMS domains for your enterprise.
Skip this step if the SMS provider is not one of these providers.
If Reseller is providing SMS phone numbers to enterprise, upload new phone numbers with SMS capability or edit existing phone numbers to add SMS support. Make sure each number is configured with the correct SMS Carrier Profile with valid API credentials, and is properly assigned to the target enterprise.

Instructions for the Enterprise Admin

In Teams Admin Center
1. Enable the Messaging Policies for SMS and Chat Apps
2. Ensure you have custom apps enabled for Teams
If you're a new enterprise, your Microsoft organization's Global Administrator should follow the instructions provided in the invitation email.
Clicking the COMPLETE button in that email will prompt the Global Admin to grant the required permissions.
Using Global Admin credentials, log in to:
- The Messaging Portal, if you're using messaging services only.
- The Enterprise Portal, if you're using both messaging and calling services.
You’ll be asked to grant permissions. These must be accepted before the enterprise can access the portal.
Sync your user groups.
If allowed by service provider to upload phone numbers, upload phone numbers with SMS capability.
Individually configure SMS users or in bulk, and any SMS Groups as needed, and assign them their respective SMS phone numbers. These tasks can be delegated to non-Global Admins.
Deploy and sync the app.
- If your enterprise uses the Unified Connector, check this guide: Deploy and Sync the Unified Connector App
- If your enterprise uses the legacy SMS Connector, check this guide: Deploy and sync the SMS Connector app..
If your navigation menu shows SMS Domains page, verify that your Domains have Subscription ID and Date Subscribed are filled and that the Expiry Date is a future date. This ensures your Teams users will your inbound SMS messages.
Otherwise, reach out to your Service Provider to troubleshoot the issue.
You won’t see this page if your underlying SMS Provider does not require you to configure this.
Direct your users to the user guide: Getting Started with SMS and MMS: End User Experience.
You may find the need to disable SMS for a user or unassign phone numbers as part of user managemen. If your enterprise is using the legacy SMS Connector, any changes to phone number assignment and SMS user configuration require a manual sync. To ensure updates are applied correctly, follow the instructions in this guide: sync the SMS Connector app.

Note to the Service Provider
Still having trouble? Submit a help desk ticket through the Enterprise Portal.

Troubleshooting Issues

There may be issues with the deployment of the app. Review the troubleshooting guides for app deployment issues here.