Feature flags: How we control exposure in VS Team Services
Oct 4, 2016Buck Hodges

Summary
This post details how Team Services uses feature flags to decouple deployment from exposure, allowing granular control over feature availability from global to individual user scope. It explains that feature flags are essentially inputs to if statements in code, enabling features to be enabled or disabled without redeploying services. An example is provided for controlling the visibility of a 'revert pull request' feature.
More from the Azure DevOps Pipelines for Dev-to-Prod Promotion trail
- Azure Developer CLI: From Dev to Prod with Azure DevOps Pipelines
- Azure Developer CLI: From Dev to Prod with One Click
- February Patches for Azure DevOps Server
- Revolutionizing Requirement Gathering: Azure DevOps Meets Azure OpenAI using Semantic kernel
- Deploy a Java application to Azure App Service using GitHub Actions