Azure App Configuration vs FeatureFlags.app: An Honest Comparison

We make FeatureFlags.app, so read this knowing we're biased. We'll try to be useful anyway, which means telling you when Azure App Configuration is the better choice. It often is.

Both feed flags to Microsoft.FeatureManagement, so your IFeatureManager, [FeatureGate], and <feature> code is the same either way and you can move between them. Prices below are public list prices from October 2026. Check before you decide.

When Azure App Configuration is the better choice

  • You already live in Azure. Managed identities, Microsoft Entra ID, and role-based access control, with no extra vendor or bill.
  • You want settings, secrets, and flags together. It stores ordinary configuration too, and Key Vault references point a setting at a secret. FeatureFlags.app only does flags.
  • You need geo-replication or an SLA. Standard and Premium support geo-replication and carry an SLA (99.9%, or 99.95% with geo-replication on Standard). We have neither.
  • You need private networking. Private Link is available from the Developer tier up.
  • You use more than .NET. It has providers for Java Spring, Python, JavaScript, and Go. Our client is .NET only.
  • Another vendor is a procurement problem. Staying inside an existing Azure agreement is a fine reason.

When FeatureFlags.app is the better choice

  • You don't use Azure. App Configuration needs a subscription, a resource group, and a store. We need an API key and a NuGet package.
  • You want a flag-focused dashboard. Environments, filters, an Evaluate page for testing a flag against a user, and an audit log, instead of the portal's Feature manager.
  • You want predictable pricing. Indie is free for 25 flags, Team is $10 a month for 100, and Business is $25 a month for 200. Environments, apps, and users are unlimited.

What it costs

Azure prices per store per day (US list prices, October 2026). Free is $0 with 1,000 requests a day, meant for evaluation. Developer is about $0.12 a day (around $3.60 a month) for non-production. Standard is about $1.20 a day (around $36 a month) with 200,000 requests a day included, then $0.06 per 10,000. Premium is about $9.60 a day with a replica. Flags aren't metered, so 10 flags and 1,000 flags cost the same.

For production with up to 100 flags, a Standard store at about $36 a month compares with $10 for our Team plan.

Both poll

Neither service changes running apps the instant you click save. App Configuration's provider polls on a refresh interval you set, and our client does too, every 15 minutes by default. Both serve from memory between refreshes, so shorten the interval for kill switches either way.

Choosing

Use App Configuration if you're on Azure, want settings and secrets with your flags, or need geo-replication, private networking, or other languages. Use FeatureFlags.app if you're not on Azure, only need flags, and want a simple dashboard with a flat price. Use appsettings.json if a few flags change with your deployments. None of these is permanent: the code that checks your flags stays the same.

The right feature flag service is the one that fits where your apps already live.

Try It in Your App

FeatureFlags.app is a hosted dashboard for Microsoft.FeatureManagement. The Quick Start adds it to your ASP.NET Core application in about five minutes.