Merge branch 'main' of https://github.com/seesharprun/azure-docs-pr into patch-2

Author: seesharprun

articles/iot-central/core/how-to-connect-devices-x509.md

@@ -93,9 +93,7 @@ Make a note of the location of these files. You need it later.
 
 1. Open the enrollment group you created and select **Manage Primary**.
 
-1. Select file option to upload the root certificate file called _mytestrootcert_cert.pem_ that you generated previously:
-
-    ![Certificate Upload](./media/how-to-connect-devices-x509/certificate-upload.png)
+1. Select file option to upload the root certificate file called _mytestrootcert_cert.pem_ that you generated previously.
 
 1. To complete the verification, generate the verification code, copy it, and then use it to create an X.509 verification certificate at the command prompt:
 
@@ -243,9 +241,7 @@ These commands produce the following device certificates:
 
 1. Open the device you created and select **Connect**.
 
-1. Select **Individual Enrollments** as the **Connect Method** and **Certificates (X.509)** as the mechanism:
-
-    ![Individual enrollment](./media/how-to-connect-devices-x509/individual-device-connect.png)
+1. Select **Individual Enrollments** as the **Connect Method** and **Certificates (X.509)** as the mechanism.
 
 1. Select file option under primary and upload the certificate file called _mytestselfcertprimary_cert.pem_ that you generated previously.
 

articles/iot-central/core/howto-connect-eflow.md

@@ -107,15 +107,11 @@ To enable an operator to view the telemetry from the device, define a view in th
 
 1. Select **Save** to save the **View IoT Edge device telemetry** view.
 
-:::image type="content" source="media/howto-connect-eflow/template-telemetry-view.png" alt-text="Device template with telemetry view.":::
-
 ### Publish the template
 
 Before you can add a device that uses the **Environmental Sensor Edge Device** template, you must publish the template.
 
-Navigate to the **Environmental Sensor Edge Device** template and select **Publish**. On the **Publish this device template to the application** panel, select **Publish** to publish the template:
-
-:::image type="content" source="media/howto-connect-eflow/publish-template.png" alt-text="Publish the device template.":::
+Navigate to the **Environmental Sensor Edge Device** template and select **Publish**. On the **Publish this device template to the application** panel, select **Publish** to publish the template
 
 ## Add an IoT Edge device
 

articles/iot-central/core/howto-connect-rigado-cascade-500.md

@@ -36,15 +36,11 @@ To onboard a Cascade 500 gateway device into your Azure IoT Central application
 
 To add a Cascade 500 device template:
 
-1. Navigate to the **Device Templates** tab in the left pane, select **+ New**:
-
-    ![Create new device template](./media/howto-connect-rigado-cascade-500/device-template-new.png)
+1. Navigate to the **Device Templates** tab in the left pane, select **+ New**
 
 1. The page gives you an option to **Create a custom template** or **Use a preconfigured device template**.
 
-1. Select the C500 device template from the list of preconfigured device templates as shown below:
-
-    ![Select C500 device template](./media/howto-connect-rigado-cascade-500/device-template-preconfigured.png)
+1. Select the C500 device template from the list of preconfigured device templates.
 
 1. Select **Next: Customize** to continue to the next step.
 

articles/iot-central/core/howto-connect-ruuvi.md

@@ -36,15 +36,9 @@ To onboard a RuuviTag sensor into your Azure IoT Central application instance, y
 
 To add a RuuviTag device template:
 
-1. Navigate to the **Device Templates** tab in the left pane, select **+ New**:
+1. Navigate to the **Device Templates** tab in the left pane, select **+ New**. The page gives you an option to **Create a custom template** or **Use a preconfigured device template**.
 
-    ![Create new device template](./media/howto-connect-ruuvi/device-template-new.png)
-
-    The page gives you an option to **Create a custom template** or **Use a preconfigured device template**.
-
-1. Select the RuuviTag Multisensor device template from the list of preconfigured device templates:
-
-    ![Select RuuviTag device template](./media/howto-connect-ruuvi/device-template-pre-configured.png)
+1. Select the RuuviTag Multisensor device template from the list of preconfigured device templates.
 
 1. Select **Next: Customize** to continue to the next step.
 

