Azure Communication Services is now Generally Available, in 6 regions with SLA

At Microsoft Ignite, on March 2nd, Scott Van Vliet announced that Azure Communication Services would become Generally Available “later this month”.

True to their word (just!), yesterday a blog post on the Azure Communication Services Tech Community blog announced that the service is now GA.

What does this mean?

• It means that the service is now officially supported by Microsoft and you can log Azure service tickets if you encounter any issues.
• Microsoft Teams Interop is still in public preview
• You can choose from 6 different regions to host the data and media associated with your Azure Communication Services instance. These are:
  • United States
  • Asia Pacific
  • Australia
  • Europe
  • United Kingdom
  • United States
• GA also brings with it new capabilities for monitoring your Azure Communication Services instance, with a variety of diagnostic hooks to send data to Log Analytics, Storage Account or Event Hubs.
• There is an official SLA for the service which covers PSTN, VoIP, SMS and Chat communication as well as underlying parts such as Events and Notifications.

There are some other features as well around PSTN and SIP coverage which are interesting. They’ve been written up by Tom Arbuthnot so I won’t cover them here.

Time to learn ACS?

If this means that it’s now time for you to start learning how Azure Communication Services works, you might be interested in a series of blog posts I have to help you get started, with sample code on GitHub and full instructions.

Visit learnacs.dev to get started.