Personalized Community is here!
Quickly customize your community to find the content you seek.
Now Available in Community - New TechTalk Videos for 2020
Read More about New TechTalks for 2020
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
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.
It would be really great if we could somehow use versioning instead of endlessly creating new Asset Library entries with every release.
Regarding MFA. We have attempted to utilize a MSFT managed VM provisioned as a Build Server which permits us to specify an outbound IP address that is set-up to skip the MFA process. The problem we are encountering is that AzureRM powershell cmdlets are required and there is no capability for us to perform that action as MSFT clients (us) are not admins on those machines. Is there a contact group that can make this happen or specialized task that we can use to perform this action. (I'm thinking of something equivalent to the NuGet versioning task)
First of all. Thanks for a great post and a great tool.
I have been using it back 'n forth in different scenarios and it's working mostly as expected.
My challenge right now is, that the VM has to have the Deployed state in LCS, to be able to run the task from DevOps, but the state can sometimes be something different from Deployed for different reasons.
Why this happends..
For all tier1 Cloud hosted environments, we use an Azure automation account, to automatically shutdown and start the environments, to save some of the costs of the VMs. The LCS only communicates with the VM on-demand and therefore, it does not always have the correct status of the VM.
Is there any way that this challenge can be handled in an automated way? Making sure that the state of LCS matches the state of the VM.
My first thought, was to add an some PowerShell, that verify that the D365 application is running and when that is okay, it will proceed with the deployment (this will solve other issues, making sure that everything is running, before proceeding). But that does not solve the state in LCS.
Since we are working on removing the need for a build VM, we have no plans to add AZPS on it. You can install it without admin, for just your user:Install-Module -Name AZ -AllowClobber -Scope CurrentUser -Force -Confirm:$False -SkipPublisherCheck
Business Applications communities