Skip to content

Commit 3d98b3f

Browse files
committed
Resolves comments
1 parent d4e4a16 commit 3d98b3f

File tree

1 file changed

+6
-10
lines changed

1 file changed

+6
-10
lines changed

articles/azure-app-configuration/use-variant-feature-flags.md

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -53,27 +53,23 @@ Variant feature flags have two variant defaults, **DefaultWhenEnabled** and **De
5353

5454
The **kill switch** is used to stop users from allocating. Usually it is used when one or more of the variants have a problem- whether it's a bug, regression, or bad performance. To use the kill switch, set the **Enabled** field of the variant flag to false. Regardless of which percentiles users were a part of, all users will now be given the **DefaultWhenDisabled** variant.
5555

56-
## Create a variant feature flag
56+
## Build an app with a variant feature flag
5757

58-
Create a variant feature flag called *Greeting* with no label and three variants, *None*, *Simple*, and *Long*. Creating variant flags is described in the [Feature Flag quickstart](./manage-feature-flags.md#create-a-variant-feature-flag).
58+
In this tutorial, you will create a web app named _Quote of the Day_. When the app is loaded, it displays a quote. Users can interact with the heart button to like it. To improve user engagement, you want to explore whether a personalized greeting message will increase the number of users who like the quote. Users who receive the _None_ variant will see no greeting. Users who receive the _Simple_ variant will get a simple greeting message. Users who receive the _Long_ variant will get a slightly longer greeting.
59+
60+
1. Create a variant feature flag called *Greeting* with no label in your App Configuration store. It includes three variants: *None*, *Simple*, and *Long*, each corresponding to different greeting messages. Refer to the following table for their configuration values and allocation settings. For more information on how to add a variant feature flag, see [Create a variant feature flag](./manage-feature-flags.md#create-a-variant-feature-flag).
5961

6062
| Variant Name | Variant Configuration Value | Allocation|
6163
|---|---|---|
6264
| None *(Default)* | null | 50% |
6365
| Simple | "Hello!" | 25% |
6466
| Long | "I hope this makes your day!" | 25% |
6567

66-
## Set up an app to use the variants
67-
68-
In this tutorial, you will create a web app named _Quote of the Day_. When the app is loaded, it displays a quote. Users can interact with the heart button to like it. To improve user engagement, you want to explore whether a personalized greeting message will increase the number of users who like the quote. Users who receive the _None_ variant will see no greeting. Users who receive the _Simple_ variant will get a simple greeting message. Users who receive the _Long_ variant will get a slightly longer greeting.
68+
2. Continue to the following instructions to use the variant feature flag in your application for the language or platform you are using.
69+
* > [ASP.NET Core](./use-variant-feature-flags-aspnet-core.md)
6970
7071
## Next steps
7172

72-
To build the example app, continue to one the following tutorials.
73-
74-
> [!div class="nextstepaction"]
75-
> [Tutorial: Use variant feature flags from Azure App Configuration in an ASP.NET application](./use-variant-feature-flags-aspnet-core.md)
76-
7773
For the full feature rundown of the .NET feature management library, refer to the following document.
7874

7975
> [!div class="nextstepaction"]

0 commit comments

Comments
 (0)