Updated README.md files (microsoft#3306)

mkcomer · Jun 4, 2021 · e6342cb · e6342cb
1 parent bc4d5d1
commit e6342cb
Show file tree

Hide file tree

Showing 34 changed files with 36 additions and 1,708 deletions.
diff --git a/samples/java_springboot/02.echo-bot/README.md b/samples/java_springboot/02.echo-bot/README.md
@@ -31,53 +31,8 @@ This sample is a Spring Boot app and uses the Azure CLI and azure-webapp Maven p
 Enter text in the emulator. The text will be echoed back by the bot.
 
 ## Deploy the bot to Azure
-As described on [Deploy your bot](https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-deploy-az-cli), you will perform the first 4 steps to setup the Azure app, then deploy the code using the azure-webapp Maven plugin.
-
-### 1. Login to Azure
-From a command (or PowerShell) prompt in the root of the bot folder, execute:  
-`az login`
-
-### 2. Set the subscription
-`az account set --subscription "<azure-subscription>"`
-
-If you aren't sure which subscription to use for deploying the bot, you can view the list of subscriptions for your account by using `az account list` command. 
-
-### 3. Create an App registration
-`az ad app create --display-name "<botname>" --password "<appsecret>" --available-to-other-tenants`
-
-Replace `<botname>` and `<appsecret>` with your own values.
-
-`<botname>` is the unique name of your bot.  
-`<appsecret>` is a minimum 16 character password for your bot. 
-
-Record the `appid` from the returned JSON
-
-### 4. Create the Azure resources
-Replace the values for `<appid>`, `<appsecret>`, `<botname>`, and `<groupname>` in the following commands:
-
-#### To a new Resource Group
-```
-az deployment sub create --name "echoBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="<appid>" appSecret="<appsecret>" botId="<botname>" botSku=S1 newAppServicePlanName="echoBotPlan" newWebAppName="echoBot" groupLocation="westus" newAppServicePlanLocation="westus"
-```
-
-#### To an existing Resource Group
-```
-az deployment group create --resource-group "<groupname>" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="<appid>" appSecret="<appsecret>" botId="<botname>" newWebAppName="echoBot" newAppServicePlanName="echoBotPlan" appServicePlanLocation="westus" --name "echoBot"
-```
-
-### 5. Update app id and password
-In src/main/resources/application.properties update 
-  - `MicrosoftAppPassword` with the botsecret value
-  - `MicrosoftAppId` with the appid from the first step
-
-### 6. Deploy the code
-- Execute `mvn clean package` 
-- Execute `mvn azure-webapp:deploy -Dgroupname="<groupname>" -Dbotname="<bot-app-service-name>"`
-
-If the deployment is successful, you will be able to test it via "Test in Web Chat" from the Azure Portal using the "Bot Channel Registration" for the bot.
-
-After the bot is deployed, you only need to execute #6 if you make changes to the bot.
 
+To learn more about deploying a bot to Azure, see [Deploy your bot to Azure](https://aka.ms/azuredeployment) for a complete list of deployment instructions.
 
 ## Further reading
 

diff --git a/samples/java_springboot/03.welcome-user/README.md b/samples/java_springboot/03.welcome-user/README.md
@@ -36,53 +36,7 @@ The primary goal when creating any bot is to engage your user in a  meaningful c
 
 ## Deploy the bot to Azure
 
-As described on [Deploy your bot](https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-deploy-az-cli), you will perform the first 4 steps to setup the Azure app, then deploy the code using the azure-webapp Maven plugin.
-
-### 1. Login to Azure
-From a command (or PowerShell) prompt in the root of the bot folder, execute:  
-`az login`
-
-### 2. Set the subscription
-`az account set --subscription "<azure-subscription>"`
-
-If you aren't sure which subscription to use for deploying the bot, you can view the list of subscriptions for your account by using `az account list` command. 
-
-### 3. Create an App registration
-`az ad app create --display-name "<botname>" --password "<appsecret>" --available-to-other-tenants`
-
-Replace `<botname>` and `<appsecret>` with your own values.
-
-`<botname>` is the unique name of your bot.  
-`<appsecret>` is a minimum 16 character password for your bot. 
-
-Record the `appid` from the returned JSON
-
-### 4. Create the Azure resources
-Replace the values for `<appid>`, `<appsecret>`, `<botname>`, and `<groupname>` in the following commands:
-
-#### To a new Resource Group
-```
-az deployment sub create --name "welcomeBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="<appid>" appSecret="<appsecret>" botId="<botname>" botSku=S1 newAppServicePlanName="welcomeBotPlan" newWebAppName="welcomeBot" groupLocation="westus" newAppServicePlanLocation="westus"
-```
-
-#### To an existing Resource Group
-```
-az deployment group create --resource-group "<groupname>" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="<appid>" appSecret="<appsecret>" botId="<botname>" newWebAppName="welcomeBot" newAppServicePlanName="welcomeBotPlan" appServicePlanLocation="westus" --name "welcomeBot"
-```
-
-### 5. Update app id and password
-In src/main/resources/application.properties update 
-  - `MicrosoftAppPassword` with the botsecret value
-  - `MicrosoftAppId` with the appid from the first step
-
-### 6. Deploy the code
-- Execute `mvn clean package` 
-- Execute `mvn azure-webapp:deploy -Dgroupname="<groupname>" -Dbotname="<bot-app-service-name>"`
-
-If the deployment is successful, you will be able to test it via "Test in Web Chat" from the Azure Portal using the "Bot Channel Registration" for the bot.
-
-After the bot is deployed, you only need to execute #6 if you make changes to the bot.
-
+To learn more about deploying a bot to Azure, see [Deploy your bot to Azure](https://aka.ms/azuredeployment) for a complete list of deployment instructions.
 
 ## Further reading
 

diff --git a/samples/java_springboot/05.multi-turn-prompt/README.md b/samples/java_springboot/05.multi-turn-prompt/README.md
@@ -36,53 +36,7 @@ The `botbuilder-dialogs` library includes a variety of pre-built prompt classes,
 
 ## Deploy the bot to Azure
 
-As described on [Deploy your bot](https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-deploy-az-cli), you will perform the first 4 steps to setup the Azure app, then deploy the code using the azure-webapp Maven plugin.
-
-### 1. Login to Azure
-From a command (or PowerShell) prompt in the root of the bot folder, execute:  
-`az login`
-
-### 2. Set the subscription
-`az account set --subscription "<azure-subscription>"`
-
-If you aren't sure which subscription to use for deploying the bot, you can view the list of subscriptions for your account by using `az account list` command. 
-
-### 3. Create an App registration
-`az ad app create --display-name "<botname>" --password "<appsecret>" --available-to-other-tenants`
-
-Replace `<botname>` and `<appsecret>` with your own values.
-
-`<botname>` is the unique name of your bot.  
-`<appsecret>` is a minimum 16 character password for your bot. 
-
-Record the `appid` from the returned JSON
-
-### 4. Create the Azure resources
-Replace the values for `<appid>`, `<appsecret>`, `<botname>`, and `<groupname>` in the following commands:
-
-#### To a new Resource Group
-```
-az deployment sub create --name "multiTurnPromptBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="<appid>" appSecret="<appsecret>" botId="<botname>" botSku=S1 newAppServicePlanName="multiTurnPromptBotPlan" newWebAppName="multiTurnPromptBot" groupLocation="westus" newAppServicePlanLocation="westus"
-```
-
-#### To an existing Resource Group
-```
-az deployment group create --resource-group "<groupname>" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="<appid>" appSecret="<appsecret>" botId="<botname>" newWebAppName="multiTurnPromptBot" newAppServicePlanName="multiTurnPromptBotPlan" appServicePlanLocation="westus" --name "multiTurnPromptBot"
-```
-
-### 5. Update app id and password
-In src/main/resources/application.properties update 
-  - `MicrosoftAppPassword` with the botsecret value
-  - `MicrosoftAppId` with the appid from the first step
-
-### 6. Deploy the code
-- Execute `mvn clean package` 
-- Execute `mvn azure-webapp:deploy -Dgroupname="<groupname>" -Dbotname="<bot-app-service-name>"`
-
-If the deployment is successful, you will be able to test it via "Test in Web Chat" from the Azure Portal using the "Bot Channel Registration" for the bot.
-
-After the bot is deployed, you only need to execute #6 if you make changes to the bot.
-
+To learn more about deploying a bot to Azure, see [Deploy your bot to Azure](https://aka.ms/azuredeployment) for a complete list of deployment instructions.
 
 ## Further reading
 

diff --git a/samples/java_springboot/06.using-cards/README.md b/samples/java_springboot/06.using-cards/README.md
@@ -43,53 +43,7 @@ When [designing the user experience](https://docs.microsoft.com/en-us/azure/bot-
 
 ## Deploy the bot to Azure
 
-As described on [Deploy your bot](https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-deploy-az-cli), you will perform the first 4 steps to setup the Azure app, then deploy the code using the azure-webapp Maven plugin.
-
-### 1. Login to Azure
-From a command (or PowerShell) prompt in the root of the bot folder, execute:  
-`az login`
-
-### 2. Set the subscription
-`az account set --subscription "<azure-subscription>"`
-
-If you aren't sure which subscription to use for deploying the bot, you can view the list of subscriptions for your account by using `az account list` command. 
-
-### 3. Create an App registration
-`az ad app create --display-name "<botname>" --password "<appsecret>" --available-to-other-tenants`
-
-Replace `<botname>` and `<appsecret>` with your own values.
-
-`<botname>` is the unique name of your bot.  
-`<appsecret>` is a minimum 16 character password for your bot. 
-
-Record the `appid` from the returned JSON
-
-### 4. Create the Azure resources
-Replace the values for `<appid>`, `<appsecret>`, `<botname>`, and `<groupname>` in the following commands:
-
-#### To a new Resource Group
-```
-az deployment sub create --name "usingCardsBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="<appid>" appSecret="<appsecret>" botId="<botname>" botSku=S1 newAppServicePlanName="usingCardsBotPlan" newWebAppName="usingCardsBot" groupLocation="westus" newAppServicePlanLocation="westus"
-```
-
-#### To an existing Resource Group
-```
-az deployment group create --resource-group "<groupname>" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="<appid>" appSecret="<appsecret>" botId="<botname>" newWebAppName="usingCardsBot" newAppServicePlanName="usingCardsBotPlan" appServicePlanLocation="westus" --name "usingCardsBot"
-```
-
-### 5. Update app id and password
-In src/main/resources/application.properties update 
-  - `MicrosoftAppPassword` with the botsecret value
-  - `MicrosoftAppId` with the appid from the first step
-
-### 6. Deploy the code
-- Execute `mvn clean package` 
-- Execute `mvn azure-webapp:deploy -Dgroupname="<groupname>" -Dbotname="<bot-app-service-name>"`
-
-If the deployment is successful, you will be able to test it via "Test in Web Chat" from the Azure Portal using the "Bot Channel Registration" for the bot.
-
-After the bot is deployed, you only need to execute #6 if you make changes to the bot.
-
+To learn more about deploying a bot to Azure, see [Deploy your bot to Azure](https://aka.ms/azuredeployment) for a complete list of deployment instructions.
 
 ## Further reading
 - [Spring Boot](https://spring.io/projects/spring-boot)

diff --git a/samples/java_springboot/07.using-adaptive-cards/README.md b/samples/java_springboot/07.using-adaptive-cards/README.md
@@ -44,53 +44,7 @@ A message exchange between user and bot can contain media attachments, such as c
 
 ## Deploy the bot to Azure
 
-As described on [Deploy your bot](https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-deploy-az-cli), you will perform the first 4 steps to setup the Azure app, then deploy the code using the azure-webapp Maven plugin.
-
-### 1. Login to Azure
-From a command (or PowerShell) prompt in the root of the bot folder, execute:  
-`az login`
-
-### 2. Set the subscription
-`az account set --subscription "<azure-subscription>"`
-
-If you aren't sure which subscription to use for deploying the bot, you can view the list of subscriptions for your account by using `az account list` command. 
-
-### 3. Create an App registration
-`az ad app create --display-name "<botname>" --password "<appsecret>" --available-to-other-tenants`
-
-Replace `<botname>` and `<appsecret>` with your own values.
-
-`<botname>` is the unique name of your bot.  
-`<appsecret>` is a minimum 16 character password for your bot. 
-
-Record the `appid` from the returned JSON
-
-### 4. Create the Azure resources
-Replace the values for `<appid>`, `<appsecret>`, `<botname>`, and `<groupname>` in the following commands:
-
-#### To a new Resource Group
-```
-az deployment sub create --name "adaptiveCardsBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="<appid>" appSecret="<appsecret>" botId="<botname>" botSku=S1 newAppServicePlanName="adaptiveCardsBotPlan" newWebAppName="adaptiveCardsBot" groupLocation="westus" newAppServicePlanLocation="westus"
-```
-
-#### To an existing Resource Group
-```
-az deployment group create --resource-group "<groupname>" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="<appid>" appSecret="<appsecret>" botId="<botname>" newWebAppName="adaptiveCardsBotBot" newAppServicePlanName="adaptiveCardsBotPlan" appServicePlanLocation="westus" --name "adaptiveCardsBotBot"
-```
-
-### 5. Update app id and password
-In src/main/resources/application.properties update 
-  - `MicrosoftAppPassword` with the botsecret value
-  - `MicrosoftAppId` with the appid from the first step
-
-### 6. Deploy the code
-- Execute `mvn clean package` 
-- Execute `mvn azure-webapp:deploy -Dgroupname="<groupname>" -Dbotname="<bot-app-service-name>"`
-
-If the deployment is successful, you will be able to test it via "Test in Web Chat" from the Azure Portal using the "Bot Channel Registration" for the bot.
-
-After the bot is deployed, you only need to execute #6 if you make changes to the bot.
-
+To learn more about deploying a bot to Azure, see [Deploy your bot to Azure](https://aka.ms/azuredeployment) for a complete list of deployment instructions.
 ## Further reading
 
 - [Spring Boot](https://spring.io/projects/spring-boot)

diff --git a/samples/java_springboot/08.suggested-actions/README.md b/samples/java_springboot/08.suggested-actions/README.md
@@ -38,54 +38,7 @@ Unlike buttons that appear within rich cards (which remain visible  and accessib
 
 ## Deploy the bot to Azure
 
-As described on [Deploy your bot](https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-deploy-az-cli), you will perform the first 4 steps to setup the Azure app, then deploy the code using the azure-webapp Maven plugin.
-
-### 1. Login to Azure
-From a command (or PowerShell) prompt in the root of the bot folder, execute:  
-`az login`
-
-### 2. Set the subscription
-`az account set --subscription "<azure-subscription>"`
-
-If you aren't sure which subscription to use for deploying the bot, you can view the list of subscriptions for your account by using `az account list` command. 
-
-### 3. Create an App registration
-`az ad app create --display-name "<botname>" --password "<appsecret>" --available-to-other-tenants`
-
-Replace `<botname>` and `<appsecret>` with your own values.
-
-`<botname>` is the unique name of your bot.  
-`<appsecret>` is a minimum 16 character password for your bot. 
-
-Record the `appid` from the returned JSON
-
-### 4. Create the Azure resources
-Replace the values for `<appid>`, `<appsecret>`, `<botname>`, and `<groupname>` in the following commands:
-
-#### To a new Resource Group
-```
-az deployment sub create --name "suggestedActionsBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="<appid>" appSecret="<appsecret>" botId="<botname>" botSku=S1 newAppServicePlanName="suggestedActionsBotPlan" newWebAppName="suggestedActionsBot" groupLocation="westus" newAppServicePlanLocation="westus"
-```
-
-#### To an existing Resource Group
-```
-az deployment group create --resource-group "<groupname>" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="<appid>" appSecret="<appsecret>" botId="<botname>" newWebAppName="suggestedActionsBot" newAppServicePlanName="suggestedActionsBotPlan" appServicePlanLocation="westus" --name "suggestedActionsBot"
-```
-
-### 5. Update app id and password
-In src/main/resources/application.properties update 
-  - `MicrosoftAppPassword` with the botsecret value
-  - `MicrosoftAppId` with the appid from the first step
-
-### 6. Deploy the code
-- Execute `mvn clean package` 
-- Execute `mvn azure-webapp:deploy -Dgroupname="<groupname>" -Dbotname="<bot-app-service-name>"`
-
-If the deployment is successful, you will be able to test it via "Test in Web Chat" from the Azure Portal using the "Bot Channel Registration" for the bot.
-
-After the bot is deployed, you only need to execute #6 if you make changes to the bot.
-
-
+To learn more about deploying a bot to Azure, see [Deploy your bot to Azure](https://aka.ms/azuredeployment) for a complete list of deployment instructions.
 ## Further reading
 
 - [Spring Boot](https://spring.io/projects/spring-boot)

diff --git a/samples/java_springboot/11.qnamaker/README.md b/samples/java_springboot/11.qnamaker/README.md
@@ -49,52 +49,7 @@ One of the basic requirements in writing your own bot is to seed it with questio
 
 ## Deploy the bot to Azure
 
-As described on [Deploy your bot](https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-deploy-az-cli), you will perform the first 4 steps to setup the Azure app, then deploy the code using the azure-webapp Maven plugin.
-
-### 1. Login to Azure
-From a command (or PowerShell) prompt in the root of the bot folder, execute:  
-`az login`
-
-### 2. Set the subscription
-`az account set --subscription "<azure-subscription>"`
-
-If you aren't sure which subscription to use for deploying the bot, you can view the list of subscriptions for your account by using `az account list` command. 
-
-### 3. Create an App registration
-`az ad app create --display-name "<botname>" --password "<appsecret>" --available-to-other-tenants`
-
-Replace `<botname>` and `<appsecret>` with your own values.
-
-`<botname>` is the unique name of your bot.  
-`<appsecret>` is a minimum 16 character password for your bot. 
-
-Record the `appid` from the returned JSON
-
-### 4. Create the Azure resources
-Replace the values for `<appid>`, `<appsecret>`, `<botname>`, and `<groupname>` in the following commands:
-
-#### To a new Resource Group
-```
-az deployment sub create --name "qnaBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="<appid>" appSecret="<appsecret>" botId="<botname>" botSku=S1 newAppServicePlanName="qnaBotPlan" newWebAppName="qnaBot" groupLocation="westus" newAppServicePlanLocation="westus"
-```
-
-#### To an existing Resource Group
-```
-az deployment group create --resource-group "<groupname>" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="<appid>" appSecret="<appsecret>" botId="<botname>" newWebAppName="qnaBot" newAppServicePlanName="qnaBotPlan" appServicePlanLocation="westus" --name "qnaBot"
-```
-
-### 5. Update app id and password
-In src/main/resources/application.properties update 
-  - `MicrosoftAppPassword` with the botsecret value
-  - `MicrosoftAppId` with the appid from the first step
-
-### 6. Deploy the code
-- Execute `mvn clean package` 
-- Execute `mvn azure-webapp:deploy -Dgroupname="<groupname>" -Dbotname="<bot-app-service-name>"`
-
-If the deployment is successful, you will be able to test it via "Test in Web Chat" from the Azure Portal using the "Bot Channel Registration" for the bot.
-
-After the bot is deployed, you only need to execute #6 if you make changes to the bot.
+To learn more about deploying a bot to Azure, see [Deploy your bot to Azure](https://aka.ms/azuredeployment) for a complete list of deployment instructions.
 
 ## Further reading