Merge pull request #291147 from MicrosoftDocs/main

11/27/2024 AM Publish

Author: Taojunshen

articles/active-directory-b2c/custom-policies-series-sign-up-or-sign-in.md

@@ -1,5 +1,5 @@
 ---
-title: Set up a sign-up and sign-in flow for a local account by using Azure Active Directory B2C custom policy
+title: Set up a sign-up and sign-in flow for a local account
 titleSuffix: Azure AD B2C
 description: Learn how to configure a sign-up and sign-in flow for a local account, using email and password, by using Azure Active Directory B2C custom policy.  
 
@@ -10,7 +10,7 @@ ms.service: azure-active-directory
 
 ms.topic: how-to
 ms.custom: b2c-docs-improvements
-ms.date: 10/11/2024
+ms.date: 11/27/2024
 ms.author: kengaderdus
 ms.reviewer: yoelh
 ms.subservice: b2c

articles/active-directory-b2c/data-residency.md

@@ -9,7 +9,7 @@ manager: CelesteDG
 ms.service: azure-active-directory
 
 ms.topic: reference
-ms.date: 01/11/2024
+ms.date: 11/27/2024
 ms.author: kengaderdus
 ms.subservice: b2c
 ms.custom: references_regions
@@ -26,7 +26,7 @@ Azure Active Directory B2C (Azure AD B2C) stores customer data in a geographic l
 Region availability and data residency are two different concepts that apply to Azure AD B2C. This article explains the differences between these two concepts, and compares how they apply to Azure versus Azure AD B2C. [Region availability](#region-availability) refers to where a service is available for use whereas [Data residency](#data-residency) refers to where user data is stored.
 
 
-Azure AD B2C is **generally available worldwide** with the option for **data residency** in the **United States, Europe, Asia Pacific, or Australia**.
+Azure AD B2C is **generally available worldwide** with the option for **data residency** in the **United States, Europe, Asia Pacific Australia or New Zealand**.
 
 [Region availability](#region-availability) refers to where a service is available for use. [Data residency](#data-residency) refers to where customer data is stored. For customers in the EU and EFTA, see [EU Data Boundary](#eu-data-boundary).
 
@@ -59,7 +59,7 @@ Data resides in **Asia Pacific** for the following locations:
 
 > Afghanistan (AF), Hong Kong SAR (HK), India (IN), Indonesia (ID), Japan (JP), Korea (KR), Malaysia (MY), Philippines (PH), Singapore (SG), Sri Lanka (LK), Taiwan (TW), and Thailand (TH)
 
-Data resides in **Australia** for the following locations:
+Data resides in Australia or New Zealand for the following locations:
 
 > Australia (AU) and New Zealand (NZ)
 

articles/active-directory-b2c/https-cipher-tls-requirements.md

@@ -9,7 +9,7 @@ manager: CelesteDG
 ms.service: azure-active-directory
 
 ms.topic: reference
-ms.date: 01/11/2024
+ms.date: 11/27/2024
 ms.author: kengaderdus
 ms.subservice: b2c
 
@@ -66,7 +66,7 @@ The following endpoints used in your Azure AD B2C environment must comply with t
 
 ## Check your endpoint compatibility
 
-To verify that your endpoints comply with the requirements described in this article, perform a test using a TLS cipher and scanner tool. Test your endpoint using [SSLLABS](https://www.ssllabs.com/ssltest/analyze.html).
+To verify that your endpoints comply with the requirements described in this article, perform a test using a TLS cipher and scanner tool. Test your endpoint using [SSL LABS](https://www.ssllabs.com/ssltest/analyze.html).
 
 
 ## Next steps

articles/azure-app-configuration/TOC.yml

@@ -150,7 +150,7 @@
         href: howto-timewindow-filter.md
       - name: ASP.NET Core
         href: howto-timewindow-filter-aspnet-core.md
-      - name: JavaScipt
+      - name: JavaScript
         href: howto-timewindow-filter-javascript.md
     - name: Roll out features to targeted audience
       items:

articles/azure-app-configuration/howto-feature-filters.md

@@ -31,7 +31,7 @@ You can create custom feature filters that enable features based on your specifi
 
 ## Add a custom feature filter
 
-1. Create a feature flag named *Beta* in your App Configuration store and open to edit it. For more information about how to add and edit a feature flag, see [Manage feature flags](./manage-feature-flags.md).
+1. Create a feature flag named *Beta* in your App Configuration store and edit it. For more information about how to add and edit a feature flag, see [Manage feature flags](./manage-feature-flags.md#edit-feature-flags).
 
 1. In the **Edit feature flag** pane that opens, check the **Enable feature flag** checkbox if it isn't already enabled. Then check the **Use feature filter** checkbox and select **Create**.
 

articles/azure-app-configuration/howto-targetingfilter.md

@@ -24,7 +24,7 @@ In this article, you will learn how to add and configure a targeting filter for
 
 ## Add a targeting filter
 
-1. Create a feature flag named *Beta* in your App Configuration store and open to edit it. For more information about how to add and edit a feature flag, see [Manage feature flags](./manage-feature-flags.md).
+1. Create a feature flag named *Beta* in your App Configuration store and edit it. For more information about how to add and edit a feature flag, see [Manage feature flags](./manage-feature-flags.md#edit-feature-flags).
 
 1. In the **Edit feature flag** pane that opens, check the **Enable feature flag** checkbox if it isn't already enabled. Then check the **Use feature filter** checkbox and select **Create**.
 

articles/azure-app-configuration/howto-timewindow-filter-aspnet-core.md

@@ -49,6 +49,8 @@ Once the start time has passed, refresh your browser a few times. You'll notice
 > [!div class="mx-imgBorder"]
 > ![Screenshot of browser with Beta menu.](./media/quickstarts/aspnet-core-feature-flag-local-after.png)
 
+If recurrence is enabled when you set up the time window filter, the **Beta** menu will disappear once your current time passes the end time you set in the time window filter. However, the **Beta** menu will reappear according to your recurrence settings and continue this pattern until the recurrence expiration time, if set.
+
 ## Next steps
 
 To learn more about the feature filters, continue to the following tutorials.

articles/azure-app-configuration/howto-timewindow-filter-javascript.md

@@ -64,6 +64,8 @@ Beta is enabled: true
 Beta is enabled: true
 ```
 
+If recurrence is enabled when you set up the time window filter, the console outputs will change to `Beta is enabled: false` once your current time passes the end time you set in the time window filter. However, it will change to `Beta is enabled: true` again according to your recurrence settings and continue this pattern until the recurrence expiration time, if set.
+
 ## Next steps
 
 To learn more about the feature filters, continue to the following tutorials.

articles/azure-app-configuration/howto-timewindow-filter.md

@@ -1,50 +1,63 @@
 ---
 title: Enable features on a schedule
 titleSuffix: Azure App Configuration
-description: Learn how to enable feature flags on a schedule.
+description: Learn how to enable feature flags on a schedule using time window filters in Azure App Configuration.
 ms.service: azure-app-configuration
 ms.devlang: csharp
 author: zhiyuanliang-ms
 ms.author: zhiyuanliang
 ms.topic: how-to
-ms.date: 03/26/2024
+ms.date: 10/31/2024
+#customer intent: As an application developer, I want to enable a recurring time window filter in a feature flag so that I can enable or disable features on a schedule.
 ---
 
 # Tutorial: Enable features on a schedule
 
 [Feature filters](./howto-feature-filters.md#what-is-a-feature-filter) allow a feature flag to be enabled or disabled conditionally. The time window filter is one of the feature management library's built-in feature filters. It allows you to turn on or off a feature on a schedule. For example, when you have a new product announcement, you can use it to unveil a feature automatically at a planned time. You can also use it to discontinue a promotional discount as scheduled after the marketing campaign ends.
 
-In this article, you will learn how to add and configure a time window filter for your feature flags.
+In this article, you learn how to add and configure a time window filter for your feature flags.
 
 ## Add a time window filter
 
-1. Create a feature flag named *Beta* in your App Configuration store and open to edit it. For more information about how to add and edit a feature flag, see [Manage feature flags](./manage-feature-flags.md).
+1. Create a feature flag named *Beta* in the **Feature Manager** menu of your App Configuration store and move to the right end of the feature flag you want to modify, then select the **More actions** ellipsis (**...**) action and **Edit**. For more information about how to add and edit a feature flag, see [Manage feature flags](./manage-feature-flags.md).
 
-1. In the **Edit feature flag** pane that opens, check the **Enable feature flag** checkbox if it isn't already enabled. Then check the **Use feature filter** checkbox and select **Create**.
+1. In the **Edit** pane that opens, check the **Enable feature flag** checkbox if it's currently unchecked, then check the **Use feature filter** checkbox and select **Create**.
 
-    > [!div class="mx-imgBorder"]
-    > ![Screenshot of the Azure portal, filling out the form 'Edit feature flag'.](./media/feature-filters/edit-a-feature-flag.png)
+    :::image type="content" source="media/time-window-filters/edit-a-feature-flag.png" alt-text="Screenshot of the Azure portal showing how to edit a feature flag.":::
 
-1. The pane **Create a new filter** opens. Under **Filter type**, select the **Time window filter** in the dropdown.
+1. The **Create a new filter** pane opens on the side. Under **Filter type**, select **Time window filter** in the dropdown.
 
-    > [!div class="mx-imgBorder"]
-    > ![Screenshot of the Azure portal, creating a new time window filter.](./media/feature-filters/add-timewindow-filter.png)
+    :::image type="content" source="media/time-window-filters/add-timewindow-filter.png" alt-text="Screenshot of the Azure portal showing time window feature filter configuration.":::
+
+1. A time window filter includes a start time and/or an end time. Both **Start time** and **End time** checkboxes are checked by default.
+   - Setting a start time allows you to enable the feature flag on a specific date and time. A time window filter with no start time is active as soon as you save the feature filter details. 
+   - Setting an end time allows you to disable the feature flag at a specific date and time. A time window filter with no end time remains active until you disable it. 
+
+   Uncheck the end time and enter a start time a few minutes ahead of your current time to schedule the *Beta* feature to be enabled automatically in a few minutes and never be disabled once enabled.
+
+1. A time zone is selected by default, based on your browser's current time zone. Optionally select another time zone.
+
+1. Optionally set a time window recurrence. This option allows you to define a repeating time window, ensuring that the feature flag is automatically activated and deactivated according to your specified schedule, such as during periods of low or high traffic. 
+
+   A recurring time window filter always has a start time and an end time, defining a base time window that recurs according to the recurrence pattern you specify. Enter a **Start time** and an **End time**, then select the **Enable recurrence** checkbox, and select the recurrence details, including a recurrence pattern and an **expiration time**.
+
+   In this example, you activate the *Beta* feature daily from 5:00 PM to 6:00 PM, starting November 25 and continuing until December 31. You can alternatively select a weekly frequency and select one or more days of the week for the recurrence.
+
+    :::image type="content" source="media/time-window-filters/add-timewindow-filter-recurrence.png" alt-text="Screenshot of the Azure portal showing feature filter recurrence.":::
 
-1. A time window filter includes two parameters: start and expiry date. Set the **Start date** to **Custom** and select a time a few minutes ahead of your current time. Set the **Expiry date** to **Never**. In this example, you schedule the *Beta* feature to be enabled automatically at a future time, and it will never be disabled once enabled.
 
 1. Select **Add** to save the configuration of the time window filter and return to the **Edit feature flag** screen.
 
-1. The time window filter is now listed in the feature flag details. Select **Apply** to save the feature flag.
+1. The time window filter is now listed in the feature filter details, under **Feature filters**. Select **Apply** to save the feature flag with the new feature filter.
 
-    > [!div class="mx-imgBorder"]
-    > ![Screenshot of the Azure portal, applying new time window filter.](./media/feature-filters/feature-flag-edit-apply-timewindow-filter.png)
+    :::image type="content" source="media/time-window-filters/feature-flag-edit-apply-timewindow-filter.png" alt-text="Screenshot of the Azure portal, applying new time window filter.":::
 
-    Now, you successfully added a time window filter to a feature flag. 
+    Now, you successfully added a time window filter to a feature flag.
 
 1. Continue to the following instructions to use the feature flag with a time window filter in your application for the language or platform you are using.
 
     - [ASP.NET Core](./howto-timewindow-filter-aspnet-core.md)
-    - [Node.js](./howto-timewindow-filter-javascript.md)
+    - [JavaScript](./howto-timewindow-filter-javascript.md)
 
 ## Next steps
 
@@ -54,4 +67,4 @@ To learn more about the feature filters, continue to the following tutorials:
 > [Enable conditional features with feature filters](./howto-feature-filters.md)
 
 > [!div class="nextstepaction"]
-> [Roll out features to targeted audience](./howto-targetingfilter.md)
+> [Roll out features to targeted audience](./howto-targetingfilter.md)