Skip to content

Commit af6ae42

Browse files
authored
Merge pull request #298454 from vac0224/vc-urgent-toc-2025-04-18
Fix missing SMS articles
2 parents 497b1ea + 8d41c6c commit af6ae42

File tree

6 files changed

+32
-30
lines changed

6 files changed

+32
-30
lines changed

articles/communication-services/concepts/sms/ten-digit-long-code-guidelines.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Ten digit long code (10DLC) registration guidelines
3-
titleSuffix: An Azure Communication Services concept document
3+
titleSuffix: An Azure Communication Services article
44
description: This article describes how to prepare for 10 digit long code (10DLC) brand registration and campaign registration.
55
author: prakulka
66
manager: darmour
@@ -16,7 +16,7 @@ ms.custom: references_regions
1616

1717
# Ten digit long code (10DLC) registration guidelines
1818

19-
To send Application-to-Person (A2P) SMS messages using 10 digit long codes (10DLC), businesses must complete **brand registration** and **campaign registration**. This ensures compliance with carrier and CTIA guidelines while enabling high-quality message delivery.
19+
To send Application-to-Person (A2P) SMS messages using 10 digit long codes (10DLC), businesses must complete **brand registration** and **campaign registration**. Registering ensures compliance with carrier and Cellular Telecommunications Industry Association (CTIA) guidelines while enabling high-quality message delivery.
2020

2121
This article describes how to complete the required fields for **brand registration** and **campaign registration**.
2222

