For many businesses, Microsoft Dynamics GP (Great Plains) still runs on a server in the office. It works, but the server is getting older, more of your team works from home, and your IT provider is asking whether it is time to buy new hardware.
There is another option. You can move Dynamics GP to the cloud by running it on Microsoft Azure. It is the same Dynamics GP your team knows, with the same screens, data and reports. Only the place where it runs changes.
Before you decide, there is one fact we want to emphasize. Moving Dynamics GP to Azure does not change Microsoft’s retirement dates. Product and tax updates end on December 31, 2029, and security updates end on April 30, 2031. So think of cloud hosting as a way to make the remaining years of GP safer and easier, not as a permanent answer.
In this guide, we explain what Azure is, how the hosting options compare, how the move works, and how to decide what is right for your business.
What Is Microsoft Azure?
Microsoft Azure is Microsoft’s public cloud platform. In simple terms, it is a worldwide network of data centers where you rent computing power instead of buying your own servers.
For a Dynamics GP user, the useful parts of Azure are:
- Virtual machines: servers that you rent by the hour or month. GP and SQL Server are installed on these, just as they would be on a physical server.
- Storage and backups: your data is kept in several copies, and you can also store copies in a second region.
- Security: Microsoft protects the buildings, hardware and network, and gives you tools such as multi-factor authentication and firewalls.
- Flexible sizing: if Dynamics GP feels slow at month-end, you can increase the size of a virtual machine. If you need less, you can reduce it.
- Pay for what you use: there is no large purchase at the start. You pay a monthly amount based on usage.
Azure also holds a wide range of compliance certifications, which helps businesses in regulated industries meet audit requirements.
One point to understand clearly: Microsoft Dynamics GP (Great Plains) on Azure is still the same product. Microsoft’s own guidance says the GP you deploy in Azure is the same one you would install in your own office. Azure changes where it runs, not what it does.
On-Premise vs. Cloud Hosting
There are three ways to run a finance system today. This table shows how they differ:
| Area | On-Premise GP | GP Hosted on Azure | True Cloud ERP (Business Central) |
|---|---|---|---|
| Starting cost | High: servers and setup | Low: monthly fee | Low: monthly subscription |
| Hardware | You buy and replace it | Rented from Microsoft | None to manage |
| Software updates | Installed by you or your partner | Still installed by you or your partner | Applied automatically by Microsoft |
| Backups | Your responsibility | Easier, but must be set up | Included |
| Remote access | Needs VPN or remote desktop | Secure access from anywhere | Any browser or mobile device |
| Supported after 2031 | No | No | Yes |
Benefits of Hosting Dynamics GP on Azure
- No new server to buy. You avoid a large hardware purchase for a system with a limited life.
- Lower IT workload. There is no server room, cooling or failed hardware to deal with.
- Better protection for your data. Backups can run automatically and be stored in a second location.
- Secure remote work. Staff can reach GP from home or another office without a slow VPN.
- Room to grow or shrink. You can change server size as your needs change.
What Hosting Does Not Change
It is just as important to recognize the limits:
- Dynamics GP updates, including the year-end tax update, still need to be installed.
- Your customizations, add-ons and integrations still need care and testing.
- You do not get Copilot, automatic updates or the modern features of a cloud ERP.
- Dynamics GP’s retirement dates stay the same. If you use GP on a subscription license, your right to use it ends on April 30, 2031.
So hosting improves the infrastructure under GP. It does not modernize GP itself.
How to Migrate Dynamics GP to Azure
Every setup is different, but most moves follow the same eight steps.
- Review your current GP system. List your Dynamics GP version, modules, third-party add-ons, integrations, reports and number of users. Note the size of your databases. This tells you what must move and what can be left behind.
- Create your Azure subscription and choose a region. Pick the Azure region closest to most of your users. This keeps GP fast and can also matter for data residency rules.
- Design the environment. A typical design has a resource group, a private virtual network and two or three virtual machines: one for SQL Server, one for the GP application and user sessions, and often one for sign-in services. Smaller businesses can sometimes combine roles. Older guides mention “affinity groups”, but Azure no longer uses them.
- Set up SQL Server on an Azure virtual machine. This is the step where many projects go wrong. GP needs a full SQL Server installed on a virtual machine. Microsoft states that Dynamics GP cannot use Azure SQL Database or a managed instance. Place data files and log files on separate disks for better performance.
- Back up and move your data. Take a full backup of the GP system database and every company database, then restore them on the new SQL Server. Remember the items outside the databases too: SQL logins, modified forms and reports, Management Reporter data, and integration files.
- Install GP and set up user access. Install Dynamics GP and your add-ons on the application server. Then decide how users will connect. Most businesses today use Azure Virtual Desktop or Remote Desktop Services, publishing GP as a remote app. Turn on multi-factor authentication for every user.
- Test before you switch. Run at least one full trial move. Ask real users to post transactions, run reports and print checks. Printing and emailing documents are the two areas that most often need adjustment after a move to the cloud, so test them carefully.
- Go live, then maintain. Choose a quiet time, such as a weekend after month-end. Take a final backup, restore it in Azure and switch users over. Afterwards, set up automatic backups, monitoring and a schedule for Windows and SQL Server patches.
Costs and Licenses to Plan For
- Dynamics GP license: your existing GP license moves with you.
- SQL Server: you can bring your own license if you have Software Assurance, or pay for SQL Server as part of the virtual machine price.
- Remote access: Remote Desktop Services needs its own licenses.
- Azure usage: start on pay-as-you-go for the first few months to learn what size you really need. After that, reserved instances can lower the cost considerably. Microsoft says the saving can be up to 72 percent compared with pay-as-you-go.
We recommend working with a partner who knows both Microsoft Dynamics GP and Azure. A mistake in sizing or security is much easier to prevent than to repair later.
Upgrading Dynamics GP While Migrating to the Cloud
If your Dynamics GP version is old, the move to Azure is the best time to upgrade it. You are already building a new environment and planning downtime, so doing both together means one project and one period of disruption instead of two.
Your version also decides whether Microsoft still supports you:
- GP 2016 and earlier: these follow the Fixed Lifecycle Policy and are now out of support. GP 2016 support ended on July 14, 2026.
- GP 2018 and 2018 R2: support ends on January 11, 2028.
- GP 18.2 and later (October 2019 onward): these follow the Modern Lifecycle Policy. You stay supported as long as you install at least one of Microsoft’s all-inclusive updates each year.
The newest release, Dynamics GP 18.9, is planned for October 2026. To upgrade to it directly, Microsoft expects you to start from a recent GP 18.7 build or later. Older systems need extra upgrade steps along the way.
Putting an unsupported version of GP on a new cloud server gives you modern infrastructure with out-of-date software. Upgrading at the same time means you get tax updates, security fixes and Microsoft support until the end of 2029.
There is one more benefit. Microsoft’s tool for moving GP data to Business Central works best with a recent, well-maintained GP system. So an upgrade today also prepares you for your next move.
Next Steps
Before you move Dynamics GP to Azure, ask one question: how long do we plan to stay on GP?
Hosting Dynamics GP on Azure makes sense if:
- Your server needs replacing soon, and you are not ready to change ERP systems yet
- You need secure remote access now
- You want two or three stable years to plan your next system properly
Going directly to a cloud ERP makes more sense if:
- You were already planning to leave Dynamics GP within the next year or two
- You want automatic updates, Copilot and built-in links with Microsoft 365
- You would rather pay for one project than two
For many GP users, the second path leads to Microsoft Dynamics 365 Business Central, Microsoft’s cloud ERP for small and mid-sized businesses. With Business Central, there are no servers, no update projects and no end-of-support date to plan around. Our guide to Dynamics GP end of support explains the timeline in more detail.
Summarizing the choice: Azure hosting buys you time and stability, while Business Central gives you a long-term system. Neither is wrong. The right answer depends on your timeline, your budget and how much change your team can take on now.
Nevas Technologies helps Microsoft Dynamics GP (Great Plains) customers with both paths:
- Staying on GP for now: upgrades, Azure hosting design, migration and ongoing support
- Moving forward: a complete Dynamics GP to Business Central migration, from assessment to go-live
Not sure which path suits your organization? Talk to our consultants. We will review your GP system and give you a clear recommendation with scope, timeline and cost.
Frequently Asked Questions
Can Dynamics GP run in the cloud?
Yes. Microsoft Dynamics GP (Great Plains) can be installed on virtual machines in Microsoft Azure. It is the same software, running on rented cloud servers instead of your own hardware.
Does moving GP to Azure extend its support?
No. Product and tax updates still end on December 31, 2029, and security updates end on April 30, 2031, wherever GP is installed.
Can GP use Azure SQL Database?
No. GP requires SQL Server installed on a virtual machine. Azure SQL Database and managed instances are not supported.
How long does it take to move GP to Azure?
It depends on your database size, add-ons and integrations. A simple system can move in a few weeks, while a complex one with an upgrade included takes longer. A review of your system will give you a realistic timeline.
Is it better to host GP on Azure or move to Business Central?
Hosting suits businesses that need a few more stable years on GP. Business Central suits businesses that want a long-term cloud system. Many companies host GP first and move later, but going directly can save the cost of a second project.
