Thanks for submitting the idea and the question! Would you mind elaborate more how the TFS and the VMs will be used for in this case? Does the TFS behave as VM-request-management role here, or is it more about creating VMs from the latest bits for testing from the build/release pipeline from TFS? Today you can use DevTest Labs tasks for VSTS/TFS to create a VM: https://marketplace.visualstudio.com/items?itemName=ms-azuredevtestlabs.tasks. Depending on your real scenario, it may already be automatable today (with some additional setup).JunQian shared this idea ·
Thanks for the feedback! Integration with on-prem TFS is in our backlog, although we don’t have an ETA to share yet. Meanwhile, could you please provide more details at which point you want to publish your build artifacts to a Lab VM? There are a couple of solutions based on the scenarios. One scenario is baking the latest build into a VM template in the Lab as part of the CI pipeline. We are currently working on the cmdlets which allows you to use when authoring a post-build task. Another scenario is to access the build from within a running Lab VM. This requires the network configuration to connect the Lab with your on-prem environments. Azure has provided a couple of options including Express Route, site-to-site, and point-to-site, etc. Thanks!
An error occurred while saving the commentJunQian commented
possible to reuse the use info in on-premise TFS? there is no need to set up new account for developers since they already have their own TFS account. I have this query based on the below secnarios, is it possible now?
1) each developer and test have their TFS account.
2) developer and test will apply for the VM resourced on TFS through TFS workitem workflow.
3) once the VM apply is approved, the requested VM will be created automatically. and the workitem in TFS will be updated, the requestor will be informed the VM login info.
it is need to users who use on-premise TFS, and want to use the backed Azure for dev/test lab.JunQian supported this idea ·