The Dynamics GP Blogster

In Part 1 of this series, I walked through the process and experience of signing up for the Azure SQL Managed Instance preview and the deployment process once approved. I also covered some of the issues I ran into. In this installment, I will take a look at deploying Microsoft Dynamics GP and, again, looking at the process and experiences I encountered while doing so. Pre-Microsoft Dynamics GP Deployment One of the steps within the deployment of a Managed Instance is the provisioning of a VM to be able to connect to the service. The instructions call for downloading and installing Microsoft SQL Server Management Studio on the VM. I figured, this is the VM I would also be using to install Dynamics GP, IIS, and Web Client. NOTE : Currently, you cannot connect to a Managed Instance from outside of the Azure vNet infrastructure, and frankly it makes a lot of sense. A few things I noticed right off the bat after connecting to the Managed Instance: a) A Managed Instance is confi...

A few weeks aback, I went through a series of video articles explaining the limitations preventing you from deploying Microsoft Dynamics GP on Azure SQL. See my video blog series here: Microsoft Dynamics GP: Running System and Company Databases on Azure SQL - Part 1 Microsoft Dynamics GP: Running System and Company Databases on Azure SQL - Part 2 Microsoft Dynamics GP: Running System and Company Databases on Azure SQL - Part 3 A few days later, my friend and fellow MVP Steve Endow introduced me to a new Azure preview feature called Azure SQL Managed Instance . Being a preview feature, there was a lengthy application process in order to gain access to it. Overview According to Microsoft, Azure SQL Managed Instance (further referred to herein as "Managed Instance" for simplicity sake) delivers the full capabilities of Microsoft SQL Server running on Azure service infrastructure. This is, all the limitations currently imposed by Azure SQL are, technically speaking,...