web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Error while creation o...
Microsoft Dynamics AX (Archived)

Error while creation of D365FO VM using Hyper-V on Azure VM

(0) ShareShare
ReportReport
Posted on by krishna.rao@dax 3,008

Hi All,

Greetings.

Aim: Created D365FO VM on Azure VM(using Hper-v)

Steps followed:

1. We have created a virtual machine using Azure portal.  configurations: Windows 10 pro, 28 GB ram

2. Enabled hyper v .. a) go to run -> optionalfeatures.exe -> installed by selecting hyper v components(Hyper-v Hypervisor not grayed out//might be issue)

HyperVWindowsFeatures.PNG

3. Added new Virtual machine & attached existing hard disc image file D365VHD-file.PNG

4. While starting vm getting error "Hyper v virtual machine error failed to start the virtual machine because fo the hyper-v components is not running" HyperVError_5F00_WhileStarting.PNG

  -- tried below command -- Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart

   https://docs.microsoft.com/en-us/azure/virtual-machines/windows/nested-virtualization  //getting error term  Install-  WindowsFeature is not recogized as the name of cmdlet

Highly appreciate your guidance..

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Martin Dráb Profile Picture
    Martin Dráb 239,082 Most Valuable Professional on at

    Let's change the goal first. It should be "Created D365FO VM on Azure " instead of "Created D365FO VM on Azure VM(using Hper-v)". Hyper-V is used for hosting VMs on premise; if you use Azure, you don't need another hypervisor. Therefore it makes no sense having "using Hyper-V" as a requirement.

    Then let's look how to achieve the goal. Don't try to install D365FO by yourself; it's not supported. Instead, deploy a pre-installed machine from LCS.

  • Suggested answer
    nmaenpaa Profile Picture
    nmaenpaa 101,166 Moderator on at

    You shouldn't deploy new empty VMs. And you will definetely not need Hyper V if you want toto deploy to Azure.

    Instead you need to let LCS deploy a ready-to-use environment to your Azure subscription. Follow the instructions of this article (don't forget to study and follow the instructions in the linked articles, too): [View:https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/deployment/deploy-demo-environment]

  • krishna.rao@dax Profile Picture
    krishna.rao@dax 3,008 on at

    Hi Martin & Nikolaos.

    Thank you so much for directing in right path.

    I will explore more on this & will post here.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Joris dG Profile Picture

Joris dG 5

#2
Andrew Jones a1x Profile Picture

Andrew Jones a1x 2

#3
Basit Profile Picture

Basit 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans