SMS Support for Teams

Not applicable

Can we get a definitive answer on this? I have clients who are eagerly trying to ditch RingCentral and go all-in on Teams Cloud PBX, but the lack of SMS support doesn't allow them to make the jump. We've been clamoring this for years and with only janky third party solutions at best to fill the gap. What's the obstacle or objection here? After the partner call yesterday, it's apparent that 365 Cloud PBX sales are priority, so this should be a no-brainer.



130 Replies

Hi @Deleted!


Thank you for your feedback! Please help us share this survey to those you know who may be interested in SMS integration: This will definitely help us understand the use cases.


Thank you!

@Lorraine Wong that link doesn't work. I appreciate the response, but this is the same canned answer we've seen for a long time now. There are pages upon pages of examples of clients wanting this going back to 2013 in Skype for Business. 

Is this even roadmap? For a an application centered on collaboration and communication, and with the migration of all Cloud PBX functions to Teams, I can't fathom how there isn't more information on this. The revenue it would generate as a killer of products like RingCentral is blatantly obvious, even without the resounding mountain of past posts from community contributors and clients about wanting it.

Apologies! Just corrected the link on my original post. We are looking to it!

I agree with the original poster. I just started using Teams and Cloud PBX, and this is one of most important functions in today's comms world which is lacking. + for this one.

This is a badly needed feature for us. We had it before with RingCentral and really hope to have it soon with Teams and PSTN.

I agree, SMS truely would properly and more completely unify UC. It’s the most universal messaging system around, everyone with a 3/4G mobile can send and recieve SMS messages where as the same can’t be said for other messaging Apps if the recipient even has the app installed.

Hello @Deleted 


I agree with you on this, can you share more details about the use-case for SMS in/out functionality with Microsoft teams ? Do you think each channel should have its own unique PSTN number(s) where teams can text out and receive messages in from outside ? 


Am interested to know how other users see the SMS functionality working for them, would be awesome if you can share that.


Cheers !

For a specific use case. I am a Recruiting Manager and since implementing SMS into my communications with applicants my response rates have gone thru the roof!


My org just recently left Ring Central as their pricing started to become unfeasible for a growing company thru our transitional sizing. Before switching services, it was a huge point that the new service would allow for the SMS Communication model to continue. I personally would like to see MMS available as well.


More than just bringing SMS/MMS into the PBX/PSTN calling of MS Teams, integrations of this could be connected with Flow or API/Webhooks with an Applicant Tracking System (in a perfect recruiting world).

I think you guys are missing the point. For each DID, SMS should be a feature. I don't think anyone is clamoring for the ability to have SMS go to specific channels or groups of people, though I suppose why not.


Here's an example: Earlier this week a potential client tried to reach me via text on the phone number on my business card, which runs off Teams Cloud PBX. I learned later on that this person was unable to reach me, and as such moved on. I lost a potential client because of this, and as such I'm taking my organization off the Teams Cloud PBX platform. This is how business is done in 2019, and that every other cloud PBX provider seems to understand this without their users having to continually justify it for over 6 years on forums speaks volumes to either how tone-deaf or misguided this project team is.


I've had clients wanting to move off of platforms like RingCentral for over a year, but they can't because:


  • They need SMS.
  • Microsoft has been advertising "Teams Ready" devices to drive sales for over a year and yet none of these devices have firmware to do so. 


I don't know how else we as a community can tell you this. SMS is a non-negotiable feature for Cloud PBX. Without it, service providers like us will absolutely not be steering our clients to use it, and as I mentioned above, we're moving our team off it as well because we no longer have faith in this project team's ability to manage realistic expectations. There is zero accountability here and in the face of a mountain of feedback, the canned response is always "help us understand why and how you use this". Maybe as people continue to leave the platform will you understand how and why.


best response

The point for SMS support is for each of our phone users to be able to send and receive SMS messages using the Teams app (both desktop and mobile) and using their own personal phone number. This is a standard feature with all other cloud PBX services and is a glaring omission with Teams PBX service.


The SMS is a critical channel for communicating with clients and coworkers and cannot be that difficult to implement since all other providers are doing that already.



Exactly! It seems as though rather than asking end users for years why it is they would need it, perhaps we as paying customers and service providers which drive sales to the platform, should be asking the Teams developers why they feel we don't need it.

Let's not try to over engineer and overcomplicate this by tying SMS to Channels. A simple SMS capability for individual phone numbers is all we need.



At this point we've moved internally as well as will be directing our clients to move away from the Teams Cloud PBX platform and onto Dialpad, which integrates with O365 and provides similar or better features, including SMS support. I encourage anyone who happens upon this thread looking for answers to do the same as it's become clear no answers or roadmap for this most basic feature are to be found here.

I looked at Dial Plan and it seems like a good substitution.


I found a connection to an SMS vendor in MS Flow that could be very easy for Teams Cloud PBX to integrate or aquire. TXTsync works almost exclusively with Microsoft integrations.

I have EDU customers who need SMS so parents can confirm or alert on student  absences

@Deleted @Deleted @Irene Rossaert @Jakov Zaidman @ameedjamous 


Check out this video demonstrating two way SMS Enabling Microsoft Teams for a job recruiter, would love to know your option on this.




More details on how to do it can be found here :



SMS Support for Microsoft Teams (MS Teams)Short video demonstrating SMS Enabling Microsoft Teams to send and receive SMS messages with mobile phone users out...

While this is a good step in the right direction. It is still far from being comparable to SMS I've used with other telephony providers. 


I engage with an average of 30 new recruits each week and need to be able to track the conversations with each accordingly. Utilizing SMS for recruiting is simply adapting the communication methods to the media that is social acceptable. A personalized touch must be maintained with every conversation which also means that recruit should be able to make a phone call directly back to the number that was SMS Messaging with them.


To Say:

'You can text me at: #####; but you have to call me at 800.###.#### *##'

is highly robotic and less impactful to make a genuine connection to recruits or clients alike.

Thanks a lot for your valuablefeedback. Totally agree. Our initial effort was to get two-way sms working reliably with MS Teams. The personalization and integration with contacts, third party cloud tools will be next. I’ll keep sharing Dev updates and would be very thankful for your point of views and feedback on what you dislike and like to continue improving it.

Thanks again!