4 Ways to Connect Microsoft Teams and Cisco Webex in 2019
Enterprises end up with users on both Microsoft and Cisco platforms all the time.
For many reasons and in many businesses, we regularly see organizations with instances of both Microsoft Teams and Cisco Webex.
This post addresses how enterprises got to this situation and highlights the best ways to connect the two platforms together.
Why Microsoft Teams and Cisco Webex?
Common reasons for instances of both Microsoft Teams and Cisco Webex include:
- Legacy or current Cisco hardware like telepresence, VoIP handsets, and Cisco Spark boards
- Office 365 packages offering free Skype for Business and Microsoft Teams licenses
- Mergers and acquisitions where one company uses Cisco Webex Teams and the other uses Microsoft Teams
- A new CIO or IT Manager started and implemented their preferred
1 – Cisco Webex Teams and Office 365 integration
Cisco recently announced integration between their Webex Teams app and the Office 365 suite.
Users can access files like apps like SharePoint and OneDrive from within the Webex Teams app.
If your end goal is to use the Microsoft Office 365 suite within the Webex Teams app, this integration will work just fine.
a. Users no longer have to leave their Webex Teams app if they use Office 365 for productivity tools like Microsoft PowerPoint and Microsoft Word.
b. You can benefit from data governance and data privacy from Office 365 whilst never leaving your Webex Teams app.
c. Share content created in Microsoft apps in Cisco Webex Teams spaces.
a. This integration is available for multiple Microsoft apps, but not Microsoft Teams.
b. If you’re a Webex Teams for Web user, you can only view these types of files, but not make
The Cisco Webex Teams and Office 365 integration is great for users that are happy to live in Webex Teams – but it doesn’t take into account users that prefer Microsoft Teams for collaboration.
2 – Bot integration for Microsoft Teams and Cisco Webex
If This Then That (IFTTT) helps apps and devices work together.
There are examples of IFTTT working in homes and businesses alike.
When rules are set for one app or device to do something based on the behavior of another app of device, these are called recipes.
From common scenarios like turning up the heating in your home when the temperature drops below a certain threshold to syncing your Instagram and Dropbox account, recipes come in all shapes and sizes.
When setting recipes for both Microsoft and Cisco, this typically includes what happens on Microsoft Teams when a message is posted in Webex Teams.
For this scenario, a Webex Teams users sends a message and the bot in Microsoft Teams gets a notification.
a. Bot integrations come with many pre-built recipes to choose from across a range of apps and devices.
b. Familiar look and feel to consumer IFTTT apps.
c. Options to add your own customized recipes.
a. Administration time can be lengthy as scenarios have to be set up one-by-one.
b. When new users are added, administrators must build new recipes.
c. Functionality across platforms is limited.
d. Cross platform experience is not seamless. Notifications are received in a bot rather than native to a chat, space or direct message etc.
3 – Host meetings in Microsoft Teams
For users that prefer Microsoft Teams for messaging and collaboration, but must use Cisco Webex for meetings, there is the Cisco Webex Meeting app.
This is perfect for running Cisco Webex meetings direct from Microsoft Teams.
The meeting app is also available for Slack, Workplace by Facebook and Google Calendar.
a. Schedule and join Cisco Webex meetings without leaving Microsoft Teams.
b. Microsoft Teams users just need to add the Webex Meetings app to their Microsoft Teams app.
c. Simple administration in the Cisco Webex Control Hub.
a. The Cisco Webex Meetings app for Microsoft Teams doesn’t support accounts on webex.meetings.com, on meetingsln.webex.com, or on Cisco Webex Meetings Server sites.
b. Limited to Cisco Webex Meeting functionality.
c. Messages, chats, files etc cannot be exchanged via the Webex Meeting app for Microsoft Teams. A meeting must be launched to communicate across platform.
d. Customers of both Cisco and Microsoft using the integration have labelled it clumsy, forcing them to consider back to working in silos.
4 – Full synchronization between Microsoft and Cisco
For full synchronization between your distributed users, there is a way.
Instead of trying to shoehorn one app into the other, your teams could be chatting together on the app of their choice across platform – without changing the way a single user in your organization collaborates.
Mio is the “behind the scenes” interoperability tool that syncs everything together. Messaging interoperability achieved.
Mio’s “full synchronization” feature works completely in the background of existing messaging platforms (like Microsoft Teams and Cisco Webex Teams) to provide seamless chat interoperability across channels and DMs.
What’s more, you only have to
Mio’s user experience means no change of habit for employees.
Neither do they need to worry about learning how to use a new tool – so training and adoption is not a concern either.
When a Microsoft Teams user needs to
The same is true for posting in a Webex space, sending a file and even includes rich text formatting.
Mio provides comprehensive interoperability and syncs all the features your teams depend on every day.
This feature matrix breaks down what you can achieve across
To see how Mio keeps your teams in sync, and provides seamless messaging interoperability, check out this video or get started by hitting the button below.