Microsoft gives date for ACS-Teams Interoperability Launch

Microsoft has revealed that interoperability between Azure Communication Services and Teams will hit general availability in December.

First announced at the Microsoft Ignite event in March, the combination means that users of an application built on the ACS platform can interact with users of Microsoft Teams.

Watch UC Today’s overview of ACS from earlier this year

The second Ignite event of the year has now seen the vendor confirm that the integration will step out of preview early next month.

Kristin Dunning, Director of Product Marketing for Azure at Microsoft, said: “One of the key things we continue to learn from developers is that their business’ need the control and flexibility to integrate custom voice and video communication into everyday customer experiences, without the burden of owning and operating the infrastructure needed for scale.

“Our objective is to help developers easily build those customizable communication experiences across platforms, purpose-built for scenarios ranging from healthcare professionals delivering remote care, to finance advisors helping consumers with a loan application, or support staff helping end-users install a new product.”

ACS, which was itself launched in September 2020, lets developers connect into the same technology that powers Microsoft Teams, allowing them to build communication capabilities into custom platforms.

A key use case for the interoperability will be delivering customer service, connecting customers using a custom-built app to the supplier’s agent using Teams.

Developers have complete control over how the meeting is rendered for the customer, with customisation available around screen sharing, the size of the video and the buttons that are displayed.

The interoperability supports two types of interactions for ACS in Teams:

  1. Bring your own identity, where Teams views the ACS-based application as an external user with limited permissions. This is targeted primarily at business-to-consumer scenarios
  2. Azure Active Directory authentication, where the application is treated as a Teams user. Microsoft said this is aimed at the creation of custom attendant consoles designed for handling incoming calls.

 

 



from UC Today https://ift.tt/3GFXhFw

Post a Comment

0 Comments