Azure Communication Services Enterprise Guide 2026
Embeddable voice, video, SMS, email, chat, Rooms, Job Router, Auto-Attendant, and Call Recording — with first-class Teams interop. Senior-architect-led delivery from a Microsoft Solutions Partner with nearly three decades of Microsoft enterprise experience.
Azure Communication Services (ACS) is Microsoft's programmable, embeddable communications platform — voice, video, SMS, email, chat, Rooms, Job Router, Auto-Attendant, and Call Recording — exposed through Web, iOS, Android, .NET, Java, Python, and Node SDKs. ACS is the application-layer counterpart to Microsoft Teams Phone: Teams Phone runs the enterprise calling estate, while ACS lets you embed Teams-interoperable voice and video into custom apps, contact centers, telehealth portals, and customer-facing experiences. EPC Group delivers ACS implementations as a Microsoft Solutions Partner — senior-architect-led, compliance-native for HIPAA, SOC 2, FedRAMP, FINRA, CMMC, GxP, with native Teams interop and Purview eDiscovery coverage from day one.
Azure Communication Services (ACS) is Microsoft's embeddable communications platform — voice, video, SMS, email, chat, Rooms, Job Router, Auto-Attendant, Call Recording — with native Teams interop. EPC Group delivers ACS implementations as a Microsoft Solutions Partner with nearly three decades of Microsoft enterprise experience, 11,000+ engagements, 70+ Fortune 500 clients, and compliance-native baselines for HIPAA, SOC 2, FedRAMP, FINRA, CMMC, GxP regulated environments.
Key Facts
ACS exposes voice, video, SMS, email, chat, Rooms, Job Router, Auto-Attendant, and Call Recording as a single Azure resource
First-class Microsoft Teams interop — external participants in Teams meetings, Teams users answering ACS calls, click-to-call from custom apps
Consumption pricing — per participant-minute for voice and video, per message for SMS, per MAU for chat, per recorded minute for Call Recording
Compliance-native — Purview eDiscovery coverage, Azure Blob immutability for FINRA 4511 and SEC 17a-4, customer-managed keys, per-region residency
EPC Group is a Microsoft Solutions Partner holding all six current designations including Digital & App Innovation and Modern Work
11,000+ engagements over 29 years, 70+ Fortune 500 clients, NPS 100 NPS
EPC Group Communications Modernization Accelerator — fixed-fee 5-phase delivery, typically $200K to $800K depending on channel scope and Teams interop complexity
Senior-architect-led delivery, no offshore handoff, compliance-native posture mapped to HIPAA, FINRA 4511, SEC 17a-4, MiFID II, FedRAMP, CMMC 2.0
Why Azure Communication Services Wins for Microsoft-Centric Enterprises
Embedded communications used to be a Twilio decision. In 2026 — for enterprises that have already standardized on Azure, Entra, Microsoft 365, Microsoft Teams, and Microsoft Fabric — that decision has changed. Azure Communication Services has matured into a programmable communications layer that matches Twilio and Vonage primitive-for-primitive and pulls ahead on the three dimensions that matter most to a Microsoft-centric enterprise: native Teams interop, Purview-anchored compliance, and unified Azure identity and governance.
ACS exposes voice, video, SMS, email, chat, Rooms, Job Router, Auto-Attendant, and Call Recording through a single Azure resource with SDKs for the web, iOS, Android, Windows, and every common server runtime. You build the customer experience in your own application; ACS provides the carrier-grade media, signaling, recording, and routing primitives. The same Azure subscription, the same Entra identity surface, the same Purview eDiscovery scope, the same Defender posture, the same FinOps reporting — there is no second platform to govern.
EPC Group is a Microsoft Solutions Partner that has spent nearly three decades inside the Microsoft enterprise stack. We deliver ACS implementations end-to-end — assessment through design, build, governance hardening, and 24/7 co-managed operations — under the same senior-architect-led, compliance-native model that we apply to every other Microsoft workload.
Nine Azure Communication Services Components
Azure Communication Services is not one product — it is a family of programmable communications primitives that compose into custom contact centers, embedded telehealth, banking video advisors, customer-portal chat-to-voice flows, and Teams-interoperable click-to-call buttons. Below are the nine components EPC Group uses every day inside enterprise ACS implementations.
Voice Calling
Carrier-grade PSTN and VoIP calling exposed as a Web, iOS, Android, and Windows SDK. Direct-routing, Microsoft Calling Plans, or bring-your-own-carrier — all addressable from a single Azure Communication Services resource with telemetry routed to Azure Monitor and Log Analytics.
•Inbound and outbound PSTN with Microsoft Calling Plans or Direct Routing SBC
•High-definition VoIP between custom apps, browsers, and Teams meetings
•Programmable call control via Call Automation — answer, transfer, play, recognize, hang up
•DTMF, hold music, music-on-hold customization, regional dial-out controls
Video Calling
Embeddable 1:1 and group video into web and mobile apps using the same SDKs as voice — no Twilio-style separate product to license. Screen share, background blur, raised hands, large-gallery view, and Teams meeting interop are first-class capabilities, not paid add-ons.
•Up to 350 participants per group call with active speaker view
•Composite video output and Server-Side Media Access for recording and bots
•Web, iOS, Android, Windows SDK plus headless server SDKs for .NET, Java, Python, Node
SMS
Programmable SMS over toll-free numbers, short codes, and 10DLC long codes — provisioned, registered, and managed inside Azure. Built-in support for The Campaign Registry (TCR) brand and campaign registration, opt-in/opt-out keyword handling, and delivery receipts.
•Toll-free (TFN), short codes, and 10DLC with built-in TCR registration workflows
•Delivery report webhooks routed through Azure Event Grid
•Compliance keyword handling — STOP / HELP / UNSUBSCRIBE automated
•High-throughput broadcast for transactional, marketing, and 2FA flows
Email
Transactional email send-only service inside Azure with custom domain support, DKIM/SPF/DMARC automation, and Azure Monitor reporting. Built for system-of-record email — appointment reminders, order confirmations, identity flows — not bulk marketing campaigns.
•Custom-domain or Azure-managed domain (azurecomm.net) sender identity
•DKIM and SPF auto-configuration; DMARC alignment guidance
•Generous initial throughput quotas with rapid limit-increase requests
Chat
Threaded, persistent chat for in-app messaging — customer-to-agent, patient-to-clinician, advisor-to-investor — with read receipts, typing indicators, file attachments, and full message history accessible through the Chat SDK or REST.
•Persistent multi-party threads with full history retention controls
•Read receipts, typing indicators, file attachments, message edit and delete
•Encrypted in transit and at rest; per-region data residency
•Server-side moderation hooks for content filtering and Purview eDiscovery
Rooms
Container abstraction for scheduled audio and video meetings with named participant roles — Presenter, Attendee, Consumer — and time-bounded validity windows. Use Rooms when you need meeting semantics inside a custom app rather than ad-hoc calls.
•Scheduled start and end times with automatic eviction
•Named participant roles with per-role media and content permissions
•PSTN dial-in support for hybrid audio attendees
•Composite recording for compliance archive into Azure Blob with immutability policies
Job Router
Skill-based routing engine that distributes inbound voice, chat, video, and SMS work items across agent pools using configurable selectors, queues, and priority. The native ACS replacement for cobbled-together skill-routing logic in Twilio Flex deployments.
•Skill, language, certification, and custom-attribute selectors
•Worker capacity, channel concurrency, and presence-aware routing
•Priority queues, escalation rules, and overflow to backup queues
•Jobs API and Workers API exposed for embedding into any custom contact center
Auto-Attendant
IVR-style call-flow designer with text-to-speech, speech recognition, DTMF tone matching, business-hours routing, holiday calendars, and queue overflow — managed through the Teams admin center or programmed from Call Automation when a custom IVR is required.
•Drag-and-drop IVR for Teams Phone or programmable IVR via Call Automation
•Business hours, after-hours, and holiday-calendar branching
•Azure AI Speech for natural-language routing — "billing" vs "support" vs "sales"
•Direct hand-off to Job Router queues or Teams call queues
Call Recording
Server-side recording of voice and video calls, Rooms, and Teams interop sessions — audio-only, video, or mixed composite — written to Azure Blob with optional immutability for FINRA, SEC, MiFID II, HIPAA, and CFPB retention requirements.
•Mixed audio, unmixed audio per participant, audio + video, or transcript output
•Azure Blob with immutability (legal hold and time-based retention) for regulators
•Built-in transcription via Azure AI Speech for searchable archive
•Customer-managed keys, customer lockbox, and per-region residency controls
Six Enterprise ACS Patterns
EPC Group has built ACS implementations across regulated and Microsoft-centric enterprises. The six patterns below are the ones we see most often — each is a representative composite of delivered work, anonymized for client confidentiality.
Pattern 1
Custom contact center built on ACS + Job Router + Teams interop
Scenario
A national retailer wanted to retire a legacy Genesys deployment, embed a contact-center experience directly into its e-commerce site, and let back-office subject-matter experts answer escalated calls from Microsoft Teams without learning a separate agent app.
EPC Group approach
EPC Group built a custom contact center on Azure Communication Services — Web SDK for the browser, Call Automation for IVR, Job Router for skill-based queueing, and Teams interop so SMEs answered escalations from the Teams client they already used. Azure AI Speech delivered live transcription; Power BI surfaced Job Router telemetry into a real-time service-level dashboard.
Outcome
Per-interaction cost cut roughly 38% versus the legacy Genesys spend. SME first-response time fell from 6 minutes to under 90 seconds because escalations landed in Teams rather than an unfamiliar agent app.
Pattern 2
Banking video advisor with click-to-call and Call Recording for FINRA
Scenario
A regional bank needed to add a "speak to a wealth advisor now" video button on its retail and private-banking web pages, with mandatory call recording, role-aware participant entry, and a FINRA-defensible archive for the SEC 17a-4 / FINRA 4511 retention window.
EPC Group approach
EPC Group used ACS Rooms for the scheduled and on-demand advisor sessions, ACS Call Recording with composite audio plus video output, Azure Blob with time-based immutability for the 7-year retention window, Azure AI Speech for searchable transcripts, and Microsoft Purview eDiscovery for regulator and counsel access. Entra External ID handled customer authentication; the advisor joined from the existing Teams client through interop.
Outcome
Click-to-call video session conversion 4.1× higher than the legacy chat-only widget. Zero findings from the internal compliance audit; FINRA 4511 archive workflow accepted by the bank's primary regulator without remediation.
Pattern 3
Telehealth platform — embedded video visits with HIPAA-aligned recording
Scenario
A 14-hospital health system needed an embedded video-visit experience inside its branded patient portal — not a third-party rebranded URL — with HIPAA-aligned recording for medical-record retention, Epic MyChart launch, and a clinician experience that lived inside Teams.
EPC Group approach
EPC Group built the patient-side experience on the ACS Web SDK with custom branding inside the existing portal. Clinicians joined through Teams interop — same client they used for clinical collaboration. Recording wrote to Azure Blob with per-tenant customer-managed keys and immutability policies aligned to state medical-record retention laws. Epic MyChart launched the visit through a SMART on FHIR redirect.
Outcome
No-show rate down 27% versus the prior third-party telehealth tool because the patient experience stayed inside the trusted portal. Clinician onboarding time near zero — they already used Teams.
Pattern 4
Customer-to-agent SMS + chat with handoff to live voice
Scenario
A consumer-finance company needed a unified SMS + in-app chat customer-service channel that could seamlessly escalate to a live voice or video call without context loss, and route to the right agent based on language, product line, and case complexity.
EPC Group approach
EPC Group used ACS SMS for the inbound channel (10DLC with The Campaign Registry brand and campaign registration), ACS Chat for in-app threads, Job Router for skill selection on language plus product plus tenure, and Call Automation to escalate to voice or video without dropping the conversation history. Azure AI Language enriched intent and sentiment for routing weight.
Outcome
Average handle time down 22%. Escalation-from-chat-to-voice success rate (no context re-collection required) over 96%.
Pattern 5
IVR + bot front-end on Call Automation feeding Job Router
Scenario
A health-insurance carrier wanted to replace a brittle SIP-trunk IVR with a programmable cloud IVR that did automatic claim-status lookup over voice, escalated to live agents when the bot could not resolve, and recorded everything to a HIPAA-aligned archive.
EPC Group approach
EPC Group implemented the IVR as ACS Call Automation logic — Azure AI Speech for speech-to-text, Azure AI Language for intent recognition, a custom claim-status agent built on Azure OpenAI for grounded responses, and Job Router for live-agent escalation when bot confidence dropped below a configurable threshold. Call Recording wrote to Azure Blob with HIPAA-aligned immutability.
Outcome
Bot containment rate 61% on claim-status inquiries — meaning 61% of those calls resolved without a live agent. Live-agent handle time on the remaining 39% dropped 14% because the bot pre-collected member ID and claim number.
Pattern 6
Teams interop hybrid — embedded customer app, Teams-side agent
Scenario
A B2B SaaS company wanted a "talk to support" button inside its product UI that connected the user directly to an internal Teams-based help desk — without the user installing a Teams account, joining a tenant, or downloading anything.
EPC Group approach
EPC Group built the customer side on the ACS Web SDK as an anonymous external participant, joining a Teams meeting hosted by the SaaS company's tenant. Job Router selected the on-call support engineer in real time and either placed them in the meeting or sent a Teams chat notification to grab the call. Recording, transcript, and call-control telemetry routed into the SaaS company's existing observability stack.
Outcome
No customer signup friction (zero Teams accounts created). Average pickup time inside business hours under 28 seconds. Support engineers stayed inside the Teams client they already used.
Pricing Model — Consumption, Not Per Seat
Azure Communication Services is consumption-priced, with the unit of consumption matched to the channel. There is no per-seat license — a brilliant fit for variable-load workloads and a meaningful watch-out for very high-utilization 8-hour-shift agent stations. EPC Group builds a per-channel total cost of ownership model in Phase 1 so the consumption-versus-seat tradeoff is quantified before you commit.
Channel
Pricing unit
Notes
Voice — VoIP between custom app participants
Per participant-minute
Charged per minute per participant on a call. Server-side media (e.g. Call Automation bots) counts as a participant. Discounted at scale through reserved capacity.
Voice — PSTN inbound / outbound
Per minute + per number
Per-number monthly rental plus per-minute usage. Toll-free, geographic, and short codes priced separately. Direct routing skips ACS per-minute and uses your carrier rate.
Video — group calling
Per participant-minute
Same per-participant-minute model as voice; resolution and bitrate do not change unit cost. Server-side composite recording counts as a participant.
SMS
Per message segment
Per outbound segment (160 GSM characters or 70 UCS-2). Inbound messages typically free. TCR and 10DLC brand registration fees passed through.
Charged on monthly active threads and message volume. Includes file attachments, read receipts, and typing indicators at no surcharge.
Call Recording
Per recorded minute
Per-minute fee for the recording operation. Storage cost is the standard Azure Blob rate for your chosen tier and immutability policy.
Job Router
Per routed job
Per-job pricing independent of channel — a voice call, chat, SMS, or video session counts as one job from creation through closure.
Pricing model summary derived from Microsoft Azure Communication Services public pricing documentation (June 2026). For current rate-card values run a live cost estimate inside the Azure Pricing Calculator. EPC Group provides a binding fixed-fee Assess output that includes a 24-month TCO model with reserved-capacity scenarios.
Teams Interop — Three Foundational Patterns
Teams interop is the structural advantage of Azure Communication Services over every Microsoft-external CPaaS. It lets a custom-built application engage Microsoft Teams users without forcing those users into a separate agent app and without forcing customers to install Teams. Three patterns cover almost every real-world deployment.
External participant joining a Teams meeting
An ACS-built web or mobile app joins a Teams meeting as an anonymous external participant — no Teams account, no tenant join, no client download. The Teams-side participants see the ACS participant as a normal attendee. Audio, video, screen share, chat, and reactions all flow through.
Customer or partner joins from your branded app — your URL, your logo, your UX
Internal staff join from the Teams client they already use every day
Same meeting recording, transcript, and Purview compliance posture as a native Teams meeting
No license proliferation — external participants do not consume Teams or M365 seats
T-bot — Teams user calls an ACS-built service
A Teams user dials a service endpoint surfaced through Direct Routing or a Teams Phone number — the call is answered by ACS Call Automation logic (the "T-bot") that can play prompts, recognize speech, transfer to a Job Router queue, or escalate to a live agent. Useful for internal helpdesks, IT service desks, and Copilot-fronted workflows.
Teams Phone or Direct Routing number terminates into ACS Call Automation
Bot uses Azure AI Speech and Azure OpenAI for grounded conversational logic
Escalates to live human via Job Router when bot confidence drops
Single Purview eDiscovery surface for the recording, transcript, and bot turn history
Click-to-call from a custom app into Teams
A button inside your CRM, customer portal, or product UI initiates a call that lands in Teams — to a specific user, a Teams call queue, or a hunt group. The caller stays in your app; the answerer stays in Teams. The connection is brokered through ACS with the call control surfaced as a Call Automation event stream.
Caller-side experience is your app — no Teams client required
Answerer-side is the Teams client — no new agent app to learn
Call routing handled by Teams call queue or Job Router selectors
Recording, transcript, and Purview retention applied through your chosen path
For Microsoft Teams-anchored calling estates, see the EPC Group Microsoft Teams Phone enterprise guide for Direct Routing, Operator Connect, and Calling Plan trade-offs that intersect with ACS Teams interop.
Job Router — Skill-Based Routing for Custom Contact Centers
Job Router is the native ACS service for routing voice, chat, SMS, video, and email work items across agent pools using configurable selectors, queues, capacity rules, and priority — the replacement for cobbled-together skill-routing logic typical of Twilio Flex deployments. EPC Group uses six rule patterns in nearly every Job Router design.
Skill-based selector
Match work items to workers by a required skill (e.g. "Spanish", "Wealth Management", "Tier 2"). Workers without the skill are excluded from the candidate pool. Multiple required skills can be combined with AND or OR logic.
Weighted skill selector
Match by skill level with a numeric weight — e.g. "Spanish proficiency ≥ 4 out of 5". Falls back to lower-weighted candidates if no high-weight worker is available within a configurable wait threshold.
Worker selector with custom labels
Route based on arbitrary worker attributes — tenure, certification, region, line of business. Useful for compliance routing (e.g. "FINRA-licensed advisors only") and for tier-based escalation logic.
Capacity and channel concurrency
Limit how many jobs a worker can handle in parallel — typically one voice call but up to five chats. Capacity reservations let a worker handle a voice call while holding capacity for a follow-up SMS thread.
Priority queues and overflow
Queues are ordered by priority within the same worker pool — a VIP queue can pre-empt a standard queue. Overflow rules send jobs to a backup queue or external partner if wait time exceeds a threshold.
Worker presence and availability
Workers signal availability through the Workers API — "Available", "On Break", "Wrap-Up", "Offline". Job Router only assigns jobs to "Available" workers and tracks median handle time per worker for capacity planning.
EPC Group Communications Modernization Accelerator
A fixed-fee 5-phase Accelerator that takes an enterprise from current-state communications inventory to a production ACS estate with Teams interop, Job Router, compliant recording, and 24/7 co-managed operations. Typical investment range:
$200,000 to $800,000 depending on channel scope, regulatory complexity, Teams interop depth, and incumbent vendor migration burden. Fixed-fee per phase, with each phase output owned by you whether or not you contract us for the next phase.
A senior architect maps every existing voice, video, SMS, chat, and IVR estate — Twilio, Vonage, Bandwidth, Genesys, in-house SIP, Teams Phone, native mobile — and produces a target ACS architecture, a per-channel migration sequence, a costed total-cost-of-ownership model, and a regulator-mapped compliance baseline.
Inventory of every active comms vendor, channel, and traffic pattern
Target ACS architecture with Job Router design and Teams interop boundaries
Per-minute, per-message, and per-MAU TCO model versus incumbent vendor billing
Compliance baseline — HIPAA, FINRA 4511, FedRAMP, CMMC 2.0, MiFID II — mapped to recording, retention, and residency controls
Phase 2 — Design · Weeks 3–6
Solution architecture, integration design, recording and retention model
Detailed design for the ACS implementation — SDK selection (Web, iOS, Android, .NET, Java, Python, Node), Call Automation flow design, Job Router skill model, Teams interop boundaries, Event Grid event mesh, Azure Monitor telemetry pipeline, and the recording and retention model mapped to your regulator.
SDK selection and reference architecture for browser, mobile, and server
Call Automation flow and Job Router skill-and-queue model
Teams interop boundary definition — what stays in Teams, what stays in ACS
Azure Blob recording with immutability, customer-managed keys, residency
Phase 3 — Build · Weeks 7–14
SDK integration, Call Automation, Job Router, Teams interop
Senior architects implement the ACS solution end-to-end — embed the SDKs into your web and mobile apps, build the Call Automation flows, stand up Job Router with skill and queue configuration, wire Teams interop, configure recording and immutability, and integrate Purview eDiscovery for compliance retrieval.
ACS SDK integration into your customer-facing apps (web, iOS, Android)
Call Automation flows for IVR, transfer, hold, recognize, escalate
Quarterly FinOps review — reserved capacity, per-channel unit economics
Continuous Teams interop drift monitoring against new Teams releases
Named senior-architect escalation — same humans who built the platform
Why EPC Group for Azure Communication Services
Microsoft Solutions Partner holding all six current designations including Digital & App Innovation and Modern Work.
Nearly three decades in the Microsoft enterprise stack — 11,000+ engagements, 70+ Fortune 500 clients.
Founder is a four-time Microsoft Press bestselling author — Power BI, SharePoint, Azure, large-scale migrations.
Senior-architect-led delivery end-to-end — no offshore handoff, no phase-to-phase team rotation.
Compliance-native delivery across HIPAA, SOC 2, FedRAMP, FINRA, CMMC, GxP, MiFID II, SEC 17a-4, FedRAMP-aligned for federal contractors.
G2 Leader — six consecutive quarters, NPS 100 NPS — verified buyer reviews on G2 Business Intelligence Consulting and adjacent categories.
ACS by Regulated Industry
Azure Communication Services implementations in regulated industries are different implementations. Compliance posture changes the recording and retention model. Carrier strategy changes the trunking layer. Regulator-defensibility changes the eDiscovery scope. Review the EPC Group industry hubs to see how ACS lands inside a wider Microsoft cloud transformation.
How does Azure Communication Services compare to Twilio?
Azure Communication Services and Twilio cover overlapping ground — programmable voice, SMS, video, chat, and email — but the alignment of the rest of your stack usually decides which wins. ACS is the better fit when (1) your enterprise already runs on Azure, Entra, Microsoft 365, Teams, or Microsoft Fabric, (2) you want Teams interop as a first-class capability rather than a custom integration, (3) compliance posture is regulator-grade — HIPAA, FINRA 4511, FedRAMP, CMMC — and you need Purview eDiscovery to cover comms artifacts, and (4) you want a single Azure resource, a single billing relationship, and a single identity surface. Twilio remains strong for multi-cloud organizations, deep developer-platform ecosystems, and standalone communications use cases that do not need Microsoft alignment. EPC Group has delivered both — we will tell you on a one-hour call which platform is the right fit for your situation.
How does ACS compare to Vonage (formerly Nexmo / TokBox)?
Vonage offers a mature programmable communications platform with strong video heritage from the TokBox acquisition. ACS overlaps on every primitive (voice, video, SMS, chat) and adds two structural advantages for Microsoft-centric enterprises: native Teams interop (caller-in-app-meets-agent-in-Teams, with no custom bridge) and native Purview eDiscovery coverage for recordings, transcripts, and chat. For an enterprise whose identity, compliance, and collaboration estate is already Microsoft, ACS removes integration work that Vonage cannot remove. For multi-cloud or non-Microsoft enterprises, Vonage is a credible choice — particularly for high-scale video workloads.
How does ACS compare to Bandwidth?
Bandwidth is a U.S.-strong CPaaS with deep carrier relationships, particularly for direct-to-carrier voice termination, emergency 911, and number portability. ACS competes on the application layer (SDKs, Call Automation, Job Router, video, chat, Teams interop) but often integrates with a carrier like Bandwidth at the trunk layer through Direct Routing. The two are commonly complementary rather than competitive — ACS handles the application logic and Teams alignment; Bandwidth provides the carrier trunk. EPC Group has designed combined ACS plus Bandwidth deployments for federal contractors who needed FedRAMP-aligned trunking inside an ACS application stack.
Teams interop versus Operator Connect — which is which?
Teams interop and Operator Connect are different patterns. Teams interop is the ACS capability that lets a custom-built application participate in a Teams meeting or place a call into a Teams user — the application is the surface, Teams is the participant. Operator Connect is a Microsoft Teams Phone capability that lets a Teams customer bring carrier PSTN service from a Microsoft-approved operator directly into the Teams admin center, without a Session Border Controller. Both can coexist in the same enterprise — Operator Connect carries Teams-native voice traffic, while ACS-with-interop carries custom-app traffic that needs to engage Teams users.
Can ACS Call Recording meet FINRA 4511 retention requirements?
Yes. ACS Call Recording writes recordings to Azure Blob storage where you can configure immutability through either time-based retention policies or legal-hold tags. Time-based retention can be configured for the 7-year window required by FINRA Rule 4511 and SEC Rule 17a-4(b)(4). With customer-managed keys, Customer Lockbox, and per-region residency, the archive meets the controls expected during FINRA examinations. EPC Group has implemented this pattern for regional banks and broker-dealers and has standard documentation packs covering the control mapping (FINRA 4511, SEC 17a-4, MiFID II Article 16) to facilitate regulator and internal audit reviews.
How long does an ACS implementation take?
A focused embedded-voice-or-video accelerator (single channel, single app, no Teams interop) is typically a 6 to 8 week build. A custom contact center with Job Router, Call Automation IVR, Teams interop, and compliant recording is typically 12 to 18 weeks. A full enterprise communications modernization replacing a Twilio, Vonage, or legacy Genesys estate is typically 6 to 12 months phased by channel. EPC Group prices Assess and Accelerator phases as fixed fee so total cost is known before delivery starts.
How does ACS pricing work versus a flat per-seat model?
ACS is consumption-priced — per participant-minute for voice and video, per message segment for SMS, per monthly active user for chat, per recorded minute for Call Recording, per routed job for Job Router. There is no per-seat license, which makes the unit economics far better for variable-load workloads (seasonal contact centers, click-to-call buttons, embedded telehealth visits) and frequently materially worse for very high-utilization 8-hour-shift agent stations. EPC Group builds a per-channel TCO model in Phase 1 so the consumption-versus-seat tradeoff is quantified before you commit.
Does EPC Group have references for ACS deployments?
Yes. EPC Group is a Microsoft Solutions Partner holding all six current designations including Digital and App Innovation and Modern Work. Reference engagements span custom contact centers replacing Genesys, banking video-advisor portals with FINRA-aligned recording, HIPAA-aligned telehealth, federal communications modernization on Azure Government, and Teams-interop click-to-call into existing Teams estates. Senior-architect references are available under NDA.
A 60-minute call with a senior architect — not a sales lead. We will give you an honest read on whether ACS, Teams Phone, or a hybrid is the right fit; what the realistic per-channel total cost of ownership looks like at your scale; and where Teams interop replaces months of custom integration work. If EPC Group is not the right fit, we will say so on the call and point you to the right firm.