This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 44%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
Just like it says in the title - I know we can use feature filters to selectively enable a feature with its default being "disabled". What I'm looking for is a way to do the inverse - selectively disabling a flag whose default is "enabled". Is that possible with Azure feature flags?
Thanks in advance!
Of course. The way you choose to use the feature flag value in your code is up to you! 😎
In the case of exclusions, this has been added to 2.6.0-preview of the library, please see this comment on GitHub for more information: https://github.com/Azure/AppConfiguration/issues/759#issuecomment-1550347762
Right, but I'm specifically wondering if we can use feature flag targeting this way. An example use case:
We roll out a new feature, disabled for everyone except beta users. (This is simple using Targeting filtering.)
Then the new feature is rolled out to everyone. (Rollout percentage 100%)
However, one of our clients has an issue, so we want to turn the feature off for them, and only them, without altering our code.
Is there a way to set feature flag targeting this way, and if so, how?
Put more simply, is it possible to set the feature flag targeting such that it returns "true" for all users except one?
Ah ok. So you're wanting a Default Percentage of 100% and then a TargettedGroup Percentage of 0%
It's not a documented scenario, but one that does sound feasible.
Aha! That does look like what I want, thank you!
Thinking it through though - is it possible to target one specific user, or does it only work on the group level? No big deal either way, we can create a group, but..
The UI only allows percentage to be set on a group.
Thank you so much!
Quick followup, I spun up a test site to try this out and unfortunately it doesn't seem to work. Setting DefaultRolloutPercentage to 100 and having my group set to 0 still returns "true" for that group - I'm guessing DefaultRolloutPercentage overrides any more specific filter settings.
I did check to make sure I was hitting the group properly by checking the reverse scenario - default rollout 0, group rollout 100 behaved as expected.
Perhaps Microsoft will add this functionality later on but for now it seems it cannot be done.
You beat me to it, i was just creating a functionApp to test the scenario!
I've raised it as an issue on the AppConfig repo here : https://github.com/Azure/AppConfiguration/issues/759
Please feel free to add more commentary to the issue.
Definitely! I'm trying to work out how to respond to it myself (getting a strange error), but this has to be up there in the annals of "thoroughly answered questions". :D