Merge branch 'main' into release-ignite-functions-flex-consumption-ga

Author: v-alje

articles/api-center/build-register-apis-vscode-extension.md

@@ -4,7 +4,7 @@ description: API developers can use the Azure API Center extension for Visual St
 author: dlepow
 ms.service: azure-api-center
 ms.topic: how-to
-ms.date: 10/16/2024
+ms.date: 11/08/2024
 ms.author: danlep 
 ms.collection: ce-skilling-ai-copilot
 ms.custom: 
@@ -16,7 +16,8 @@ ms.custom:
 API developers in your organization can build and register APIs in your [API center](overview.md) inventory by using the Azure API Center extension for Visual Studio Code. API developers can:
 
 * Add an existing API to an API center as a one-time operation, or integrate a development pipeline to register APIs as part of a CI/CD workflow.
-* Generate OpenAPI specification files from API code using GitHub Copilot, and register the API to an API center.
+* Use GitHub Copilot to generate new OpenAPI specs from API code.
+* Use natural language prompts with the API Center plugin for GitHub Copilot for Azure to create new OpenAPI specs.
 
 API developers can also take advantage of features in the extension to [discover and consume APIs](discover-apis-vscode-extension.md) in the API center and ensure [API governance](govern-apis-vscode-extension.md).
 
@@ -27,6 +28,7 @@ The following Visual Studio Code extensions are needed for the specified scenari
 * [GitHub Actions](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-github-actions) - to register APIs using a CI/CD pipeline with GitHub Actions
 * [Azure Pipelines](https://marketplace.visualstudio.com/items?itemName=ms-azure-devops.azure-pipelines) - to register APIs using a CI/CD pipeline with Azure Pipelines
 * [GitHub Copilot](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot) - to generate OpenAPI specification files from API code
+* [GitHub Copilot for Azure](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azure-github-copilot) - to generate OpenAPI specification files using the Azure API Center Plugin for GitHub Copilot for Azure
 
 [!INCLUDE [vscode-extension-setup](includes/vscode-extension-setup.md)]  
 
@@ -51,9 +53,9 @@ The following steps register an API in your API center with a CI/CD pipeline. Wi
 
 Learn more about setting up a [GitHub Actions workflow](register-apis-github-actions.md) to register APIs with your API center.
 
-## Generate OpenAPI specification file from API code 
+## Generate OpenAPI spec from API code 
 
-Use the power of GitHub Copilot with the Azure API Center extension for Visual Studio Code to create an OpenAPI specification file from your API code. Right-click on the API code, select **Copilot** from the options, and select **Generate API documentation**. GitHub Copilot creates an OpenAPI specification file.
+Use the power of [GitHub Copilot](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot) with the Azure API Center extension for Visual Studio Code to create an OpenAPI specification file from your API code. Right-click on the API code, select **Copilot** from the options, and select **Generate API documentation**. GitHub Copilot creates an OpenAPI specification file.
 
 > [!NOTE]
 > This feature is available in the pre-release version of the API Center extension.
@@ -62,6 +64,33 @@ Use the power of GitHub Copilot with the Azure API Center extension for Visual S
 
 After generating the OpenAPI specification file and checking for accuracy, you can register the API with your API center using the **Azure API Center: Register API** command.
 
+## Generate OpenAPI spec using natural language prompts
+
+The API Center plugin for [GitHub Copilot for Azure](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azure-github-copilot) helps you design new APIs starting from natural language prompts. With AI assistance, quickly generate an OpenAPI spec for API development that complies with your organization's standards.
+
+> [!NOTE]
+> This feature is available in the pre-release version of the API Center extension.
+
+1. If desired, set an active API style guide. Use the **Ctrl+Shift+P** keyboard shortcut to open the Command Palette. Type **Azure API Center: Set API Style Guide**, make a selection, and hit **Enter**. 
+
+    If no style guide is set, the default `spectral:oas` ruleset is used.
+1. In the chat panel, make a request in natural language to the `@azure` agent to describe what the API does. Example:
+
+    ```vscode
+    @azure Generate OpenAPI spec: An API that allows customers to pay for an order using various payment methods such as cash, checks, credit cards, and debit cards.
+    ```  
+
+    The agent responds with an OpenAPI specification document.
+
+    :::image type="content" source="media/build-register-apis-vscode-extension/generate-api-specification.png" alt-text="Screenshot showing how to use @azure extension to generate an OpenAPI spec from a prompt.":::
+
+
+1. Review the generated output for accuracy and compliance with your API style guide. Refine the prompt if needed to regenerate.
+
+    > [!TIP]
+    > Effective prompts focus on an API's business requirements rather than implementation details. Shorter prompts sometimes work better than longer ones.
+1. When it meets your requirements, save the generated OpenAPI specification to a file. 
+1. Register the API with your API center. Select **Register your API in API Center** button in the chat panel, or select **Azure API Center: Register API** from the Command Palette, and follow the prompts.
 
 ## Related content
 

articles/api-center/media/build-register-apis-vscode-extension/generate-api-specification.png

@@ -7,7 +7,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: how-to
-ms.date: 01/31/2023
+ms.date: 09/06/2024
 ms.author: danlep 
 ms.custom: devx-track-azurepowershell
 ---
@@ -129,6 +129,38 @@ Backup-AzApiManagement -ResourceGroupName $apiManagementResourceGroup -Name $api
 
 Backup is a long-running operation that may take several minutes to complete. During this time the API gateway continues to handle requests, but the state of the service is Updating.
 
+### [CLI](#tab/cli)
+
+[Sign in](/cli/azure/authenticate-azure-cli) with Azure CLI.
+
+In the following examples:
+
+* An API Management instance named *myapim* is in resource group *apimresourcegroup*.
+* A storage account named *backupstorageaccount* is in resource group *storageresourcegroup*. The storage account has a container named *backups*.
+* A backup blob will be created with name *ContosoBackup.apimbackup*.
+
+Set variables in Bash:
+
+```azurecli-interactive
+apiManagementName="myapim";
+apiManagementResourceGroup="apimresourcegroup";
+storageAccountName="backupstorageaccount";
+storageResourceGroup="storageresourcegroup";
+containerName="backups";
+backupName="ContosoBackup.apimbackup";
+```
+
+### Access using storage access key
+
+```azurecli-interactive
+storageKey=$(az storage account keys list --resource-group $storageResourceGroup --account-name $storageAccountName --query [0].value --output tsv)
+
+az apim backup --resource-group $apiManagementResourceGroup --name $apiManagementName \
+    --storage-account-name $storageAccountName --storage-account-key $storageKey --storage-account-container $containerName --backup-name $backupName
+```
+
+Backup is a long-running operation that may take several minutes to complete. During this time the API gateway continues to handle requests, but the state of the service is Updating.
+
 ### [REST](#tab/rest)
 
 See [Azure REST API reference](/rest/api/azure/) for information about authenticating and calling Azure REST APIs.
@@ -261,6 +293,35 @@ Restore-AzApiManagement -ResourceGroupName $apiManagementResourceGroup -Name $ap
 
 Restore is a long-running operation that may take up to 45 minutes or more to complete. 
 
+### [CLI](#tab/cli)
+
+In the following examples, 
+
+* An API Management instance named *myapim* is restored from the backup blob named *ContosoBackup.apimbackup* in storage account *backupstorageaccount*.
+* The backup blob is in a container named *backups*.
+
+Set variables in Bash:
+
+```azurecli-interactive
+apiManagementName="myapim";
+apiManagementResourceGroup="apimresourcegroup";
+storageAccountName="backupstorageaccount";
+storageResourceGroup="storageresourcegroup";
+containerName="backups";
+backupName="ContosoBackup.apimbackup"
+```
+
+### Access using storage access key
+
+```azurecli-interactive
+storageKey=$(az storage account keys list --resource-group $storageResourceGroup --account-name $storageAccountName --query [0].value --output tsv)
+
+az apim restore --resource-group $apiManagementResourceGroup --name $apiManagementName \
+    --storage-account-name $storageAccountName --storage-account-key $storageKey --storage-account-container $containerName --backup-name $backupName
+```
+
+Restore is a long-running operation that may take up to 45 minutes or more to complete. 
+
 ### [REST](#tab/rest)
 
 To restore an API Management service from a previously created backup, make the following HTTP request:

articles/api-management/api-management-howto-disaster-recovery-backup-restore.md

@@ -99,7 +99,7 @@ Outbound traffic from your app is now routed through the integrated virtual netw
 1. Navigate to the firewall's overview page and select its firewall policy.
 
 1. In the firewall policy page, from the left navigation, select **Application Rules** > **Add a rule collection**.
-1. In **Rules**, add a network rule with the App Service subnet as the source address, and specify an FQDN destination. In the screenshot below, the destination FQDN is set to `api.my-ip.io`.
+1. In **Rules**, add a network rule with the App Service subnet as the source address, and specify an FQDN destination. In the screenshot below, the destination FQDN is set to `contoso.com`.
 
     :::image type="content" source="./media/network-secure-outbound-traffic-azure-firewall/config-azfw-policy-app-rule.png" alt-text="Screenshot of configure Azure Firewall policy rule.":::
 
@@ -113,7 +113,7 @@ Outbound traffic from your app is now routed through the integrated virtual netw
 An easy way to verify your configuration is to use the `curl` command from your app's SCM debug console to verify the outbound connection.
 
 1. In a browser, navigate to `https://<app-name>.scm.azurewebsites.net/DebugConsole`.
-1. In the console, run `curl -s <protocol>://<fqdn-address>` with a URL that matches the application rule you configured, To continue example in the previous screenshot, you can use **curl -s https://api.my-ip.io/ip**. The following screenshot shows a successful response from the API, showing the public IP address of your App Service app.
+1. In the console, run `curl -s <protocol>://<fqdn-address>` with a URL that matches an application rule you configured. The following screenshot is an example to a website that shows a successful response from a API, showing an IP address.
 
     :::image type="content" source="./media/network-secure-outbound-traffic-azure-firewall/verify-outbound-traffic-fw-allow-rule.png" alt-text="Screenshot of verifying the success outbound traffic by using curl command in SCM debug console.":::
 

articles/app-service/network-secure-outbound-traffic-azure-firewall.md

@@ -24,7 +24,7 @@
       href: quickstart-java-spring-app.md
     - name: Python
       href: quickstart-python-provider.md
-    - name: JavaScript/Node.js
+    - name: Node.js
       href: quickstart-javascript-provider.md
     - name: Azure Functions
       href: quickstart-azure-functions-csharp.md
@@ -42,8 +42,10 @@
       href: quickstart-feature-flag-spring-boot.md
     - name: Azure Functions
       href: quickstart-feature-flag-azure-functions-csharp.md
-    - name: Python app
+    - name: Python
       href: quickstart-feature-flag-python.md
+    - name: Node.js
+      href: quickstart-feature-flag-javascript.md
     - name: Azure Kubernetes Service
       href: quickstart-feature-flag-azure-kubernetes-service.md
   - name: Service integration
@@ -88,7 +90,7 @@
       href: enable-dynamic-configuration-java-spring-app.md
     - name: Python
       href: enable-dynamic-configuration-python.md
-    - name: JavaScript
+    - name: Node.js
       href: enable-dynamic-configuration-javascript.md
     - name: Azure Kubernetes Service
       href: enable-dynamic-configuration-azure-kubernetes-service.md
@@ -138,6 +140,8 @@
         href: howto-feature-filters.md
       - name: ASP.NET Core
         href: howto-feature-filters-aspnet-core.md
+      - name: JavaScript
+        href: howto-feature-filters-javascript.md
       - name: Python
         href: howto-feature-filters-python.md
     - name: Enable features on a schedule
@@ -146,6 +150,8 @@
         href: howto-timewindow-filter.md
       - name: ASP.NET Core
         href: howto-timewindow-filter-aspnet-core.md
+      - name: JavaScipt
+        href: howto-timewindow-filter-javascript.md
     - name: Roll out features to targeted audience
       items:
       - name: Overview

articles/automation/change-tracking/media/enable-vms-monitoring-agent/select-change-tracking-multiple-vms-expanded.png

@@ -0,0 +1,81 @@
+---
+title: Enable conditional features with a custom filter in a Node.js application
+titleSuffix: Azure App Configuration
+description: Learn how to implement a custom feature filter to enable conditional feature flags for your Node.js application.
+ms.service: azure-app-configuration
+ms.devlang: javascript
+author: zhiyuanliang-ms
+ms.author: zhiyuanliang
+ms.topic: how-to
+ms.custom: mode-other, devx-track-js
+ms.date: 09/26/2024
+---
+
+# Tutorial: Enable conditional features with a custom filter in a JavaScript application
+
+Feature flags can use feature filters to enable features conditionally. To learn more about feature filters, see [Tutorial: Enable conditional features with feature filters](./howto-feature-filters.md).
+
+The example used in this tutorial is based on the Node.js application introduced in the feature management [quickstart](./quickstart-feature-flag-javascript.md). Before proceeding further, complete the quickstart to create a Node.js application with a *Beta* feature flag. Once completed, you must [add a custom feature filter](./howto-feature-filters.md) to the *Beta* feature flag in your App Configuration store. 
+
+In this tutorial, you'll learn how to implement a custom feature filter and use the feature filter to enable features conditionally. We are using the Node.js console app as an example, but you can also use the custom feature filter in other JavaScript applications.
+
+## Prerequisites
+
+- Create a [console app with a feature flag](./quickstart-feature-flag-javascript.md).
+- [Add a custom feature filter to the feature flag](./howto-feature-filters.md)
+
+## Implement a custom feature filter
+
+You've added a custom feature filter named **Random** with a **Percentage** parameter for your *Beta* feature flag in the prerequisites. Next, you implement the feature filter to enable the *Beta* feature flag based on the chance defined by the **Percentage** parameter.
+
+1. Open the file *app.js* and add the `RandomFilter` with the following code.
+
+    ``` javascript
+    class RandomFilter {
+        name = "Random";
+        evaluate(context) {
+            const percentage = context.parameters.Percentage;
+            const randomNumber = Math.random() * 100;
+            return randomNumber <= percentage;
+        }
+    }
+    ```
+
+    You added a `RandomFilter` class that has a single method named `evaluate`, which is called whenever a feature flag is evaluated. In `evaluate`, a feature filter enables a feature flag by returning `true`.
+
+    You set the name to of `RandomFilter` to **Random**, which matches the filter name you set in the *Beta* feature flag in Azure App Configuration.
+
+1. Register the `RandomFilter` when creating the `FeatureManager`.
+
+    ``` javascript
+    const fm = new FeatureManager(ffProvider, {customFilters: [new RandomFilter()]});
+    ```
+
+## Feature filter in action
+
+When you run the application the configuration provider will load the *Beta* feature flag from Azure App Configuration. The result of the `isEnabled("Beta")` method will be printed to the console. As the `RandomFilter` is implemented and used by the *Beta* feature flag, the result will be `True` 50 percent of the time and `False` the other 50 percent of the time.
+
+Running the application will show that the *Beta* feature flag is sometimes enabled and sometimes not.
+
+``` bash
+Beta is enabled: true
+Beta is enabled: false
+Beta is enabled: false
+Beta is enabled: true
+Beta is enabled: true
+Beta is enabled: false
+Beta is enabled: false
+Beta is enabled: false
+Beta is enabled: true
+Beta is enabled: true
+```
+
+## Next steps
+
+To learn more about the built-in feature filters, continue to the following tutorials.
+
+> [!div class="nextstepaction"]
+> [Enable features on a schedule](./howto-timewindow-filter.md)
+
+> [!div class="nextstepaction"]
+> [Roll out features to targeted audience](./howto-targetingfilter.md)

articles/automation/change-tracking/media/enable-vms-monitoring-agent/select-change-tracking-multiple-vms-inline.png

@@ -55,19 +55,15 @@ You can create custom feature filters that enable features based on your specifi
     > [!div class="mx-imgBorder"]
     > ![Screenshot of the Azure portal, applying new custom filter.](./media/feature-filters/feature-flag-edit-apply-filter.png)
 
-You have successfully added a custom filter to a feature flag. Follow the instructions in the [Next Steps](#next-steps) section to implement the feature filter into your application for the language or platform you are using.
+    You have successfully added a custom filter to a feature flag. 
 
-## Next steps
-
-In this tutorial, you learned the concept of feature filter and added a custom feature filter to a feature flag.
-
-To learn how to implement a custom feature filter, continue to the following tutorial:
+1. Continue to the following instructions to implement the feature filter into your application for the language or platform you are using.
 
-> [!div class="nextstepaction"]
-> [ASP.NET Core](./howto-feature-filters-aspnet-core.md)
+    - [ASP.NET Core](./howto-feature-filters-aspnet-core.md)
+    - [Node.js](./howto-feature-filters-javascript.md)
+    - [Python](./howto-feature-filters-python.md)
 
-> [!div class="nextstepaction"]
-> [Python](./howto-feature-filters-python.md)
+## Next steps
 
 To learn more about the built-in feature filters, continue to the following tutorials: