Azure.Communication.Sms
1.1.0-beta.2
Prefix Reserved
dotnet add package Azure.Communication.Sms --version 1.1.0-beta.2
NuGet\Install-Package Azure.Communication.Sms -Version 1.1.0-beta.2
<PackageReference Include="Azure.Communication.Sms" Version="1.1.0-beta.2" />
paket add Azure.Communication.Sms --version 1.1.0-beta.2
#r "nuget: Azure.Communication.Sms, 1.1.0-beta.2"
// Install Azure.Communication.Sms as a Cake Addin #addin nuget:?package=Azure.Communication.Sms&version=1.1.0-beta.2&prerelease // Install Azure.Communication.Sms as a Cake Tool #tool nuget:?package=Azure.Communication.Sms&version=1.1.0-beta.2&prerelease
Azure Communication SMS client library for .NET
This package contains a C# SDK for Azure Communication Services for SMS and Telephony.
Source code | Package (NuGet) | Product documentation
Getting started
Install the package
Install the Azure Communication SMS client library for .NET with NuGet:
dotnet add package Azure.Communication.Sms
Prerequisites
You need an Azure subscription and a Communication Service Resource to use this package.
To create a new Communication Service, you can use the Azure Portal, the Azure PowerShell, or the .NET management client library.
Key concepts
SmsClient
provides the functionality to send messages between phone numbers.
Using statements
using System;
using Azure.Communication.Sms;
Authenticate the client
SMS clients can be authenticated using the connection string acquired from an Azure Communication Resource in the Azure Portal.
var connectionString = "<connection_string>"; // Find your Communication Services resource in the Azure portal
SmsClient client = new SmsClient(connectionString);
Alternatively, SMS clients can also be authenticated using a valid token credential. With this option,
AZURE_CLIENT_SECRET
, AZURE_CLIENT_ID
and AZURE_TENANT_ID
environment variables need to be set up for authentication.
string endpoint = "<endpoint_url>";
TokenCredential tokenCredential = new DefaultAzureCredential();
SmsClient client = new SmsClient(new Uri(endpoint), tokenCredential);
Examples
Send a 1:1 SMS Message
To send a SMS message, call the Send
or SendAsync
function from the SmsClient
.
SmsSendResult sendResult = await smsClient.SendAsync(
from: "<from-phone-number>", // Your E.164 formatted from phone number used to send SMS
to: "<to-phone-number>", // E.164 formatted recipient phone number
message: "Hi");
Console.WriteLine($"Sms id: {sendResult.MessageId}");
Send a 1:N SMS Message
To send a SMS message to a list of recipients, call the Send
or SendAsync
function from the SmsClient
with a list of recipient's phone numbers.
You may also add pass in an options object to specify whether the delivery report should be enabled and set custom tags.
var response = await smsClient.SendAsync(
from: "<from-phone-number>", // Your E.164 formatted from phone number used to send SMS
to: new string[] { "<to-phone-number-1>", "<to-phone-number-2>" }, // E.164 formatted recipient phone numbers
message: "Weekly Promotion!",
options: new SmsSendOptions(enableDeliveryReport: true) // OPTIONAL
{
Tag = "marketing", // custom tags
DeliveryReportTimeoutInSeconds = 90
});
foreach (SmsSendResult result in response.Value)
{
Console.WriteLine($"Sms id: {result.MessageId}");
Console.WriteLine($"Send Result Successful: {result.Successful}");
}
Troubleshooting
SMS operations will throw an exception if the request to the server fails.
Exceptions will not be thrown if the error is caused by an individual message, only if something fails with the overall request.
Please use the Successful
flag to validate each individual result to verify if the message was sent.
try
{
var response = await smsClient.SendAsync(
from: "<from-phone-number>" // Your E.164 formatted phone number used to send SMS
to: new string [] {"<to-phone-number-1>", "<to-phone-number-2>"}, // E.164 formatted recipient phone number
message: "Weekly Promotion!",
options: new SmsSendOptions(enableDeliveryReport: true) // OPTIONAL
{
Tag = "marketing", // custom tags
});
foreach (SmsSendResult result in response.Value)
{
if (result.Successful)
{
Console.WriteLine($"Successfully sent this message: {result.MessageId} to {result.To}.");
}
else
{
Console.WriteLine($"Something went wrong when trying to send this message {result.MessageId} to {result.To}.");
Console.WriteLine($"Status code {result.HttpStatusCode} and error message {result.ErrorMessage}.");
}
}
}
catch (RequestFailedException ex)
{
Console.WriteLine(ex.Message);
}
Next steps
- Read more about SMS in Azure Communication Services
- For a basic guide on how to configure Delivery Reporting for your SMS messages please refer to the Handle SMS Events quickstart.
Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit cla.microsoft.com.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
.NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen40 was computed. tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- Azure.Core (>= 1.44.1)
- System.Text.Json (>= 6.0.10)
-
net8.0
- Azure.Core (>= 1.44.1)
NuGet packages (14)
Showing the top 5 NuGet packages that depend on Azure.Communication.Sms:
Package | Downloads |
---|---|
OrchardCore.Application.Cms.Core.Targets
Orchard Core CMS is a Web Content Management System (CMS) built on top of the Orchard Core Framework. Converts the application into a modular OrchardCore CMS application with TheAdmin theme but without any front-end Themes. |
|
OrchardCore.Application.Cms.Targets
Orchard Core CMS is a Web Content Management System (CMS) built on top of the Orchard Core Framework. Converts the application into a modular OrchardCore CMS application with following themes. - TheAdmin Theme - SafeMode Theme - TheAgency Theme - TheBlog Theme - TheComingSoon Theme - TheTheme theme |
|
Soenneker.Communication.Sms.Client
An async thread-safe singleton for the Azure Communication Services SMS client |
|
Bot.Builder.Community.Adapters.ACS.SMS
Adapter for v4 of the Bot Builder .NET SDK to allow for a bot to be used with SMS via Azure Communication Services. |
|
Bot.Builder.Community.Adapters.ACS.SMS.Core
Core package containing request / response mapper, and helper methods for when using Bot Builder .NET ACS Adapter. |
GitHub repositories (4)
Showing the top 4 popular GitHub repositories that depend on Azure.Communication.Sms:
Repository | Stars |
---|---|
OrchardCMS/OrchardCore
Orchard Core is an open-source modular and multi-tenant application framework built with ASP.NET Core, and a content management system (CMS) built on top of that framework.
|
|
phongnguyend/Practical.CleanArchitecture
Full-stack .Net 8 Clean Architecture (Microservices, Modular Monolith, Monolith), Blazor, Angular 19, React 18, Vue 3, BFF with YARP, Domain-Driven Design, CQRS, SOLID, Asp.Net Core Identity Custom Storage, OpenID Connect, Entity Framework Core, OpenTelemetry, SignalR, Hosted Services, Health Checks, Rate Limiting, Cloud Services (Azure, AWS, GCP).
|
|
BotBuilderCommunity/botbuilder-community-dotnet
Part of the Bot Builder Community Project. Repository for extensions for the Bot Builder .NET SDK, including middleware, dialogs, recognizers and more.
|
|
Azure-Samples/communication-services-AI-customer-service-sample
A sample app for the customer support center running in Azure, using Azure Communication Services and Azure OpenAI for text and voice bots.
|
Version | Downloads | Last updated |
---|---|---|
1.1.0-beta.2 | 207 | 12/6/2024 |
1.1.0-beta.1 | 2,669 | 4/24/2024 |
1.0.1 | 1,152,014 | 5/25/2021 |
1.0.0 | 43,188 | 3/29/2021 |
1.0.0-beta.4 | 2,679 | 3/10/2021 |
1.0.0-beta.3 | 35,965 | 11/16/2020 |
1.0.0-beta.2 | 123,137 | 10/6/2020 |
1.0.0-beta.1 | 10,393 | 9/22/2020 |