Migration on-premise ERP(Legacy) to Azure Part2 : Azure SQL

 

Previously topic We have already migration group of Workload VM from Hyper-V to azure 

Migration On-Premise ERP (Legacy) Application from Hyper-V to Azure Part1 (Lift and Ship)

 

  

We have success fully lift up 4 VMs running with zero downtime. The customer wants to reduce activity to maintain SQL Server VMs. And increased Hight availability. So, the solution is to convert SQL servers using  Azure DMA

On Azure portal. You can start with Azure Migration and select SQL server (Only)

Download: Data Migration Assitant and install on your Hyper-V host

- Assessment 

that will discover your SQL environment is compatibility

- Migration Step

one assessment is complete you can add a new project and select Migration.

Follow Migration Step

 1.  Select source: point to source SQL Server Instant  On-premise

2. Select Target: Point to your Azure SQL

3. Select object: select Database to migrate

4. System generate Scrip and Deploy schema

5. Select Table (Select all)

6. Confirm Migrate

after migrated check the SQL Table  in Azure

Change Database server endpoint  in Application Server 

You can follow SQL Migration from Azure documentation : 

https://docs.microsoft.com/en-us/azure/dms/

so this is the last outcome. Our database has been converting into Azure SQL

In this case, The ERP application is named  Microsoft Dynamics NAV

Microsoft Dynamics NAV is an older version of Dynamics 365 Business Central Currently it's available as SaaS of Microsoft Dynamics 365 ERP Family. 

I'm going to change the configuration of the NAV Application server to change the target Database server from  On-permiss SQL 2017 to  Azure SQL.

https://docs.microsoft.com/en-us/dynamics-nav/how-to--deploy-a-microsoft-dynamics-nav-database-to-azure-sql-database

Change NAV Service configuration

Change Database credentials to SQL authentication

Finally, we can reduce the infrastructure of the ERP application 

Next Topic. We will improve the NAV Application server to scalable and high availability by using a Virtual Machine Scale set

Part 3

Migration on-premise ERP(Legacy) to Azure Part1: Lift and Ship Hyper-V

  

In this scenario, the customer has a Microsoft ERP (Legacy) running On-permiss under Hyper-V Technology

The company want to move the ERP to the Azure Could environment without modification

because they will have a lot of customization and dependency inside the ERP system.

There is 4 VMs workload for application Group

1 VM running Active Directory Domain Service

2 VM running Application Server 

1 VM running SQL Server 2017

The best tools for this requirement in Azure can be using Azure Migrate

Under Server, Database and web app

    There is two-step 

    1. Assessment Tools

"To discover your on-premises environment, you will need to deploy the Azure Migrate appliance. The following steps will help you set up and configure the appliance."

I download appliance VHD files and deploy to the Hyper-hosting  server follow Discover Step

 after connect to the appliance VM, the Appliance configuration manager will be running you have to input parameters required  your Hyper-V hostname, administrator user name & Password

 Once your complete the appliance step. This app will send back discovered your VM to azure for assessment.

this assessment section will help you estimate the cost and plan to host the VMs.

 

2. Migration Tools

you already discover your on-premise environment and complete the assessment. Now it's time to migrate 

- Discover server

Discover server for migration will be different from Discover for assessment .you may need to install 

Azure Site Recovery Provider on your Hyper-V hosting server

Next step is replicating data from VMs

Once the replication server is complete you can go next for you can test migration or skip to migrate.

This step System will generate VM by replication data from Hyper-V

Resource visualizer from 4 VMs

Next Topic . We will improve SQL Server by converting to Azure SQL

https://anusornkrongkeaha.blogspot.com/2021/08/migration-on-premise-erp-legacy_81.html

Power Virtual Agents Chatbot Create Lead in Dynamics 365 for Sales (No Code)

In this topic we will leveraged Chatbot represent as sales person to simulate software selling scenario. Once get requirement from customer the Bot will trigger the flow to create record in Dynamics 365 Sales with Lead information.

There is 2 Part to achieve

Part1 : Create Power Virtual Agents Chat bot to capture requirement from Customer

Part2 : Create Microsoft Automate flow to Create Lead in Dynamics 365 Sales using Dataverse

Create Leads record in D365 Sales will use Dataverse Connectaion replace D365 connector (Deprecated)

Part1: Create Power Virtual Agents Chat bot to capture requirement from Customer

  1.1  Login to   Microsoft Power Apps    and select Environment. 

- Select Chatbot >> Crate

1.2 Power App will navigate to Power Virtual Agents >> New Topic

   

1.3  name the Topic and add phrases  to trigger the topic .for example phrases  is  "CRM" >> go to authoring canvas

1.4 Add multiple choices refer to available product.

1.4  the three conditional has been create as per each option

1.5 Create Question for E-mail

1.6 Drags three condition to one point before E-mail Step

1.7 Add another question.

-Person Name

-Budget Amount

Part2 : Create Microsoft Automate flow to Create Lead in Dynamics 365 Sales using Dataverse

2.1 add call an action step after "Processing your request" Message

2.2  System will navigate to Power Automate

- add Input to Power Virtual Agents step as follow

2.3 Add Microsoft Dataverse >>Add new Record

-  Select Entity "Leads" and assign variable from Power Virtual agents step.

2.4 add Last step return Value to Virtual agents then save

2.5 Back to Power Virtual agent and Map input variable to the flow. Save

2.5  Input variable for  Record created from Dynamics 365 Sales

Now time to test the Bot------------------------

- Test your bot and say Hi ,Standard topic (Greeting) are response    

- Input "CRM" , system detect Trigger Phrases and show the option

- After customer select product Bot will ask for more information

- The last question will trigger The flow to create Lead in Dynamics 365 Sales

- Open Dynamics 365 Sales Hub . Check Lead already create from Bot