When access VSO you have two authentication options; either a LiveID (or an MSA using it’s newest name) or a Work Account ID (a domain account). The latter is used to provide extra security, so a domain admin can easily control who has access to a whole set of systems. It does assume you have used Azure Active Directory (AAD) that is sync’d with your on premises AD, and that this AAD is used to back your VSO instance....

At my session at DDDNorth I mentioned that some of the settings you needed to configure in SonarQube 5.1, such as DB connection strings for SonarRunner, would not need to be made once 5.2 was release. Well it was released today. Most important changes for we are Server handles all DB connections LDAP support for user authentication Should make the install process easier

Thanks to everyone who came to my session at DDDNorth on SonarQube, hope you found it useful. The links to resources for my session are SonarQube documentation Microsoft Product Team posts on Technical Debt ALM Rangers Guide on SonarQube (source) ALM Rangers Guide on SonarQube (explanatory post) SonarLint And you can find my slides on my GitHub repo https://github.com/rfennell/Presentations

In case you had not noticed, our MD and Connected Systems MVP Robert Hogg posted about the new Patterns & Practices Architecture Track he is hosting on Day 1 of the Microsoft Future Decoded event next month in London. This track is an additional track to the now full Future Decoded. If you are interested in attending then get in touch with enquiries@blackmarble.com, for the attention of Linda, and she can help you out with a special code (if there are still any left)....

Whilst working with a vNext Release Management pipeline I started seeing the error Microsoft.TeamFoundation.Release.Common.Helpers.OperationFailedException: New deployment is not allowed as an another deployment is in progress. Retry the deployment after sometime. Problem was I could not see any blocked or paused deployment releases. All Internet searches mentioned multiple pipelines that share components, but this was not the issue. Eventually I found the issue, my release pipeline included a step that ran CodedUI tests via TCM, hence a previous running of this template had triggered the test via TCM, but they had stalled....