End of mainstream support for Microsoft Dynamics AX 2009, 2012, and 2012Mainstream support for Dynamics AX 2009 Service Pack 1 (SP1), Dynamics AX 2012, and Dynamics AX 2012 R2 ended Oct. 9, 2018. After that date, only security hotfixes will be provided for these three versions through the extended support period that until Oct. 12, 2021. Read more
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
The first automation task to close the continuous integration cycle in Dynamics 365 for Finance and Operations with Azure DevOps pipelines was released recently as described on the official announcement.
These are some high-level instructions to set it up while the official documentation is released:
To keep things simpler, these prerequisites should be prepared before starting this process:
In order to authorize DevOps Pipelines to connect to the new Lifecycle Services (LCS) API, an application must be created in the organization's Azure Active Directory. Elevated permissions are required for this operation.
More information about registering applications in AAD here:
And about permission consent here:
A release pipeline will be used to connect the Build output with the Asset Library in LCS. New build packages will be uploaded to LCS automatically through this pipeline.
Use the Create a release button to create a new release manually (or launch a build, if you configured the Continuous Integration trigger):
Hopefully your results will look like that (otherwise check the logs to understand what’s happening, most common error so far is authentication with the AAD app):
If everything went well, you have a new file in the Software deployable package folder on the LCS Asset Library.
To get more information about this release and the setup process check the official announcement here and this blog post.
Hope these instructions are useful to understand how to setup this first automation task, that hopefully won’t be the last one. Check the documentation for upcoming changes regarding Developer tools and application lifecycle management.
Business Applications communities