Azure DevOps now supports AzureAD (AAD) users accessing organizations that are backed by Microsoft accounts (MSA). For administrators, this means that if your organization uses MSAs for corporate users, new employees can use their AAD credentials for access instead of creating a new MSA identity.
Back in June of this year, we rolled out the first iteration of our new navigation model for Azure DevOps. We’ve spent the summer improving that experience based on the feedback many of you have provided. Thank you! Our next step is to move from the new model being a preview, to becoming the navigation for the product. In this post, I’ll walk through some of the key feedback we’ve addressed and lay out the schedule you can expect going forward.
If you are using Azure DevOps – we want to hear what reporting metrics are important to you. We've authored a short survey to gather this data.
Last week, we released both TFS 2018 Update 3 and TFS 2018 Update 1.1. Update 3 is a roll up of bug fixes on top of Team Foundation Server 2018 Update 2. You can see a list of the bugs that were fixed in the release notes.
Wow, y'all: seven years ago today, at the BUILD conference, we announced the preview of what we called "Team Foundation Service". That service offering became Visual Studio Team Services. And on Monday, we announced the newest evolution of what that vision has become: Azure DevOps.
In the new 5.0 (preview) version we combined the two inherited REST API's under a single domain. Making it much easier to determine what REST API endpoints to use. What domain you need depends on the process model used by your projects.
Basic authorization is now enabled on the communication between the TFS and Search services to make it more secure.
We shared some exciting news this morning on the Azure blog: We’re bringing Azure DevOps to developers and enterprises around the world who need flexible and efficient tools for their development process.