Suggest a new Idea

  • 147

    LCS: Sync up actual LCS status of cloud-hosted environments with Azure

    Suggested by Khee ChanPlanned – Mid-Term 2
    Category: Lifecycle Services

    When the VM in a cloud-hosted environment is stopped or started in Azure (e.g. via Azure automation run books), the status of the environment is not reflected in LCS. This is causing confusion on the part of users who navigate to these environments via LCS.

    Our customer is using the automation run books to manage their Azure VMs in order to optimize their Azure run costs. The Azure management portal shows the correct status of the VMs in these environments.

  • 128

    Automated upload of Build package to LCS

    Suggested by Victer ChristyPlanned – Mid-Term 14
    Category: Lifecycle Services

    When the full build completes through VSTS the package should get  uploaded to the shared asset library of LCS for the subscription . So that deployment can happen to multiple environment at the same time on a click.

  • 41

    Be able to Schedule Deployable Package installation to Sandbox/Demo Environments.

    Suggested by Mattias LindgrenNew 5
    Category: Lifecycle Services

    Be able to schedule a time for deployment of a selected Deplyable Package for Sandbox Environments and Demo environments rather than it´s being applied immediately.

    Time saving for "off hours" when its usually deployed, since you got the status emails for the environments to check up on the progress.

  • 29

    Generic API for LCS

    Suggested by Stefan FrankenNew 5
    Category: Lifecycle Services

    Many tasks in Azure/365 can be automated. On.y in LCS is no chance to control with e.g. PowerShell. An API like REST would be very fine for automating LCS tasks.

  • 23

    Improve IP Access Restrictions

    Suggested by Thomas ZakNew 2
    Category: Lifecycle Services

    The new IP access restrictions are very cumbersome and hard to maintain. It takes over a minute for each IP address range to be entered and we have to enter an average of 3 ranges for about 3 environments per client and about 50 clients. That's nearly a full day of time for just data entry. 

    This could be greatly simplified by: 

    1. Making it possible to set the restrictions at the LCS project level instead of the environment level. 

    2. When saving an IP address range, do not take 35 seconds to save (presumably you are directly updating the firewall and getting an acknowledgement back). Instead just save the data and asynchronously change the firewall. In the 0.01% of the cases where setting the firewall rules is a problem, alert people via e-mail. 

  • 19

    Link LCS VSTS to a customized VSTS Template

    Suggested by Claus AndersenNew 1
    Category: Lifecycle Services

    The current integration of Work item types (and maybe other things) between LCS and VSTS is hardcoded, which means that you cannot link LCS to a customized VSTS Template (it is possible, but you're informed that i "May cause errors").

    Since the way of using VSTS is very much dependent on how the partner works with implementations and product development (probably different from partner to partner), it should be possible to setup the mapping yourself.

    So, the proposed idea is to allow for setting up the mapping instead of it being hardcoded.

  • 19

    Allow deploying DEV VMs to DevTest Labs

    Suggested by Martin DrábNew 1
    Category: Lifecycle Services

    Azure DevTest labs ( are intended for exactly this purpose; they simplify management of Dev/Test VMs, allow stopping and starting VMs on schedule (without writing any code) and so on.

  • 18

    LCS API for RDP IP Address Restrictions

    Suggested by Brad BatemanNew 0
    Category: Lifecycle Services

    Create an API for maintaining the LCS RDP IP address restrictions (aka IP white listing, LCS firewall rules) which appear under "Maintain > Enable access".  This would allow the rules to be updated via a script, which would make it much more manageable when working with many environments.  It would be nice if these rules could be applied at the project level, and overridden at the environment level if needed.  

  • 18

    Add Granular Security per Environment in LCS Projects

    Suggested by LUCIO MOSCHELLANew 1
    Category: Lifecycle Services

    To avoid creating and managing different projects for each D365FO environment which needs a different set of security configuration, please consider adding granular security per environment.


  • 17

    Downtime Landing Page

    Suggested by Lane SwenkaNew 0
    Category: Lifecycle Services

    It would be great to support a downtime landing page.  This would go hand-in-hand with the downtime message that we can send to users in the system prior to the outage.

    During an outage, there is no way for users to understand that the system is offline on purpose.  A simple static page showing the downtime was planned would be helpful - not everyone reads their email or was in the system prior to the downtime notification.

    Something simple such as this elegant 404 page: