This past week I needed to move a client’s Hyper-V machine to a Windows Azure VM. If you haven’t figured it out already, the process isn’t as straightforward as one may hope – especially, since there’s a rather large chasm between the new and old Azure management portals as neither offer an entire end-to-end solution. As with most things Microsoft nowadays, PowerShell seems to be the best solution for truly accomplishing your needs.
Below, you’ll find a resource for tackling all of the different components of moving a Hyper-V VM to Azure. There are some ways to do parts of this through the various GUI’s, but, again, none of the GUI’s offer a complete solution.
This week, while moving a client’s VM to Windows Azure, I was also required to upgrade their database from SQL 2005 to SQL Azure. While not extremely difficult, there were a few gotcha’s along the way. These “gotacha’s” were primarily features that had been deprecated. Those deprecated features aren’t the purpose of blog post, however. This post is addressing a connection string issue.