Integrations · guide

Setting up Webex Calling inside Microsoft Teams

Webex Calling to Microsoft Teams

Verified 2026-10-01 · 72 sources · tier 2 · 1 disputed

For Collaboration administrators who hold the Teams Administrator role and administer Control Hub, rolling Cisco Call out to a commercial Microsoft 365 tenant..

Cisco Call for Microsoft Teams places calls through Cisco Unified Communications Manager, Webex Calling or Webex Calling Dedicated Instance 3. In October 2024 Cisco renamed this integration, previously the Webex Call app, to Cisco Call, and its enterprise application appears as Webex Calling in the Microsoft Entra admin center and Azure portal 41 26.

Before you start

Microsoft requires the Teams Administrator role to use the Teams admin center for app management and recommends it over higher-privilege roles 45.
Users of Cisco Call for Microsoft Teams must have the Call on Webex service enabled in Control Hub and must have both Webex App and Microsoft Teams installed on their devices 32.
For managed Windows installs of Webex App, the MSI switch /qn runs a silent installation and ACCEPT_EULA=TRUE suppresses the end-user licence agreement prompt; see Deploying the Webex App for Webex Calling users 61.
The enterprise application to look for in Microsoft Entra is named Webex Calling, with application ID 263d10a3-85d9-493b-9593-984d0e28a895 26.
For on-premises Unified CM users, Cisco Call requires Unified CM 12.5 SU7 or 14 SU3 at minimum, Unity Connection 12.5 or 14 for voicemail, and the cluster onboarded to Webex Cloud-Connected UC 33.
In Microsoft 365 Government GCC, GCC High and DoD deployments of Teams, all third-party apps are blocked by default 13.
Plan for waiting time: after an app setup policy is edited or assigned it can take a few hours for changes to take effect, and rolling a policy back also takes a few hours 31.

What changes by situation

Pick your answers to see only your path. Nothing is sent anywhere until you make a plan.

Which client do users treat as their phone?

What happens to Teams' own calling?

Should Webex and Teams presence sync both ways?

Where do the users' lines live?

Four questions. One permanent page you can send to your manager.

Step 1 Confirm prerequisites

Webex Calling or Dedicated Instance (cloud)

Do

Check that each pilot user has the Call on Webex service enabled in Control Hub and has both Webex App and Microsoft Teams installed 32.
If users run on VDI, check that Cisco Call and Microsoft Teams both run in the same virtual machine 58.

Verify

Suggested check: open a pilot user's record and confirm the calling service is enabled, then confirm the desktop calling client is installed and signed in on that user's machine.

On-premises Unified CM through Webex Cloud-Connected UC

Do

Check that each pilot user has the Call on Webex service enabled in Control Hub and has both Webex App and Microsoft Teams installed 32.
Check that Unified CM is at 12.5 SU7 or 14 SU3 at minimum, that Unity Connection is 12.5 or 14 for voicemail, and that the cluster is onboarded to Webex Cloud-Connected UC 33.
Cloud-Connected UC is set up in Control Hub under Services > Connected UC 62.
Check that each user's Unified CM Mail ID matches their Control Hub primary email; Cisco recommends syncing users from on-premises Active Directory or a cloud directory such as Azure into Control Hub Common Identity 53.
If users run on VDI, check that Cisco Call and Microsoft Teams both run in the same virtual machine 58.

Verify

Suggested check: confirm the cluster is listed in the inventory of connected clusters.
Suggested check: compare the mail address and primary email for a sample of pilot users and confirm they match.

Step 2 Align identities and the Entra enterprise app

Do

Make each user's Teams sign-in email or UPN match their Control Hub primary email 57.
In the Microsoft Entra admin center, find the enterprise application named Webex Calling, application ID 263d10a3-85d9-493b-9593-984d0e28a895 26.
To avoid sign-in failures, Cisco says no Attributes and Claims should be configured under Single sign-on settings for the Webex Calling enterprise application 27.
Sign-in fails for users whose IdP SAML attributes do not resolve to a valid Webex user 27.

Verify

Suggested check: spot-check a sample of pilot users and confirm their sign-in name and primary email match.
Where the addresses differ, the user can choose Use a different account during Cisco Call sign-in 57.

Rollback

Suggested rollback: revert any directory attribute changes you made in your identity source.

Step 3 Allow Cisco Call and set who can use it

Do

In the Teams admin center, go to Teams apps > Manage apps, search for Cisco Call, select it and choose Allow 46.
On the app's Users and groups tab, choose Edit availability and select Everyone, Specific users or groups, or No one; Specific users or groups lets you limit the app to a pilot group 47.
Sources disagree on the older procedure: Cisco TAC technote 220504 instructs admins to allow the app under Permission policies > Third-party apps with Allow specific apps and block all others, a step that relies on app permission policies Microsoft now describes as deprecated 51.
Microsoft states that app permission policies are deprecated and that user access to Teams apps is defined through app centric management assignment, to which tenants have been automatically migrated since April 2025 23.
Optionally, Teams admins can customize 9 Cisco Call app properties, including short name, descriptions and icon, as a default org-wide customization or as up to 10 additional customizations each assigned through one app setup policy 6.

Verify

Suggested check: confirm the app shows as allowed and that its availability lists only your pilot group.

Rollback

Set availability to No one on the app's Users and groups tab 47.
Revert any app customization with Reset to default 6.

Step 4 Grant admin consent

Presence sync on

Do

