How to develop and deploy several different bots in Azure?
up vote
0
down vote
favorite
I have developed a bot using Microsoft Bot Framework v3 and C#.Net. I have also deployed the bot in Azure with in a resource group having necessary resources like App Service Plan, App Service, Bot Service etc. Now there is a requirement to create a new bot for different workflow. I want to know what are my chances to use my existing Azure resources. Should I create a new Bot service & App Service in same App Service Plan?
If anyone have created and deployed various different bots in Azure please share the strategy.
azure 
botframework bots asked Nov 19 at 12:40
TechGeek
115
add a comment |
up vote
0
down vote
favorite
I have developed a bot using Microsoft Bot Framework v3 and C#.Net. I have also deployed the bot in Azure with in a resource group having necessary resources like App Service Plan, App Service, Bot Service etc. Now there is a requirement to create a new bot for different workflow. I want to know what are my chances to use my existing Azure resources. Should I create a new Bot service & App Service in same App Service Plan?
If anyone have created and deployed various different bots in Azure please share the strategy.
azure botframework bots asked Nov 19 at 12:40
TechGeek
115
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have developed a bot using Microsoft Bot Framework v3 and C#.Net. I have also deployed the bot in Azure with in a resource group having necessary resources like App Service Plan, App Service, Bot Service etc. Now there is a requirement to create a new bot for different workflow. I want to know what are my chances to use my existing Azure resources. Should I create a new Bot service & App Service in same App Service Plan?
If anyone have created and deployed various different bots in Azure please share the strategy.
azure botframework bots asked Nov 19 at 12:40
TechGeek
115
I have developed a bot using Microsoft Bot Framework v3 and C#.Net. I have also deployed the bot in Azure with in a resource group having necessary resources like App Service Plan, App Service, Bot Service etc. Now there is a requirement to create a new bot for different workflow. I want to know what are my chances to use my existing Azure resources. Should I create a new Bot service & App Service in same App Service Plan?
If anyone have created and deployed various different bots in Azure please share the strategy.
azure botframework bots azure botframework bots asked Nov 19 at 12:40
TechGeek
115
asked Nov 19 at 12:40
TechGeek
115
asked Nov 19 at 12:40
TechGeek
115
asked Nov 19 at 12:40
TechGeek
115
asked Nov 19 at 12:40
TechGeek
115
115
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
It highly depends on your scenarios.
But considering that your different bots must run in parallel:
- App Service Plan can be reused, if its pricing is high enough to size to the demands of both bots
- Storage account can also be reused as it uses bot Id in its keys (but it would be better to specify different tables for each bot in your dependency injection if using Table Storage)
- App Service (where you are exposing your
/api/messagesendpoint) must be specific if you don't manage a special configuration - App Bot Service (which is linked to this endpoint) must be specific also, as Bot Channel Registration is specific to each bot
answered Nov 19 at 16:10
Nicolas R
8,82521643
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
It highly depends on your scenarios.
But considering that your different bots must run in parallel:
- App Service Plan can be reused, if its pricing is high enough to size to the demands of both bots
- Storage account can also be reused as it uses bot Id in its keys (but it would be better to specify different tables for each bot in your dependency injection if using Table Storage)
- App Service (where you are exposing your
/api/messagesendpoint) must be specific if you don't manage a special configuration - App Bot Service (which is linked to this endpoint) must be specific also, as Bot Channel Registration is specific to each bot
answered Nov 19 at 16:10
Nicolas R
8,82521643
add a comment |
up vote
0
down vote
It highly depends on your scenarios.
But considering that your different bots must run in parallel:
- App Service Plan can be reused, if its pricing is high enough to size to the demands of both bots
- Storage account can also be reused as it uses bot Id in its keys (but it would be better to specify different tables for each bot in your dependency injection if using Table Storage)
- App Service (where you are exposing your
/api/messagesendpoint) must be specific if you don't manage a special configuration - App Bot Service (which is linked to this endpoint) must be specific also, as Bot Channel Registration is specific to each bot
answered Nov 19 at 16:10
Nicolas R
8,82521643
add a comment |
up vote
0
down vote
up vote
0
down vote
It highly depends on your scenarios.
But considering that your different bots must run in parallel:
- App Service Plan can be reused, if its pricing is high enough to size to the demands of both bots
- Storage account can also be reused as it uses bot Id in its keys (but it would be better to specify different tables for each bot in your dependency injection if using Table Storage)
- App Service (where you are exposing your
/api/messagesendpoint) must be specific if you don't manage a special configuration - App Bot Service (which is linked to this endpoint) must be specific also, as Bot Channel Registration is specific to each bot
answered Nov 19 at 16:10
Nicolas R
8,82521643
It highly depends on your scenarios.
But considering that your different bots must run in parallel:
- App Service Plan can be reused, if its pricing is high enough to size to the demands of both bots
- Storage account can also be reused as it uses bot Id in its keys (but it would be better to specify different tables for each bot in your dependency injection if using Table Storage)
- App Service (where you are exposing your
/api/messagesendpoint) must be specific if you don't manage a special configuration - App Bot Service (which is linked to this endpoint) must be specific also, as Bot Channel Registration is specific to each bot
answered Nov 19 at 16:10
Nicolas R
8,82521643
answered Nov 19 at 16:10
Nicolas R
8,82521643
answered Nov 19 at 16:10
Nicolas R
8,82521643
answered Nov 19 at 16:10
Nicolas R
8,82521643
8,82521643
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53374865%2fhow-to-develop-and-deploy-several-different-bots-in-azure%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
