Today we are happy to announce the release of our second Azure DevOps task in the marketplace, which allows you to deploy code from the asset library into a cloud test and sandbox environment. This completes are first version of end-to-end CI/CD automation for Dynamics 365 for Finance and Operations. If you already have the extension enabled in your Azure DevOps account, the update upload task and new deploy task should be available without any action needed. Search for "LCS" when adding new tasks to your release pipeline and you will find the new Asset Deployment task. We are also actively working on official documentation on the usage and setup of the tasks, so stay tuned for that.
As outlined in our original post when we released the asset library upload task, you will need to perform some setup around Azure Active Directory to create a Dynamics Lifecycle Services (LCS) connection in Azure DevOps. If you've already performed this setup previously, you can re-use the same connection for this new task.
With this release, there are a few notes to make.
For the upload task:
For the new deploy task:
We are excited about these first steps in our CI/CD story and are looking forward to your feedback.
I was so waiting for this! Great news! Thanks Joris!
Excellent work Joris and the team, I will configure it first thing tomorrow :-)
Is there a way to make MFA working with the connection ?
@Arnaud sadly no. We've looked into authentication (with MFA) when you setup the connection, and just retaining the token instead of the full user/pass. However, LCS has a time limit on logins - so you would literally have to log in again every day... We're considering what we can do with the LCS team without having to sacrifice any security on their part.
That said, most people run into this issue, and people just setup a special service account for this integration bit. It's probably the best way to go anyway, it's enforces better security by using a separate account and avoids a person leaving the company or changing their password and breaking your release pipeline.