Secure files

Last Update: 5/24/2017

Team Services

Use the Secure Files library to store files such as signing certificates, Apple Provisioning Profiles, Android Keystore files, and SSH keys on the server without having to commit them to your source repository. Secure files are defined and managed in the Library tab of the Build & Release hub.

The contents of the secure files are encrypted and can only be used during the build or release process by referencing them from a task. The secure files are be available across multiple build and release definitions in the team project based on the security settings. Secure files follow the library security model.

There's a size limit of 10 MB for each secure file.


How can I create a custom task using secure files?

You can build your own tasks that use secure files by using inputs with type secureFile in the task.json. Learn how to build a custom task.

The Install Apple Provisioning Profile task is a simple example of a task using a secure file. See the reference documentation and source code.

To handle secure files during build or release, you can refer to the common module available here.

My task can't access the secure files. What do I do?

Make sure your agent is running version of 2.116.0 or higher. See Agent version and upgrades.