diff --git a/samples/java_springboot/02.echo-bot/README.md b/samples/java_springboot/02.echo-bot/README.md index 30c36ee342..16acf22f7d 100644 --- 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` 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="" appSecret="" botId="" botSku=S1 newAppServicePlanName="echoBotPlan" newWebAppName="echoBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" 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="" -Dbotname=""` - -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 index e01da2dd83..814e7730b6 100644 --- 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` 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="" appSecret="" botId="" botSku=S1 newAppServicePlanName="welcomeBotPlan" newWebAppName="welcomeBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" 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="" -Dbotname=""` - -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 index 270b954562..d9671d90ee 100644 --- 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` 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="" appSecret="" botId="" botSku=S1 newAppServicePlanName="multiTurnPromptBotPlan" newWebAppName="multiTurnPromptBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" 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="" -Dbotname=""` - -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 index 5f000c9d19..58cfd9a678 100644 --- 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` 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="" appSecret="" botId="" botSku=S1 newAppServicePlanName="usingCardsBotPlan" newWebAppName="usingCardsBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" 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="" -Dbotname=""` - -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 index 76a4c9a626..8e3dfd6270 100644 --- 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` 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="" appSecret="" botId="" botSku=S1 newAppServicePlanName="adaptiveCardsBotPlan" newWebAppName="adaptiveCardsBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" 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="" -Dbotname=""` - -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 index 2fee58f304..ff1a6b1600 100644 --- 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` 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="" appSecret="" botId="" botSku=S1 newAppServicePlanName="suggestedActionsBotPlan" newWebAppName="suggestedActionsBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" 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="" -Dbotname=""` - -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 index a1e030cfe9..02000d4cd1 100644 --- 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` 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="" appSecret="" botId="" botSku=S1 newAppServicePlanName="qnaBotPlan" newWebAppName="qnaBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" 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="" -Dbotname=""` - -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/13.core-bot/README.md b/samples/java_springboot/13.core-bot/README.md index a3ac889d2b..8bbb4b160b 100644 --- a/samples/java_springboot/13.core-bot/README.md +++ b/samples/java_springboot/13.core-bot/README.md @@ -52,66 +52,7 @@ Once you created the LUIS model, update `application.properties` with your `Luis ## 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 "" -``` - -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 "" --password "" --available-to-other-tenants -``` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. - `` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group - -``` -az deployment sub create --name "coreBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="coreBotPlan" newWebAppName="coreBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group - -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="coreBot" newAppServicePlanName="coreBotPlan" appServicePlanLocation="westus" --name "coreBot" -``` - -### 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="" -Dbotname=""` - -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/14.nlp-with-dispatch/README.md b/samples/java_springboot/14.nlp-with-dispatch/README.md index 50acf58ada..032231611d 100644 --- a/samples/java_springboot/14.nlp-with-dispatch/README.md +++ b/samples/java_springboot/14.nlp-with-dispatch/README.md @@ -50,54 +50,7 @@ Once you are comfortable with the concepts presented in this sample, you may wan ## 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "dispatchBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="dispatchBotPlan" newWebAppName="dispatchBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="dispatchBot" newAppServicePlanName="dispatchBotPlan" appServicePlanLocation="westus" --name "dispatchBot" -``` - -### 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="" -Dbotname=""` - -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/15.handling-attachments/README.md b/samples/java_springboot/15.handling-attachments/README.md index 85837a5b2b..b2fae2a11c 100644 --- a/samples/java_springboot/15.handling-attachments/README.md +++ b/samples/java_springboot/15.handling-attachments/README.md @@ -40,53 +40,7 @@ The types of attachments that may be sent and received varies by channel. Additi ## 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "attachmentsBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="attachmentsBotPlan" newWebAppName="attachmentsBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="attachmentsBot" newAppServicePlanName="attachmentsBotPlan" appServicePlanLocation="westus" --name "attachmentsBot" -``` - -### 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="" -Dbotname=""` - -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/16.proactive-messages/README.md b/samples/java_springboot/16.proactive-messages/README.md index a174008ced..e86209c8fe 100644 --- a/samples/java_springboot/16.proactive-messages/README.md +++ b/samples/java_springboot/16.proactive-messages/README.md @@ -65,53 +65,7 @@ To send proactive messages, acquire a conversation reference, then use `adapter. ## 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "proactiveBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="proactiveBotPlan" newWebAppName="proactiveBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="proactiveBot" newAppServicePlanName="proactiveBotPlan" appServicePlanLocation="westus" --name "proactiveBot" -``` - -### 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="" -Dbotname=""` - -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/17.multilingual-bot/README.md b/samples/java_springboot/17.multilingual-bot/README.md index 9cad2430df..1de7bb0792 100644 --- a/samples/java_springboot/17.multilingual-bot/README.md +++ b/samples/java_springboot/17.multilingual-bot/README.md @@ -57,55 +57,9 @@ Users can specify their language preference, which is stored in the user state. The [Microsoft Translator Text API](https://docs.microsoft.com/en-us/azure/cognitive-services/translator/), Microsoft Translator Text API is a cloud-based machine translation service. With this API you can translate text in near real-time from any app or service through a simple REST API call. The API uses the most modern neural machine translation technology, as well as offering statistical machine translation technology. -## Deploy this 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "multilingualBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="multilingualBotPlan" newWebAppName="multilingualBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="multilingualBot" newAppServicePlanName="multilingualBotPlan" appServicePlanLocation="westus" --name "multilingualBot" -``` - -### 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="" -Dbotname=""` - -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. +## Deploy the bot to Azure +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. ### Add `TranslatorKey` to Application Settings If you used the `application.properties` file to store your `TranslatorKey` then you'll need to add this key and its value to the Application Settings for your deployed bot. diff --git a/samples/java_springboot/18.bot-authentication/README.md b/samples/java_springboot/18.bot-authentication/README.md index 618c4093a2..55076c4474 100644 --- a/samples/java_springboot/18.bot-authentication/README.md +++ b/samples/java_springboot/18.bot-authentication/README.md @@ -41,53 +41,7 @@ This sample uses bot authentication capabilities in Azure Bot Service, providing ## 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "authenticationBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="authenticationBotPlan" newWebAppName="authenticationBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="authenticationBot" newAppServicePlanName="authenticationBotPlan" appServicePlanLocation="westus" --name "authenticationBot" -``` - -### 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="" -Dbotname=""` - -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) - [Maven Plugin for Azure App Service](https://docs.microsoft.com/en-us/java/api/overview/azure/maven/azure-webapp-maven-plugin/readme?view=azure-java-stable) diff --git a/samples/java_springboot/19.custom-dialogs/README.md b/samples/java_springboot/19.custom-dialogs/README.md index d23167b132..e7bc9b59a5 100644 --- a/samples/java_springboot/19.custom-dialogs/README.md +++ b/samples/java_springboot/19.custom-dialogs/README.md @@ -44,53 +44,7 @@ all full, at which point the dialog completes. ## 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "customDialogsBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="customDialogsBotPlan" newWebAppName="customDialogsBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="customDialogsBot" newAppServicePlanName="customDialogsBotPlan" appServicePlanLocation="westus" --name "customDialogsBot" -``` - -### 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="" -Dbotname=""` - -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/23.facebook-events/README.md b/samples/java_springboot/23.facebook-events/README.md index 5a540654e2..c9e93b1631 100644 --- a/samples/java_springboot/23.facebook-events/README.md +++ b/samples/java_springboot/23.facebook-events/README.md @@ -36,53 +36,7 @@ This sample is a Spring Boot app and uses the Azure CLI and azure-webapp Maven p ## 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "facebookBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="facebookBotPlan" newWebAppName="facebookBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="facebookBot" newAppServicePlanName="facebookBotPlan" appServicePlanLocation="westus" --name "facebookBot" -``` - -### 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="" -Dbotname=""` - -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/24.bot-authentication-msgraph/README.md b/samples/java_springboot/24.bot-authentication-msgraph/README.md index 10ba585bcb..9d1b818a59 100644 --- a/samples/java_springboot/24.bot-authentication-msgraph/README.md +++ b/samples/java_springboot/24.bot-authentication-msgraph/README.md @@ -56,53 +56,7 @@ the Microsoft Graph builds on Office 365 APIs and allows developers to integrate ## 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "authenticationBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="authenticationGraphBotPlan" newWebAppName="authenticationGraphBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="authenticationGraphBot" newAppServicePlanName="authenticationGraphBotPlan" appServicePlanLocation="westus" --name "authenticationGraphBot" -``` - -### 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="" -Dbotname=""` - -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. ## GraphError 404: ResourceNotFound, Resource could not be discovered This error may confusingly present itself if either of the following are true: diff --git a/samples/java_springboot/25.message-reaction/README.md b/samples/java_springboot/25.message-reaction/README.md index 04b7f88329..bba0e2ffa9 100644 --- a/samples/java_springboot/25.message-reaction/README.md +++ b/samples/java_springboot/25.message-reaction/README.md @@ -62,66 +62,7 @@ Message the bot and it will respond with an 'Echo: [your message]'. Add a messa ## 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 "" -``` - -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 "" --password "" --available-to-other-tenants -``` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group - -``` -az deployment sub create --name "messageReactionBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="messageReactionBotPlan" newWebAppName="messageReactionBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group - -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="messageReactionBot" newAppServicePlanName="messageReactionBotPlan" appServicePlanLocation="westus" --name "messageReactionBot" -``` - -### 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="" -Dbotname=""` - -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/42.scaleout/README.md b/samples/java_springboot/42.scaleout/README.md index ddbef1e647..1ead31e771 100644 --- a/samples/java_springboot/42.scaleout/README.md +++ b/samples/java_springboot/42.scaleout/README.md @@ -31,53 +31,7 @@ This sample is a Spring Boot app and uses the Azure CLI and azure-webapp Maven p ## 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "scaleoutBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="scaleoutBotPlan" newWebAppName="scaleoutBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="scaleoutBot" newAppServicePlanName="scaleoutPlan" appServicePlanLocation="westus" --name "scaleoutBot" -``` - -### 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="" -Dbotname=""` - -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/43.complex-dialog/README.md b/samples/java_springboot/43.complex-dialog/README.md index 9f00673409..ea94cc5c67 100644 --- a/samples/java_springboot/43.complex-dialog/README.md +++ b/samples/java_springboot/43.complex-dialog/README.md @@ -29,53 +29,7 @@ This sample is a Spring Boot app and uses the Azure CLI and azure-webapp Maven p ## 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "complexDialogBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="complexDialogBotPlan" newWebAppName="complexDialogBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="complexDialogBot" newAppServicePlanName="complexDialogPlan" appServicePlanLocation="westus" --name "complexDialogBot" -``` - -### 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="" -Dbotname=""` - -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/45.state-management/README.md b/samples/java_springboot/45.state-management/README.md index 54fc73f265..b6afbe94c5 100644 --- a/samples/java_springboot/45.state-management/README.md +++ b/samples/java_springboot/45.state-management/README.md @@ -63,66 +63,7 @@ return new CosmosDbPartitionedStorage(options); ## 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 "" -``` - -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 "" --password "" --available-to-other-tenants -``` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group - -``` -az deployment sub create --name "stateManagementDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="stateManagementPlan" newWebAppName="stateManagement" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group - -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="stateManagement" newAppServicePlanName="stateManagementPlan" appServicePlanLocation="westus" --name "stateManagement" -``` - -### 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="" -Dbotname=""` - -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. ## Bot State A key to good bot design is to track the context of a conversation, so that your bot remembers things like the answers to previous questions. Depending on what your bot is used for, you may even need to keep track of state or store information for longer than the lifetime of the conversation. A bots state is information it remembers in order to respond appropriately to incoming messages. The Bot Builder SDK provides classes for storing and retrieving state data as an object associated with a user or a conversation. diff --git a/samples/java_springboot/46.teams-auth/README.md b/samples/java_springboot/46.teams-auth/README.md index 974c0ddca8..2f265a141c 100644 --- a/samples/java_springboot/46.teams-auth/README.md +++ b/samples/java_springboot/46.teams-auth/README.md @@ -46,53 +46,8 @@ the Teams service needs to call into the bot. You can interact with this bot by sending it a message. The bot will respond by requesting you to login to AAD, then making a call to the Graph API on your behalf and returning the results. ## 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "teamsAuthDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="teamsAuthPlan" newWebAppName="teamsAuth" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="teamsAuth" newAppServicePlanName="teamsAuthPlan" appServicePlanLocation="westus" --name "teamsAuth" -``` - -### 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="" -Dbotname=""` - -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) - [Maven Plugin for Azure App Service](https://github.com/microsoft/azure-maven-plugins/tree/develop/azure-webapp-maven-plugin) diff --git a/samples/java_springboot/47.inspection/README.md b/samples/java_springboot/47.inspection/README.md index e5b5916f60..10adf808f4 100644 --- a/samples/java_springboot/47.inspection/README.md +++ b/samples/java_springboot/47.inspection/README.md @@ -46,53 +46,7 @@ This sample is a Spring Boot app and uses the Azure CLI and azure-webapp Maven p ## 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "inspectionBotDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="inspectionBotPlan" newWebAppName="inspectionBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="inspectionBot" newAppServicePlanName="inspectionBotPlan" appServicePlanLocation="westus" --name "inspectionBot" -``` - -### 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="" -Dbotname=""` - -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/49.qnamaker-all-features/README.md b/samples/java_springboot/49.qnamaker-all-features/README.md index cb2721ffe5..a0065f910e 100644 --- a/samples/java_springboot/49.qnamaker-all-features/README.md +++ b/samples/java_springboot/49.qnamaker-all-features/README.md @@ -84,53 +84,8 @@ QnA knowledge base setup and application configuration steps can be found [here] - Enter a Bot URL of `http://localhost:3978/api/messages` ## 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "qnaMakerAllFeaturesDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="qnaMakerAllFeaturesPlan" newWebAppName="qnaMakerAllFeatures" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="qnaMakerAllFeatures" newAppServicePlanName="qnaMakerAllFeaturesPlan" appServicePlanLocation="westus" --name "qnaMakerAllFeatures" -``` - -### 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="" -Dbotname=""` - -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][160] - [Maven Plugin for Azure App Service][161] diff --git a/samples/java_springboot/50.teams-messaging-extensions-search/README.md b/samples/java_springboot/50.teams-messaging-extensions-search/README.md index caea391600..3c46eccb4c 100644 --- a/samples/java_springboot/50.teams-messaging-extensions-search/README.md +++ b/samples/java_springboot/50.teams-messaging-extensions-search/README.md @@ -46,66 +46,7 @@ You may encounter permission-related errors when sending a proactive message. Th ## 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 "" -``` - -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 "" --password "" --available-to-other-tenants -``` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group - -``` -az deployment sub create --name "teamsSearchDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="teamsSearchPlan" newWebAppName="teamsSearch" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group - -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="teamsSearch" newAppServicePlanName="teamsSearchPlan" appServicePlanLocation="westus" --name "teamsSearch" -``` - -### 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="" -Dbotname=""` - -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) - [Maven Plugin for Azure App Service](https://github.com/microsoft/azure-maven-plugins/tree/develop/azure-webapp-maven-plugin) diff --git a/samples/java_springboot/51.teams-messaging-extensions-action/README.md b/samples/java_springboot/51.teams-messaging-extensions-action/README.md index f30b6e0ca6..f3abfcab5d 100644 --- a/samples/java_springboot/51.teams-messaging-extensions-action/README.md +++ b/samples/java_springboot/51.teams-messaging-extensions-action/README.md @@ -53,51 +53,7 @@ or ## 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "teamsActionDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="teamsActionPlan" newWebAppName="teamsActionBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="teamsActionBot" newAppServicePlanName="teamsActionPlan" appServicePlanLocation="westus" --name "teamsActionBot" -``` - -### 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="" -Dbotname=""` - -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/52.teams-messaging-extensions-search-auth-config/README.md b/samples/java_springboot/52.teams-messaging-extensions-search-auth-config/README.md index ad553c6fd1..6eda34344e 100644 --- a/samples/java_springboot/52.teams-messaging-extensions-search-auth-config/README.md +++ b/samples/java_springboot/52.teams-messaging-extensions-search-auth-config/README.md @@ -57,66 +57,7 @@ You may encounter permission-related errors when sending a proactive message. Th ## 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 "" -``` - -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 "" --password "" --available-to-other-tenants -``` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group - -``` -az deployment sub create --name "teamsSearchAuthDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="teamsSearchAuthPlan" newWebAppName="teamsSearchAuth" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group - -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="teamsSearchAuth" newAppServicePlanName="teamsSearchAuthPlan" appServicePlanLocation="westus" --name "teamsSearchAuth" -``` - -### 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="" -Dbotname=""` - -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) - [Maven Plugin for Azure App Service](https://github.com/microsoft/azure-maven-plugins/tree/develop/azure-webapp-maven-plugin) diff --git a/samples/java_springboot/53.teams-messaging-extensions-action-preview/README.md b/samples/java_springboot/53.teams-messaging-extensions-action-preview/README.md index 0b78887822..faf32e3f96 100644 --- a/samples/java_springboot/53.teams-messaging-extensions-action-preview/README.md +++ b/samples/java_springboot/53.teams-messaging-extensions-action-preview/README.md @@ -44,53 +44,8 @@ the Teams service needs to call into the bot. Click the Messaging Extension icon in the Compose Box's Messaging Extension menu. ## 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "teamsActionPreviewDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="teamsActionPreviewPlan" newWebAppName="teamsActionPreview" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="teamsActionPreview" newAppServicePlanName="teamsActionPreviewPlan" appServicePlanLocation="westus" --name "teamsActionPreview" -``` - -### 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="" -Dbotname=""` - -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) - [Maven Plugin for Azure App Service](https://github.com/microsoft/azure-maven-plugins/tree/develop/azure-webapp-maven-plugin) diff --git a/samples/java_springboot/54.teams-task-module/README.md b/samples/java_springboot/54.teams-task-module/README.md index ba5d330ba8..9cf86407c7 100644 --- a/samples/java_springboot/54.teams-task-module/README.md +++ b/samples/java_springboot/54.teams-task-module/README.md @@ -47,51 +47,7 @@ You can interact with this bot by sending it a message. The bot will respond wit ## 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "teamsTaskModuleDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="teamsTaskModulePlan" newWebAppName="teamsTaskModuleBot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="teamsTaskModuleBot" newAppServicePlanName="teamsTaskModulePlan" appServicePlanLocation="westus" --name "teamsTaskModuleBot" -``` - -### 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="" -Dbotname=""` - -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/55.teams-link-unfurling/README.md b/samples/java_springboot/55.teams-link-unfurling/README.md index 195db79198..fab083d25a 100644 --- a/samples/java_springboot/55.teams-link-unfurling/README.md +++ b/samples/java_springboot/55.teams-link-unfurling/README.md @@ -40,53 +40,8 @@ the Teams service needs to call into the bot. If you copy and paste a link from https://www.BotFramework.com into the compose message area the link will unfurl. ## 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "teamsUnfurlDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="teamsUnfurlPlan" newWebAppName="teamsUnfurl" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="teamsUnfurl" newAppServicePlanName="teamsUnfurlPlan" appServicePlanLocation="westus" --name "teamsUnfurl" -``` - -### 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="" -Dbotname=""` - -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) - [Maven Plugin for Azure App Service](https://github.com/microsoft/azure-maven-plugins/tree/develop/azure-webapp-maven-plugin) diff --git a/samples/java_springboot/56.teams-file-upload/README.md b/samples/java_springboot/56.teams-file-upload/README.md index a915d7104e..4e318897cd 100644 --- a/samples/java_springboot/56.teams-file-upload/README.md +++ b/samples/java_springboot/56.teams-file-upload/README.md @@ -47,66 +47,7 @@ the Teams service needs to call into 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 "" -``` - -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 "" --password "" --available-to-other-tenants -``` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group - -``` -az deployment sub create --name "teamsFileUploadDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="teamsFileUploadPlan" newWebAppName="teamsFileUpload" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group - -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="teamsFileUpload" newAppServicePlanName="teamsFileUploadPlan" appServicePlanLocation="westus" --name "teamsFileUpload" -``` - -### 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="" -Dbotname=""` - -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) - [Maven Plugin for Azure App Service](https://github.com/microsoft/azure-maven-plugins/tree/develop/azure-webapp-maven-plugin) diff --git a/samples/java_springboot/57.teams-conversation-bot/README.md b/samples/java_springboot/57.teams-conversation-bot/README.md index 35fb1d4b43..11c4852fb7 100644 --- a/samples/java_springboot/57.teams-conversation-bot/README.md +++ b/samples/java_springboot/57.teams-conversation-bot/README.md @@ -62,64 +62,7 @@ You may encounter permission-related errors when sending a proactive message. Th ## 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 "" -``` - -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 "" --password "" --available-to-other-tenants -``` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group - -``` -az deployment sub create --name "teamsConversationBot" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="teamsConversationBotPlan" newWebAppName="teamsConversation" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group - -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="teamsConversationBot" newAppServicePlanName="teamsConversationBotPlan" appServicePlanLocation="westus" --name "teamsConversation" -``` - -### 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="" -Dbotname=""` - -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/58.teams-start-new-thread-in-channel/README.md b/samples/java_springboot/58.teams-start-new-thread-in-channel/README.md index a2c128e57a..b97545ceed 100644 --- a/samples/java_springboot/58.teams-start-new-thread-in-channel/README.md +++ b/samples/java_springboot/58.teams-start-new-thread-in-channel/README.md @@ -47,53 +47,8 @@ the Teams service needs to call into the bot. You can interact with this bot by sending it a message. The bot will respond by creating a new thread in the channel and replying to that new thread. ## 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 ""` - -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 "" --password "" --available-to-other-tenants` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group -``` -az deployment sub create --name "teamsNewThreadDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="teamsNewThreadPlan" newWebAppName="teamsNewThread" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="teamsNewThread" newAppServicePlanName="teamsNewThreadPlan" appServicePlanLocation="westus" --name "teamsNewThread" -``` - -### 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="" -Dbotname=""` - -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) - [Maven Plugin for Azure App Service](https://github.com/microsoft/azure-maven-plugins/tree/develop/azure-webapp-maven-plugin) diff --git a/samples/java_springboot/80.skills-simple-bot-to-bot/README.md b/samples/java_springboot/80.skills-simple-bot-to-bot/README.md index a2e07f91a3..3ee56073e2 100644 --- a/samples/java_springboot/80.skills-simple-bot-to-bot/README.md +++ b/samples/java_springboot/80.skills-simple-bot-to-bot/README.md @@ -50,64 +50,4 @@ The solution includes a parent bot (`SimpleRootBot`) and a skill bot (`EchoSkill ## 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. - -These steps should be followed to deploy the DialogRootBot and DialogSkillBot. - -### 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 "" -``` - -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 "" --password "" --available-to-other-tenants -``` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group - -``` -az deployment sub create --name "botDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="botPlan" newWebAppName="bot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group - -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="bot" newAppServicePlanName="botPlan" appServicePlanLocation="westus" --name "bot" -``` - -### 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="" -Dbotname=""` - -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. diff --git a/samples/java_springboot/81.skills-skilldialog/README.md b/samples/java_springboot/81.skills-skilldialog/README.md index 86e4269e8d..52781ff3c6 100644 --- a/samples/java_springboot/81.skills-skilldialog/README.md +++ b/samples/java_springboot/81.skills-skilldialog/README.md @@ -53,66 +53,6 @@ It demonstrates how to post activities from the parent bot to the skill bot and - File -> Open Bot - Enter a Bot URL of `http://localhost:3978/api/messages`, the `MicrosoftAppId` and `MicrosoftAppPassword` for the `dialog-root-bot` -## Deploy the bots to Azure +## 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. - -These steps should be followed to deploy the DialogRootBot and DialogSkillBot. - -### 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 "" -``` - -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 "" --password "" --available-to-other-tenants -``` - -Replace `` and `` with your own values. - -`` is the unique name of your bot. -`` 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 ``, ``, ``, and `` in the following commands: - -#### To a new Resource Group - -``` -az deployment sub create --name "botDeploy" --location "westus" --template-file ".\deploymentTemplates\template-with-new-rg.json" --parameters appId="" appSecret="" botId="" botSku=S1 newAppServicePlanName="botPlan" newWebAppName="bot" groupLocation="westus" newAppServicePlanLocation="westus" -``` - -#### To an existing Resource Group - -``` -az deployment group create --resource-group "" --template-file ".\deploymentTemplates\template-with-preexisting-rg.json" --parameters appId="" appSecret="" botId="" newWebAppName="bot" newAppServicePlanName="botPlan" appServicePlanLocation="westus" --name "bot" -``` - -### 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="" -Dbotname=""` - -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.