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
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Does anyone know if the Navision 2016 needs some remediation for Log4j vulnerability?
Here is a Microsoft statement on this:
OK, but specific for NAV application not exists any vulnerability, right?
Microsoft no longer supports Dynamics NAV 2016 and this month we shipped last CU for Dynamics NAV 2017. Best is to consider an upgrade to a supported release of Dynamics NAV / Dynamics 365 Business Central.
Based on Marco's reply you should consider upgrading to NAV 2017 since 2016 will not be supported or updated.
Yes, I know about that but I can't perform an update at now.
Is there any vulnerability involving NAV2016 version?
We cannot make such an official statement since our official testing stopped around time frame we shipped last CU for Dynamics NAV 2016 (Apr 13, 2021). If upgrade cannot be done, at least consider to uptake last CU for Dynamics NAV 2016:
You may also want to consider to perform a technical upgrade to a support release. This is still not supported by Microsoft because the database still considered to be a Dynamics NAV 2016 environment.
Business Applications communities