---
schema_version: "1"
id: 5f30fa5818728b740364981893a892e6524f6acd886ff7731ed84812bd393b78
title: Improve Security for Partner Telephony by Migrating to an External Client App
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/262-0-0/rn_voice_byot_eca.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_voice_byot_eca.htm&release=262.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: d866a91788529e1e8f5054ae89fcdbbb8bf7a8a848b9683ecb8dd7bc0f4f9dce
description: External client apps (ECAs) are the next generation of connected apps, designed to improve security and address packaging and distribution issues. While existing connected apps for Salesforce Voice with Partner Telephony integrations continue to work, you aren’t able to create new connected apps without first requesting the ability from Salesforce Support. Because Salesforce plans to eventually replace connected apps with ECAs, consider migrating to an external client app for Salesforce Voice with Partner Telephony.
products:
  - Cross Cloud
release: "262"
---
# Improve Security for Partner Telephony by Migrating to an External Client App

External client apps (ECAs) are the next generation of connected apps, designed to improve security and address packaging and distribution issues. While existing connected apps for Salesforce Voice with Partner Telephony integrations continue to work, you aren’t able to create new connected apps without first requesting the ability from Salesforce Support. Because Salesforce plans to eventually replace connected apps with ECAs, consider migrating to an external client app for Salesforce Voice with Partner Telephony.

**Where:** This change is available in Salesforce orgs with this [telephony model](https://help.salesforce.com/s/articleView?id=service.voice_telephony_models.htm&language=en_US).

- Salesforce Voice with Partner Telephony

[View supported editions for Salesforce Voice](https://help.salesforce.com/s/articleView?id=service.voice_editions.htm&language=en_US).

**Who:** This change impacts partners who create integrations for Salesforce Voice with Partner Telephony. It also affects customers who configure single sign-on (SSO) with Salesforce as the identity provider.

**How:** Inventory your connected apps and consider migrating to ECAs to prepare for the end of support. For new integrations, use an external client app. If you must create a new connected app, contact Salesforce Support to request access to this functionality.

#### See Also

- [_Salesforce Voice with Partner Telephony Developer Guide_: Create Developer Hub and Namespace Orgs](https://developer.salesforce.com/docs/atlas.en-us.voice_pt_developer_guide.meta/voice_pt_developer_guide/voice_pt_hub_namespace_orgs.htm)
- [_Salesforce Voice with Partner Telephony Developer Guide_: Set Up Single Sign-On](https://developer.salesforce.com/docs/atlas.en-us.voice_pt_developer_guide.meta/voice_pt_developer_guide/voice_pt_sso.htm)
- [_Salesforce Help_: Configure Single Sign-On (SSO) with Salesforce as the Identity Provider](https://help.salesforce.com/s/articleView?id=service.voice_pt_setup_config_sso.htm&language=en_US)
- [_Salesforce Knowledge Article_: New connected apps can no longer be created in Spring ‘26](https://help.salesforce.com/s/articleView?id=005228017&type=1&language=en_US)