Yes, I need a single server BizTalk Environment on Azure IaaS in one click!
After watching the Azure Tech-Ed sessions back online, I was interested in the session of Stephen W Thomas ‘Microsoft BizTalk Server 2013 in Windows Azure IaaS and emailed about the status of his last 10% of getting the script together.
Sure enough, he finished it within a week, and I tested it out and really recommend to look into it. It provides a lot of insight in the various features PowerShell for Azure has, how to do automation and more.
You can find the script at: Need a single server BizTalk Environment on Azure IaaS? Just give this a click!
As I had a new computer which was not yet ready for Azure, PowerShell and all these goodies, I wrote down the steps, and things I encountered.
- Get an Azure Account (e.g. using your MSDN subscription)
- Setup Powershell for Azure
- Start powershell
Get-AzurePublishSettingsFile (browser will open)
- Ensure that everything is setup
Update the settings you want;
- View the portal before we start doing all this magic
- Start the script ‘MakeVM.ps1’
- Get some coffee, go for a quick lunch, do something that doesn’t take to long!
- Watch the Portal just for fun…
- A pop-up with does the finishing work as configuring BizTalk / BizTalk 360
- Verify the installation by looking at the portal
- Connect to the virtual machine
- View the BizTalk configuration
Hey! Why is not everything deployed? This is because the ProvisioningTool is only configured for these components, see:
# Download Needed Files for BizTalk Multi-Server Configuration
$remoteUriConfig = https://biztalkgurus.blob.core.windows.net/tools/multinodeconfigDemo.xml"
- BizTalk 360
As a bonus, the BizTalk 360 portal is deployed, and after updating the license key, you can directly go ahead and give a demo/presentation, look at the return of the HAT like query editor
Stephen W Thomas did an amazing job, and although this script is at the moment for a single server, it shows, that a few lines of PowerShell can accomplish a lot!
- Clean up (prevent unwanted costs) by calling ‘.\RemoveVM.ps1’