Migration Guide: Azure Communication Services (ACS) to Blip November 18, 2026 12:10 Updated Channel comparison summary Architecture and integration changes Code and architecture changes to plan for Email Capabilities What changes SMS Capabilities What changes WhatsApp Capabilities What changes What Blip adds beyond the ACS experience Sources Microsoft (Azure Communication Services) Blip This is a migration guide from Azure Communication Services (ACS) to Blip for the Email, SMS and WhatsApp channels.Legend Icon Meaning ✅ Supported ⚠️ Partially supported, limited, or with conditions (see the cell) ❌ Not supported 1. Channel comparison summary 📧 Email 💬 SMS 🟢 WhatsApp What the Blip channel is Two-way, conversational email channel for bots: text and file attachments, no HTML [B6][B7] SMS channel with API sends and portal blasts; replies can be routed to bots or human agents [B10][B42] WhatsApp channel with templates, interactive messages, Flows, catalog, campaigns, bots and human agents [B12]–[B29] Overall fit Conversational use cases. Not a feature-for-feature match for ACS Email. Good fit for two-way and campaign SMS. Sender setup, country coverage and carrier registration are arranged with your Blip Account Manager. Broadest overlap with ACS, plus additional capabilities Largest change No HTML, CC/BCC, custom sending domain, SMTP relay or suppression management SMS content must match a template registered with Blip support [B10][B11] Different API and event model; number migration to Blip as the new provider Number or domain move Custom sending domains are not supported ACS port-out is supported [M1]; plan the Blip port-in with your Blip Account Manager Incoming number portability is supported [B13][M1] 2. Architecture and integration changesACS and Blip use different request, authentication and event models: Topic ACS Blip Programming model One client per service (EmailClient, SmsClient, NotificationMessagesClient), each with its own payload schema One message model for every channel. The recipient address (name@domain) selects the channel, and content is adapted to each channel's capabilities [B1] Sending POST to the service endpoint, asynchronous (for example, email returns 202 and an operation ID) [M10] POST to the bot's HTTP messages endpoint (https://{contract-id}.http.msging.net/messages) [B2][B7] Authentication Access key or Microsoft Entra ID [M45] Bot access key sent as Authorization: Key; SDK identifier + access key [B2][B4] Receiving messages Event Grid subscription (webhook, Azure Functions, Logic Apps and others) [M9][M22][M39] Public HTTPS endpoint configured in the Blip portal, or an SDK connection [B2][B4] Status tracking Event Grid status events, plus a status API for email [M9][M11][M15] Notifications to a notification URL. Logged notifications can be queried for up to 3 days (logging is off by default) [B3][B40] Status vocabulary Per service (email statuses, SMS delivery report, WhatsApp delivery status) Unified: accepted, dispatched, received, consumed, failed. Availability depends on the channel [B3] Webhook security Event Grid Separate message and notification URLs. Blip can call them with OAuth 2.0 (client credentials only) or custom headers [B2] SDKs .NET, Java, JavaScript, Python [M11][M21][M29] Platform SDKs: C#, JavaScript; Python guide [B4][B44] Platform API limits Per service [M3][M19] Messages: 3/s (free), 50/s (paid). HTTP 429 for 2 minutes when exceeded [B5] Low-code / no-code Not part of ACS. Customers build their own app, or use Copilot Studio for WhatsApp [M35] Builder, Desk, Studio and Active Campaign [B25]–[B28] Code and architecture changes to plan for Replace the service clients. Remove the per-service ACS clients and send through Blip's single message API or an SDK. Channel selection moves from the client type to the recipient address. Re-map identifiers. ACS operation IDs, channel registration IDs and Event Grid event types have no direct equivalent in Blip. Use the Blip message id and notifications instead [B3]. Replace Event Grid subscriptions. Expose a public HTTPS endpoint for inbound messages and one for notifications, or connect through an SDK. Decide whether to enable OAuth 2.0 on the webhook [B2]. Rework status handling. Map your ACS delivery, bounce and engagement handling to Blip's notification statuses, which depend on the channel: email reports received, consumed (opened) and failed; SMS reports dispatched, received and failed; WhatsApp reports received, consumed (read) and failed [B3]. Respect Blip rate limits. Add handling for HTTP 429 and for the 3/s (free) or 50/s (paid) message limit [B5]. Re-create credentials and secrets. Swap the ACS access key or Entra ID authentication for the Blip bot access key [B2]. Decide where logic lives. Blip can host conversational logic in Builder or Studio. Otherwise, keep your own application and use Blip as the messaging layer [B26][B27]. 3. Email3.1 Capabilities Capability ACS Email Blip Email Outbound email ✅ Transactional, bulk and marketing [M2] ✅ Sent by the bot via API, SDK or Builder [B6][B7] Inbound email and two-way conversations ❌ Outbound only. The email SDK exposes only send and get-status, and Event Grid email events cover only delivery and engagement reports; no inbound email API or event is documented [M2][M9][M11][M43] ✅ Users email the bot; the message enters the bot flow as text (with attachments as media), with quoted reply history and signatures removed [B6][B9] Plain-text body ✅ [M10] ✅ Text formatting such as bold and italic is removed, and menu (select) messages are sent as a numbered list [B7] HTML body ✅ [M10] ❌ Not supported. Emails are sent as plain text, and the HTML part of incoming email is ignored [B7] File attachments ✅ Up to 10 MB per request; up to 30 MB on request [M3][M12] ✅ Supported in both directions: a media message is sent as one attachment, and attachments in incoming email reach the bot as media. Files follow Blip's media policy: virus-scanned, supported media types only (images, audio, video, PDF, Office documents, ZIP/RAR archives, CSV, HTML and plain text) [B30]. The effective size limit is set by the mail transport and the recipient's mail server, typically about 25 MB per message Inline images (CID) ✅ [M13] ❌ Not supported CC / BCC / multiple recipients ✅ Up to 50 recipients [M3] ❌ One recipient per message. Send one message per recipient Reply-To, custom headers ✅ [M10] ❌ Not supported Platform-managed sending domain ✅ Azure-managed domain [M4] ✅ Each bot sends from its own address on a Blip-managed domain, documented as <bot-id>@blip.bot [B7] Custom sending domain, SPF / DKIM ✅ [M4] ❌ Not supported Multiple sender addresses / display name ✅ Up to 100 sender usernames per domain [M3][M14] ❌ One sender address per bot, with no display name Delivery status events ✅ Delivered, Bounced, Suppressed, FilteredSpam, Quarantined and more [M9][M15] ⚠️ received (delivered) and failed (send rejected, with a reason) notifications only. Bounce, spam and suppression events are not reported [B3] Subject line ✅ Set per message [M10] ✅ Set per message with the mail.subject metadata; the default is the bot identifier. Replies reuse the incoming subject (see Reply threading) Open and click tracking ✅ [M8] ⚠️ Open tracking only, reported as a consumed notification. Click tracking is not supported [B3] Suppression lists / unsubscribe management ✅ [M6][M7] ❌ Not supported SMTP relay ✅ [M5] ❌ Not supported. Email is sent through the Blip API Bulk / marketing email ✅ [M2] ❌ Not a bulk or marketing email service. Each message has one recipient, and there is no unsubscribe management Reply threading ❌ Not listed among the ACS Email features [M2][M11] ✅ Replies reuse the subject of the incoming email, and are sent from the address the user wrote to, for about 7 days Unread-message email ❌ Not listed among the ACS Email features [M2][M11] ✅ Blip can email a user who has unread messages, with a subject and text configurable per bot, at most once every 12 hours by default Published email rate and size limits ✅ [M3] ⚠️ Blip does not apply email-specific rate or size limits. Platform message limits [B5] and the media policy [B30] apply, and recipient mail servers enforce their own limits; see Section 3 Analytics ✅ Email Insights, Azure Monitor logs [M15][M16] ⚠️ Generic Analytics extension [B38] 3.2 What changes ACS concept Blip equivalent Source Email Communication Service resource A Blip bot, which has the email channel built in [B8] Azure-managed domain (*.azurecomm.net) Blip-managed sender address per bot, documented as <bot-id>@blip.bot [B7] Custom verified domain + SPF/DKIM records Not supported – EmailClient.beginSend / POST /emails:send Message POST with type: text/plain (or a media link for an attachment) to the recipient address with @ encoded as %40, followed by @mailgun.gw.msging.net; set the subject with the mail.subject metadata. SDK send and Builder HTTP actions work the same way [B6][B7] Operation ID + Get Status Message id + notifications to the notification URL [B3] Event Grid delivery report events received notification when delivered, or a failed notification with a reason when the send is rejected. Bounce, suppression and spam events are not available [B3] Event Grid engagement report events consumed notification when the email is opened. Click events are not available [B3] SMTP (smtp.azurecomm.net) Not available. Send through the Blip API – Suppression lists Not supported – Email Insights / Azure Monitor logs Blip Analytics extension (generic) [B38] 4. SMS4.1 Capabilities Capability ACS SMS Blip SMS Outbound SMS ✅ [M18] ✅ API (+<number>@sms.gw.msging.net) and portal sends [B42][B10] Inbound / two-way SMS ✅ All sender types except alphanumeric [M18] ✅ Replies arrive as text messages in your bot, and blast replies can be routed to a smart contact or a human agent [B10] Sender types ✅ Toll-free (US, PR, CA), short code (US, CA, UK), 10DLC (US), alphanumeric and mobile numbers (selected countries) [M18][M20] ⚠️ The sender is configured per account when SMS is activated. Confirm the sender type for each country with your Blip Account Manager Number acquisition ⚠️ Azure portal. Limited to existing customers whose resources already have ACS numbers [M1] ⚠️ Not self-service: SMS sending is activated through your Blip Account Manager [B42] Published country coverage ✅ [M18][M20] ⚠️ Coverage is confirmed per account by your Blip Account Manager. Recipient numbers must include the country code; numbers without one are treated as Brazilian numbers Long (concatenated) messages ✅ [M19] ✅ Billed per segment [B10] Special characters ✅ GSM-7: 160, UCS-2: 70 chars per segment [M19] ✅ 160 (simple) / 70 (special) chars per segment [B10] MMS ⚠️ Private preview only [M25] ❌ Not supported. Blip SMS carries text only Delivery reports ✅ Event Grid [M22] ✅ Notifications: dispatched (handed to the carrier), received (delivered to the handset) and failed (rejected, expired or undeliverable, with a reason code and description) [B3] Opt-out / STOP handling ✅ Sender-dependent: automatic handling for toll-free and US short codes; other cases vary. Opt-Out Management API is in preview [M18][M19][M23] ❌ No automatic opt-out list or opt-out API. Replies such as STOP reach your bot like any other reply, and your bot must honor them Regulatory registration (toll-free, 10DLC, short code) ✅ [M19] ⚠️ Carrier registration is handled during account setup. Confirm requirements for your traffic and countries with your Blip Account Manager Pre-approved content ❌ No message-template requirement for SMS content ⚠️ Required. Every SMS text must match a template registered with Blip support [B10][B11] Bulk sending ✅ Multiple recipients per request [M19] ✅ Portal blasts from CSV with variables; API sends to distribution lists [B10][B42] Scheduled sending ❌ Not listed among the ACS SMS features [M21][M41] ✅ Portal blasts: send now or schedule [B10] Published throughput ✅ For example, toll-free 200/min, short code 6,000/min per number [M18] ⚠️ Platform limits of 3 messages/s (free) and 50 messages/s (paid) [B5]. Confirm carrier throughput for your sender with your Blip Account Manager Number porting ✅ Port-out from ACS supported (re-verification may be needed) [M1] ⚠️ Plan number porting with your Blip Account Manager Bots / human agents on replies ❌ Not part of ACS SMS ✅ [B10] Analytics ✅ SMS Insights, logs, metrics [M24] ✅ Portal "Sending Summary" report [B10] 4.2 What changes ACS concept Blip equivalent Source Communication Services resource + phone numbers Blip bot with SMS activated through your Blip Account Manager, who also sets up the sender [B42][B10] Toll-free verification / 10DLC / short-code program brief Carrier registration is arranged with your Blip Account Manager. Template registration with Blip support is a separate, mandatory step [B11] Port numbers out of ACS ACS: support ticket + the destination provider's port-in process [M1]. Blip: plan the port-in with your Blip Account Manager [M1] SmsClient.send Message POST (text/plain) to +<number>@sms.gw.msging.net; for several recipients, a distribution list; or a portal blast [B42][B10] Event Grid SMSReceived Message delivered to the bot's message webhook or SDK [B2] Event Grid SMSDeliveryReportReceived Notifications: dispatched, received or failed [B3] Opt-out Management API / STOP keywords No equivalent. Your bot receives the reply and must handle it – SMS Insights / logs Portal "Sending Summary" [B10] 5. WhatsApp5.1 Capabilities Capability ACS Advanced Messaging Blip WhatsApp WhatsApp Business Account onboarding ✅ Embedded signup in the Azure portal [M27][M28] ✅ "Connect to Facebook" flow in the Blip portal [B12] Number migration between providers ✅ Out of ACS to a provider that supports WhatsApp's process [M1] ✅ Incoming portability from another provider, including numbers already on the WhatsApp Cloud API [B13][B14] Template messages (marketing, utility, authentication) ✅ Text, media, interactive (quick reply, call to action) and location-header templates [M28][M40][M44] ✅ [B15] Template creation and approval tracking ⚠️ Created in Meta WhatsApp Manager [M28] ✅ Create, submit and track in the Blip portal, or list, create and delete through the Blip API [B15] 24-hour session messages ✅ [M29] ✅ [B16] Inbound messages ✅ [M30] ✅ Text, media, location, contact cards, stickers, interactive replies and Flow responses reach the bot as messages [B2] Stickers ✅ [M33] ✅ [B23] Location messages ⚠️ Only as a location parameter in a template header; no standalone location message [M44] ✅ Send and receive native location messages Contact cards ❌ Not listed among the supported ACS message types [M26][M29][M44] ✅ Send and receive Reactions ✅ Send and receive [M30][M32] ⚠️ Receive only. Blip has no content type to send reactions [B37] Reply buttons and list messages ✅ [M31] ✅ Up to 3 reply buttons (20 characters each) and 10 list options (24 characters each); body up to 1,024 characters. No template approval is needed [B17] CTA URL buttons ✅ Interactive CTA URL message [M31] ✅ Interactive CTA URL messages as dynamic JSON content; also in templates and carousels, and in utility messages through Direct Send (Open Beta) [B17][B15][B31][B43] Carousels ❌ Not among the supported template or interactive types [M44] ✅ [B31] WhatsApp Flows ❌ Not listed among the supported ACS message types [M26][M29][M44] ✅ Send Flows and receive Flow responses; create, publish and deprecate Flows [B18] Catalog / product messages, cart, orders ❌ Not listed among the supported ACS message types [M26][M29][M44] ✅ [B19] Payments ❌ Not listed among the supported ACS message types [M26][M29][M44] ⚠️ Payment block (Brazil and India); active payment messages in Alpha [B20][B21] Delivery and read receipts ✅ [M26][M30] ✅ Notifications: received (delivered), consumed (read) and failed (with the error details) [B3] Typing indicator / mark as read ❌ Not listed among the supported ACS features [M26][M29] ✅ Enabled per bot [B22] WhatsApp usernames / BSUID ✅ [M34] ✅ Supported [B24] WhatsApp Groups ❌ Not listed among the supported ACS features [M26] ⚠️ Create and manage groups, members and invite links through the Blip API; subject to Meta eligibility Voice calling ❌ Not part of ACS Advanced Messaging ✅ Blip Calls in Desk (requires contracting; Meta eligibility applies) [B29] Campaigns / bulk sending ⚠️ Recipient lists in the SDK; no campaign tool documented [M29] ✅ Active Campaign with audiences, dispatch and reports [B25] No-code conversational flows ❌ Customer-built ✅ Builder [B26] AI agents ✅ Copilot Studio agents [M35] ✅ Blip Studio AI agents [B27] Human agent desk ❌ Not part of ACS. Dynamics 365 is a separate offering [M1] ✅ Blip Desk [B28] Media size limits ⚠️ Only sticker limits are documented [M33] ⚠️ 100 MB documents, 16 MB audio/video; stickers 100 KB; template attachments up to 16 MB [B30][B23] Throughput ⚠️ Set by Meta's messaging limits and your number's quality rating [M40] ⚠️ Set by Meta's messaging limits and your number's quality rating. Blip platform limits of 3 messages/s (free) and 50 messages/s (paid) also apply [B5] Analytics ✅ Azure Monitor metrics and logs [M36][M42] ✅ Campaign and agent productivity reports [B38] 5.2 What changes ACS concept Blip equivalent Source Channel registration in the Azure portal Blip portal → Channels → WhatsApp → Connect (Facebook authorization, WABA and number selection) [B12] Existing ACS-connected number Meta number migration to Blip as the destination provider (prerequisites below) [M1][B13] Approved templates Copied to the new WABA during portability; validate afterward [B13] channelRegistrationId + NotificationMessagesClient Bot credentials + message POST or SDK send [B2][B4] MessageTemplateClient.GetTemplates Portal Contents → Message Templates, or the Blip API to list, create and delete templates [B15] Event Grid AdvancedMessageReceived Message webhook or SDK receiver [B2] Event Grid AdvancedMessageDeliveryStatusUpdated Blip notifications [B3] Phone number / BSUID addressing Blip WhatsApp identity model with BSUID support [B24] Conversation history, consent records, bot logic Not imported automatically. Export your data from ACS [M1], keep opt-in records in your own systems, and rebuild bot logic in Builder or Studio, or keep it in your application [M1] 6. What Blip adds beyond the ACS experienceThese Blip capabilities are not listed in the ACS documentation for the same channels. Where ACS is ahead, for example HTML email, CC/BCC and custom sending domains for email, or sending WhatsApp reactions, see Sections 4–6. Capability Channel Source Inbound email and two-way email conversations with bots; reply threading; unread-message emails Email [B6][B9] (ACS Email: [M2][M9][M11][M43]) Routing SMS replies to a bot or a human agent SMS [B10] SMS blasts from CSV with variables, with scheduling and a sending summary SMS [B10] WhatsApp Flows WhatsApp [B18] Catalog, product messages, cart and orders WhatsApp [B19] Carousels WhatsApp [B31] Typing indicator and read marking (enabled per bot) WhatsApp [B22] Native location messages and contact cards WhatsApp – WhatsApp Groups management (subject to Meta eligibility) WhatsApp – Template creation, submission and approval tracking in the Blip portal and through the Blip API WhatsApp [B15] Payments (payment block in Brazil and India; active payment messages in Alpha) WhatsApp [B20][B21] Voice calling (Blip Calls, requires contracting) WhatsApp [B29] Active Campaign (audiences, dispatch and reports) WhatsApp [B25] Builder (visual, no-code flows) Blip channels (availability depends on the channel) [B26] Studio AI agents Blip channels (availability depends on the channel) [B27] Desk (human agent handoff) Blip channels (availability depends on the channel) [B28] One API and webhook model across channels, plus other channels (Instagram, Messenger, Telegram, Microsoft Teams, Apple Messages for Business, Google RCS and others) Platform [B1][B2][B32] SourcesMicrosoft (Azure Communication Services) Ref Source M1 Retirement and breaking changes guide for Azure Communication Services M2 Email overview M3 Service limits – Email M4 Email domains and sender authentication M5 Email SMTP overview M6 Email opt-out management (suppression lists) M7 Managed suppression list M8 Enable user engagement tracking M9 Handle email events M10 Email REST API – Send M11 Email SDK features M12 Allowed attachment MIME types M13 Inline attachments M14 Add multiple sender addresses M15 Email logs M16 Email Insights M18 SMS concepts M19 SMS FAQ M20 SMS number types M21 SMS SDK features M22 Handle SMS events M23 SMS opt-out management API M24 SMS Insights M25 Apply for a short code (MMS private preview note) M26 Advanced Messaging for WhatsApp overview M27 Connect a WhatsApp Business Account M28 WhatsApp template messages M29 Send WhatsApp text and media messages M30 Advanced Messaging Event Grid events M31 Send interactive messages M32 Send reaction messages M33 Send sticker messages M34 WhatsApp usernames and BSUID M35 WhatsApp channel prerequisites (Copilot Studio) M36 Advanced Messaging metrics M39 Handle Advanced Messaging events M40 WhatsApp Business Account FAQ M41 Send an SMS message (quickstart) M42 Advanced Messaging logs M43 Azure Communication Services – Email events (Event Grid) M44 Send WhatsApp template messages (supported template types) M45 Authentication in Azure Communication Services Blip Ref Source B1 Blip Docs – Concepts and channels B2 Blip Docs – Using HTTP (sending, receiving, webhooks, authentication) B3 Blip Docs – Notifications B4 Blip Docs – SDKs B5 Blip Docs – Throughputs B6 Blip Docs – E-mail channel B7 How to send email by the chatbot through Builder B8 How to publish your chatbot in email B9 How to interact with users through email B10 How to send SMS blasts via the Blip platform B11 SMS channel change – template requirement (PT) B12 How to connect the WhatsApp channel in Blip (PT) B13 WhatsApp API number portability (PT) B14 How to migrate a WhatsApp number (PT) B15 How to create, approve and use WhatsApp templates (PT) B16 Blip Docs – WhatsApp B17 WhatsApp interactive messages (PT) B18 What is WhatsApp Flows (PT) B19 Multi-product list, cart and sales on WhatsApp (PT) B20 Payment flows with the payment block (PT) B21 Active payment messages – Alpha (PT) B22 New WhatsApp message parameters – typing indicator, read receipt, voice notes (PT) B23 WhatsApp stickers (PT) B24 WhatsApp usernames and BSUID in Blip (PT) B25 Blip Docs – Active Campaign B26 Blip Docs – Using Builder B27 Blip Studio – AI agents (PT) B28 Blip Docs – Desk B29 Blip Calls – calls in Desk (PT) B30 Media upload policy (PT) B31 Carousel – dynamic content (PT) B32 Blip website B37 Blip Docs – Reaction B38 Blip Docs – Analytics · Campaign report · Agent productivity B40 Blip Docs – Get notifications of a message · Toggle message and notification logs B42 FAQ – Channels B43 [Open Beta] Direct Send for Utility Messages · via the Growth API B44 Blip SDK packages: C# – NuGet Take.Blip.Client; JavaScript – npm blip-sdk; Python – PyPI blip-sdk Need more help? Explore our content on Blip Academy or Blip Community, watch tutorials on our YouTube channel or get your questions answered through our support channel 😃 Related articles Blip Calls: Making Calls in Desk How to connect to a personalized service channel