You can synchronize the BPM library hierarchy into your Azure DevOps/VSTS project as a hierarchy of work items (epics, features, and so on) by clicking on the VSTS sync option:

This is a limited two-way sync from LCS to Azure DevOps/VSTS that will keep your Azure DevOps/VSTS work items updated with any changes that are made to the LCS BPM library. Only when the requirements have been added to the right level can Azure DevOps/VSTS be synchronized with BPM. 

Once the work items have been synchronized, you will notice a new requirement tab that's visible to your work item in BPM, showing the Azure DevOps/VSTS requirements ID:

Inside Azure DevOps/VSTS, the sync work items can easily be seen under the work section of the project and under the Backlog features:

Once the work item is available in Azure DevOps/VSTS, as shown in the preceding screenshot, you can perform all the necessary steps and actions to update it with additional information, links, documents, and so on and use them for various purposes throughout the project (such as reporting, tracking, status, planning, and so on). The following screenshot shows a sample BPM library work item being edited in Azure DevOps/VSTS and an example of a work item type called feature:

Note the acronyms and their relationship between Azure DevOps/VSTS and BPM:

• 1 (LCS) project: n (Azure DevOps/VSTS) epics
• 1 (Azure DevOps/VSTS) epic: n (Azure DevOps/VSTS) features
• 1 (Azure DevOps/VSTS) feature: n (Azure DevOps/VSTS) stories
• 1 (Azure DevOps/VSTS) story: 1 LCS BPM (requirement)