articles/iot-central/core/howto-create-and-manage-applications-csp.md

@@ -31,13 +31,7 @@ You land on the Azure IoT Central Application Manager page. Azure IoT Central ke
 
 ![Create Manager for CSPs](media/howto-create-and-manage-applications-csp/image3.png)
 
-To create an Azure IoT Central application, select **Build** in the left menu. Choose one of the industry templates, or choose **Custom app** to create an application from scratch. This will load the Application Creation page. You must complete all the fields on this page and then choose **Create**. You find more information about each of the fields below.
-
-![Screenshot that shows the "Build your IoT application" page with the "Build" button selected.](media/howto-create-and-manage-applications-csp/image4.png)
-
-![Create Application Page for CSPs](media/howto-create-and-manage-applications-csp/image4-1.png)
-
-![Create Application Page for CSPs Billing Info](media/howto-create-and-manage-applications-csp/image4-2.png)
+To create an Azure IoT Central application, select **Build** in the left menu. Choose one of the industry templates, or choose **Custom app** to create an application from scratch. This will load the Application Creation page. You must complete all the fields on this page and then choose **Create**. 
 
 ## Application name
 

articles/iot-central/core/howto-create-iot-central-application.md

@@ -64,8 +64,6 @@ The easiest way to get started creating IoT Central applications is on the [Azur
 
 The [Build](https://apps.azureiotcentral.com/build) lets you select the application template you want to use:
 
-:::image type="content" source="media/howto-create-iot-central-application/choose-template.png" alt-text="Screenshot of build page that lets you choose an application template.":::
-
 If you select **Create app**, you can provide the necessary information to create an application from the template:
 
 :::image type="content" source="media/howto-create-iot-central-application/create-application.png" alt-text="Screenshot showing create application page for IoT Central.":::
@@ -121,7 +119,6 @@ To create an application template from an existing IoT Central application:
 1. On the **Template Export** page, enter a name and description for your template.
 1. Select the **Export** button to create the application template. You can now copy the **Shareable Link** that enables someone to create a new application from the template:
 
-:::image type="content" source="media/howto-create-iot-central-application/create-template.png" alt-text="Screenshot that shows create an application template.":::
 
 :::image type="content" source="media/howto-create-iot-central-application/create-template-2.png" alt-text="Screenshot that shows export an application template.":::
 

articles/iot-central/core/howto-manage-devices-in-bulk.md

@@ -33,8 +33,6 @@ The following example shows you how to create and run a job to set the light thr
 
     To configure a **Property** job, select a property and set its new value. A property job can set multiple properties. To configure a **Command** job, choose the command to run. To configure a **Change device template** job, select the device template to assign to the devices in the device group.
 
-    :::image type="content" source="media/howto-manage-devices-in-bulk/configure-job.png" alt-text="Screenshot that shows selections for creating a property job called Set Light Threshold":::
-
     Select **Save and exit** to add the job to the list of saved jobs on the **Jobs** page. You can later return to a job from the list of saved jobs.
 
 1. Select **Next** to move to the **Delivery Options** page. The **Delivery Options** page lets you set the delivery options for this job: **Batches** and **Cancellation threshold**.
@@ -43,9 +41,7 @@ The following example shows you how to create and run a job to set the light thr
 
     The cancellation threshold lets you automatically cancel a job if the number of errors exceeds your set limit. The threshold can apply to all the devices in the job, or to individual batches.
 
-    :::image type="content" source="media/howto-manage-devices-in-bulk/job-wizard-delivery-options.png" alt-text="Screenshot of job wizard delivery options page":::
-
-1. Select **Next** to move to the **Schedule** page. The **Schedule** page lets you enable a schedule to run the job in the future:
+1. Select **Next** to move to the **Schedule** page. The **Schedule** page lets you enable a schedule to run the job in the future.
 
     Choose a recurrence option for the schedule. You can set up a job to run:
 
@@ -62,8 +58,6 @@ The following example shows you how to create and run a job to set the light thr
 
     Scheduled jobs always run on the devices in a device group, even if the device group membership changes over time.
 
-    :::image type="content" source="media/howto-manage-devices-in-bulk/job-wizard-schedule.png" alt-text="Screenshot of job wizard schedule options page":::
-
 1. Select **Next** to move to the **Review** page. The **Review** page shows the job configuration details. Select **Schedule** to schedule the job:
 
     :::image type="content" source="media/howto-manage-devices-in-bulk/job-wizard-schedule-review.png" alt-text="Screenshot of scheduled job wizard review page":::
@@ -72,12 +66,8 @@ The following example shows you how to create and run a job to set the light thr
 
     On this page, you can **Unschedule** the job or **Edit** the scheduled job. You can return to a scheduled job from the list of scheduled jobs.
 
-    :::image type="content" source="media/howto-manage-devices-in-bulk/job-schedule-details.png" alt-text="Screenshot of scheduled job details page":::
-
 1. In the job wizard, you can choose to not schedule a job, and run it immediately. The following screenshot shows a job without a schedule that's ready to run immediately. Select **Run** to run the job:
 
-    :::image type="content" source="media/howto-manage-devices-in-bulk/job-wizard-schedule-immediate.png" alt-text="Screenshot of job wizard review page":::
-
 1. A job goes through *pending*, *running*, and *completed* phases. The job execution details contain result metrics, duration details, and a device list grid.
 
     When the job is complete, you can select **Results log** to download a CSV file of your job details, including the devices and their status values. This information can be useful for troubleshooting.
@@ -93,8 +83,6 @@ The following example shows you how to create and run a job to set the light thr
 
 To stop a running job, open it and select **Stop**. The job status changes to reflect that the job is stopped. The **Summary** section shows which devices have completed, have failed, or are still pending.
 
-:::image type="content" source="media/howto-manage-devices-in-bulk/manage-job.png" alt-text="Screenshot that shows a running job and the button for stopping a job":::
-
 When a job is in a stopped state, you can select **Continue** to resume running the job. The job status changes to reflect that the job is now running again. The **Summary** section continues to update with the latest progress.
 
 :::image type="content" source="media/howto-manage-devices-in-bulk/stopped-job.png" alt-text="Screenshot that shows a stopped job and the button for continuing a job":::
@@ -217,8 +205,6 @@ To bulk export devices from your application:
 
 1. Select the devices that you want to export and then select the **Export** action.
 
-    :::image type="content" source="media/howto-manage-devices-in-bulk/export-1.png" alt-text="Screenshot showing export action settings.":::
-
 1. The export process starts. You can track the status using the **Device Operations** panel.
 
 1. When the export completes, a success message is shown along with a link to download the generated file.

articles/iot-central/core/howto-use-commands.md

@@ -206,10 +206,6 @@ The call to `onDeviceMethod` sets up the `commandHandler` method. This command h
 1. Completes the long-running operation.
 1. Uses a reported property with the same name as the command to tell IoT Central that the command completed.
 
-The following screenshot shows how the command response displays in the IoT Central UI when it receives the 202 response code:
-
-:::image type="content" source="media/howto-use-commands/long-running-start.png" alt-text="Screenshot that shows immediate response from device":::
-
 The following screenshot shows the IoT Central UI when it receives the property update that indicates the command is complete:
 
 :::image type="content" source="media/howto-use-commands/long-running-finish.png" alt-text="Screenshot that shows long-running command finished":::

articles/iot-central/core/howto-use-properties.md

@@ -220,11 +220,7 @@ For more information on device twins, see [Configure your devices from a back-en
 
 When the operator sets a writable property in the Azure IoT Central application, the application uses a device twin desired property to send the value to the device. The device then responds by using a device twin reported property. When Azure IoT Central receives the reported property value, it updates the property view with a status of **Accepted**.
 
-The following view shows the writable properties. When you enter the value and select **Save**, the initial status is **Pending**. When the device accepts the change, the status changes to **Accepted**.
-
-:::image type="content" source="media/howto-use-properties/status-pending.png" alt-text="Screenshot that shows Pending status for a property update.":::
-
-:::image type="content" source="media/howto-use-properties/accepted.png" alt-text="Screenshot that shows Accepted property for a completed update.":::
+When you enter the value and select **Save**, the initial status is **Pending**. When the device accepts the change, the status changes to **Accepted**.
 
 ## Use properties on unassigned devices