Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into container-vulnerability

Author: ElazarK

.openpublishing.redirection.json

@@ -8,7 +8,7 @@ author: dlepow
 
 ms.service: api-management
 ms.topic: article
-ms.date: 02/02/2022
+ms.date: 02/10/2022
 ms.author: danlep 
 ms.custom: devx-track-azurepowershell
 ---
@@ -44,6 +44,9 @@ Customize and style the managed portal through the built-in, drag-and-drop visua
 
 See [this tutorial](api-management-howto-developer-portal-customize.md) for example customizations.
 
+> [!NOTE]
+> The managed developer portal receives and applies updates automatically. Changes that you've saved but not published to the developer portal remain in that state during an update.
+
 ## <a name="managed-vs-self-hosted"></a> Extensibility
 
 In some cases you might need functionality beyond the customization and styling options supported in the managed developer portal.  If you need to implement custom logic, which isn't supported out-of-the-box, you can modify the portal's codebase, available on [GitHub](https://github.com/Azure/api-management-developer-portal). For example, you could create a new widget to integrate with a third-party support system. When you implement new functionality, you can choose one of the following options:

articles/api-management/api-management-howto-developer-portal.md

@@ -1,17 +1,10 @@
 ---
 title: Import SOAP API using the Azure portal | Microsoft Docs
 description: Learn how to import a standard XML representation of a SOAP API, and then test the API in the Azure and Developer portals.
-services: api-management
-documentationcenter: ''
 author: dlepow
-manager: cfowler
-editor: ''
-
 ms.service: api-management
-ms.workload: mobile
-ms.tgt_pltfrm: na
-ms.topic: article
-ms.date: 04/22/2020
+ms.topic: how-to
+ms.date: 02/10/2022
 ms.author: danlep
 
 ---
@@ -24,7 +17,6 @@ In this article, you learn how to:
 > [!div class="checklist"]
 > * Import SOAP API
 > * Test the API in the Azure portal
-> * Test the API in the Developer portal
 
 ## Prerequisites
 
@@ -57,7 +49,7 @@ Complete the following quickstart: [Create an Azure API Management instance](get
 8. Enter other API settings. You can set the values during creation or configure them later by going to the **Settings** tab. The settings are explained in the [Import and publish your first API](import-and-publish.md#import-and-publish-a-backend-api) tutorial.
 9. Select **Create**.
 
-### Test the new API in the administrative portal
+### Test the new API in the portal
 
 Operations can be called directly from the administrative portal, which provides a convenient way to view and test the operations of an API.  
 
@@ -70,6 +62,18 @@ Operations can be called directly from the administrative portal, which provides
 
     Backend responds with **200 OK** and some data.
 
+## Wildcard SOAP action
+
+If you need to pass a SOAP request that doesn't have a dedicated action defined in the API, you can configure a wildcard SOAP action. The wildcard action will match any SOAP request that isn't defined in the API.  
+
+To define a wildcard SOAP action:
+
+1. In the portal, select the API you created in the previous step.
+1. In the **Design** tab, select **+ Add Operation**.
+1. Enter a **Display name** for the operation.
+1. In the URL, select `POST` and enter `/soapAction={any}` in the resource. The template parameter inside the curly brackets is arbitrary and doesn't affect the execution.
+
+
 [!INCLUDE [api-management-navigate-to-instance.md](../../includes/api-management-append-apis.md)]
 
 [!INCLUDE [api-management-define-api-topics.md](../../includes/api-management-define-api-topics.md)]

articles/api-management/import-soap-api.md

@@ -1,5 +1,5 @@
 ---
-title: Manually create and deploy an Azure Precept Devkit
+title: How to do a manual default container deployment to Azure Percept DK
 description: this article shows the audience how to manually create and deploy an Azure Precept Devkit
 author: nkhuyent
 ms.author: keithke
@@ -10,71 +10,77 @@ ms.custom: template-how-to
 ---
 
 
-# Manually create and deploy an Azure Precept Devkit 
-The following guide is to help customers manually deploy a factory fresh IoT Edge deployment to existing Azure Percept devices. We have also included the steps to manually create your Azure Percept IoT Edge device instance.
+# How to do a manual default container deployment to Azure Percept DK 
+
+The following guide is to help customers manually deploy a factory fresh IoT Edge deployment to existing Azure Percept devices. We've also included the steps to manually create your Azure Percept IoT Edge device instance.
 
 ## Prerequisites
 
-- Highly recommended: Update your Percept Devkit to the [latest version](./software-releases-usb-cable-updates.md)
-- Azure account with IoT Hub created 
+- Highly recommended: Update your Azure Percept DK to the [latest version](./software-releases-usb-cable-updates.md)
+- Create an Azure account with an IoT Hub 
 - Install [VSCode](https://code.visualstudio.com/Download)
 - Install the [Azure IoT Tools](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-tools) Extension for VSCode
-- Find the software image version running on your Percept Devkit (see below). 
+- Find the software image version running on your Azure Percept Devkit (see below)
 
-## How to identify your Azure Percept Devkit software version 
+## Identify your Azure Percept DK software version 
 
-SSH (Secure Shell) into your devkit and run the following command then write down the output for later reference. 
+Using SSH (Secure Shell), run the command line below. Write down the output for later reference. 
 
 `cat /etc/adu-version`
 
 Example output: 2021.111.124.109 
 
-## Create an Azure IoT Edge device for the Devkit
-If you have a device already created, you can skip to the [Manually deploy the deployment.json to the device](#manually-deploy-the-deploymentjson-to-the-azure-percept-device) section. 
-1. Go to [Azure portal](https://portal.azure.com) and select the **IoT Hub** where you will create the device. 
+## Create an Azure IoT Edge device for the Azure Percept DK
+If you already have an IoT Edge device instance created in your subscription for the devkit, you can skip to the [Manually deploy the deployment.json to the Azure Percept DK](#manually-deploy-the-deploymentjson-to-the-azure-percept-dk) section. 
+1. Go to [Azure portal](https://portal.azure.com) and select the **IoT Hub** where you'll create the device 
 2. Navigate to **IoT Edge** and select **Add an IoT Edge device**
-3. On the **Create a Device** screen, name your device in the **Device ID** section and leave all other fields as default, then click the **Save** button.  
-![create new device](./media/manually-deploy-azure-precept-devkit-images/create-device.png)
+3. On the **Create a Device** screen, name your device in the **Device ID** section and leave all other fields as default, then select **Save**  
+:::image type="content" source="./media/manually-deploy-azure-precept-devkit-images/create-device.png" alt-text="create new device":::
 
-1. Select your newly created device.  
-![select new device.](./media/manually-deploy-azure-precept-devkit-images/select-new-device.png)
+1. Select your newly created device  
+:::image type="content" source="./media/manually-deploy-azure-precept-devkit-images/select-new-device.png" alt-text="select new device.":::
 
-2. Copy the **Primary Connection String**. We will use this copied text in the Azure Percept Onboarding/setup web pages.  
-![Primary Connection String](./media/manually-deploy-azure-precept-devkit-images/primary-connection-string.png)   
+2. Copy the **Primary Connection String**, we will use this copied text in the Azure Percept Onboarding/setup web pages  
+:::image type="content" source="./media/manually-deploy-azure-precept-devkit-images/primary-connection-string.png" alt-text="primary connection string.":::
 
 
-## Connect to and Setup the Devkit 
+## Connect to and set up the Azure Percept DK
 <!-- Introduction paragraph -->
-1. Setup your Devkit using the main instructions and **STOP** at to the **Select your preferred configuration** page 
+1. Set up your devkit using the main instructions and **STOP** at to the **Select your preferred configuration** page 
 1. Select **Connect to an existing device** 
-1. Paste the **Primary Connection String** that you copied from the earlier steps. 
-2. Click Finish. 
-3. The **Device setup complete!** page should now display.  
+1. Paste the **Primary Connection String** that you copied from the earlier steps
+2. Select Finish 
+3. The **Device set up complete!** page should now display 
    **If this page does not disappear after 10 secs, don’t worry. Just go ahead with the next steps** 
-4. You will be disconnected from the Devkit’s Wi-Fi hotspot. Reconnect your computer to your main Wi-Fi (if needed).  
-
-
-## Manually deploy the deployment.json to the Azure Percept device 
-The deployment.json files are a representation of all default modules necessary to begin using the Azure Percept devkit. 
-1. Download the appropriate deployment.json from [GitHub](https://github.com/microsoft/azure-percept-advanced-development/tree/main/default-configuration) for your reported software version. Refer to the [How to Identify your Azure Percept Devkit software version](#how-to-identify-your-azure-percept-devkit-software-version) section above.
-   1. For 2021.111.124.xxx and later   -----> use [default-deployment-2112.json](https://github.com/microsoft/azure-percept-advanced-development/blob/main/default-configuration/default-deployment-2112.json)
-   2. For 2021.109.129.xxx and lower use ----> use [default-deployment-2108.json](https://github.com/microsoft/azure-percept-advanced-development/blob/main/default-configuration/default-deployment-2108.json)
-2. Launch VSCode and Sign into Azure. Be sure you have installed the [Azure IoT Tools](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-tools) Extension 
-3. Connect to your subscription and select your IoTHub 
-4. Locate your IoT Edge Device then right click it and choose **Create deployment for a Single Device**.  
-![find edge device](./media/manually-deploy-azure-precept-devkit-images/iot-edge-device.png) ![create deployment for edge device](./media/manually-deploy-azure-precept-devkit-images/create-deployment.png)
-
-5. Navigate to the "Deployment.json" you saved from step 1 and use this. 
-6. Deployment will take 1-5 mins to fully complete. 
-   1. For those interested in watching the IoT Edge log as this deployment is going on, you can SSH into your Azure Percept devkit and watch the iotedge logs by issuing the command below.  
+4. You'll be disconnected from the devkit’s Wi-Fi hotspot, reconnect your computer to your main Wi-Fi (if needed)  
+
+
+## Manually deploy the deployment.json to the Azure Percept DK
+
+The deployment.json files are a representation of all default modules necessary to begin using the Azure Percept DK. 
+1. Download the appropriate deployment.json from [GitHub](https://github.com/microsoft/azure-percept-advanced-development/tree/main/default-configuration) for your reported software version. Refer to the [Identify your Azure Percept DK software version](#identify-your-azure-percept-dk-software-version) section above.
+   1. For 2021.111.124.xxx and later, use [default-deployment-2112.json](https://github.com/microsoft/azure-percept-advanced-development/blob/main/default-configuration/default-deployment-2112.json)
+   2. For 2021.109.129.xxx and lower, use [default-deployment-2108.json](https://github.com/microsoft/azure-percept-advanced-development/blob/main/default-configuration/default-deployment-2108.json)
+2. Launch VSCode and Sign into Azure. Be sure you've installed the [Azure IoT Tools](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-tools) Extension.  
+   
+   ![Sign into Azure in VScode.](./media/manually-deploy-azure-precept-devkit-images/azure-sign-in.png)
+
+3. Connect to your subscription and select your IoT Hub 
+4. Locate your IoT Edge Device then right select it and choose **Create deployment for a Single Device**.  
+
+   ![find edge device.](./media/manually-deploy-azure-precept-devkit-images/iot-edge-device.png) ![create deployment for edge device](./media/manually-deploy-azure-precept-devkit-images/create-deployment.png)  
+
+5. Navigate to the "Deployment.json" you saved from step 1 and select it. Then select OK.
+6. Deployment will take 1-5 minutes to fully complete 
+   1. If you are interested in watching the Azure IoT Edge log while the deployment is going on, you can SSH into your Azure Percept DK and watch the Azure IoT Edge logs by issuing the command below.  
     `sudo journalctl -u iotedge -f` 
-7. Your Devkit is now ready to use!
+7. Your Azure Percept DK is now ready to use!
 
 
 <!-- 5. Next steps
-Required. Provide at least one next step and no more than three. Include some 
-context so the customer can determine why they would click the link.
+	@@ -77,4 +76,4 @@ context so the customer can determine why they would click the link.
 -->
 
 ## Next steps
-Navigate to the [Azure Percept portal](https://portal.azure.com/#blade/AzureEdgeDevices/Main/overview) for more AI models. 
+Navigate to the [Azure Percept Studio](https://ms.portal.azure.com/#blade/AzureEdgeDevices/Main/overview) for more AI models. 
+