Add lightbox

Author: cdpark

articles/connectors/connectors-native-http.md

@@ -15,6 +15,7 @@ ms.date: 05/09/2025
 Some scenarios might require that you create a logic app workflow that sends outbound requests to endpoints on other services or systems over HTTP or HTTPS. For example, suppose that you want to monitor a service endpoint for your website by checking that endpoint on a specific schedule. When a specific event happens at that endpoint, such as your website going down, that event triggers your workflow and runs the actions in that workflow.
 
 > [!NOTE]
+>
 > To create a workflow that receives and responds to inbound HTTPS calls instead, see 
 > [Create workflows that you can call, trigger, or nest using HTTPS endpoints in Azure Logic Apps](../logic-apps/logic-apps-http-endpoint.md). To use the Request built-in trigger, see [Receive and respond to inbound HTTPS calls to workflows in Azure Logic Apps](../connectors/connectors-native-reqres.md).
 
@@ -208,6 +209,7 @@ For example, if you're working in Visual Studio Code, follow these steps:
    ```
 
 > [!NOTE]
+>
 > To find the thumbprint, follow these steps:
 > - On your logic app resource menu, under **Settings**, select **Certificates**.
 > - Select **Bring your own certificates (.pfx)** or **Public key certificates (.cer)**.

articles/connectors/connectors-native-reqres.md

@@ -57,7 +57,7 @@ The Request trigger creates a manually callable endpoint that handles *only* inb
 
    The following example shows a sample JSON schema:
 
-   :::image type="content" source="media/connectors-native-reqres/provide-json-schema-consumption.png" alt-text="Screenshot showing Consumption workflow and Request trigger with example JSON schema.":::
+   :::image type="content" source="media/connectors-native-reqres/provide-json-schema-consumption.png" alt-text="Screenshot showing Consumption workflow and Request trigger with example JSON schema." lightbox="media/connectors-native-reqres/provide-json-schema-consumption.png":::
 
    The following example shows the complete sample JSON schema:
 
@@ -117,11 +117,11 @@ The Request trigger creates a manually callable endpoint that handles *only* inb
 
    1. In the Request trigger, select **Use sample payload to generate schema**.
 
-      :::image type="content" source="media/connectors-native-reqres/generate-from-sample-payload-consumption.png" alt-text="Screenshot showing Consumption workflow, Request trigger, and option to use sample payload to generate schema.":::
+      :::image type="content" source="media/connectors-native-reqres/generate-from-sample-payload-consumption.png" alt-text="Screenshot showing Consumption workflow, Request trigger, and option to use sample payload to generate schema." lightbox="media/connectors-native-reqres/generate-from-sample-payload-consumption.png":::
 
    1. Enter the sample payload, and select **Done**.
 
-      :::image type="content" source="media/connectors-native-reqres/enter-payload-consumption.png" alt-text="Screenshot showing Consumption workflow, Request trigger, and sample payload entered to generate schema.":::
+      :::image type="content" source="media/connectors-native-reqres/enter-payload-consumption.png" alt-text="Screenshot showing Consumption workflow, Request trigger, and sample payload entered to generate schema." lightbox="media/connectors-native-reqres/enter-payload-consumption.png":::
 
       The following example shows the sample payload:
 
@@ -169,15 +169,15 @@ The Request trigger creates a manually callable endpoint that handles *only* inb
 
 1. Select the **Method** dropdown list and choose a method from the list.
 
-   :::image type="content" source="media/connectors-native-reqres/select-method-standard.png" alt-text="Screenshot showing Standard workflow, Request trigger, and the Method list opened with a method selected.":::
+   :::image type="content" source="media/connectors-native-reqres/select-method-standard.png" alt-text="Screenshot showing Standard workflow, Request trigger, and the Method list opened with a method selected." lightbox="media/connectors-native-reqres/select-method-standard.png":::
 
 1. When you're ready, save your workflow. On the designer toolbar, select **Save**.
 
    This step generates the URL that you can use to send a request that triggers the workflow.
 
 1. To copy the generated URL, select the copy icon next to the URL.
 
-   :::image type="content" source="media/connectors-native-reqres/generated-url-consumption.png" alt-text="Screenshot showing Consumption workflow, Request trigger, and URL copy button selected.":::
+   :::image type="content" source="media/connectors-native-reqres/generated-url-consumption.png" alt-text="Screenshot showing Consumption workflow, Request trigger, and URL copy button selected." lightbox="media/connectors-native-reqres/generated-url-consumption.png":::
 
    > [!NOTE]
    >
@@ -201,7 +201,7 @@ The Request trigger creates a manually callable endpoint that handles *only* inb
 
    The following example shows a sample JSON schema:
 
-   :::image type="content" source="media/connectors-native-reqres/provide-json-schema-standard.png" alt-text="Screenshot showing Standard workflow and Request trigger with example JSON schema.":::
+   :::image type="content" source="media/connectors-native-reqres/provide-json-schema-standard.png" alt-text="Screenshot showing Standard workflow and Request trigger with example JSON schema." lightbox="media/connectors-native-reqres/provide-json-schema-standard.png":::
 
    The following example shows the complete sample JSON schema:
 
@@ -261,11 +261,11 @@ The Request trigger creates a manually callable endpoint that handles *only* inb
 
    1. In the Request trigger, select **Use sample payload to generate schema**.
 
-      :::image type="content" source="media/connectors-native-reqres/generate-from-sample-payload-standard.png" alt-text="Screenshot showing Standard workflow, Request trigger, and option to use sample payload to generate schema.":::
+      :::image type="content" source="media/connectors-native-reqres/generate-from-sample-payload-standard.png" alt-text="Screenshot showing Standard workflow, Request trigger, and option to use sample payload to generate schema." lightbox="media/connectors-native-reqres/generate-from-sample-payload-standard.png":::
 
    1. Enter the sample payload, and select **Done**.
 
-      :::image type="content" source="media/connectors-native-reqres/enter-payload-standard.png" alt-text="Screenshot showing Standard workflow, Request trigger, and sample payload entered to generate schema.":::
+      :::image type="content" source="media/connectors-native-reqres/enter-payload-standard.png" alt-text="Screenshot showing Standard workflow, Request trigger, and sample payload entered to generate schema." lightbox="media/connectors-native-reqres/enter-payload-standard.png":::
 
       The following example shows the sample payload:
 
@@ -313,15 +313,15 @@ The Request trigger creates a manually callable endpoint that handles *only* inb
 
 1. Select the **Method** dropdown list and choose a method from the list.
 
-   :::image type="content" source="media/connectors-native-reqres/select-method-standard.png" alt-text="Screenshot showing Standard workflow, Request trigger, and the Method list opened with a method selected.":::
+   :::image type="content" source="media/connectors-native-reqres/select-method-standard.png" alt-text="Screenshot showing Standard workflow, Request trigger, and the Method list opened with a method selected." lightbox="media/connectors-native-reqres/select-method-standard.png":::
 
 1. When you're ready, save your workflow. On the designer toolbar, select **Save**.
 
    This step generates the URL that you can use to send a request that triggers the workflow.
 
 1. To copy the generated URL, select the copy icon next to the URL.
 
-   :::image type="content" source="media/connectors-native-reqres/generated-url-standard.png" alt-text="Screenshot showing Standard workflow, Request trigger, and URL copy button selected.":::
+   :::image type="content" source="media/connectors-native-reqres/generated-url-standard.png" alt-text="Screenshot showing Standard workflow, Request trigger, and URL copy button selected." lightbox="media/connectors-native-reqres/generated-url-standard.png":::
 
    > [!NOTE]
    >
@@ -416,11 +416,11 @@ When you use the Request trigger to receive inbound requests, you can model the
 
    For example, in the **Headers** field, include `Content-Type` as the key name, and set the key value to `application/json` as mentioned earlier in this article. For the **Body** box, you can select the trigger body output from the dynamic content list.
 
-   :::image type="content" source="media/connectors-native-reqres/response-details-consumption.png" alt-text="Screenshot showing Azure portal, Consumption workflow, and Response action information.":::
+   :::image type="content" source="media/connectors-native-reqres/response-details-consumption.png" alt-text="Screenshot showing Azure portal, Consumption workflow, and Response action information." lightbox="media/connectors-native-reqres/response-details-consumption.png":::
 
    To view the headers in JSON format, select **Switch to text view**.
 
-   :::image type="content" source="media/connectors-native-reqres/switch-to-text-view-consumption.png" alt-text="Screenshot showing Azure portal, Consumption workflow, and Response action headers in Switch to text view.":::
+   :::image type="content" source="media/connectors-native-reqres/switch-to-text-view-consumption.png" alt-text="Screenshot showing Azure portal, Consumption workflow, and Response action headers in Switch to text view." lightbox="media/connectors-native-reqres/switch-to-text-view-consumption.png":::
 
 1. To add more properties for the action, such as a JSON schema for the response body, from the **Add new parameter** list, select the parameters that you want to add.
 
@@ -444,11 +444,11 @@ When you use the Request trigger to receive inbound requests, you can model the
 
    For example, for the **Headers** box, enter `Content-Type` as the key name, and set the key value to `application/json` as mentioned earlier in this article. For the **Body** box, you can select the trigger body output from the dynamic content list.
 
-   :::image type="content" source="media/connectors-native-reqres/response-details-standard.png" alt-text="Screenshot showing Azure portal, Standard workflow, and Response action information.":::
+   :::image type="content" source="media/connectors-native-reqres/response-details-standard.png" alt-text="Screenshot showing Azure portal, Standard workflow, and Response action information." lightbox="media/connectors-native-reqres/response-details-standard.png":::
 
    To view the headers in JSON format, select **Switch to text view**.
 
-   :::image type="content" source="media/connectors-native-reqres/switch-to-text-view-standard.png" alt-text="Screenshot showing Azure portal, Standard workflow, and Response action headers in Switch to text view.":::
+   :::image type="content" source="media/connectors-native-reqres/switch-to-text-view-standard.png" alt-text="Screenshot showing Azure portal, Standard workflow, and Response action headers in Switch to text view." lightbox="media/connectors-native-reqres/switch-to-text-view-standard.png":::
 
 1. To add more properties for the action, such as a JSON schema for the response body, open the **Add new parameter** list, and select the parameters that you want to add.