Skip to main content
29 September 2026

How can you synchronise status and availability between your Broadsoft investments and Microsoft Teams?

If your B2B customers use both Cisco Broadsoft and Microsoft Teams, they may experience a common issue: the two platforms are not aligned, which means that status cannot be federated effectively between them. Gintel’s new MBS solution solves this problem with harmonised, federated status and availability – in real-time, at scale and for all your B2B customers.

The synchronisation issue – for your customers using two platforms in their workplaces

Many operators have invested in Broadsoft (Cisco) BroadWorks platforms for the delivery of IP Centrex and IP PBX services to their business customers. These continue to deliver and are likely to do so for some years to come, even if some operators are also evaluating their options as they transform their networks.

At the same time, most of your B2B customers have also adopted Microsoft Teams in their workplaces. While the numbers haven’t changed much in the last couple of years, analysts Statista reckoned that the total has now reached around 320 million, according to a research update in September 2026.

As a result, your customers are likely to be using both platforms.

Each has its own mechanisms to govern user status and availability. On the one side, if a user is in a call on BroadWorks, logic is applied to route new calls to their terminals – to voicemail, to a colleague, whatever. On the other, user status is updated according to rules in Teams, so if a user is in a meeting or on a call, similar rules can be applied.

The problem is that these worlds co-exist but are not harmonised. So, any given customer may be busy with respect to their Broadsoft channels, but Teams has no knowledge of this and will show different status and availability indicators.

This, naturally, can lead to glitches – with calls being presented to users when they are in a Teams meeting, and vice versa. The two platforms deliver excellent experiences, but where both are used in the same workplace, this lack of harmonisation can lead to significant user dissatisfaction.

Synchronising status and availability between Broadsoft and Microsoft Teams will deliver better experiences and increase efficiency for your B2B customers.

Federating status and restoring harmonisation

So, what’s the solution? How can you restore harmony and offer your B2B customers a better experience when using both Broadsoft and Microsoft Teams?

Well, this is a problem we’ve solved in deployments like this. Most of our operator customers and partners offer integration between our solutions and Teams, which delivers the desired harmonisation and synchronisation.

Recognising that not everyone is ready to disrupt the existing B2B service portfolio, we’ve now taken steps to expose this integrated function as a standalone solution: Microsoft / Broadsoft Synchronisation, or MBS.

Gintel’s new, standalone Microsoft / Broadsoft Synchronisation function

MBS is a logical function that enables harmonisation between the two parallel worlds of Microsoft applications and Broadsoft communications platforms, principally, BroadWorks, now rebranded as Cisco BroadWorks.

MBS solves that common problem that can be experienced by end-user B2B customers of operators. Simultaneously, such a customer can be both a user of operator-delivered Broadsoft services and Microsoft applications, like Teams.

Both channels enable communication but the two can be in conflict. For example, when a user is active on a Broadsoft client, they may also appear to be available on the Microsoft channel. As a result, a colleague or external user may seek to reach them via Teams, but the event may interrupt the active session.

MBS solves this problem by harmonising events between the two platforms and delivering an optimised experience.

It achieves this through dual integration with Microsoft applications (Teams, Exchange and Active Directory) via the Microsoft Graph API and with Broadsoft via XSI (event broadcast and notification) and OCI-P (control interface for manipulating key settings).

Seamless synchronisation and federation

This integration enables seamless, two-way synchronisation and federation between the two platforms, delivering a unified experience. If a user is busy on a Teams call, their status can be changed in BroadWorks, so that the appropriate logic can be applied by the Broadsoft platform.

The synchronisation is continuous and applied to all relevant users of both services. MBS can be deployed alongside your existing investments, in your IMS core and enables you to deliver better experiences to your B2B customers.

If you’d like to learn how you can synchronise experiences for your BroadWorks customers that also use Microsoft Teams, why not get in touch? We can show you how this works in practice and explore how we can deploy MBS in your network.

Latest posts

How can you synchronise status and availability between your Broadsoft investments and Microsoft Teams?

Does your network transformation and automation programme risk leaving legacy service silos in its wake and building up hidden costs?

Launching a new mobile service for local businesses – nationally

MVNEs: supporting B2B-focused MVNOs with the use cases they need to deliver

MVNEs: are you able to support B2B-focused MVNOs?

Tags