Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Learn Build Service GitHub App

.openpublishing.redirection.json

@@ -772,6 +772,16 @@
       "redirect_url": "/azure/azure-app-configuration/concept-experimentation",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/azure-app-configuration/use-variant-feature-flags.md",
+      "redirect_url": "/azure/azure-app-configuration/howto-variant-feature-flags",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/azure-app-configuration/use-variant-feature-flags-aspnet-core.md",
+      "redirect_url": "/azure/azure-app-configuration/howto-variant-feature-flags-aspnet-core",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/public-multi-access-edge-compute-mec/considerations-for-deployment.md",
       "redirect_url": "/previous-versions/azure/public-multi-access-edge-compute-mec/considerations-for-deployment",

articles/api-center/register-apis-github-actions.md

@@ -3,7 +3,7 @@ title: Register APIs using GitHub Actions - Azure API Center
 description: Learn how to automate the registration of APIs in your API center using a CI/CD workflow based on GitHub Actions.
 ms.service: azure-api-center
 ms.topic: how-to
-ms.date: 07/24/2024
+ms.date: 12/23/2024
 ms.author: danlep
 author: dlepow
 ms.custom: devx-track-azurecli
@@ -20,9 +20,9 @@ The following diagram shows how API registration in your API center can be autom
 
 :::image type="content" source="media/register-apis-github-actions/scenario-overview.svg" alt-text="Diagram showing steps to trigger a GitHub actions workflow to register an API in an Azure API center." lightbox="media/register-apis-github-actions/scenario-overview.svg":::
 
-1. Set up a GitHub Actions workflow in your repository that triggers when a pull request that adds an API definition file is merged.
+1. Set up a GitHub Actions workflow in your repository that triggers when a pull request adding an API definition file is merged.
 1. Create a branch from the main branch in your GitHub repository.
-1. Add an API definition file, commit the changes, and push them to the new branch.
+1. Add an API definition file, commit the changes, and push to the new branch.
 1. Create a pull request to merge the new branch into the main branch.
 1. Merge the pull request.
 1. The merge triggers a GitHub Actions workflow that registers the API in your API center.
@@ -133,37 +133,32 @@ In this example:
 To configure the workflow file:
 
 1. Copy and save the file under a name such as `register-api.yml`.
-1. Update the values for the environment variables to match your API center in Azure.
 1. Confirm or update the name of the repository folder (`APIs`) where you'll add the API definition file.
 1. Add this workflow file in the  `/.github/workflows/` path in your GitHub repository.
+1. Set the [Actions variables](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/store-information-in-variables) `SERVICE_NAME` and `RESOURCE_GROUP` in your repo for your API center name and resource group name in Azure.
 
 > [!TIP]
-> Using the [Visual Studio Code extension](build-register-apis-vscode-extension.md) for Azure API Center, you can generate a starting workflow file by running an extension command. In the Command Palette, select **Azure API Center: Register APIs**. Select **CI/CD** > **GitHub**. You can then modify the file for your scenario.
+> Using the [Visual Studio Code extension](build-register-apis-vscode-extension.md) for Azure API Center, you can generate a starting workflow file by running an extension command. In the Command Palette, select **Azure API Center: Register APIs**. Select **CI/CD** > **GitHub**. You can then modify or extend the file for your scenario.
 
 ```yml
 name: Register API Definition to Azure API Center
 on:
   pull_request:
-    types: [closed]
+    types: [ closed ]
     branches:
-      - main
+      - [ "main" ]
     paths:
       - "APIs/**/*.json"
 permissions:
   contents: read
   pull-requests: read
-env:
-  # set this to your Azure API Center resource group name
-  RESOURCE_GROUP: <YOUR_RESOURCE_GROUP>
-  # set this to your Azure API Center service name
-  SERVICE_NAME: <YOUR_API_CENTER>
 jobs:
   register:
     runs-on: ubuntu-latest
     environment: production
     steps:
       - uses: actions/checkout@v2
-    
+      
       - name: Get specification file path in the PR
         id: get-file-location
         uses: actions/github-script@v5
@@ -180,23 +175,24 @@ jobs:
             });
             if (files.data.length === 1) {
               const filename = files.data[0].filename;
-              core.exportVariable('API_FILE_LOCATION', hfilename);
+              core.exportVariable('API_FILE_LOCATION', filename);
               console.log(`API_FILE_LOCATION: ${{ env.API_FILE_LOCATION }}`);
             }
             else {
               console.log('The PR does not add exactly one specification file.');
             }
+
       - name: Azure login
         uses: azure/login@v1
         with:
           creds: ${{ secrets.AZURE_CREDENTIALS }}
-          
+
       - name: Register to API Center
         uses: azure/CLI@v2
         with:
           azcliversion: latest
           inlineScript: |
-            az apic api register -g ${{ env.RESOURCE_GROUP }} -n ${{ env.SERVICE_NAME }} --api-location ${{ env.API_FILE_LOCATION }}
+            az apic api register -g ${{ vars.RESOURCE_GROUP }} -n ${{ vars.SERVICE_NAME }} --api-location ${{ env.API_FILE_LOCATION }}
 ```
 
 
@@ -258,7 +254,7 @@ You can extend the GitHub Actions workflow to include other steps, such as addin
         with:
           azcliversion: latest
           inlineScript: |
-            az apic api update -g ${{ env.RESOURCE_GROUP }} -n ${{ env.SERVICE_NAME }} --api-id {{ env.API_ID }} --custom-properties {{ env.METADATA_FILE }}
+            az apic api update -g ${{ vars.RESOURCE_GROUP }} -n ${{ vars.SERVICE_NAME }} --api-id {{ env.API_ID }} --custom-properties {{ env.METADATA_FILE }}
     ```
 
 ## Related content

articles/api-management/api-management-features.md

@@ -26,7 +26,7 @@ Each API Management [pricing tier](api-management-key-concepts.md#api-management
 | -------------------------------------------------------------------------------------------- | ----------- | --------- | --------- | --------- | ----- | -------- | ------- | ------- | 
 | Microsoft Entra integration<sup>1</sup>                                                             | No          | Yes       | No    | Yes      | Yes      | Yes      | Yes     | Yes |
 | Virtual network injection support                                                               | No          | Yes       | No    | No       | No       | No       | Yes    | Yes |
-| Private endpoint support for inbound connections                                                               | No          | Yes       | Yes    | No       | Yes       | Yes       | Yes  | No   |
+| Private endpoint support for inbound connections                                                               | No          | Yes       | Yes    | No       | Yes      | Yes (preview)       | Yes  | No   |
 | Outbound virtual network integration support                                                             | No          | No       | No    | No       | No       | Yes       | No    | Yes |
 | Multi-region deployment                                                                      | No          | No        | No    | No       | No       | No       | Yes     | No |
 | Availability zones                                                                           | No          | No        | No    | No       | No       | No       | Yes     | No  |
@@ -59,4 +59,4 @@ Each API Management [pricing tier](api-management-key-concepts.md#api-management
 * [Overview of Azure API Management](api-management-key-concepts.md)
 * [API Management limits](/azure/azure-resource-manager/management/azure-subscription-service-limits?toc=/azure/api-management/toc.json&bc=/azure/api-management/breadcrumb/toc.json#api-management-limits)
 * [V2 tiers overview](v2-service-tiers-overview.md)
-* [API Management pricing](https://azure.microsoft.com/pricing/details/api-management/)
+* [API Management pricing](https://azure.microsoft.com/pricing/details/api-management/)

articles/app-service/app-service-asp-net-migration.md

@@ -56,7 +56,7 @@ __App Service Migration Assistant tool and App Service migration assistant for P
 |Migration Tools| Description | Documentation |
 |-----------|-------------|---------------|
 |[App Service Migration Assistant](https://appmigration.microsoft.com/api/download/windowspreview/AppServiceMigrationAssistant.msi)|Migrate .NET web apps from Windows OS to App Service.|[App Service Migration Assistant Documentation](https://github.com/Azure/App-Service-Migration-Assistant/wiki)|
-|[App Service migration assistant for Java on Apache Tomcat (Windows—preview)](https://appmigration.microsoft.com/api/download/windows/AppServiceMigrationAssistant.msi)|Download prerelease software for migrating Java web applications on Tomcat web server running on Windows servers.|[App Service Migration Assistant Documentation](https://github.com/Azure/App-Service-Migration-Assistant/wiki)|
+|[App Service migration assistant for Java on Apache Tomcat (Windows—preview)](https://appmigration.microsoft.com/api/download/windowspreview/AppServiceMigrationAssistant.msi)|Download prerelease software for migrating Java web applications on Tomcat web server running on Windows servers.|[App Service Migration Assistant Documentation](https://github.com/Azure/App-Service-Migration-Assistant/wiki)|
 |[App Service Migration Assistant PowerShell scripts](https://appmigration.microsoft.com/api/download/psscripts/AppServiceMigrationScripts.zip)|Download PowerShell scripts for discovering and assessing all Microsoft Internet Information Services (IIS) web apps on a single server in bulk and migrating .NET web apps from Windows OS to App Service.|[App Service Migration Assistant Powershell Documentation](https://github.com/Azure/App-Service-Migration-Assistant/wiki/PowerShell-Scripts)<br>[SHA256 Identifier](https://github.com/Azure/App-Service-Migration-Assistant/wiki/Release-Notes)|
 
 | More resources to migrate .NET apps to the cloud |

articles/azure-app-configuration/TOC.yml

@@ -161,9 +161,9 @@
     - name: Use variant feature flags
       items:
       - name: Overview
-        href: use-variant-feature-flags.md
+        href: howto-variant-feature-flags.md
       - name: ASP.NET Core
-        href: use-variant-feature-flags-aspnet-core.md
+        href: howto-variant-feature-flags-aspnet-core.md
   - name: Enable Azure monitoring
     items:
     - name: Monitor App Configuration

articles/azure-app-configuration/use-variant-feature-flags-aspnet-core.md renamed to articles/azure-app-configuration/howto-variant-feature-flags-aspnet-core.md

@@ -13,12 +13,12 @@ ms.date: 12/18/2024
 
 # Tutorial: Use variant feature flags in an ASP.NET Core application
 
-In this tutorial, you use a variant feature flag to manage experiences for different user segments in an example application, *Quote of the Day*. You utilize the variant feature flag created in [Use variant feature flags](./use-variant-feature-flags.md). Before proceeding, ensure you create the variant feature flag named *Greeting* in your App Configuration store.
+In this tutorial, you use a variant feature flag to manage experiences for different user segments in an example application, *Quote of the Day*. You utilize the variant feature flag created in [Use variant feature flags](./howto-variant-feature-flags.md). Before proceeding, ensure you create the variant feature flag named *Greeting* in your App Configuration store.
 
 ## Prerequisites
 
 * Ensure the [.NET CLI](/dotnet/core/tools) is installed on your machine.
-* Follow the [Use variant feature flags](./use-variant-feature-flags.md) tutorial and create the variant feature flag named *Greeting*.
+* Follow the [Use variant feature flags](./howto-variant-feature-flags.md) tutorial and create the variant feature flag named *Greeting*.
 
 ## Create an ASP.NET Core web app
 
@@ -249,13 +249,13 @@ In this tutorial, you use a variant feature flag to manage experiences for diffe
     ```
 1. Once the application is loaded, select **Register** at the top right to register a new user.
 
