---
title: "SMS Connector Installation Step-by-Step Guide"
slug: "sms-connector-installation-step-by-step-guide"
updated: 2026-07-21T16:30:59Z
published: 2026-07-21T16:30:59Z
canonical: "kb.connecttoteams.com/sms-connector-installation-step-by-step-guide"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.connecttoteams.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SMS Connector Installation Step-by-Step Guide

## Introduction

Use this guide as an overview to help you configure SMS services using the **legacy 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.

![](https://cdn.us.document360.io/312e5ae5-e3c1-465d-8e37-f253a7ba8eee/Images/Documentation/sms-connector-and-unified-connector(1).png)

> [!NOTE]
> Introducing the Unified Connector App
> 
> 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.
> 
> 
> 
> **Key Benefits**
> 
> **One app, four services:** A single installation now supports PBX, CallApp, SMS, and Chat services — no more juggling multiple Teams apps.
> 
> **Simpler setup:** Fewer configuration points and a more streamlined deployment experience.
> 
> **Consistent user experience:** One unified interface across all connector services.
> 
> **Easier maintenance**
> 
> - Simplified updates and version control
> - Improved reliability through shared services
> - Reduced administrative overhead
> - Clearer support and troubleshooting model
> 
> **New: AI-powered actions:** Starting with system upgrade **2.19.0 on March 17, 2026**, the Unified Connector App includes AI support. Users can perform actions like sending SMS messages using plain, everyday language directly from any Microsoft Teams conversation screen — no special commands or navigation required.

> [!NOTE]
> 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, CallApp and SMS, rather than relying on standalone connector apps.
> 
> 
> 
> **The end of life date for PBX, CallApp and SMS Connector Apps will be announced soon.**

## Setting Up the SMS Connector Service for an Enterprise

Setting up an SMS Connector involves the collaboration of the Service Provider and the [Enterprise Admin with Global Admin role](/v1/docs/global-administrator-requirement) in Teams Admin Center. Some tasks can be delegated to [non-Global Admins](/v1/docs/enterprise-manage-users-without-global-admin), but due to Microsoft’s security policies there is no way to complete setup without the Global Administrator’s initial involvement.

![](https://cdn.us.document360.io/312e5ae5-e3c1-465d-8e37-f253a7ba8eee/Images/Documentation/sms_connector_setup_collaboration.svg)

### Instructions for the Service Provider

Carry out the following steps in the ConnecttoTeams [Service Portal](https://service.connecttoteams.com).

1. **Configure the enterprise for SMS service.**

Choose the path that applies:

| Scenario | Action |
| --- | --- |
| New enterprise | [Create the enterprise](/v1/docs/manage-enterprises#add-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. |
| Existing enterprise | [Edit the enterprise](/v1/docs/manage-enterprises#edit-enterprise) to add SMS to the Service field. |
2. **Review your app template.** If you wish to apply app template changes to all your enterprises, update your Reseller-level default app template: - Unified Connector App → [Build Unified App Template](/v1/docs/reseller-build-unified-app-template). - Legacy SMS Connector App → [Build SMS App Template](/v1/docs/managing-sms-app-template).
3. **Customize settings specific for the enterprise** This prepares the app for the deployment by the Global Admin (covered in the next section): - Unified Connector App → [Customize and Deploy Unified Connector App for an Enterprise](/v1/docs/customize-and-deploy-unified-connector-app-for-an-enterprise) - Legacy SMS Connector App → [Customize and Deploy SMS App for an Enterprise](/v1/docs/prep-sms-app-instance-for-an-enterprise).
4. **Configure SMS carrier profiles** [Configure SMS Carrier Profiles](/v1/docs/sms-carrier-configuration-as-a-reseller-admin-2) and assign applicable profile(s) to the enterprise.

> [!NOTE]
> Note to the Master Reseller
> 
> Before the Reseller can configure SMS Carriers, you must configure SMS carrier profile (even partially) for the particular service provider and assign profile(s) to the Reseller. See instruction [here](/v1/docs/sms-carrier-configuration-as-a-master-reseller-admin).
5. **Configure SMS Domains (conditional)** If the underlying SMS provider is one of these SMS providers - Netsapiens, RingLogix, United Cloud, Viirtue, configure the [SMS domains for your enterprise](/v1/docs/configure-sms-domains-for-the-enterprise). Otherwise, skip this step.
6. **Upload SMS Capable Numbers** If the Reseller is providing [SMS phone numbers to enterprise](/v1/docs/manage-sms-phone-numbers), upload new phone numbers with SMS capability or edit existing phone numbers to add SMS support. Ensure each number is: - Configured with the correct [SMS Carrier Profile](/v1/docs/sms-carrier-configuration-as-a-reseller-admin-2) with valid API credentials, - Properly assigned to the target enterprise.

### Instructions for the Enterprise Admin

1. **Prepare Teams Admin Center** - Enable the [Messaging Policies for SMS and Chat Apps](/v1/docs/messaging-policies-for-sms-and-chat-apps)

- Ensure you have [custom apps enabled](https://learn.microsoft.com/en-us/microsoftteams/teams-custom-app-policies-and-settings#org-wide-custom-app-setting) for Teams
2. **Accept the invitation and grant permissions (new enterprises)** If you are a new enterprise, your Microsoft organization's Global Administrator should follow the instructions provided in the [invitation email](/v1/docs/getting-started-as-an-enterprise).

Clicking the **COMPLETE** button in that email will prompt the Global Admin to grant the required permissions.

Then, using Global Admin credentials, log in to the appropriate portal:

| Your services | Portal to use |
| --- | --- |
| Messaging only (SMS, Chat) | [Messaging Portal](/v1/docs/enterprise-messaging-portal) |
| Both messaging (SMS, Chat) and calling (PBX, CallApp) | [Enterprise Portal](/v1/docs/enterprise-portal-standard) |

You’ll be asked to [grant permissions](/v1/docs/microsoft-permissions-for-the-enterprise-portal). These must be accepted before the enterprise can access the portal.
3. **Sync your user groups (optionally)** **Limiting service to specific user groups**

If your organization is large and you only need to enable services for a subset of users, you can scope the rollout by selecting the Teams groups that ConnecttoTeams syncs with. See instructions [here](/v1/docs/enterprise-user-groups).

> **Recommendation:** If your organization does not have strict requirements on which users are managed, leave the group selection blank. Limiting by group comes with a performance trade-off due to technical limitations in the Microsoft API integration.

**Things to know**
  - **Sync latency.** Updated group selections may take up to **10 minutes** to reflect in the user list, due to latency when pulling data from Microsoft.
  - **Performance impact.** Narrowing by group is slower than syncing the full directory.
4. **Upload phone numbers (if applicable)** If allowed by service provider, [upload phone numbers with SMS capability](/v1/docs/manage-sms-phone-numbers).
5. **Configure SMS Users and SMS Groups** **Note**: This tasks can be delegated to [non-Global Admins](/v1/docs/enterprise-manage-users-without-global-admin). [Configure SMS users](/v1/docs/configure-sms-users) individually or in [bulk](/v1/docs/configure-sms-users-in-bulk), and any [SMS Groups](/v1/docs/configure-sms-groups) as needed.
6. **Deploy and sync the app** Choose the path that applies:

- **Unified Connector** **App** → [Deploy and Sync the Unified Connector App](/v1/docs/deploy-and-sync-the-unified-connector-app) - **Legacy SMS Connector App** → [Deploy and sync the SMS Connector app](/v1/docs/deploying-the-sms-app-to-a-microsoft-teams-organization)..
7. **Verify SMS Domain (if shown)** ![](https://cdn.us.document360.io/312e5ae5-e3c1-465d-8e37-f253a7ba8eee/Images/Documentation/image-SSQTL7Z6.png) If your navigation menu shows the **SMS Domains** page, verify that your Domains have - **Subscription ID** filled in - **Date Subscribed** filled in - **Expiry Date** set to a future date. This ensures your Teams users will your inbound SMS messages. If any of these are incorrect, reach out to your Service Provider to troubleshoot the issue. **Note**: You won’t see this page if your underlying SMS Provider does not require you to configure this.
8. **Direct your users to the user guide** Share the applicable user guide to your members:

- For Unified Connector App, share [Using the Unified Connector App for SMS](/v1/docs/using-the-unified-connector-app-for-sms).

- For SMS Connector App (Legacy), share [Using the SMS Connector App (Legacy)](/v1/docs/using-the-sms-connector-app-legacy).
9. **Ongoing user management**
  1. You may find the need to [disable SMS for a user](/v1/docs/manage-sms-user-numbers#disable-sms-user) or [unassign phone numbers](/v1/docs/manage-sms-user-numbers#add-or-remove-phone-numbers-from-sms-user) as part of user management.
  2. Sync the connector app **When a sync is required**

When changes are made to SMS assignments, a sync of the deployed connector app may be required so that the changes take effect for the affected Teams users.

The trigger depends on which app your enterprise uses:

| Connector App | Sync required when… |
| --- | --- |
| Legacy SMS Connector App | Any SMS number is assigned or unassigned |
| Unified Connector App | A user is assigned an SMS number for the first time - either as a personal number or as a member of an SMS group |

**Completing the sync** When a sync is needed, a sync task automatically appears in the **Dashboard's Tasks table**. The enterprise admin should:
    1. Open the **Tasks** table in the Dashboard
    2. Locate a **Sync SMS App** task (legacy) or **Sync Unified App** task (Unified)
    3. Complete the task to finalize the changes

## Troubleshooting Issues

There may be issues with the deployment of the app. Review the [troubleshooting guides for app deployment issues here](/v1/docs/troubleshooting-app-deployment-issues).

## Suggested Further Reading

- For the step by step guide for configuring PBX Connector app, [click here](/v1/docs/pbx-connector-installation-step-by-step-guide).
- For the step by step guide for configuring SIP Trunk Connector app, [click here](/v1/docs/sms-connector-installation-step-by-step-guide).