Azure Communication Services review

Azure Communication Services (ACS) is a hosted Azure service billed by communication usage, rather than a self-hosted server or a standalone desktop app. Its listed charges cover voice and video calling over IP, SIP Direct Routing, chat, SMS, email, messaging, call recording, captions, phone-number lookup and Job Router. That puts it in the communications layer of an application stack: developers pay for specific communication events or units rather than a recurring seat subscription.

The Azure homepage presents Azure products and solutions but does not describe ACS, its users, or how it fits alongside other services. The pricing details indicate a range of communication capabilities, but do not establish which are available in each region or how they connect to an application. Confirm the service scope, regional availability and supported integration paths in ACS documentation before choosing it. Reddit users also point to a retirement and breaking-changes guide, making roadmap checks part of the architecture decision.

The available vendor homepage text does not explain the ACS API style or describe its developer workflow. Pricing does refer to Teams API/SDK interactions for qualifying Microsoft 365 users, but that is not enough to determine the general API surface, authentication model, event handling or implementation requirements. The homepage lists broad Azure links to Documentation, Developer resources and the Azure portal, not ACS-specific integration instructions.

Before committing, confirm supported SDKs, languages, protocols, authentication options and CLI support in the ACS documentation. Also check whether the features you need use the same integration surface: the listed services span calling, chat, email, SMS and routing, but the homepage does not explain how they fit together. Ask for current examples and guidance on deployment, error handling, retries and migration. This matters more given Reddit users’ reports about the retirement notice; a working integration is not enough if the service’s planned lifespan does not fit your application.

ACS uses Pay-As-You-Go billing, with no fixed recurring fee and no published monthly or annual subscription price. Job Router includes 0–100 jobs per month free, then costs $0.01 per job routed. Qualifying Microsoft 365 users get free Teams API/SDK interactions, though seat and specific usage limits are not published. The Azure Free Account includes $200 in credit; its duration is not published. There is no free ACS plan listed.

Published rates include $0.004 per user minute for Voice and Video Calling over IP and $0.004 per minute for SIP Direct Routing. Chat is $0.0008 per message sent; email is $0.00025 per email sent plus $0.00012 per MB transferred. Messaging Connect (Preview) is $0.0025 per message, and Advanced Messaging is $0.005 per user message. Call recording, captions and phone-number lookup add separate per-minute or per-request charges. PSTN voice rates, many SMS rates and phone-number leasing prices are not published on the main page. Model traffic by unit and check the current rate card before launch.

The Azure homepage does not state an ACS source-code licence or offer a self-hosted distribution. Its pricing describes Azure usage charges, so plan for an Azure-hosted service rather than assuming you can run ACS in your own environment. The vendor homepage also does not explain data export, retention or migration tooling; ask Microsoft how to retrieve communication records and configuration before adopting the service.

Moving away may mean replacing feature-specific integrations, changing billing and permissions, and transferring phone-number or messaging arrangements. Reddit commenters describe teams moving workloads to ACS from SendGrid or Twilio and now facing another migration after the retirement notice. One commenter says their team had consolidated voice, text and email on ACS. That is not a measure of migration effort, but it shows why an abstraction layer and a documented exit plan matter. Confirm the retirement scope and migration recommendations with Microsoft before building a new dependency.

The published pricing details do not state throughput limits, rate limits, regional availability, service-level commitments, or reliability targets. The Azure homepage also does not describe ACS security controls or compliance coverage. Before production, verify those terms for each feature and region, as well as authentication, data retention, retry behavior, delivery reporting and incident support. Usage charges can accumulate across messages, minutes, requests and transferred email data, so instrument usage and set Azure budgets or alerts where available.

The clearest production concern in the Reddit threads we read is roadmap risk. Reddit threads link to Microsoft’s ACS retirement and breaking-changes guide, and users report that most offerings are due to retire in September 2028. ACS Email users describe having recently migrated from SendGrid or other mail paths and now needing another plan. A commenter also says the service worked well but was poorly documented. Treat these as user reports, not a substitute for Microsoft’s current service notice; confirm affected features and migration dates directly before depending on ACS.