A: Yes, after you activate your subscriber benefits with your Microsoft account. You can then add a work account to your subscription on the My Account page. That way, you can use this work account with your subscriber benefits in Visual Studio Team Services and Microsoft Azure, if your subscription includes these benefits. You get the same level of benefits whether you use a work account or a Microsoft account. Find out how to add a work account to your MSDN subscription.
A: When you sign in for the first time, we ask you for some extra information so that we can personalize your experience. If our Terms of Service have changed since you last signed in, you might be asked to agree and confirm that your information is up-to-date.
A: We follow industry best practices and have enterprise-grade security measures to help protect your code and project data. Also, all communication between your computer and the service takes place over an encrypted HTTPS connection. Learn how we secure and protect your data.
A: Visual Studio Team Services uses many Microsoft Azure storage features to make sure your data is available in case of hardware failure, service disruption, or data center disasters. Also, the Visual Studio Team Services team has procedures to protect data from accidental or malicious deletion. Learn how we store, back up, and protect your data.
A: Visual Studio Team Services works with two major IDEs in the market today: Visual Studio and Eclipse. We also support integration with other tools through the TFS MSSCCI Provider, and with our command-line tools, which can be installed by downloading the free Team Explorer Everywhere product.
A: Yes! All source code is treated equally, so for the majority of the capabilities we provide, it doesn’t make a difference what platform you’re developing for. The hosted build functionality has some restrictions; see the Hosted build controller topic in our Get Started section to learn more about what is supported.
A: Yes, you can use any language for just about any type of development project. Most features like version control, project management tools, and feedback collection are language agnostic. Some capabilities, notably build, have limitations based on our default build configuration. But, you can add the additional software that you need in order to support your build automation.
A: You can use our tools in Visual Studio, Eclipse, or from the command line to keep a local copy of your source code on your machine. Today there isn’t a way to export work items or other project data to your local machine, but we’re planning on adding this capability at a later date.
Currently, we do not have support for continuous deployment to Azure using an on-premises build controller, so if you are trying to setup continuous deployment to Azure, you will need to use a hosted build controller.