With the release of OpenSSH 8.2 last month, connections to SSH servers using SHA-1 was disabled by default in the OpenSSH client. We understand that this move helps improve the security of SSH connections, by encouraging all users to adopt the SHA-2 class of algorithms,
We are rolling out a new tenant policy in Azure DevOps to configure who are allowed to create new Azure DevOps organizations in your company.
Today we’re announcing the next step in the journey of making Azure DevOps and GitHub work great together. If you are an admin, sign into Azure DevOps with your GitHub identity, and you can now invite your GitHub team members.
Auditing for Azure DevOps is now available for all organizations as a Public Preview! A new way to monitor activities and changes throughout Azure DevOps organizations.
We 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.
Today 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.
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.
On 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.
As 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.
Today, 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.