No. As of May 2026, Mio (m.io) is still commercially operating and self-describes on its own website as 'Google's official interoperability partner.' The 'Mio is discontinued' narrative circulating on some publisher sites is inaccurate at the company level. What is true is that on 1 August 2025 Google publicly announced that Google Chat ↔ Microsoft Teams interoperability is delivered through NextPlane OpenHub, not through Mio (https://workspaceupdates.googleblog.com/2025/08/enhanced-chat-interoperability.html).

What changed for Mio in August 2025?

Google's Workspace Updates blog announced on 1 August 2025 that 'interoperability between Google Chat and Microsoft Teams is now available through NextPlane OpenHub.' That post does not name Mio. Mio's own marketing still describes itself as 'Google's official interoperability partner,' but Google's current public statement about Chat ↔ Teams interop points to NextPlane. Mio's Slack ↔ Teams product is a separate offering and is unaffected by the Google Chat development.

Who actually offers Slack ↔ Microsoft Teams bridging in 2026?

Five vendors are actively shipping a Slack ↔ Microsoft Teams bridge as of May 2026: Mio (enterprise, sales-led, all-users-licensed), NextPlane (enterprise sales-led, Google's named Chat-Teams partner), Conclude.io (Slack-Teams chat plus ticketing, 14-day free trial), SyncRivo (multi-platform iPaaS, $49 Growth tier with a 50,000 message-per-month cap per their pricing page as of 2026-05-28), and SlackBridge (self-serve, per-workspace flat $49.99 Pro, free tier).

Which option is right for an enterprise with thousands of users?

Mio and NextPlane are the two enterprise-sales-led options. Both expect to license every active user on both sides and both go to market through sales conversations rather than self-serve sign-up. If your buying process requires named account management, a master services agreement, and tenant-wide deployment, those are the two to talk to.

Which option is right for a single Slack channel that needs to talk to a single Teams channel?

Per-user enterprise licensing is overkill for one-channel use cases. Conclude.io, SyncRivo, and SlackBridge all support per-channel or per-workspace pricing models. SlackBridge specifically charges a flat $49.99 per Slack workspace on the Pro plan regardless of user count, which tends to be the cheapest option for a small two-org bridge. Conclude bundles ticketing into the same product. SyncRivo is the right choice if you also need to bridge into Discord, WhatsApp, or other platforms in the same workflow.

Is this article written by a Mio competitor?

Yes. This article is published by SlackBridge, which sells a Slack ↔ Microsoft Teams bridge and is one of the five options listed. The facts about Mio's operational status and the August 2025 Google announcement are sourced from primary documents — Google's Workspace Updates blog and Mio's own website — and you can verify them at the URLs cited in the article.

Mio alternatives for Slack ↔ Microsoft Teams bridging (2026)

Q: Where can I read Google's actual announcement?

The Google Workspace Updates post is at https://workspaceupdates.googleblog.com/2025/08/enhanced-chat-interoperability.html. The relevant sentence is 'interoperability between Google Chat and Microsoft Teams is now available through NextPlane OpenHub.' That post is the primary source for any claim about the current Google-side interop partner.

TL;DR. Mio is still operating commercially as of May 2026 — it has not been discontinued. What changed is that on 1 August 2025 Google announced that Google Chat ↔ Microsoft Teams interoperability is now delivered through NextPlane OpenHub. For Slack ↔ Microsoft Teams specifically, the five active options in 2026 are Mio, NextPlane, Conclude.io, SyncRivo, and SlackBridge — each built for a different buyer.

What's the short version?

Mio is not discontinued. As of 28 May 2026, m.io is still online, still selling, and still self-describes as "Google's official interoperability partner."

What is true is that on 1 August 2025, Google's Workspace Updates blog announced that Google Chat ↔ Microsoft Teams interoperability is now delivered through NextPlane OpenHub. That post does not name Mio. The two statements — "Mio says it is Google's partner" and "Google says NextPlane provides the interop" — are both publicly visible right now, and the gap between them is what has fuelled the "Mio is discontinued" narrative.

For the specific question this article exists to answer — what are my real options for bridging Slack and Microsoft Teams in 2026? — there are five:

Mio — enterprise, sales-led, all-users-licensed. See SlackBridge vs Mio for a side-by-side.
NextPlane — enterprise sales-led, Google's named Chat-Teams partner since August 2025.
Conclude.io — Slack-Teams chat plus ticketing, 14-day free trial. See SlackBridge vs Conclude.
SyncRivo — multi-platform iPaaS bridging Slack, Teams, Discord, WhatsApp, and others. See SlackBridge vs SyncRivo.
SlackBridge — self-serve, per-workspace pricing, free tier. (That is us; we published this article.) See all SlackBridge comparisons.

The rest of this piece walks through what each one is built for so you can route yourself to the right one.

Is Mio still operating? (Yes, with one major caveat)

Mio Holdings, Inc. — the company behind m.io — is operational. Their homepage is live, their product pages describe an active Slack-Teams-Webex bridge, and they continue to market themselves to enterprises.

The caveat: on the specific subject of Google Chat ↔ Microsoft Teams, Google's current public statement names a different vendor.

On 1 August 2025, the Google Workspace Updates blog announced an "Enhanced chat interoperability between Google Chat and Microsoft Teams." The exact sentence in that post is:

"interoperability between Google Chat and Microsoft Teams is now available through NextPlane OpenHub"

That post does not mention Mio.

Mio's own website, at the time this article was last verified, continues to describe Mio as "Google's official interoperability partner." Mio is welcome to make that claim about its own positioning; it just isn't reflected in Google's public messaging anymore.

For Slack ↔ Microsoft Teams specifically — which is what this article is about — none of the above changes Mio's product status. Mio still sells a Slack-Teams bridge. The August 2025 Google announcement is a Chat-side story, not a Slack-side story.

What changed in August 2025

The simplest way to read the August 2025 update is to read the post itself. The relevant facts are:

Google publicly named NextPlane OpenHub as the provider of Chat ↔ Teams interop.
Google did not name Mio.
Google did not say Mio's products are discontinued. (No public statement from Google addresses Mio at all.)
Mio's own website still describes Mio as "Google's official interoperability partner," which is a marketing claim by Mio about Mio, not a current statement from Google.

If you are a Google Workspace admin specifically trying to enable Chat ↔ Teams interop today, the path Google points you to is NextPlane.

If you are a Slack admin trying to bridge to Microsoft Teams, the August 2025 Google announcement is not directly relevant — Slack is a separate product from Google Chat, and the Slack-Teams bridging market has its own set of vendors.

The 5 active Slack ↔ Microsoft Teams bridging options in 2026

Listed in alphabetical order so we are not implicitly ranking anyone.

Conclude.io

Conclude bundles a Slack ↔ Microsoft Teams chat bridge with a ticketing and incident-management workflow on top. The product positioning is "shared workspace for cross-company support," and the chat bridging is one feature inside a larger collaboration product rather than a standalone bridge.

Per their pricing page as of 2026-05-28, Conclude offers a 14-day free trial. Confirm current per-seat pricing on their site.

Built for: teams who want chat-bridging and shared ticketing in the same product — for example, a vendor and a customer running a joint support workflow.

Not built for: straight message-relay without the surrounding ticketing layer.

Mio (m.io)

Mio is the incumbent and the longest-running player in the cross-platform messaging interop space. The product bridges Slack, Microsoft Teams, and Webex. The business model is enterprise sales-led, with all-users licensing on both sides of the bridge.

The "Mio is discontinued" claim that has circulated since August 2025 is not accurate at the company level. Mio is still operating. What is accurate is that Google's August 2025 announcement named NextPlane (not Mio) as the Chat-Teams interop provider.

Built for: large enterprises that want a single vendor relationship covering Slack, Teams, and Webex bridging across thousands of users, with sales-led procurement.

Not built for: self-serve sign-up, per-channel pricing, or small teams that do not want to license every user.

NextPlane

NextPlane is the vendor Google publicly named on 1 August 2025 as the Chat ↔ Teams interop provider via its OpenHub product. NextPlane also sells Slack ↔ Microsoft Teams bridging, like Mio, in an enterprise sales-led motion with all-users licensing.

NextPlane's elevated position in the Google ecosystem since August 2025 has made it the default enterprise alternative cited when buyers move off Mio.

Built for: enterprises that want the vendor Google currently points to for Chat-Teams interop, and that are happy to expand the same relationship to cover Slack-Teams. Same buyer profile as Mio.

Not built for: self-serve buyers, single-channel use cases, or teams that want transparent online pricing.

SlackBridge

This article is published by SlackBridge, so treat this section as the vendor describing itself.

SlackBridge is a self-serve Slack ↔ Microsoft Teams bridge. There is a free tier and a Pro plan at $49.99 per Slack workspace per month, flat, regardless of user count. Channel mappings are per-channel — you can bridge one Slack channel to one Teams channel without paying for every employee.

Onboarding is OAuth-only (no manual provisioning), and the data-handling posture is documented in our data retention article — message body text is not persistently stored; only the metadata needed for thread replies is, and it expires in seven days.

Built for: two organizations that want to bridge specific Slack and Teams channels without an enterprise procurement cycle.

Not built for: all-users-everywhere tenant-wide bridging across thousands of seats — that's what Mio and NextPlane are built for.

SyncRivo

SyncRivo positions itself as a multi-platform iPaaS for messaging: it bridges Slack and Microsoft Teams, plus Discord, WhatsApp, and other platforms in the same product. Per their pricing page as of 2026-05-28, the Growth tier is $49/month with a 50,000 message-per-month cap.

SyncRivo has also been the loudest publisher of the "Mio is discontinued" claim in 2026. Readers should be aware that SyncRivo is a competitor of Mio's and has commercial incentive to amplify that narrative.

Built for: workflows that need to span more than two platforms — for example, a community team bridging Slack to both Microsoft Teams and Discord, or a customer-support team that wants Teams plus WhatsApp.

Not built for: buyers who specifically need only Slack-Teams and would prefer not to pay for the iPaaS layer underneath, or for teams whose monthly message volume materially exceeds the 50,000 message cap on the cheapest tier.

Choosing between them by use case

A pragmatic decision tree, from most-enterprise to most-self-serve:

You are a Fortune-2000-scale buyer with a multi-vendor procurement process and you want every user on both sides licensed under one MSA. → Talk to Mio and NextPlane. Compare pricing and product depth. NextPlane is currently Google's named Chat-Teams partner; Mio is the longer-running incumbent for cross-platform interop generally.

You and another company want to run a shared support or incident workflow, not just bridge messages. → Look at Conclude.io. The chat bridge plus shared ticketing in one product is the differentiator.

You need to bridge more than two platforms — for example, Slack and Teams and Discord, or Slack and Teams and WhatsApp. → SyncRivo. Verify the 50,000 message cap on their Growth tier against your actual monthly volume before signing up.

You are two organizations that want to bridge specific Slack channels to specific Teams channels, ideally today, with no sales call. → Try SlackBridge's free tier. If you need more than the free tier covers, Pro is a flat $49.99 per Slack workspace, no per-user math. (Again — we publish this article. We say so explicitly.)

You are a Google Workspace admin trying to enable Chat ↔ Teams interop (not Slack). → This article is about Slack-Teams, but for completeness: Google's August 2025 announcement points you to NextPlane OpenHub for that specific use case.

How we sourced this article

We used three categories of source for the factual claims:

Primary statements from the platform vendors. Google's Workspace Updates blog for the NextPlane announcement.
The named companies' own marketing. m.io, nextplane.net, conclude.io, and syncrivo.ai for product descriptions and pricing. Pricing claims are qualified as "per their pricing page as of 2026-05-28" because vendor pricing changes more often than this article will be re-verified.
Our own product, for the SlackBridge section. That section is the vendor describing itself, marked as such.

We did not source claims from third-party publishers, analyst reports, or vendor-funded comparison pages.

FAQ

See the FAQ block at the top of this article (rendered separately on the page) for: whether Mio is discontinued, what changed in August 2025, who the five active vendors are, which option suits enterprise versus single-channel use cases, and who wrote this article.

If you have a fact-correction for any claim above — including any of the SlackBridge claims — email support@slackbridge.com with the URL of the primary source and we will update the article and the last_verified date.