Skip to main content
Dynamics 365

The Microsoft Dynamics Lifecycle Services team is happy to announce the immediate availability of the February release of Lifecycle Services. 

Update experience 

In the February release of LCS, we have reduced the lead time to submit a request to apply an update to a Production environment from 8 hours down to 4 hours.


In the January release of LCS, we began supporting application updates by using the automated update experience in LCS to a Dev/Build topology. Based on feedback, we have made a change to allow only the application of binary updates on a Dev/Build topology. To apply an application hotfix/customization, you can manually apply the code package and then generate a deployable package from the build environments which can then be applied on sandbox and production environments.  

Environment details

We have moved the environment release and version information to the Environment details page. We have also made fixes to harden the backing infrastructure used to retrieve version information. Going forward, you will now see Application Release, Platform release, Platform version under the Environment version information section.  


 License checks

In the February release of LCS, we have made a change to the license checks to ensure that a customer has purchased the minimum number of licenses required to go live in Production. The Licensing guide currently states that a customer must buy at least 20 Enterprise, Plan 2, or Device licenses.  The license checks don’t impact Tier 1 and Tier 2 deployments but prevent the deployment of a Production environment. Customers that don’t yet have deployed Production environments and don’t meet the minimum licensing requirement will receive a warning in the Action Center on the Project dashboard page.


Monitoring and diagnostics

In the February release of LCS, we have added the ability to start data collection on demand. To do this, click Start collection on the Index analysis tab under SQL Insights in the Monitoring portal. After you have started the collection, refresh the page. The collection will take about ten minutes to complete. After it is completed, enter the date and time information to view the results. You can also view the last collection date update on the Index analysis page.
Business process modeler (BPM) 

The new user interface of BPM described here now allows you to create a new BPM library hierarchy by loading the information from a Microsoft Excel workbook. 

On the Business process libraries page, click on Import from Excel. Use this feature if you are starting a brand new library. 



Enter a library name, browse for the Excel file that contains your hierarchy, and then click Import. 


If this is your first time creating a BPM library from an Excel workbook, click Download template to download an Excel file that illustrates the expected format. In the Excel file,  you can specify business process names, descriptions, hierarchies, regions, and industries. 


Microsoft Dynamics 365 – Translation Service  

With the February release of LCS, Microsoft Dynamics 365 – Translation Service has added the following support: 

  • Microsoft Dynamics NAV 2017 was added to the supported product versions. 
  • The Translation source language list and the Translation target language list dropdowns now contain all languages and are sorted in alphabetical order. The product’s GA languages are in bold style for easier identification.  
  • A Direct support email contact is provided if you need an assistance with a language that is not listed.  

Note the following when planning o submit legacy materials: 

  • When a source or target language is a non-GA language, verify that the legacy materials contain more than 10,000 language pairs. 
  • When translating from English to a GA language, or a GA language to English, any number of legacy language pairs are accepted. 


Issue Search

With the February release of LCS, you can now view a list of issues that you have subscribed to for notification when the issue is resolved.  

You can find the list by clicking View issue notifications beneath the search box in Issue search.  


You can click View notifications on the page of any bug you are already subscribed to .  


The page will show both active and closed issues.