Merge branch 'MicrosoftDocs:main' into pipelinedocupdate

Author: n0elleli

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

@@ -109,14 +109,14 @@ Security definitions are ignored.
 When importing query parameters, only the default array serialization method (`style: form`, `explode: true`) is supported.  For more details on query parameters in OpenAPI specifications, refer to [the serialization specification](https://swagger.io/docs/specification/serialization/).
 
 <!-- Ref: 1795433 Parameter limitations -->
-Parameters [defined in cookies](https://swagger.io/docs/specification/describing-parameters/#cookie-parameters) are not supported.  You can still use policy to decode and validate the contents of cookies.  
+Parameters [defined in cookies](https://swagger.io/docs/specification/describing-parameters/#cookie-parameters) aren't supported.  You can still use policy to decode and validate the contents of cookies.  
 
 ### <a name="open-api-v2"> </a>OpenAPI version 2
 
 OpenAPI version 2 support is limited to JSON format only.
 
 <!-- Ref: 1795433 Parameter limitations -->
-["Form" type parameters](https://swagger.io/specification/v2/#parameter-object) are not supported.  You can still use policy to decode and validate `application/x-www-form-urlencoded` and `application/form-data` payloads.
+["Form" type parameters](https://swagger.io/specification/v2/#parameter-object) aren't supported.  You can still use policy to decode and validate `application/x-www-form-urlencoded` and `application/form-data` payloads.
 
 ### <a name="open-api-v3"> </a>OpenAPI version 3.x
 
@@ -128,19 +128,20 @@ API Management supports the following specification versions:
 #### HTTPS URLs
 
 * If multiple `servers` are specified, API Management will use the first HTTPS URL it finds. 
-* If there aren't any HTTPS URLs, the server URL will be empty.
+* If there aren't any HTTPS URLs, the server URL is empty.
 
 #### Supported
 
 - `example`
 
 #### Unsupported
 
-The following fields are included in [OpenAPI version 3.0.x](https://swagger.io/specification/), but are not supported:
+The following fields are included in either [OpenAPI version 3.0.x](https://swagger.io/specification/) or [OpenAPI version 3.1.x](https://spec.openapis.org/oas/v3.1.0), but aren't supported:
 
 | Object | Field |
 | ----------- | ----------- |
 | **OpenAPI** | `externalDocs` |
+| **Info** | `summary` |
 | **Components** | <ul><li>`responses`</li><li>`parameters`</li><li>`examples`</li><li>`requestBodies`</li><li>`headers`</li><li>`securitySchemes`</li><li>`links`</li><li>`callbacks`</li></ul> |
 | **PathItem** | <ul><li>`trace`</li><li>`servers`</li></ul> |
 | **Operation** | <ul><li>`externalDocs`</li><li>`callbacks`</li><li>`security`</li><li>`servers`</li></ul> |
@@ -159,10 +160,10 @@ For configuration management of API definitions across different services/enviro
 
 ### Add new API via OpenAPI import
 
-For each operation found in the OpenAPI document, a new operation will be created with:
+For each operation found in the OpenAPI document, a new operation is created with:
 * Azure resource name set to `operationId`.
     * `operationId` value is normalized.
-    *  If `operationId` isn't specified (not present, `null`, or empty), Azure resource name value will be generated by combining HTTP method and path template.
+    *  If `operationId` isn't specified (not present, `null`, or empty), Azure resource name value is generated by combining HTTP method and path template.
         * For example, `get-foo`.
 
 * Display name set to `summary`. 
@@ -174,9 +175,9 @@ For each operation found in the OpenAPI document, a new operation will be create
 **Normalization rules for `operationId`**
 - Convert to lower case.
 - Replace each sequence of non-alphanumeric characters with a single dash.
-    - For example, `GET-/foo/{bar}?buzz={quix}` will be transformed into `get-foo-bar-buzz-quix-`.
+    - For example, `GET-/foo/{bar}?buzz={quix}` is transformed into `get-foo-bar-buzz-quix-`.
 - Trim dashes on both sides.
-    - For example, `get-foo-bar-buzz-quix-` will become `get-foo-bar-buzz-quix`
+    - For example, `get-foo-bar-buzz-quix-` becomes `get-foo-bar-buzz-quix`
 - Truncate to fit 76 characters, four characters less than maximum limit for a resource name.
 - Use remaining four characters for a de-duplication suffix, if necessary, in the form of `-1, -2, ..., -999`.
 
@@ -185,12 +186,12 @@ For each operation found in the OpenAPI document, a new operation will be create
 During import, the existing API operation:
 * Changes to match the API described in the OpenAPI document. 
 * Matches to an operation in the OpenAPI document by comparing its `operationId` value to the existing operation's Azure resource name. 
-    * If a match is found, existing operation’s properties will be updated "in-place".
+    * If a match is found, existing operation’s properties are updated "in-place".
     * If a match isn't found:
-        * A new operation will be created by combining HTTP method and path template, for example, `get-foo`. 
+        * A new operation is created by combining HTTP method and path template, for example, `get-foo`. 
         * For each new operation, the import will attempt to copy policies from an existing operation with the same HTTP method and path template.
 
-All existing unmatched operations will be deleted.
+All existing unmatched operations are deleted.
 
 To make import more predictable, follow these guidelines:
 
@@ -201,17 +202,17 @@ To make import more predictable, follow these guidelines:
 **Normalization rules for `operationId`**
 - Convert to lower case.
 - Replace each sequence of non-alphanumeric characters with a single dash.
-    - For example, `GET-/foo/{bar}?buzz={quix}` will be transformed into `get-foo-bar-buzz-quix-`.
+    - For example, `GET-/foo/{bar}?buzz={quix}` is transformed into `get-foo-bar-buzz-quix-`.
 - Trim dashes on both sides.
-    - For example, `get-foo-bar-buzz-quix-` will become `get-foo-bar-buzz-quix`
+    - For example, `get-foo-bar-buzz-quix-` becomes `get-foo-bar-buzz-quix`
 - Truncate to fit 76 characters, four characters less than maximum limit for a resource name.
 - Use remaining four characters for a de-duplication suffix, if necessary, in the form of `-1, -2, ..., -999`.
 
 ### Export API as OpenAPI
 
-For each operation, its:
-* Azure resource name will be exported as an `operationId`.
-* Display name will be exported as a `summary`.
+For each operation, it's:
+* Azure resource name is exported as an `operationId`.
+* Display name is exported as a `summary`.
 
 Note that normalization of the `operationId` is done on import, not on export.
 
@@ -230,7 +231,7 @@ You can create [SOAP pass-through](import-soap-api.md) and [SOAP-to-REST](restif
 
 ### WS-* specifications
 
-WSDL files incorporating WS-* specifications are not supported.
+WSDL files incorporating WS-* specifications aren't supported.
 
 ### Messages with multiple parts 
 This message type is not supported.
@@ -244,13 +245,13 @@ This message type is not supported.
 - Official support isn't offered at this time.
 
 ### Recursion
-- Types defined recursively are not supported by API Management.
+- Types defined recursively aren't supported by API Management.
 - For example, refer to an array of themselves.
 
 ### Multiple Namespaces
 While multiple namespaces can be used in a schema, only the target namespace can be used to define message parts. These namespaces are used to define other input or output elements.
 
-Namespaces other than the target are not preserved on export. While you can import a WSDL document defining message parts with other namespaces, all message parts will have the WSDL target namespace on export.
+Namespaces other than the target aren't preserved on export. While you can import a WSDL document defining message parts with other namespaces, all message parts will have the WSDL target namespace on export.
 
 ### Arrays 
 SOAP-to-REST transformation supports only wrapped arrays shown in the example below:

articles/azure-arc/data/validation-program.md

@@ -34,8 +34,8 @@ To see how all Azure Arc-enabled components are validated, see [Validation progr
 
 |Solution and version | Kubernetes version | Azure Arc-enabled data services version | SQL engine version | PostgreSQL server version
 |-----|-----|-----|-----|-----|
-| Unity XT |1.25.4|1.15.0_2023-01-10|16.0.816.19223 |Not validated|
-| PowerStore T|1.25.4|1.15.0_2023-01-10|16.0.816.19223 |Not validated|
+| [Unity XT](https://www.dell.com/en-us/dt/storage/unity.htm) |1.25.4|1.15.0_2023-01-10|16.0.816.19223 |Not validated|
+| [PowerStore T](https://www.dell.com/en-us/dt/storage/powerstore-storage-appliance.htm) |1.25.4|1.15.0_2023-01-10|16.0.816.19223 |Not validated|
 | Dell EMC PowerFlex |1.21.5|1.4.1_2022-03-08|15.0.2255.119 | postgres 12.3 (Ubuntu 12.3-1) |
 | PowerFlex version 3.6 |1.21.5|1.4.1_2022-03-08|15.0.2255.119 | postgres 12.3 (Ubuntu 12.3-1) |
 | PowerFlex CSI version 1.4 |1.21.5|1.4.1_2022-03-08 | 15.0.2255.119 | postgres 12.3 (Ubuntu 12.3-1) |

articles/devtest-labs/devtest-lab-delete-lab-vm.md

@@ -19,6 +19,9 @@ When you create a VM in a lab, DevTest Labs automatically creates resources for
 - The VM's key vault in the lab's resource group.
 - Any availability set, load balancer, or public IP address in the VM's resource group. These resources are shared by multiple VMs in a resource group.
 
+> [!CAUTION]
+> Deleting VMs and labs is permanent, and cannot be undone.
+
 To delete a VM from a lab:
 
 1. On the lab's **Overview** page in the Azure portal, find the VM you want to delete in the list under **My virtual machines**.
@@ -33,7 +36,8 @@ To delete a VM from a lab:
    - Select the VM name in the list, and then on the VM's **Overview** page, select **Delete** from the top menu.
      ![Screenshot of the Delete button on the V M Overview page.](media/devtest-lab-delete-lab-vm/delete-from-vm-page.png) 
 
-1. On the **Are you sure you want to delete it?** page, select **Delete**.
+1. On the **Are you sure you want to delete it?** page, select **Delete**.</br>
+   The deletion of the VM, it's network interface, and it's associated OS disks is permanent, and cannot be undone.
 
    ![Screenshot of the V M deletion confirmation page.](media/devtest-lab-delete-lab-vm/select-lab.png) 
 
@@ -58,7 +62,8 @@ To delete a lab:
 
    ![Screenshot of the Delete button on the lab Overview page.](media/devtest-lab-delete-lab-vm/delete-button.png)
 
-1. On the **Are you sure you want to delete it?** page, under **Type the lab name**, type the lab name, and then select **Delete**.
+1. On the **Are you sure you want to delete it?** page, under **Type the lab name**, type the lab name, and then select **Delete**.</br>
+   The deletion of the lab and all it's resources is permanent, and cannot be undone.
 
    ![Screenshot of the lab deletion confirmation page.](media/devtest-lab-delete-lab-vm/confirm-delete.png) 
 

articles/logic-apps/media/view-workflow-metrics/add-filter-standard.png

@@ -416,6 +416,8 @@
     items:
       - name: Monitor logic apps
         href: monitor-logic-apps.md
+      - name: View health and performance metrics
+        href: view-workflow-metrics.md
       - name: Monitor logic apps with Azure Monitor logs
         href: monitor-logic-apps-log-analytics.md
       - name: Monitor logic apps in Microsoft Defender for Cloud

articles/logic-apps/media/view-workflow-metrics/example-add-filter-standard.png

@@ -0,0 +1,121 @@
+---
+title: View workflow health and performance metrics
+description: View health and performance metrics for workflows in Azure Logic Apps.
+services: logic-apps
+ms.suite: integration
+author: kewear
+ms.author: kewear
+ms.reviewer: estfan, azla
+ms.topic: how-to
+ms.date: 02/15/2023
+# As a developer, I want to review the health and performance metrics for workflows in Azure Logic Apps.
+---
+
+# View metrics for workflow health and performance in Azure Logic Apps
+
+[!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
+
+This guide shows how you can check the health and performance for both Consumption and Standard logic app workflows.
+
+## Prerequisites
+
+* An Azure account and subscription. If you don't have a subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+
+* A Consumption workflow or Standard workflow that is running or has run at least once
+
+## Find and view metrics
+
+### [Consumption](#tab/consumption)
+
+1. In the [Azure portal](https://portal.azure.com), open your logic app resource.
+
+1. On the logic app resource menu, under **Monitoring**, select **Metrics**.
+
+   The **Metrics** page shows the following lists: **Scope**, **Metric Namespace**, and **Metric**.
+
+1. Make sure that **Scope** is set to your Consumption logic app name and that **Metric Namespace** is set to **Logic app standard metrics**.
+
+1. Open the **Metric** list to view the available metrics for your workflow.
+
+   :::image type="content" source="./media/view-workflow-metrics/view-metrics-consumption.png" alt-text="Screenshot showing Azure portal, Consumption logic app resource menu with Metrics selected, and the Metric list opened.":::
+
+   For more information about Consumption workflow metrics, see [Supported metrics with Azure Monitor - Microsoft.Logic/workflows](../azure-monitor/essentials/metrics-supported.md#microsoftlogicworkflows).
+
+1. From the **Metric** list, select the metric that you want to review. From the **Aggregation** list, select the option for how you want to group the metric's values: **Count**, **Avg**, **Min**, **Max**, or **Sum**.
+
+### [Standard (preview)](#tab/standard)
+
+1. In the [Azure portal](https://portal.azure.com), open your logic app resource.
+
+1. On the logic app resource menu, under **Monitoring**, select **Metrics**.
+
+   The **Metrics** page shows the following lists: **Scope**, **Metric Namespace**, and **Metric**.
+
+1. Make sure that **Scope** is set to your Standard logic app name and that **Metric Namespace** is set to **App Service standard metrics**.
+
+1. In the **Metric** search box, enter **workflow** to view the metrics that start with **Workflow**.
+
+   The filtered list now shows the available metrics for your workflow:
+
+   | Metric name | Description |
+   |-------------|-------------|
+   | **Workflow Action Completed Count** | The number of completed actions, regardless of status. |
+   | **Workflow Job Execution Delay** | The amount of time between when a job was scheduled to run and when the job actually ran. |
+   | **Workflow Job Execution Duration** | The amount of time that a job took to complete execution. |
+   | **Workflow Runs Completed Count** | The number of completed workflow executions, regardless of status. |
+   | **Workflow Runs Dispatched Count** | The number of previously queued requests that are now processed. |
+   | **Workflow Runs Started Count** | The number of started workflows, regardless of outcome status. |
+   | **Workflow Triggers Completed Count** | The number of completed triggers, regardless of outcome. |
+
+   :::image type="content" source="./media/view-workflow-metrics/view-metrics-standard.png" alt-text="Screenshot showing Azure portal, Standard logic app resource menu with Metrics selected, the Metric search box with workflow entered, and the Metric list opened.":::
+
+   > [!NOTE]
+   >
+   > For information about non-workflow related metrics, such as Azure App Service metrics for Standard workflows, 
+   > see [Monitor apps in Azure App Service - Understand metrics](../app-service/web-sites-monitor.md#understand-metrics).
+
+1. From the **Metric** list, select the metric that you want to review. From the **Aggregation** list, select the option for how you want to group the metric's values: **Count**, **Avg**, **Min**, **Max**, or **Sum**.
+
+#### Filter on a specific workflow
+
+If your Standard logic app has multiple workflows running, you can filter the results by workflow.
+
+1. Under the **Metrics** toolbar, select **Add filter**.
+
+1. From the **Property** list, select **Workflow Name**.
+
+1. From the **Values** list, select the specific workflow.
+
+#### Filter on a specific workflow status
+
+1. Under the **Metrics** toolbar, select **Add filter**.
+
+1. From the **Property** list, select **Status**.
+
+1. From the **Values** list, select the status.
+
+#### Example
+
+Suppose that you want to view the number of workflow runs that have a specific status over the past 24 hours.
+
+1. From the **Metric** list, select the metric named **Workflow Runs Completed**.
+
+1. From the **Aggregation** list, select **Sum**.
+
+   :::image type="content" source="./media/view-workflow-metrics/example-metric-standard.png" alt-text="Screenshot showing example metric for Standard logic app.":::
+
+   In this example, the Standard logic app has multiple workflows running. So, you can filter the results by adding a filter.
+
+   1. Under the **Metrics** toolbar, select **Add filter**.
+
+   1. From the **Property** list, select **Workflow Name**.
+
+   1. From the **Values** list, select the specific workflow.
+
+      :::image type="content" source="./media/view-workflow-metrics/example-add-filter-standard.png" alt-text="Screenshot showing example added metrics filter for Standard logic app.":::
+
+---
+
+## Next steps
+
+- [Monitor logic apps](monitor-logic-apps.md)