{"id":17799,"date":"2022-10-27T04:29:01","date_gmt":"2022-10-26T22:59:01","guid":{"rendered":"https:\/\/jassweb.com\/solved\/solved-bot-cloning-in-azure\/"},"modified":"2022-10-27T04:29:01","modified_gmt":"2022-10-26T22:59:01","slug":"solved-bot-cloning-in-azure","status":"publish","type":"post","link":"https:\/\/jassweb.com\/solved\/solved-bot-cloning-in-azure\/","title":{"rendered":"[Solved] Bot Cloning in Azure"},"content":{"rendered":"

[ad_1]
\n<\/p>\n

\n
\n
<\/div>\n
\n
\n

So it is possible to solve this programatically. I went about it using Powershell scripts, specifically Azure CLI and Azure Powershell. However, I believe that the standard is via Terraform (aka TF) or Pulumi and if I had to do this again I would probably use one of those IaaS tools. Especially since these tools do not depend on order of configuration (at least TF does not), whereas the Powershell scripting does.<\/p>\n

Regarding the scripting, you can configure a resource group, an application registration and its settings (service principal and app credential), and the azure bot service and its settings.<\/p>\n

I had to somewhat reverse engineer this process, so I personally would recommend starting with the Get-AzBotService<\/a> command to see what you need to duplicate from your bot (note that you may prefer the Azure CLI version of this command: az bot show<\/a>).<\/p>\n

I also recommend using the Azure CLI to set up the bot service as it offers more fine control than Azure Powershell.<\/p>\n

Note that I will just be using variable name holders for each field in the Powershell commands. I realize this might not result in the clearest explanation, but my use case had more configuration details than what I believe the average use case had and MS does have documentation on each field under each of the Powershell commands. However, if a future reader would like even more details, comment below and I’ll happily supplement whatever MS docs are not clear.<\/p>\n

You will need to start by logging into both Azure CLI and Azure Powershell<\/strong>. I recommend using these code blocks so you don’t always have the login tab open in your browser:<\/p>\n

$loginStatus = Get-AzContext\nif ( -not ($loginStatus) ) {\n    Connect-AzAccount\n    $subscription_id = Get-AzSubscription\n    Set-AzContext -SubscriptionId ($subscription_id)\n}\n<\/code><\/pre>\n
and<\/p>\n
$loginStatusAz = az account show\nif ( -not ($loginStatusAz) ) {\n    az login\n}\n<\/code><\/pre>\n
I first recommend creating the resource group<\/strong> for your bot:
\nNew-AzResourceGroup -Location $location -Name $resourceGroupName<\/code><\/p>\n
Next, I would create the application registration<\/strong> for your application:<\/p>\n
$appInfo = New-AzAdApplication `\n    -DisplayName $registrationName `\n    -Web $webConfig`\n    -ReplyUrl $replyUrls `\n    -IdentifierUri $identifierUris `\n    -Api $api `\n    -SignInAudience $signInAudience\n<\/code><\/pre>\n
One note here<\/strong> – make sure your configuration of the -SignInAudience<\/code> flag results in your application being multi-tenant. I found that my use case had issues otherwise. Also, depending on how you configure this, you may need to use Update-AzADApplication<\/code> after creating a basic application registration with New-AzAdApplication<\/code>. So in my case I would create the application registration with just the -DisplayName<\/code> and -Web<\/code> flags configured and then update it with the rest of the information.<\/p>\n
You can configure other settings if you would like – I had to for my use case, but I won’t go into too much more detail here. If something more complicated is needed I would recommend using TF at this point, as it is easier to determine how to configure more complex settings of an application registration that way compared to using Powershell scripting.<\/p>\n
Creating the service principal and application credentials<\/strong>:<\/p>\n
New-AzAdServicePrincipal -ApplicationId $appInfo.AppId\n\n$secretInfo = New-AzADAppCredential -ObjectId $appInfo.Id\n<\/code><\/pre>\n
Note:<\/strong> I would save the secret creds for future use.<\/p>\n
To create the bot<\/strong>:<\/p>\n
az bot create `\n    --app-type $appType `\n    --appid $appInfo.AppId `\n    --name $botName `\n    --resource-group $resourceGroupName `\n    --endpoint $messagingEndpoint `\n    --sku $sku\n<\/code><\/pre>\n
To add channel configurations<\/strong> to the bot:<\/p>\n
az bot msteams create `\n    --name $botName `\n    --resource-group $resourceGroupName\n<\/code><\/pre>\n
You may need a different command – this is specific to the MS teams channel, but the az bot<\/code> command should have more documentation for it.<\/p>\n
To add authsetting<\/strong> to the bot:<\/p>\n
az bot authsetting create `\n    --client-id $appInfo.AppId `\n    --client-secret $secretInfo.SecretText `\n    --name $botName `\n    --provider-scope-string $providerScopeString `\n    --resource-group $resourceGroupName `\n    --service $serviceName `\n    --setting-name $connectionName `\n    --parameters \"tenantId=$($tenantId)\" \"tokenExchangeUrl=$($tokenExchangeUrl)\"\n<\/code><\/pre>\n
You may need to change your parameters depeninding on what type of auth connection service you use – I was using oauth.<\/p>\n
That’s more or less it from a high level. Again, if more questions\/details are needed, happy to update, but I believe this is a really good starting point for anyone who needs to create\/duplicate a bot in Azure programatically.<\/p>\n
Here are the docs for the commands I used and some that may be useful:<\/p>\n