Skip to content
This repository was archived by the owner on Jan 5, 2026. It is now read-only.

Commit 56a003d

Browse files
tracyboehrerTracy Boehrer
andauthored
Update 86.bot-authentication-fic readmes (#4036)
Co-authored-by: Tracy Boehrer <trboehre@microsoft.com>
1 parent 6952b9e commit 56a003d

2 files changed

Lines changed: 45 additions & 81 deletions

File tree

  • samples
    • csharp_dotnetcore/86.bot-authentication-fic
    • javascript_nodejs/86.bot-authentication-fic

samples/csharp_dotnetcore/86.bot-authentication-fic/README.md

Lines changed: 22 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -20,37 +20,31 @@ This bot has been created using [Bot Framework](https://dev.botframework.com/),
2020

2121
## To try this sample
2222

23-
- In a terminal, navigate to `AuthFederatedCredBot`
24-
25-
```bash
26-
# change into project folder
27-
cd 86.bot-authentication-fic
28-
```
29-
30-
31-
- Open from Visual Studio
32-
- Launch Visual Studio
33-
- File -> Open -> Project/Solution
34-
- Navigate to `samples/csharp_dotnetcore/86.bot-authentication-fic` folder
35-
- Select `AuthFederatedCredBot.csproj` file
36-
3723
- Create an user assigned managed identity.
38-
- Record the client ID of the managed identity and add the same to appsettings.json.
39-
40-
- Create Azure App and Bot
41-
- Create App Registration
42-
- This can be either Single or Multi tenant.
43-
- Record the Application ID.
44-
- Add the Federation Identity Certificate (FIC) to the App Registration.
45-
- To create trust using the FIC, we need to link the managed identity to the App Registration.
46-
- Click on the add credential under Federated Credential
47-
- On the Add a credential page, select the Federated credential scenario as "Customer Managed Keys".
24+
- Record the client ID of the managed identity.
25+
26+
- For a new bot
27+
- Create Azure App and Bot
28+
- Create App Registration
29+
- This can be either Single or Multi tenant.
30+
- Record the Application and Tenant ID's.
31+
- To create trust using the FIC, we need to link the managed identity to the App Registration. On the App Registration:
32+
- Click on the add credential under **Certificates & Secrets**, **Federated credentials**
33+
- On the Add a credential page, select the Federated credential scenario as **Customer Managed Keys**.
4834
- Select the managed identity that you created in the previous step.
4935
- Enter name for the credential and click on Add.
5036

51-
- Create an Azure Bot in the desired resource group. Use the App Registration from the previous step.
52-
53-
- Add the User managed identity created in previous step to the Azure App Service under Configuration -> Identity -> User Assigned Managed Identity.
37+
- Create an **Azure Bot** in the desired resource group and use the App Registration from the previous step.
38+
39+
- For an existing bot
40+
- Navigate to the **App Registration** for the **Azure Bot**
41+
- To create trust using the FIC, we need to link the managed identity to the App Registration. On the App Registration:
42+
- Click on the add credential under **Certificates & Secrets**, **Federated credentials**
43+
- On the Add a credential page, select the Federated credential scenario as **Customer Managed Keys**.
44+
- Select the managed identity that you created in the previous step.
45+
- Enter name for the credential and click on Add.
46+
- Navigate to the **App Service** for the bot
47+
- Add the User managed identity created in previous step to the Azure App Service under Configuration -> Identity -> User Assigned Managed Identity.
5448

5549
- Set appsettings.json variables
5650

@@ -62,28 +56,7 @@ This bot has been created using [Bot Framework](https://dev.botframework.com/),
6256

6357
- MicrosoftAppClientId: {clientId of managed identity}
6458

65-
- Run the bot from Visual Studio:
66-
67-
68-
69-
70-
71-
- Run the bot from a terminal or from Visual Studio, choose option A or B.
72-
73-
A) From a terminal
74-
75-
```bash
76-
# run the bot
77-
dotnet run
78-
```
79-
80-
B) Or from Visual Studio
81-
82-
- Launch Visual Studio
83-
- File -> Open -> Project/Solution
84-
- Navigate to `86.bot-authentication-fic` folder
85-
- Select `AuthFederatedCredBot.csproj` file
86-
- Press `F5` to run the project
59+
- A bot using Federated Credentials, like UserManagedIdentity, cannot be run locally. It must be deployed to Azure.
8760

8861
## Deploy the bot to Azure
8962

samples/javascript_nodejs/86.bot-authentication-fic/README.md

Lines changed: 23 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -17,36 +17,31 @@ This bot has been created using [Bot Framework](https://dev.botframework.com/),
1717

1818
## To try this sample
1919

20-
- In a terminal, navigate to `samples/javascript_nodejs/86.bot-authentication-fic`
21-
22-
```bash
23-
cd samples/javascript_nodejs/86.bot-authentication-fic
24-
```
25-
26-
- Install modules
27-
28-
```bash
29-
npm install
30-
```
31-
3220
- Create an user assigned managed identity.
33-
34-
- Record the client ID of the managed identity and add the same to .env file.
35-
36-
- Create Azure App and Bot
37-
38-
- Create App Registration
39-
- This can be either Single or Multi tenant.
40-
- Record the Application ID.
41-
- Add the Federation Identity Certificate (FIC) to the App Registration.
42-
- To create trust using the FIC, we need to link the managed identity to the App Registration.
43-
- Click on the add credential under Federated Credential
44-
- On the Add a credential page, select the Federated credential scenario as "Customer Managed Keys".
21+
- Record the client ID of the managed identity.
22+
23+
- For a new bot
24+
- Create Azure App and Bot
25+
- Create App Registration
26+
- This can be either Single or Multi tenant.
27+
- Record the Application and Tenant ID's.
28+
- To create trust using the FIC, we need to link the managed identity to the App Registration. On the App Registration:
29+
- Click on the add credential under **Certificates & Secrets**, **Federated credentials**
30+
- On the Add a credential page, select the Federated credential scenario as **Customer Managed Keys**.
4531
- Select the managed identity that you created in the previous step.
4632
- Enter name for the credential and click on Add.
47-
- Create an Azure Bot in the desired resource group. Use the App Registration from the previous step.
48-
49-
- Add the User managed identity created in previous step to the Azure App Service under Configuration -> Identity -> User Assigned Managed Identity.
33+
34+
- Create an **Azure Bot** in the desired resource group and use the App Registration from the previous step.
35+
36+
- For an existing bot
37+
- Navigate to the **App Registration** for the **Azure Bot**
38+
- To create trust using the FIC, we need to link the managed identity to the App Registration. On the App Registration:
39+
- Click on the add credential under **Certificates & Secrets**, **Federated credentials**
40+
- On the Add a credential page, select the Federated credential scenario as **Customer Managed Keys**.
41+
- Select the managed identity that you created in the previous step.
42+
- Enter name for the credential and click on Add.
43+
- Navigate to the **App Service** for the bot
44+
- Add the User managed identity created in previous step to the Azure App Service under Configuration -> Identity -> User Assigned Managed Identity.
5045

5146
- Set .env variables
5247

@@ -58,11 +53,7 @@ This bot has been created using [Bot Framework](https://dev.botframework.com/),
5853

5954
- MicrosoftAppClientId: {clientId of managed identity}
6055

61-
- Start the bot
62-
63-
```bash
64-
npm start
65-
```
56+
- A bot using Federated Credentials, like UserManagedIdentity, cannot be run locally. It must be deployed to Azure.
6657

6758
## Deploy the bot to Azure
6859

0 commit comments

Comments
 (0)