Views:

Applies to Product -Dynamics 365 Lifecycle Services


What’s happening?
Customers are concerned whether renaming a project in Dynamics Lifecycle Services (LCS) will interfere with existing connections or change the Project ID.


Reason:
Renaming a project in Dynamics Lifecycle Services (LCS) does not change the Project ID. The Project ID remains the same, ensuring that the core identity of the project is preserved. However, there are considerations regarding existing connections.


Resolution:

  • Renaming an LCS project should not inherently cause issues with existing connections to Azure DevOps. The connections are typically based on the Project ID and other configuration settings rather than the project name.
  • After renaming a project, users might need to update their local configurations or restart their clients to reflect the new project name. This is similar to renaming a project in Azure DevOps, where users need to update Git remotes or other local settings.
  • If there are service connections set up between LCS and Azure DevOps, ensure that these connections are still valid after the rename. Typically, these connections use tokens and other identifiers that should remain unaffected by a name change.