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
We are going to deploy a new package to the consultant testing environment. Does LCS provide any snapshot feature, which allow us to back up the environment just in case if the deployment is not going well, we can still roll back the environment?
If you know which exact deployable package was used before, you can re-apply that one if the new one has incorrect features. If the deployable package is created for the correct platform version, application version and using the build machine, it should not give any issues. There are some backup steps during deployment, but there is no automated recovery when something fails.
Thanks André, to create a database backup, do I need to log a request or I need to access database by myself to manually create a backup?
You can manage a database backup and restore on non production environments yourself: docs.microsoft.com/.../dbmovement-operations
If I click "Abort" when the deployment is in failed status, will the environment roll back completely to the original status?
Abort means stop the current process only. It is not a rollback option. You can deploy a new correct package when it failed and you aborted it: docs.microsoft.com/.../deployable-package-troubleshooting
Business Applications communities