Hello,
our client wants to move Epicor 10 to Kinetic 2022. Kinetic client is on premise. but the app and database they want to move to azure with their own host(NOT using epicor servers). they want to manage their server by themselves. it is the first time we configure that. so, we just want to know if there is document or the admin tool can configure such migration.
Azure is the exact same as on prem just a really long cable
Standard install works fine, however if you don’t have experience administering an azure infrastructure I’d recommend getting some help or training
so, in the config file, the appserver url is still net.tcp://appserver/Epicorxxxxx something like that.
or appserver url will be changed to https://azureserver.com/epicorxxxxx ???
The install setup and configuration is all standard in Azure(or any other computer), but you need to setup your Azure infrastructure correctly.
If you are upgrading to 2023 there is no Net.Tcp protocol anymore and how you reach that server depends on your configuration
Is you Azure instance public? Are you ok with your EPicor being on the WAN? If you don’t want that you’ll have to setup a point 2 point VPN or a private link between you and them to access azure as if it were your internal network
There is a lot of configuration that needs to be done to do this right on any host let alone a cloud host. If you aren’t already familiar with Azure and its architecture you’ll be doing your customers a dis-service by doing this for them without the proper training or help.
I would highly recommend you find someone who understands azure architecture and setup to get that up and running and then you can put epicor on it like you would any other local instance.
Your Azure Team should certainly be able to handle that question. Like Jose said, all Epicor requirements remain the same if you run on-prem, co-lo, or Public Cloud. If it’s approved by Epicor, you can do it in Azure. Note Epicor has not approved Azure SQL at this time. Rich has mentioned that in a future version of Kinetic, it will run using Azure Kubernetes Service (AKS). Until then, it’s going to be virtual machines that you pretty much have a lot of control over.
And since it’s the cloud, you can try before you buy. Unlike on-prem, where you have to provision correctly up front, you can spin up a system and try it out to see if it works for your situation. Once that is figured out, you can get better pricing by using reserved instances.