Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View 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 | Talent TechTalks | Upcoming TechTalks
I have a few doubts about deployment.
Development team (3 to 7 team) develop/customise the application & will create the deployment package.
Microsoft team will deploy in to cloud.
1)Weekly how many times request Microsoft for deployment into the cloud?
2)who will handover deployment package to Microsoft team? like Administrator or functional lead or technical lead?
3)Who will test (UAT) the application after deployment into the cloud?
(Client or Customer) or development team?
4)During testing Microsoft team will help if any issues arise? who will report to Microsoft team like client or development team
5)Where is DevOps in D365FO environment?
I am expecting answers realtime not from the document, please
1. There is no limit , I dont think anybody does production deployment on daily basis .Usually its bi weekly or weekly or sometime monthly unless some critical things happens. As long as you upload package and schedule package for deployment with proper window , DSE is going to deploy it.
2. You have to upload your package in Asset library of your project in LCS and mark the package as release candidate and select a package while scheduling the release, DSE(Microsoft Team) is going to grab that package for deployment
3. UAT package deployment has to be validated by you/Your team before even making that package as release candidate for production deployment.
4. Application related issues needs to be taken care by customer /Your team.
5. Devops is not in D365 environment. Its a separate service which enable continuous delivery of value to customers. DevOps includes core practices such as planning and tracking, development, build and test, delivery and monitoring and operations
You should read detail documentation on docs.microsoft.com about deployment process , how azure devops can be used to managed application lifestyle and other things.
Microsoft deploy code only to production and thats it. You have to deploy to all other environments, including test and UAT, so it can be done whenever you need and obviously you are responsible for testing. Usually UAT is done but a customer. Microsoft can fix only bugs in standard product and won't fix issues in your customization.
There is no such thing as handover, production deployment is scheduled through LCS and scheduling can be done by any person that has required security rights to do so.
DevOps can be used to automate deployments to non-production environments and should be used as a version control system to store source code and also connected to build environment to create deployable packages
Thank you Sukrut&Ievgen for clarification.Both of you replied with good informaton.
Sukrut & Ievgen,
I confused from this below blog about CICD mechanism.
So have you any one implemented CI/CD mechanisms in D365FO environment?
I will come back to you again still I have few doubts.
What you are confused about ?
we don't have DevOps in D365FO but blog saying CICD mechanism.
Have you ever implemented or have you ever seen CICD mechanism in D365FO environments?
Yes, you have build and release available, here is an example of release pipeline anthonyblakedev.blogspot.com/.../azure-devops-release-pipeline-for_21.html
Yes we did , If you dont have DevOps , then you should first sign up for that. You can sign up for free up to 5 users and then later pay if you want to add additional users.
Once you sign up , you should be able to do all other thing like setting up CI/CD , pipelines etc.
As Ievgen rightly pointed out, for CI/CD Anthony Blake has provided good insights in his blog. In addition to this, Senior Program Manager Joris has provided some useful insights on how to get started with the CI/CD part with Finance and Operations.
Also, there is an useful presentation that's uploaded on the AxUG website.
This presentation points you to two more references:
To answer question number 5,
5)Where is DevOps in D365FO environment?A] DevOps Project URL details are available under Lifecycle Services -> Project Settings -> Visual Studio Settings. Azure DevOps (previously known as VSTS) is a cloud service and needs to be configured in the Development machines and Build machines(if any). There are some hands on labs readily available on the Azure DevOps site. There is a lab called continuous integration in there. You can use this lab and configure Azure DevOps for Finance and Operations using Joris's presentation uploaded on the AxUG site.https://www.azuredevopslabs.com/labs/azuredevops/continuousintegration/
Hope this helps.
Thanks,Navneeth Nagrajan| Dynamics 365 Technical Consultant
As others already mentioned, deployments are controlled in Lifecycle Services. You can automate deployment to test system after your nightly build. Build and automation is handled in ADO.
Prod deployment must always be initiated manually in LCS.
Microsoft doesn't provide any functional / testing support. They simply provide service for deploying code packages to environments. Quality control of your code is your responsibility.
Thank you for providing more inputs.
I will go through all the information which you have shared links & presenations.
Business Applications communities