The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I’ve already wrote about new Microsoft Azure Portal code named Ibiza. When you look this new portal, one of the first news in that now we have two menus for virtual machines:
You will see that all virtual machines you already created using old Azure Portal are placed in Virtual Machines (classic). I want to give you a small descriptions about difference between these two options.
The new Azure Resource Manager with a new API doesn’t uses resources as the old API. Because of that, the classic API stack is still operational, but you’ll see those resources showed up as (classic). You have not a reason to convert classic VM to the new VM. You just need to know that you cannot include classic VM in a virtual network deployed with Resource Manager and they don’t have to be included in a virtual network (unless new VMs must be included).
But if you want to migrate classic VM to the newer model, first you have to be sure you can afford a downtime for your VM. If you can afford it, than you can do it using ASM2ARM PowerShell script. You can find all details here.
I hope, I helped you. I have some more information about it and I’ll prepare a real interesting example soon.
Business Applications communities