-    :::image type="content" source="media/use-variant-feature-flags-aspnet-core/register.png" alt-text="Screenshot of the Quote of the day app, showing Register.":::
+    :::image type="content" source="media/howto-variant-feature-flags-aspnet-core/register.png" alt-text="Screenshot of the Quote of the day app, showing Register.":::
 
 1. Register a new user named *[email protected]*.
 
 1. Select the link **Click here to validate email** after entering user information.
 
-    :::image type="content" source="media/use-variant-feature-flags-aspnet-core/click-to-confirm.png" alt-text="Screenshot of the Quote of the day app, showing click to confirm.":::
+    :::image type="content" source="media/howto-variant-feature-flags-aspnet-core/click-to-confirm.png" alt-text="Screenshot of the Quote of the day app, showing click to confirm.":::
 
 1. Repeat the same steps to register a second user named *[email protected]*.
 
@@ -264,15 +264,15 @@ In this tutorial, you use a variant feature flag to manage experiences for diffe
 
 1. Select **Login** at the top right to sign in as [email protected].
 
-    :::image type="content" source="media/use-variant-feature-flags-aspnet-core/login.png" alt-text="Screenshot of the Quote of the day app, showing **Login**.":::
+    :::image type="content" source="media/howto-variant-feature-flags-aspnet-core/login.png" alt-text="Screenshot of the Quote of the day app, showing **Login**.":::
 
 1. Once logged in, you see a long greeting message for **[email protected]**
 
-    :::image type="content" source="media/use-variant-feature-flags-aspnet-core/long-variant.png" alt-text="Screenshot of the Quote of the day app, showing a long message for the user.":::
+    :::image type="content" source="media/howto-variant-feature-flags-aspnet-core/long-variant.png" alt-text="Screenshot of the Quote of the day app, showing a long message for the user.":::
 
 1. Click *Logout* and login as **[email protected]**, you see the simple greeting message.
 
-    :::image type="content" source="media/use-variant-feature-flags-aspnet-core/simple-variant.png" alt-text="Screenshot of the Quote of the day app, showing a simple message for the user.":::
+    :::image type="content" source="media/howto-variant-feature-flags-aspnet-core/simple-variant.png" alt-text="Screenshot of the Quote of the day app, showing a simple message for the user.":::
 
 ## Next steps
 

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

@@ -73,4 +73,4 @@ In this tutorial, you create a web app named _Quote of the Day_. When the app is
     | Long | "I hope this makes your day!" | 25% | 
 
 2. Continue to the following instructions to use the variant feature flag in your application for the language or platform you're using.
-    * [ASP.NET Core](./use-variant-feature-flags-aspnet-core.md)
+    * [ASP.NET Core](./howto-variant-feature-flags-aspnet-core.md)

articles/azure-app-configuration/index.yml

@@ -163,7 +163,7 @@ landingContent:
         - text: Roll out features to targeted audience
           url: howto-targetingfilter.md
         - text: Use variant feature flags
-          url: use-variant-feature-flags.md
+          url: howto-variant-feature-flags.md
       - linkListType: reference
         links:
         - text: .NET feature management