In Teams apps > Manage apps, open Cisco Call, select the Permissions tab, choose Grant admin consent, confirm the presence read and read-write permissions are listed, and select Accept 48 46.
On the Webex Calling enterprise application properties, set Assignment required to No, which Cisco advises to avoid presence sync status issues 2.
In July 2025 Cisco added a delegated Presence.ReadWrite permission option for Cisco Call alongside the existing broader presence permission 7.
Microsoft Graph setPresence requires Presence.ReadWrite as its least-privileged delegated permission and Presence.ReadWrite.All as its application permission 14.

Verify

Suggested check: reopen the permissions tab and confirm consent shows as granted, including the presence permissions.
Suggested check: reopen the enterprise application properties and confirm Assignment required reads No.

Rollback

Suggested rollback: revoke the permissions granted in this step from the enterprise application and set Assignment required back to its earlier value.
To narrow presence scope instead of removing it, grant Presence.ReadWrite first and wait at least 2 hours before revoking Presence.ReadWrite.All 36.

Presence sync off

Do

Cisco documents the Grant admin consent procedure (Cisco Call in Manage apps, Permissions tab, Grant admin consent, confirm the presence read and read-write permissions, Accept) as the way to accept presence sync permissions 48.
Cisco advises setting Assignment required to No on the Webex Calling enterprise application specifically to avoid presence sync status issues, so this branch leaves that property as it is 2.

Verify

Suggested check: reopen the permissions tab and confirm it reflects the consent decision you made.

Rollback

Suggested rollback: if you granted consent, revoke those permissions from the enterprise application.

Step 5 Install and pin Cisco Call with an app setup policy

Turn off Teams calling

Do

Create a Teams app setup policy that adds Cisco Call under Installed apps and Pinned apps and places it at the top of both the App bar list and the Messaging extensions list 42.
In the same policy, remove the built-in Calling app from the App bar to unpin Teams calling 43.
Microsoft states that organizations using app centric management install apps for users from the Manage apps page, while other organizations preinstall apps through app setup policies; pinning remains in setup policies 1.
Keep at least two apps pinned, because with fewer the Teams mobile client keeps its existing configuration 22.
Assign the policy to the pilot users; only one app setup policy is effective for a user at a time, and a custom policy assigned to a user overrides the Global (Org-wide default) policy 28.

Verify

After an app setup policy is edited or assigned it can take a few hours for changes to take effect 31.
Suggested check: confirm the pilot account's assigned policies list the new setup policy.
Suggested check: confirm the new app is pinned at the top of the pilot account's app bar and the built-in calling app is gone.

Rollback

Suggested rollback: reassign the pilot users to the org-wide default policy, or edit the custom policy.
Rolling a setup policy back also takes a few hours 31.

Keep Teams calling next to Cisco Call

Do

Create a Teams app setup policy that adds Cisco Call under Installed apps and Pinned apps and places it at the top of both the App bar list and the Messaging extensions list 42.
Skip the part of Cisco's procedure that removes the built-in Calling app from the App bar, so Teams calling stays pinned 43.
Microsoft states that organizations using app centric management install apps for users from the Manage apps page, while other organizations preinstall apps through app setup policies; pinning remains in setup policies 1.
Keep at least two apps pinned, because with fewer the Teams mobile client keeps its existing configuration 22.
Assign the policy to the pilot users; only one app setup policy is effective for a user at a time, and a custom policy assigned to a user overrides the Global (Org-wide default) policy 28.

Verify

After an app setup policy is edited or assigned it can take a few hours for changes to take effect 31.
Suggested check: confirm both the new app and the built-in calling app appear in the pilot account's app bar.

Rollback

Suggested rollback: reassign the pilot users to the org-wide default policy, or edit the custom policy.
Rolling a setup policy back also takes a few hours 31.

Step 6 Set the Teams calling policy

Turn off Teams calling

Do

In the Teams admin center, go to Voice > Calling policies and set Make private calls to Off, either in the Default policy or in a new policy 38.
Microsoft defines Make private calls as controlling all calling capabilities in Teams, and turning it off turns off all calling functionality in Teams 39.
We infer that users under that policy lose Teams-to-Teams one-to-one calling as well as PSTN calling and must place every call through Cisco Call or Webex App 19.
For scripted work, Teams calling policies can be created, modified, read, assigned and removed with New-CsTeamsCallingPolicy, Set-CsTeamsCallingPolicy, Get-CsTeamsCallingPolicy, Grant-CsTeamsCallingPolicy and Remove-CsTeamsCallingPolicy, and assigned to users directly or through groups; see Teams voice administration with PowerShell 5.
Group policy assignments propagate only to direct members of the group, not to members of nested groups 63.
A policy assigned directly to a user takes precedence over any group-assigned policy of the same type 64.

Verify

Get-CsUserPolicyAssignment with -PolicyType, expanding PolicySource, shows whether a user's policy is Direct or inherited from a Group 65.
Suggested check: confirm the pilot account's assigned calling policy has private calls turned off and that the account can no longer start a call from the built-in calling app.

Rollback

Suggested rollback: turn private calls back on in the policy you changed.
Grant-CsTeamsCallingPolicy can assign the previous calling policy back to the users 5.

Keep Teams calling next to Cisco Call

Do

Cisco lists disabling built-in Teams calling as optional, so leave Make private calls unchanged in the calling policies that apply to these users 38.

Verify

Suggested check: confirm the pilot account can still start a call from the built-in calling app.

Step 7 Set Webex App behaviour in Control Hub

Cisco Call in Teams is the phone (Webex App window hidden)

Do

In Control Hub, go to Services > Calling > Settings > Webex App tab and, in the Microsoft Teams integration section, turn on Hide Webex windows 16.
For a pilot, set Hide Webex windows in a Webex App calling template assigned to user groups, or per user under Management > Users > Calling > Microsoft Teams integration; user settings override group template settings, which override organization settings 17.
Under In-call feature access, turn on Display calling dock for multi-line users only or for all users 4.
Organization in-call feature defaults apply to new users, and a user-level setting overrides them and does not automatically return to the organization default 66.
Then turn on Optimize Webex app for Microsoft Teams experience in the Microsoft Teams integration section; the toggle is disabled unless Display calling dock is enabled 30 29.
Cisco describes Optimize as giving simplified call settings, muting Cisco calls during Teams calls and meetings, and redirecting users to Cisco Call instead of Webex App 30.

Verify

Webex App must be restarted after configuration changes, and with Webex windows hidden it keeps running with its window closed and is reachable from the Windows system tray or macOS menu bar 15.
On Windows, Ctrl+Shift+X opens the calling dock, which Cisco documents as currently Windows-only 10.

Rollback

Suggested rollback: turn the toggles off at the same level where you turned them on, then have pilot users restart the desktop client.
A user-level in-call setting does not automatically return to the organization default 66.

Webex App stays the phone (Cisco Call for click-to-call and presence)

Do

Leave Hide Webex windows off at the organization level and check that no group template or per-user setting turns it on, because user settings override group template settings, which override organization settings 17.
Leave Optimize Webex app for Microsoft Teams experience off, because Cisco states it redirects users to Cisco Call instead of Webex App 30.

Verify

Suggested check: restart the desktop client for a pilot account and confirm its window opens and stays visible.

Step 8 Enable voicemail and centralized call history

Webex Calling or Dedicated Instance (cloud)

Do

For Webex Calling, Dedicated Instance and UCM Cloud customers, voicemail, centralized call history and presence sync are enabled by default for Cisco Call, so there is nothing to switch on here 60.

Verify

Suggested check: confirm voicemail and call history during the calling test in Step 11.

On-premises Unified CM through Webex Cloud-Connected UC

Do

In Control Hub, go to Services > Connected UC > Inventory, open the cluster Details, choose Service Management, turn on Voicemail and Centralized Call History, and select Submit 54.
For centralized call history to show the user name on Unified CM, associate each line number to its user ID 52.
Enabling on-premises voicemail for Cisco Call creates a template named msteamsadmintemplate and an admin user named msteamsvoicemailadmin, whose fields and settings must not be modified 55.

Verify

Voicemail enabled through Service Management takes up to 12 hours to activate 56.
Suggested check: confirm the toggles show on after submitting, and that the voicemail template and admin user created by this step exist, without editing either.

Rollback

Voicemail and centralized call history are toggled per cluster in Service Management, where you can turn them off and select Submit 54.

Step 9 Configure presence sync

Webex Calling or Dedicated Instance (cloud) + Presence sync on

Do

In Control Hub, go to Services > Calling > Settings > Webex App tab, turn on Presence sync, and turn on the toggle in the Do Not Disturb (DND) Status Sync section 37.
Tell users that with presence sync, a user who sets Do not disturb receives no notification of incoming calls and messages in Webex App, on a Webex device or in Microsoft Teams 9.
To keep presence sync working, each user must use the Cisco Call integration at least once every 90 days 34.
We infer that an organization keeping Webex App as the everyday calling client but wanting presence sync still has to deploy Cisco Call in Teams and get each user to open it at least once every 90 days 18.

Verify

Suggested check: confirm both toggles show on; functional checks follow in Step 12.

Rollback

Turn off the Presence sync toggle and the DND Status Sync toggle on the Webex App tab 37.

On-premises Unified CM through Webex Cloud-Connected UC + Presence sync on

Do

In Control Hub, go to Services > Calling > Settings > Webex App tab, turn on Presence sync, and turn on the toggle in the Do Not Disturb (DND) Status Sync section 37.
In Services > Connected UC > Inventory > cluster Details > Service Management, turn on Presence status sync and select Submit 54.
Tell users that with presence sync, a user who sets Do not disturb receives no notification of incoming calls and messages in Webex App, on a Webex device or in Microsoft Teams 9.
To keep presence sync working, each user must use the Cisco Call integration at least once every 90 days 34.
We infer that an organization keeping Webex App as the everyday calling client but wanting presence sync still has to deploy Cisco Call in Teams and get each user to open it at least once every 90 days 18.

Verify

Suggested check: confirm all three toggles show on; functional checks follow in Step 12.

Rollback

Turn off the Presence sync toggle and the DND Status Sync toggle on the Webex App tab 37.
Turn off Presence status sync in the cluster's Service Management page and select Submit 54.

Webex Calling or Dedicated Instance (cloud) + Presence sync off

Do

Presence sync is enabled by default for Webex Calling, Dedicated Instance and UCM Cloud customers, so check the Presence sync and DND Status Sync toggles on the Webex App tab and make sure both are off 60 37.

Verify

Suggested check: confirm both toggles show off.

On-premises Unified CM through Webex Cloud-Connected UC + Presence sync off

Do

Make sure the Presence sync toggle and the DND Status Sync toggle on the Webex App tab are off 37.
Leave Presence status sync off in the cluster's Service Management page 54.

Verify

Suggested check: confirm all three toggles show off.

Step 10 Pilot user first sign-in

Do

The pilot user signs in to Webex App first, as a one-time activity, and can then open Cisco Call in Teams 44.
Cisco Call sign-in is a dual sign-in through Microsoft Teams SSO followed by Webex OAuth or SSO 11.
If the user's Teams and Webex addresses differ, they choose Use a different account during Cisco Call sign-in 57.

Verify

Desktop users see their work number under My number at the top left of Cisco Call, and mobile users at the bottom of the dialpad 25.
Cisco TAC notes that when the assigned number does not appear under My number, the email address of the Teams and Webex accounts must be made to match 50.
Cisco Call shows an alert banner when phone service is disconnected, for example when the user signs in on another desktop with the same credentials or Webex App is closed or signed out 8.

Rollback

Suggested rollback: the pilot user signs out of the calling app.
To remove access entirely, set availability to No one on the app's Users and groups tab 47.

Step 11 Test calling, call history and voicemail

Do

From Teams, place Cisco calls from the Cisco Call dialpad by name, number or video address, and from the messaging extension in a one-on-one chat 20.

Verify

Suggested check: call an external number and a colleague, leave a voicemail for the pilot account, and let one test call go unanswered.
Cisco TAC notes that the user needs both Teams and Webex App open, and that if nothing happens after starting a call the admin should verify the user is authenticated in Webex App 49.
Health Checker opens on Windows from the profile picture > Help > Health Checker and on Mac from Help > Health Checker; see Troubleshooting calling in the Webex App 67.
Cisco Call shows up to 200 made, received and missed calls from the last 30 days, with missed calls in red 40.
Voicemail is available only for the user's primary line, and a Message Waiting Indicator badge counter appears next to the Voicemail tab for new messages 59.
For on-premises customers, voicemail enabled through Service Management takes up to 12 hours to activate, so wait before testing it 56.
Where E911 is set up, Cisco Call prompts users to update their emergency location when first set up and when they change location, showing an alert beside the More options menu 12.
From October 2026 the Recents, Missed and Voicemail tabs are available in Cisco Call on Teams mobile without opening Webex App 21.

Step 12 Test presence

Presence sync on

Do

Presence sync maps Webex On a call to Teams In a call both ways, Webex In a meeting to Teams In a call one way, Presenting to Presenting both ways, and Do not disturb to Do not disturb both ways 35.

Verify

Suggested check: during a test call, while presenting, and after setting do not disturb on each side in turn, confirm each status appears on the other side as the mapping describes.
If statuses do not sync, recheck that admin consent was accepted with the presence read and read-write permissions listed 48.
Cisco advises setting Assignment required to No on the Webex Calling enterprise application properties to avoid presence sync status issues 2.

Presence sync off

Do

Bidirectional presence sync is turned on only with the Presence sync toggle plus the DND Status Sync toggle, which this branch leaves off 37.

Verify

Suggested check: place a test call and confirm the chat client's presence status does not change because of it.

Step 13 Test the meeting interaction

Cisco Call in Teams is the phone (Webex App window hidden)

Do

Users can mute notifications for incoming Cisco calls while in a Teams meeting or call, optionally auto-declining them, once the admin enables Optimize Webex App for Microsoft Teams experience 24.

Verify

Suggested check: put the pilot account in a meeting with muting turned on, call its line, and confirm the call does not ring through; repeat with auto-decline on and confirm the call is declined.

Rollback

Suggested rollback: the pilot user turns the muting option off.

Webex App stays the phone (Cisco Call for click-to-call and presence)

Do

Users can mute notifications for incoming Cisco calls during a Teams meeting or call only once the admin enables Optimize Webex App for Microsoft Teams experience, which this branch leaves off 24.

Verify

Suggested check: call the pilot account during a meeting, note how the call arrives, and brief users on what they will see.

Step 14 Roll out and keep it working

Presence sync on

Do

Widen Cisco Call availability on the Users and groups tab to Everyone or to further groups 47.
Widen the app setup policy assignment, keeping in mind that only one app setup policy is effective for a user at a time 28.
New-CsBatchPolicyAssignmentOperation assigns or unassigns a policy for up to 5,000 users per batch as an asynchronous operation and returns an operation ID 68.
Its supported policy types include TeamsCallingPolicy 69.
It identifies users by object ID or SIP address, and a user given by a UPN that differs from their SIP address fails policy assignment 70.
Group policy assignment is recommended for groups of up to 50,000 users, and propagation to members runs as a background operation whose duration depends on group size 71.
Tell users that presence sync keeps working only if they use the Cisco Call integration at least once every 90 days 34.
To move from Presence.ReadWrite.All to Presence.ReadWrite, grant Presence.ReadWrite first and wait at least 2 hours before revoking Presence.ReadWrite.All, or have users sign out of Cisco Call and back in to synchronize immediately 36.

Verify

The status of a batch policy assignment is read with Get-CsBatchPolicyAssignmentOperation -OperationId, and per-user errors are in its UserState property 72.
Suggested check: spot-check presence for users added in later waves.

Rollback

Set availability back to Specific users or groups, naming only the pilot group 47.
Rolling a setup policy back takes a few hours 31.

Presence sync off

Do

Widen Cisco Call availability on the Users and groups tab to Everyone or to further groups 47.
Widen the app setup policy assignment, keeping in mind that only one app setup policy is effective for a user at a time 28.
New-CsBatchPolicyAssignmentOperation assigns or unassigns a policy for up to 5,000 users per batch as an asynchronous operation and returns an operation ID 68.
Its supported policy types include TeamsCallingPolicy 69.
It identifies users by object ID or SIP address, and a user given by a UPN that differs from their SIP address fails policy assignment 70.
Group policy assignment is recommended for groups of up to 50,000 users, and propagation to members runs as a background operation whose duration depends on group size 71.

Verify

The status of a batch policy assignment is read with Get-CsBatchPolicyAssignmentOperation -OperationId, and per-user errors are in its UserState property 72.
Suggested check: confirm users added in later waves see the app pinned and their work number displayed.

Rollback

Set availability back to Specific users or groups, naming only the pilot group 47.
Rolling a setup policy back takes a few hours 31.

Applicability

Applies to: Microsoft Teams, Cisco Call for Microsoft Teams, Cisco Webex Control Hub, Microsoft Graph, MicrosoftTeams PowerShell module, Cisco Webex App, Cisco Control Hub, and Cisco Webex Cloud-Connected UC. Deployments: cloud, on-premises, hybrid, multi-tenant, and dedicated instance. Sources checked 2026-10-01. In October 2024 Cisco renamed the integration to Cisco Call 41. In July 2025 Cisco added a delegated Presence.ReadWrite permission option for Cisco Call 7. The on-premises path requires Unified CM 12.5 SU7 or 14 SU3 at minimum and Unity Connection 12.5 or 14 for voicemail 33. Microsoft 365 Government GCC, GCC High and DoD tenants block all third-party apps by default 13. The Cisco TAC troubleshooting notes cited here come from a technote that refers to the app by its earlier name, Webex Call Integration 49.

What remains uncertain

How to deploy this integration in government tenants is not covered by the sources below.
Whether admin consent on the Permissions tab is needed when presence sync stays off is not covered by the sources below.
Whether turning off Make private calls affects calling licences or meeting dial-out is not covered by the sources below.
Which process carries the call media during a call is not covered by the sources below.
How to remove the msteamsadmintemplate template and the msteamsvoicemailadmin user after on-premises voicemail is turned off is not covered by the sources below.
Behaviour of Cisco Call in the Teams web client is not covered by the sources below.
Other voicemail platforms, AI-generated call summaries and meeting video interoperability with Teams meetings are not covered by the sources below.

Sources

1
Microsoft states that organizations using app centric management install apps for users from the Manage apps page, while other organizations preinstall apps through app setup policies; pinning remains in setup policies.
Manage agents and app setup policies in Microsoft Teams · Install agents and apps for your users on Teams; Pin apps · Checked 2026-10-01
2
Cisco advises setting Assignment required to No on the Webex Calling enterprise application properties to avoid presence sync status issues.
Configure Cisco Call for Microsoft Teams · Required API permissions / note on Enterprise Applications properties · Checked 2026-10-01
3
Cisco Call for Microsoft Teams places calls through Cisco Unified Communications Manager, Webex Calling or Webex Calling Dedicated Instance.
Cisco Call for Microsoft Teams · Overview · Checked 2026-10-01
4
The Display calling dock toggle is under Services > Calling > Settings > Webex App tab > In-call feature access and can apply to multi-line users only or to all users.
Configure Cisco Call for Microsoft Teams · Enable calling dock window · Checked 2026-10-01
5
Teams calling policies can be created, modified, read, assigned and removed with New-CsTeamsCallingPolicy, Set-CsTeamsCallingPolicy, Get-CsTeamsCallingPolicy, Grant-CsTeamsCallingPolicy and Remove-CsTeamsCallingPolicy, and can be assigned to users directly or through groups.
Configure calling policies in Microsoft Teams · Assign a custom calling policy to users; Calling policy PowerShell cmdlets · Checked 2026-10-01
6
Teams admins can customize nine Cisco Call app properties including short name, descriptions and icon as a default org-wide customization or up to 10 additional customizations each assigned through one app setup policy, and can revert with Reset to default.
Customize Cisco Call app for Microsoft Teams users · Customization options; Customization modes; Key details · Checked 2026-10-01
7
In July 2025 Cisco added a delegated Presence.ReadWrite permission option for Cisco Call alongside the existing broader presence permission.
What's New in Cisco Call for Microsoft Teams · 2025 / July entry · Checked 2026-10-01
8
Cisco Call shows an alert banner when phone service is disconnected, for example when the user signs in on another desktop with the same credentials or Webex App is closed or signed out.
Cisco Call for Microsoft Teams · Phone service disconnection · Checked 2026-10-01
9
With presence sync, a user who sets Do not disturb receives no notification of incoming calls and messages in Webex App, on a Webex device or in Microsoft Teams.
Configure Cisco Call for Microsoft Teams · Presence sync details / Do not disturb · Checked 2026-10-01
10
The Cisco Call multi-call window (calling dock), which offers mute, hold, conference, park, barge, transfer and record, is currently Windows-only and opens with Ctrl+Shift+X.
Cisco Call for Microsoft Teams · Manage all your phone calls in one place · Checked 2026-10-01
11
Cisco Call sign-in is a dual sign-in through Microsoft Teams SSO followed by Webex OAuth or SSO.
Configure Cisco Call for Microsoft Teams · User experience / sign-in flow · Checked 2026-10-01
12
Cisco Call prompts users to update their emergency location when first set up with E911 and when they change location, showing an alert beside the More options menu.
Cisco Call for Microsoft Teams · E911 emergency services · Checked 2026-10-01
13
In Microsoft 365 Government GCC, GCC High and DoD deployments of Teams all third-party apps are blocked by default.
Manage your apps in the Microsoft Teams admin center · Manage org-wide app settings for Microsoft 365 Government · Checked 2026-10-01
14
Microsoft Graph setPresence requires Presence.ReadWrite as its least-privileged delegated permission and Presence.ReadWrite.All as its application permission.
presence: setPresence - Microsoft Graph v1.0 · Permissions table · Checked 2026-10-01
15
With Webex windows hidden, Webex App keeps running with its window closed by default and is reachable from the Windows system tray or macOS menu bar, and Webex App must be restarted after configuration changes.
Configure Cisco Call for Microsoft Teams · User experience / Webex App access · Checked 2026-10-01
16
The org-level Hide Webex windows toggle is under Control Hub Services > Calling > Settings > Webex App tab in the Microsoft Teams integration section.
Configure Cisco Call for Microsoft Teams · Hide Webex App window / organization level · Checked 2026-10-01
17
Hide Webex windows can also be set in a Webex App calling template assigned to user groups or per user under Management > Users > Calling > Microsoft Teams integration, and user settings override group template settings, which override organization settings.
Configure Cisco Call for Microsoft Teams · Hide Webex App window / user-group level, user level and precedence · Checked 2026-10-01
18
An organization that keeps Webex App as the everyday calling client but wants presence sync still has to deploy Cisco Call in Teams and get each user to open it at least once every 90 days.inferred
Configure Cisco Call for Microsoft Teams · Presence sync details (90-day rule) combined with Accept presence sync permissions · Checked 2026-10-01
19
Because Make private calls Off removes all Teams calling, users under that policy lose Teams-to-Teams one-to-one calling as well as PSTN calling and must place every call through Cisco Call or Webex App.inferred
Configure calling policies in Microsoft Teams · Calling policy settings / Make private calls · Checked 2026-10-01
20
From Teams, users place Cisco calls from the Cisco Call dialpad by name, number or video address, from the messaging extension in one-on-one and group chats, or to channel members.
Cisco Call for Microsoft Teams · Make a call · Checked 2026-10-01
21
From October 2026 the Recents, Missed and Voicemail tabs are available in Cisco Call on Teams mobile without opening Webex App.
What's New in Cisco Call for Microsoft Teams · 2026 / October entry · Checked 2026-10-01
22
At least two apps must be pinned in an app setup policy for the Teams mobile client to reflect the policy; with fewer the mobile client keeps its existing configuration.
Manage agents and app setup policies in Microsoft Teams · Considerations and limitations · Checked 2026-10-01
23
Microsoft states that app permission policies are deprecated and that user access to Teams apps is defined through app centric management assignment, to which tenants have been automatically migrated since April 2025.
Manage your apps in the Microsoft Teams admin center · Introduction and Allow or block section · Checked 2026-10-01
24
Users can mute notifications for incoming Cisco calls while in a Teams meeting or call, optionally auto-declining them, once the admin enables Optimize Webex App for Microsoft Teams experience.
Cisco Call for Microsoft Teams · Mute Cisco calls when on Teams meeting or call · Checked 2026-10-01
25
Desktop users see their work number under My number at the top left of Cisco Call (mobile users at the bottom of the dialpad) and can open call settings without opening Webex App.
Cisco Call for Microsoft Teams · Find your work phone number and access call settings · Checked 2026-10-01
26
The Webex calling integration for Microsoft Teams is named Cisco Call in Teams, but its enterprise application appears as Webex Calling in the Microsoft Entra admin center and Azure portal with application ID 263d10a3-85d9-493b-9593-984d0e28a895.
Configure Cisco Call for Microsoft Teams · Overview / note on application name in Entra admin center · Checked 2026-10-01
27
To avoid sign-in failures Cisco says no Attributes and Claims should be configured under Single sign-on settings for the Webex Calling enterprise application, and sign-in fails for users whose IdP SAML attributes do not resolve to a valid Webex user.
Configure Cisco Call for Microsoft Teams · Known issues and limitations / sign-in · Checked 2026-10-01
28
Only one app setup policy is effective for a user at a time, and a custom policy assigned to a user overrides the Global (Org-wide default) policy.
Manage agents and app setup policies in Microsoft Teams · Manage agent or app setup policies; Assign a custom policy · Checked 2026-10-01
29
The Optimize Webex app for Microsoft Teams experience toggle is disabled unless Display calling dock is enabled under In-call feature access.
Configure Cisco Call for Microsoft Teams · Optimize for Microsoft Teams experience / note · Checked 2026-10-01
30
The Optimize Webex app for Microsoft Teams experience toggle (Webex App tab, Microsoft Teams integration section) gives simplified call settings, mutes Cisco calls during Teams calls and meetings, and redirects users to Cisco Call instead of Webex App.
Configure Cisco Call for Microsoft Teams · Optimize for Microsoft Teams experience · Checked 2026-10-01
31
After an app setup policy is edited or assigned it can take a few hours for changes to take effect, and rolling a policy back also takes a few hours.
Manage agents and app setup policies in Microsoft Teams · Considerations and limitations · Checked 2026-10-01
32
Users of Cisco Call for Microsoft Teams must have the Call on Webex service enabled in Control Hub and must have both Webex App and Microsoft Teams installed on their devices.
Configure Cisco Call for Microsoft Teams · Prerequisites · Checked 2026-10-01
33
For on-premises Unified CM users Cisco Call requires Unified CM 12.5 SU7 or 14 SU3 at minimum, Unity Connection 12.5 or 14 for voicemail, and the cluster onboarded to Webex Cloud-Connected UC.
Configure Cisco Call for Microsoft Teams · Prerequisites / Unified CM and Unity Connection requirements · Checked 2026-10-01
34
To keep presence sync working, each user must use the Cisco Call integration at least once every 90 days.
Configure Cisco Call for Microsoft Teams · Presence sync details · Checked 2026-10-01
35
Presence sync maps Webex On a call to Teams In a call both ways, Webex In a meeting to Teams In a call one way, Presenting to Presenting both ways, and Do not disturb to Do not disturb both ways.
Configure Cisco Call for Microsoft Teams · Bidirectional presence sync / status mapping · Checked 2026-10-01
36
When moving Cisco Call from Presence.ReadWrite.All to Presence.ReadWrite, admins grant Presence.ReadWrite first and wait at least 2 hours before revoking Presence.ReadWrite.All, or users sign out of Cisco Call and back in to synchronize immediately.
Configure Cisco Call for Microsoft Teams · Presence sync / permission migration · Checked 2026-10-01
37
Bidirectional presence sync is turned on in Control Hub at Services > Calling > Settings > Webex App tab with the Presence sync toggle, plus the toggle in the Do Not Disturb (DND) Status Sync section.
Configure Cisco Call for Microsoft Teams · Bidirectional presence sync · Checked 2026-10-01
38
Cisco lists disabling built-in Teams calling as optional, done in Teams admin center under Voice > Calling policies by setting Make private calls to Off in the Default policy or a new policy.
Configure Cisco Call for Microsoft Teams · Optional: disable built-in Teams calling · Checked 2026-10-01
39
Microsoft defines the Make private calls calling policy setting as controlling all calling capabilities in Teams; turning it off turns off all calling functionality in Teams.
Configure calling policies in Microsoft Teams · Calling policy settings / Make private calls · Checked 2026-10-01
40
Cisco Call shows up to 200 made, received and missed calls from the last 30 days, with missed calls in red.
Cisco Call for Microsoft Teams · View recent calls · Checked 2026-10-01
41
In October 2024 Cisco renamed the Webex Calling integration for Microsoft Teams (previously the Webex Call app) to Cisco Call.
What's New in Cisco Call for Microsoft Teams · 2024 / October entry · Checked 2026-10-01
42
Cisco's procedure creates a Teams app setup policy that adds Cisco Call under Installed apps and Pinned apps and places it at the top of both the App bar list and the Messaging extensions list.
Configure Cisco Call for Microsoft Teams · Microsoft Teams admin center / create setup policy · Checked 2026-10-01
43
Cisco's setup policy procedure removes the built-in Calling app from the App bar to unpin Teams calling.
Configure Cisco Call for Microsoft Teams · Microsoft Teams admin center / create setup policy · Checked 2026-10-01
44
Users sign in to Webex App first as a one-time activity and can then open Cisco Call in Teams with the same account or authenticate with different credentials.
Cisco Call for Microsoft Teams · Sign in · Checked 2026-10-01
45
Microsoft requires the Teams Administrator role to use the Teams admin center for app management and recommends it over higher-privilege roles.
Manage your apps in the Microsoft Teams admin center · Introduction paragraph on admin roles · Checked 2026-10-01
46
To allow Cisco Call org-wide, a Teams admin goes to Teams apps > Manage apps in the Teams admin center, searches for Cisco Call, selects it and chooses Allow.
Configure Cisco Call for Microsoft Teams · Microsoft Teams admin center / allow the application · Checked 2026-10-01
47
Who can install Cisco Call is set on the app's Users and groups tab with Edit availability, choosing Everyone, Specific users or groups, or No one.
Configure Cisco Call for Microsoft Teams · Microsoft Teams admin center / manage installation permissions · Checked 2026-10-01
48
To accept presence sync permissions an admin opens Cisco Call in Manage apps, selects the Permissions tab, chooses Grant admin consent, confirms the presence read and read-write permissions are listed, and selects Accept.
Configure Cisco Call for Microsoft Teams · Accept presence sync permissions · Checked 2026-10-01
49
Cisco TAC notes that the user needs both Teams and Webex App open, and that if nothing happens after starting a call the admin should verify the user is authenticated in Webex App.
Deploy and Use of Webex Call Integration with Microsoft Teams · Troubleshoot · Checked 2026-10-01
50
Cisco TAC notes that when the assigned number does not appear under My number, the email address of the Teams and Webex accounts must be made to match.
Deploy and Use of Webex Call Integration with Microsoft Teams · Troubleshoot · Checked 2026-10-01
51
Cisco TAC technote 220504 instructs admins to allow the app under Permission policies > Third-party apps with Allow specific apps and block all others, a step that relies on app permission policies Microsoft now describes as deprecated.disputed
Deploy and Use of Webex Call Integration with Microsoft Teams · Configure / Teams admin center steps · Checked 2026-10-01
52
For centralized call history to show the user name on Unified CM, the line number must be associated to the user ID.
Configure Cisco Call for Microsoft Teams · Call history and voicemail / centralized call history · Checked 2026-10-01
53
For on-premises Unified CM deployments the Unified CM Mail ID must match the user's Control Hub primary email, and Cisco recommends syncing users from on-premises Active Directory or a cloud directory such as Azure into Control Hub Common Identity.
Configure Cisco Call for Microsoft Teams · Prerequisites · Checked 2026-10-01
54
For on-premises Unified CM, voicemail, centralized call history and presence status sync are toggled per cluster in Control Hub at Services > Connected UC > Inventory > cluster Details > Service Management, then Submit.
Configure Cisco Call for Microsoft Teams · For on-premises Unified CM / Service Management · Checked 2026-10-01
55
Enabling on-premises voicemail for Cisco Call creates a template named msteamsadmintemplate and an admin user named msteamsvoicemailadmin, whose fields and settings must not be modified.
Configure Cisco Call for Microsoft Teams · Call history and voicemail / on-premises voicemail · Checked 2026-10-01
56
Voicemail enabled for on-premises customers through Service Management takes up to 12 hours to activate.
Configure Cisco Call for Microsoft Teams · For on-premises Unified CM / note · Checked 2026-10-01
57
The user's Teams sign-in email or UPN should match the user's Control Hub primary email; where they differ the user can choose Use a different account during Cisco Call sign-in.
Configure Cisco Call for Microsoft Teams · Prerequisites / identity requirements · Checked 2026-10-01
58
When Cisco Call for Microsoft Teams is used in a VDI environment, Cisco Call and Microsoft Teams must both run in the same virtual machine.
Configure Cisco Call for Microsoft Teams · Prerequisites / VDI note · Checked 2026-10-01
59
In Cisco Call, voicemail is available only for the user's primary line, and a Message Waiting Indicator badge counter appears next to the Voicemail tab for new messages.
Cisco Call for Microsoft Teams · Listen to voicemails · Checked 2026-10-01
60
For Webex Calling, Dedicated Instance and UCM Cloud customers, voicemail, centralized call history and presence sync are enabled by default for Cisco Call.
Configure Cisco Call for Microsoft Teams · Enable voicemail, centralized call history and presence sync · Checked 2026-10-01
61
The MSI switch /qn runs a silent installation and ACCEPT_EULA=TRUE suppresses the end-user licence agreement prompt.
Webex App | Installation and automatic upgrade · Command line parameters; /qn and ACCEPT_EULA · Checked 2026-09-24
62
Cloud-Connected UC is set up in Control Hub under Services > Connected UC, where the Get Started button stays enabled until an agent file and a cluster group exist.
Set up Webex Cloud-Connected UC for on-premises devices · Set up Webex Cloud-Connected UC for on-premises devices, Get started · Checked 2026-09-25
63
Group policy assignments propagate only to direct members of the group, not to members of nested groups.
Assign policies to users and groups · Assign a policy to a group, sixth paragraph · Checked 2026-09-25
64
A policy assigned directly to a user takes precedence over any group-assigned policy of the same type; among groups, the assignment with the highest ranking (lowest number, 1 is highest) wins; with neither, the Global (Org-wide default) policy applies.
Assign policies to users and groups · Assign a policy to a group > What you need to know about policy assignment to groups > Precedence rules · Checked 2026-09-25
65
Get-CsUserPolicyAssignment -PolicyType <type>, expanding PolicySource, shows whether a user's policy is Direct or inherited from a Group, which explains why a group assignment is not taking effect.
Assign policies to users and groups · Assign a policy to a group > Change the effective policy for a user · Checked 2026-09-25
66
Organization in-call feature defaults apply to new users, and a user-level setting overrides them and does not automatically return to the organization default.
Configure in-call features from Control Hub · Organization and user level settings · Checked 2026-09-24
67
Health Checker opens on Windows from the profile picture > Help > Health Checker and on Mac from Help > Health Checker.
Webex App | Test your connection with the Health Checker · Open the Health Checker · Checked 2026-09-24
68
New-CsBatchPolicyAssignmentOperation assigns or unassigns a policy for up to 5,000 users per batch as an asynchronous operation and returns an operation ID.
New-CsBatchPolicyAssignmentOperation (MicrosoftTeams) · Description, first and third paragraphs; Parameters, -Identity · Checked 2026-09-25
69
Voice-related policy types that New-CsBatchPolicyAssignmentOperation supports include OnlineVoiceRoutingPolicy, TenantDialPlan, TeamsCallingPolicy, CallingLineIdentity, TeamsCallParkPolicy, TeamsEmergencyCallingPolicy and TeamsEmergencyCallRoutingPolicy.
New-CsBatchPolicyAssignmentOperation (MicrosoftTeams) · Description, list of supported policy types (final paragraph) · Checked 2026-09-25
70
New-CsBatchPolicyAssignmentOperation identifies users by object ID or SIP address; a user given by a UPN that differs from their SIP address fails policy assignment.
New-CsBatchPolicyAssignmentOperation (MicrosoftTeams) · Description, second paragraph · Checked 2026-09-25
71
Group policy assignment is recommended for groups of up to 50,000 users, and propagation to members runs as a background operation whose duration depends on group size.
Assign policies to users and groups · Assign a policy to a group, fourth and fifth paragraphs · Checked 2026-09-25
72
The status of a batch policy assignment is read with Get-CsBatchPolicyAssignmentOperation -OperationId, and per-user errors are in its UserState property.
Assign policies to users and groups · Assign a policy to a batch of users > Use PowerShell method > Get the status of a batch assignment · Checked 2026-09-25

Documents

tier 2 current vendor documentation

Cite this page

APA

WarmTransfer. (2026, October 1). Setting up Webex Calling inside Microsoft Teams. WarmTransfer. https://warmtransfer.net/guides/webex-calling-teams-integration-setup

BibTeX

@misc{warmtransfer-webex-calling-teams-integration-setup,
  title  = {Setting up Webex Calling inside Microsoft Teams},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/guides/webex-calling-teams-integration-setup},
  note   = {Verified 2026-10-01}
}