You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communication-services/quickstarts/chat/quickstart-botframework-integration.md
+18-18Lines changed: 18 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ You will learn how to:
40
40
41
41
To use Azure Communication Services chat as a channel in Azure Bot Service, the first step is to deploy a bot. You can do so by following below steps:
42
42
43
-
### Provision an Azure bot service resource in Azure
43
+
### Create an Azure bot service resource in Azure
44
44
45
45
Refer to the Azure Bot Service documentation on how to [create a bot](/azure/bot-service/abs-quickstart?tabs=userassigned).
46
46
@@ -49,11 +49,11 @@ To use Azure Communication Services chat as a channel in Azure Bot Service, the
49
49
50
50
### Get Bot's MicrosoftAppId and MicrosoftAppPassword
51
51
52
-
Fetch your Azure bot's [Microsoft App Id and secret](/azure/bot-service/abs-quickstart?tabs=userassigned#to-get-your-app-or-tenant-id) as you will need those values for configurations.
52
+
Fetch your Azure bot's [Microsoft App ID and secret](/azure/bot-service/abs-quickstart?tabs=userassigned#to-get-your-app-or-tenant-id) as you will need those values for configurations.
53
53
54
54
### Create a Web App where the bot logic resides
55
55
56
-
You can check out some samples at [Bot Builder Samples](https://github.com/Microsoft/BotBuilder-Samples) and tweak them or use [Bot Builder SDK](/composer/introduction) to create one. One of the simplest samples is [Echo Bot](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore/02.echo-bot). Generally, the Azure Bot Service expects the Bot Application Web App Controller to expose an endpoint `/api/messages`, which handles all the messages reaching the bot. To create the bot application, you can either use Azure CLI to [provision an App Service](/azure/bot-service/provision-app-service?tabs=singletenant%2Cexistingplan) or provision from the portal using below steps.
56
+
You can check out some samples at [Bot Builder Samples](https://github.com/Microsoft/BotBuilder-Samples) and tweak them or use [Bot Builder SDK](/composer/introduction) to create one. One of the simplest samples is [Echo Bot](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore/02.echo-bot). Generally, the Azure Bot Service expects the Bot Application Web App Controller to expose an endpoint `/api/messages`, which handles all the messages reaching the bot. To create the bot application, you can either use Azure CLI to [create an App Service](/azure/bot-service/provision-app-service?tabs=singletenant%2Cexistingplan) or directly create from the portal using below steps.
57
57
58
58
1. Select `Create a resource` and in the search box, search for web app and select `Web App`.
59
59
@@ -64,7 +64,7 @@ To use Azure Communication Services chat as a channel in Azure Bot Service, the
3. Lastly, the above option opens the deployment config. Choose the Web App we had provisioned from the list of options it comes up with after signing into your Azure account. Once ready select `Finish` to complete the profile, and then select `Publish` to start the deployment.
109
+
3. Lastly, the above option opens the deployment config. Choose the Web App we had created from the list of options it comes up with after signing into your Azure account. Once ready select `Finish` to complete the profile, and then select `Publish` to start the deployment.
@@ -119,12 +119,12 @@ Now that bot is created and deployed, you will need an Azure Communication Servi
119
119
## Step 3 - Enable Azure Communication Services Chat channel
120
120
With the Azure Communication Services resource, you can set up the Azure Communication Services channel in Azure Bot to assign an Azure Communication Services User ID to a bot.
121
121
122
-
1. Go to your Bot Services resource on Azure portal. Navigate to `Channels` blade and select `Azure Communications Services - Chat` channel from the list provided.
122
+
1. Go to your Bot Services resource on Azure portal. Navigate to `Channels` configuration on the left pane and select `Azure Communications Services - Chat` channel from the list provided.
@@ -276,7 +276,7 @@ In addition to sending a plain text message, a bot is also able to receive many
276
276
277
277
Below are some samples to illustrate these features:
278
278
279
-
*### Send a welcome message when a new user is added to the thread
279
+
### Send a welcome message when a new user is added to the thread
280
280
The current Echo Bot logic accepts input from the user and echoes it back. If you would like to add extra logic such as responding to a participant added Azure Communication Services event, copy the following code snippets and paste into the source file: [EchoBot.cs](https://github.com/microsoft/BotBuilder-Samples/blob/main/samples/csharp_dotnetcore/02.echo-bot/Bots/EchoBot.cs)
Sending adaptive cards to the chat thread can help you increase engagement and efficiency and communicate with users in a variety of ways. You can send adaptive cards from a bot by adding them as bot activity attachments.
319
319
@@ -432,7 +432,7 @@ Event payload comprises all json fields in the message content except name field
432
432
#### Activities and fields
433
433
434
434
- Message activity
435
-
-`Id` (ACS Chat message Id)
435
+
-`Id` (ACS Chat message ID)
436
436
-`TimeStamp`
437
437
-`Text`
438
438
-`Attachments`
@@ -441,21 +441,21 @@ Event payload comprises all json fields in the message content except name field
441
441
-`MembersRemoved`
442
442
-`TopicName`
443
443
- Message update activity
444
-
-`Id` (Updated ACS Chat message Id)
444
+
-`Id` (Updated ACS Chat message ID)
445
445
-`Text`
446
446
-`Attachments`
447
447
- Message delete activity
448
-
-`Id` (Deleted ACS Chat message Id)
448
+
-`Id` (Deleted ACS Chat message ID)
449
449
- Event activity
450
450
-`Name`
451
451
-`Value`
452
452
- Typing activity
453
453
454
454
#### Other common fields
455
455
456
-
-`Recipient.Id` and `Recipeint.Name` (ACS Chat user id and display name)
457
-
-`From.Id` and `From.Name` (ACS Chat user id and display name)
458
-
-`Conversation.Id` (ACS Chat thread id)
456
+
-`Recipient.Id` and `Recipeint.Name` (ACS Chat user ID and display name)
457
+
-`From.Id` and `From.Name` (ACS Chat user ID and display name)
458
+
-`Conversation.Id` (ACS Chat thread ID)
459
459
-`ChannelId` (AcsChat if empty)
460
460
-`ChannelData` (ACS Chat message metadata)
461
461
@@ -481,11 +481,11 @@ Sometimes the bot wouldn't be able to understand or answer a question or a custo
481
481
482
482
### Bot gets a forbidden exception while replying to a message
483
483
484
-
- Verify that bot's Microsoft app id and secret are saved correctly in the bot configuration file uploaded to the webapp.
484
+
- Verify that bot's Microsoft App ID and secret are saved correctly in the bot configuration file uploaded to the webapp.
485
485
486
486
### Bot is not able to be added as a participant
487
487
488
-
- Verify that bot's ACS Id is being used correctly while sending a request to add bot to a chat thread.
488
+
- Verify that bot's ACS ID is being used correctly while sending a request to add bot to a chat thread.
0 commit comments