Announcements
No record found.
Hello All,
Please tell me the steps of service update in development environment. The current version of dev env is 10.0.4 and I have to update it in 10.0.13 which is the version of sandbox and production environment.
Hi D365 FnO developer,
1. You need to install .NET 4.7.2 runtime (needed for update to 10.0.13) and reboot VM
community.dynamics.com/.../action-required---net-version-and-visual-studio-2017
2. Next step is to apply the service update package (same applied to sandbox and prod) to your dev environment in LCS.
Hi,
The first step would be to update the .NET version in the environment to 4.7.2 and then run the update package. You will need to install VS 2017 as well. Please check this link for details.
However, you are on a pretty old version and can run into issues during the update. It might be easier to deploy a new environment with this PU (if done through LCS) or download the latest VHD files from and deploy the VM (if hosted locally).
Hi D365 FnO Developer,
The new pre-built DEV machine includes the correct configuration for Visual Studio 2017 and .NET framework 4.7.2. It would be most convenient to deploy the new DEV box, connect to DevOps, get the latest code which was checked in and continue with the development efforts.
Hi D365 FnO Developer ,
community.dynamics.com/.../d365fo-update-to-pu36-10-0-12-and-experienced-error
If you have a Microsoft-managed VM, we will take care of .NET 4.7.2 for you prior to the PU37/10.0.13 release.
If you have a VM on your own subscription, or you use the downloaded VHD, you will need to manually install .NET 4.7.2 today or any time prior to installing PU37/10.0.13.
If you have MS managed tier 1 environment (your DEV environment) then please be informed that this is going to be deleted on 1st December this year. Your best bet is to deploy cloud hosted development environment with the required version so you don't need to rework after 1st December.
From 1st Nov you will also not be able to RDP to your MS managed Development environment so you only have few days left so deploy it as cloud hosted using your own or client's azure subscription.
I recommend to simply deploy a new system. You will save a lot of time because most likely you will encounter some issues when updating such an old system. And you will get Visual Studio 2017.
In general you should try to keep your dev system up to date and in a supported D365 version (never skipping more than 2 consecutive updates).
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.
Congratulations to our 2026 Super Stars!
Thanks to all of our 2025 Community Spotlight stars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Giorgio Bonacorsi 659
André Arnaud de Cal... 465 Super User 2026 Season 1
Syed Haris Shah 304 Super User 2026 Season 1
