This site uses cookies for analytics, personalized content and ads. By continuing to browse this site, you agree to this use. Learn More
DevOps, Git, and Agile updates from the team building Azure DevOps
May 6, 2019May 6, 201905/6/19We are constantly working to improve our experience end-to-end, including how our products are purchased. In response to feedback from our customers, we are pleased to announce some changes that will simplify how some Azure DevOps services are purchased.
October 23, 2018Oct 23, 201810/23/18Today we are excited to announce that Azure DevOps is now available over Azure ExpressRoute. Customers who typically operate in the government and financial services sectors have requested this support because they want private connections that don’t go over the public Internet for security reasons. ExpressRoute also typically offers them more reliability, faster speeds, and lower latencies than typical Internet connections.
September 27, 2018Sep 27, 201809/27/18Azure 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.
August 8, 2018Aug 8, 201808/8/18On the 24th of July 2018, we notified some customers via e-mail and on this blog about a planned action that we would start taking in relation to the malicious ESLint NPM package incident. This action is now underway.
July 24, 2018Jul 24, 201807/24/18As promised in the Protecting our users from the ESLint NPM package breach blog post last week, we have deployed new REST APIs to allow administrators of Visual Studio Team Services (VSTS) accounts to centrally revoke Personal Access Tokens (PAT) and JSON Web Tokens (JWT) created by users in their accounts.
July 5, 2018Jul 5, 201807/5/18Today, we’re excited to announce that users with the Stakeholder access level can now be administrators in Visual Studio Team Services (VSTS). With these upcoming changes, Stakeholders can administer access levels, permissions, and settings – if they have been granted permissions to do so.
April 27, 2018Apr 27, 201804/27/18Visual Studio Team Services (VSTS) offers a suite of DevOps capabilities to developers including Source control, Agile planning, Build, Release, Test and more. But until now all these features require the user to first login using a Microsoft Account before they can be used.
March 28, 2018Mar 28, 201803/28/18On January 5, 2018, I announced that Visual Studio Team Services will no longer allow creation of new MSA users with custom domain names backed by AzureAD. While most customers agree with the direction of this change, I got clear feedback that they could not connect their VSTS to AzureAD by the March 31 deadline.
January 30, 2018Jan 30, 201801/30/18In February 2017, VSTS announced support for Azure Active Directory Conditional Access Policy (CAP). One caveat that was called out in that announcement was that alternate authentication mechanisms, such as personal access tokens, would not enforce CAP.
As I discussed previously,
January 29, 2018Jan 29, 201801/29/18A few weeks ago, I posted about a change coming to organizations managing their identities with Microsoft Accounts (MSAs); as of March 30th, you will no longer able to create new MSAs with a custom domain name that is linked to an Azure Active Directory tenant.
