Azure Communication Services
by Microsoft
Microsoft Azure APIs for SMS, email, chat, voice, video calling and phone numbers.
- Category
- Communication
- Type
- CPaaS
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- Signed requests, OAuth 2.0
02Data
What you can sync.
- Chat threads
- Sms
- Email status
- Phone numbers
- Call recordings
Report on Azure Communication Services chat threads with delivery and response times, next to the teams behind them.
Need more? Name any other Azure Communication Services data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- Signed requests (key and secret)
- OAuth 2.0 (client ID, client secret, refresh token)
Azure Communication Services uses signed requests (key and secret) or OAuth 2.0 (client ID, client secret, refresh token). You add the credentials once, when the AI asks for them, and it tells you where to create them in Microsoft if you need help.
04How it works
How it works in DataMind.
-
Pick Azure Communication Services.
Open Lake, pick Azure Communication Services in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Azure Communication Services API docs.
-
Answer a few questions.
The AI reads the Azure Communication Services documentation, then asks which credentials you will use, which data to sync (for example chat threads and sms), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
It builds the connector, tests it and shows you sample rows. Then Azure Communication Services data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.
05Related