@@ -44,7 +44,7 @@ Brand registration typically takes 2 to 3 business days with TCR (The Campaign R
4444
| **Brand Name** | Official name of your organization. | Contoso Inc. |
4545
| **EIN / Tax ID** | Employer Identification Number or Tax ID (required for non-Sole Proprietor entities). | 12-3456789 |
4646
| **Business Type** | Select the appropriate business type (Sole Proprietor, LLC, Corporation, and so on). | Corporation |
47-
| **Website** | Website URL associated with your business (used for verification). | https://www.contoso.com |
47+
| **Website** | Website URL associated with your business (used for verification). | `https://www.contoso.com` |
4848
| **Vertical** | Industry in which your business operates. | E-commerce |
4949
| **Email Address** | Contact email for registration-related updates. | [email protected] |
5050

@@ -56,7 +56,7 @@ Brand registration typically takes 2 to 3 business days with TCR (The Campaign R
5656

5757
## Campaign registration
5858

59-
Campaign registration enables you to specify the purpose of your messaging (such as marketing, customer service, or two-factor authentication) and how you plan to use 10DLC numbers. This step ensures that your use case complies with regulations and that carriers can properly route and filter messages based on the campaign type.
59+
Campaign registration enables you to specify the purpose of your messaging (such as marketing, customer service, or two-factor authentication) and how you plan to use 10DLC numbers. This step ensures that your use case complies with regulations so carriers can properly route and filter messages based on the campaign type.
6060

6161
Campaign details must accurately reflect the content and intent of your messages. Providing false or misleading information could lead to rejections or delays in the approval of your campaign.
6262

@@ -72,10 +72,10 @@ Campaign registration with TCR typically takes 3 to 5 business days for approval
7272
| **Campaign Name** | Name identifying your campaign. | Contoso Marketing Campaign |
7373
| **Campaign Description** | A detailed description of the campaign’s purpose. | Send promotional offers and updates to customers who opt in to Contoso's SMS notifications. |
7474
| **Use Case** | The primary purpose of the campaign (such as marketing or customer care). | Marketing |
75-
| **Message Samples** | Provide examples of the messages your campaign will send. | “Hello! Thank you for subscribing to Contoso updates. Reply STOP to opt out.” |
76-
| **Subscriber Opt-in** | Confirms that recipients have explicitly consented to receive messages. | “Thank you for subscribing to Contoso Alerts. Reply HELP for help, STOP to unsubscribe.” |
75+
| **Message Samples** | Provide examples of the messages your campaign plans to send. | “Hello! Thank you for subscribing to Contoso updates. Reply STOP to opt out.” |
76+
| **Subscriber Opt-in** | Confirms that recipients explicitly consent to receive messages. | “Thank you for subscribing to Contoso Alerts. Reply HELP for help, STOP to unsubscribe.” |
7777
| **Subscriber Opt-out** | Allows recipients to stop receiving messages at any time. | “You have unsubscribed from Contoso Alerts. Reply START to resubscribe.” |
78-
| **Subscriber Help** | Provides instructions or assistance to users. | “For assistance, visit [www.contoso.com](https://www.contoso.com) or call 1-800-CONTOSO.” |
78+
| **Subscriber Help** | Provides instructions or assistance to users. | “For assistance, visit `https://www.contoso.com` or call 1-800-CONTOSO.” |
7979
| **Embedded Links** | Indicates if messages include URLs. | Yes |
8080
| **Embedded Phone Numbers**| Indicates if messages include phone numbers. | Yes |
8181
| **Age-gated Content** | Indicates if messages are age-restricted. | No |
@@ -84,7 +84,7 @@ Campaign registration with TCR typically takes 3 to 5 business days for approval
8484

8585
1. When is brand vetting required?
8686

87-
Brand vetting for 10DLC messaging is typically required for companies outside the Russell 3000 list as these companies are considered as pre-vetted. Smaller businesses, companies without EIN, unverified brands may require brand vetting.
87+
Brand vetting for 10DLC messaging is typically required for companies outside the Russell 3000 list as these companies are considered as prevetted. Smaller businesses, companies without EIN, unverified brands may require brand vetting.
8888

8989
2. What happens when a brand is rejected during the 10DLC registration process?
9090

@@ -95,7 +95,7 @@ Brand vetting for 10DLC messaging is typically required for companies outside th
9595

9696
3. How are registration fees charged?
9797

98-
All fees for registration, including vetting fees, are charged at the time of submission and are non-refundable regardless of approval status.
98+
All fees for registration, including vetting fees, are charged at the time of submission and are nonrefundable regardless of approval status.
9999

100100
## Next steps
101101

articles/communication-services/quickstarts/sms/apply-for-ten-digit-long-code.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Apply for 10 digit long code (10DLC) brand registration and campaign registration
3-
titleSuffix: An Azure Communication Services quickstart
3+
titleSuffix: An Azure Communication Services article
44
description: This article describes how to apply for 10 digit long code (10DLC) brand registration and campaign registration.
55
author: prakulka
66
manager: darmour
@@ -123,7 +123,7 @@ Fill in the campaign and content attributes as follows:
123123
- **Subscriber Help**: Select **Yes** or **No** to indicate if subscriber help is available.
124124
- **Subscriber Help Answer**: If **Yes** is selected, provide the message for subscribers seeking assistance.
125125

126-
#### Additional attributes
126+
#### More attributes
127127

128128
- **Direct Lending or Loan Arrangement**: Indicate if the campaign involves any lending or loan arrangements.
129129
- **Embedded Link**: Select **Yes** or **No** to specify if the campaign includes an embedded link.
@@ -132,7 +132,7 @@ Fill in the campaign and content attributes as follows:
132132

133133
#### Terms and conditions
134134

135-
Affiliate marketing is not permitted on 10DLC numbers. Check the box to confirm that the campaign will not be used for Affiliate Marketing.
135+
Affiliate marketing isn't permitted on 10DLC numbers. Check the box to confirm that the campaign will not be used for Affiliate Marketing.
136136

137137
:::image type="content" source="./media/apply-for-brand-registration/campaign-registration-4.png" alt-text="Screenshot showing campaign registration form 4." lightbox="./media/apply-for-brand-registration/campaign-registration-4.png":::
138138

articles/communication-services/toc.yml

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,8 @@ items:
4040
href: concepts/identity-model.md
4141
- name: Access tokens for end users
4242
href: quickstarts/identity/access-tokens.md
43+
- name: Sign an HTTP Request using HMAC
44+
href: tutorials/hmac-header-tutorial.md
4345
- name: Authenticate services
4446
href: concepts/authentication.md
4547
- name: Enable managed identity
@@ -296,6 +298,8 @@ items:
296298
href: concepts/sms/messaging-policy.md
297299
- name: Short code program brief filling guidelines
298300
href: concepts/sms/program-brief-guidelines.md
301+
- name: Ten digit long code (10DLC) registration guidelines
302+
href: concepts/sms/ten-digit-long-code-guidelines.md
299303
- name: Opt-Out management overview
300304
href: concepts/sms/opt-out-api-concept.md
301305
- name: Events
@@ -332,10 +336,12 @@ items:
332336
href: quickstarts/sms/handle-sms-events.md
333337
- name: Apply for a short code
334338
href: quickstarts/sms/apply-for-short-code.md
335-
- name: Use Postman to send SMS messages
336-
href: tutorials/postman-tutorial.md
339+
# - name: Use Postman to send SMS messages
340+
# href: tutorials/postman-tutorial.md
337341
- name: Send short URL
338342
href: tutorials/sms-url-shortener.md
343+
- name: Apply for 10 digit long code (10DLC) registration
344+
href: quickstarts/sms/apply-for-ten-digit-long-code.md
339345
- name: Apply for toll-free verification
340346
href: quickstarts/sms/apply-for-toll-free-verification.md
341347
- name: Enable alphanumeric sender ID

articles/communication-services/tutorials/hmac-header-tutorial.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Tutorial - Learn How to Sign an HTTP Request with HMAC
3-
titleSuffix: An Azure Communication Services tutorial
4-
description: Learn how to sign an HTTP request for Azure Communication Services by using HMAC.
2+
title: Sign an HTTP Request using hash-based message authentication code (HMAC)
3+
titleSuffix: An Azure Communication Services article
4+
description: This article describes how to sign an HTTP request for Azure Communication Services by using HMAC.
55
author: alexandra142
66
manager: soricos
77
services: azure-communication-services
@@ -15,12 +15,12 @@ ms.custom: devx-track-python
1515
zone_pivot_groups: acs-programming-languages-csharp-python
1616
---
1717

18-
# Tutorial: Sign an HTTP request
18+
# Sign an HTTP request using hash-based message authentication code (HMAC)
1919

20-
In this tutorial, you learn how to sign an HTTP request with a hash-based message authentication code (HMAC) signature.
20+
This article describes how to sign an HTTP request with a hash-based message authentication code (HMAC) signature.
2121

2222
> [!NOTE]
23-
> We strongly encourage you to use [Azure SDKs](https://github.com/Azure/azure-sdk). The approach described here is a fallback option for cases when Azure SDKs can't be used for any reason.
23+
> We recommend using the [Azure SDKs](https://github.com/Azure/azure-sdk) to sign an HTTP request. The approach described in this article is a fallback option if Azure SDKs can't be used for any reason.
2424
2525
In this tutorial, you learn how to:
2626
> [!div class="checklist"]

articles/communication-services/tutorials/includes/hmac-header-csharp.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Sign an HTTP Request with C#
3-
description: This tutorial explains the C# version of signing an HTTP request with an HMAC signature for Azure Communication Services.
3+
description: This article describes how to use C# to sign an HTTP request with an HMAC signature for Azure Communication Services.
44
author: alexandra142
55
manager: soricos
66
services: azure-communication-services
@@ -12,8 +12,6 @@ ms.service: azure-communication-services
1212
---
1313
## Prerequisites
1414

15-
Before you get started, make sure to:
16-
1715
- Create an Azure account with an active subscription. If you don't have an Azure subscription, see [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
1816
- Install [Visual Studio](https://visualstudio.microsoft.com/downloads/).
1917
- Create an Azure Communication Services resource. If you don't have a resource, see [Create a Communication Services resource](../../quickstarts/create-communication-resource.md). You need to record your `resourceEndpoint` and `resourceAccessKey` parameters for this tutorial.
@@ -36,7 +34,7 @@ The `hmac-sha256-signature` consists of:
3634

3735
## Set up the authorization header
3836

39-
The following steps describe how to construct the authorization header.
37+
Complete the following steps to construct the authorization header.
4038

4139
### Create a new C# application
4240

@@ -46,7 +44,7 @@ In a console window, such as cmd, PowerShell, or Bash, use the `dotnet new` comm
4644
dotnet new console -o SignHmacTutorial
4745
```
4846

49-
Change your directory to the newly created app folder. Use the `dotnet build` command to compile your application.
47+
Change your directory to the newly created app folder. To compile your application, use the `dotnet build` command.
5048

5149
```console
5250
cd SignHmacTutorial

articles/communication-services/tutorials/includes/hmac-header-python.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Sign an HTTP Request with Python
3-
description: This tutorial explains the Python version of signing an HTTP request with an HMAC signature for Azure Communication Services.
3+
description: This article describes how to use Python to sign an HTTP request with an HMAC signature for Azure Communication Services.
44
author: maximrytych-ms
55
manager: anitharaju
66
services: azure-communication-services
@@ -12,12 +12,10 @@ ms.service: azure-communication-services
1212
---
1313
## Prerequisites
1414

15-
Before you get started, make sure to:
16-
1715
- Create an Azure account with an active subscription. If you don't have an Azure subscription, see [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
1816
- Download and install [Python](https://www.python.org/).
1917
- Download and install [Visual Studio Code](https://code.visualstudio.com/) or another integrated development environment (IDE) that supports Python.
20-
- Create an Azure Communication Services resource. If you don't have a resource, see [Create a Communication Services resource](../../quickstarts/create-communication-resource.md). You need your `resource_endpoint_name` and `resource_endpoint_secret` parameters for this tutorial.
18+
- Create an Azure Communication Services resource. If you don't have a resource, see [Create a Communication Services resource](../../quickstarts/create-communication-resource.md). You need your `resource_endpoint_name` and `resource_endpoint_secret` parameters for this example.
2119

2220
## Sign an HTTP request with Python
2321

@@ -37,7 +35,7 @@ The `hmac-sha256-signature` consists of:
3735

3836
## Set up the authorization header
3937

40-
The following steps describe how to construct the authorization header.
38+
Complete following steps to construct the authorization header.
4139

4240
### Create a new Python script
4341

0 commit comments

Comments
 (0)