Personalized Community is here!
Quickly customize your community to find the content you seek.
Latest TechTalk Videos
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All 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)
Business Applications communities