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

Author: halkazwini

articles/healthcare-apis/fhir/convert-data-azure-data-factory.md

@@ -11,8 +11,6 @@ ms.author: kesheth
 
 # Transform HL7v2 data to FHIR R4 with $convert-data and Azure Data Factory
 
-[!INCLUDE [Converter redirect statement](../includes/converter-redirect-statement.md)]
-
 In this article, we detail how to use [Azure Data Factory (ADF)](../../data-factory/introduction.md) with the `$convert-data` operation to transform [HL7v2](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=185) data to [FHIR® R4](https://www.hl7.org/fhir/R4/). The transformed results are then persisted within an [Azure storage account](../../storage/common/storage-account-overview.md) with [Azure Data Lake Storage (ADLS) Gen2](../../storage/blobs/data-lake-storage-introduction.md) capabilities.
 
 ## Prerequisites

articles/healthcare-apis/fhir/convert-data-configuration.md

@@ -11,8 +11,6 @@ ms.author: kesheth
 
 # Configure settings for $convert-data by using the Azure portal
 
-[!INCLUDE [Converter redirect statement](../includes/converter-redirect-statement.md)]
-
 This article illustrates how to configure settings for `$convert-data` using the Azure portal to convert health data into [FHIR® R4](https://www.hl7.org/fhir/R4/index.html).
 
 ## Default templates

articles/healthcare-apis/fhir/convert-data-overview.md

@@ -12,8 +12,6 @@ ms.author: kesheth
 
 # $convert-data in the FHIR service
 
-[!INCLUDE [Converter redirect statement](../includes/converter-redirect-statement.md)]
-
 The `$convert-data` operation in the FHIR® service enables you to convert health data from various formats into [FHIR R4](https://www.hl7.org/fhir/R4/index.html) data. The `$convert-data` operation uses [Liquid](https://shopify.github.io/liquid/) templates from the [FHIR Converter](https://github.com/microsoft/FHIR-Converter) project for FHIR data conversion. You can customize these conversion templates as needed. 
 
 The `$convert-data` operation supports four types of data conversion: 

articles/healthcare-apis/fhir/convert-data-troubleshoot.md

@@ -11,8 +11,6 @@ ms.author: kesheth
 
 # Troubleshoot $convert-data
 
-[!INCLUDE [Converter redirect statement](../includes/converter-redirect-statement.md)]
-
 In this article, learn how to troubleshoot `$convert-data`.
 
 ## Performance

articles/iot-operations/discover-manage-assets/howto-manage-assets-devices.md

@@ -65,101 +65,6 @@ After you select your instance, the operations experience displays the **Overvie
 
 :::image type="content" source="media/howto-manage-assets-devices/instance-overview.png" alt-text="Screenshot that shows the overview page for an instance in the operations experience." lightbox="media/howto-manage-assets-devices/instance-overview.png":::
 
-## Import and export devices
-
-Use the **Import** and **Export** buttons to import or export a device in the operations experience:
-
-:::image type="content" source="media/howto-manage-assets-devices/export-import-devices.png" alt-text="Screenshot showing the options to import and export a device." lightbox="media/howto-manage-assets-devices/export-import-devices.png":::
-
-The JSON file that you export contains the device definition. You can use this file to import the device into another instance of Azure IoT Operations or modify it to create a new device in the current instance:
-
-```yml
-{
-  "name": "<your device name>",
-  "type": "microsoft.deviceregistry/assetendpointprofiles",
-  "location": "<your location>",
-  "extendedLocation": {
-    "type": "CustomLocation",
-    "name": "/subscriptions/<your subscription id>/resourceGroups/<your resource group>/providers/Microsoft.ExtendedLocation/customLocations/<your custom location>"
-  },
-  "properties": {
-    "targetAddress": "<your target address>",
-    "endpointProfileType": "Microsoft.OpcUa",
-    "additionalConfiguration": "{\"runAssetDiscovery\":true}",
-    "authentication": {
-      "method": "Anonymous"
-    }
-  },
-  "apiVersion": "2024-11-01"
-}
-```
-
-> [!TIP]
-> Export an existing device to discover the `extendedLocation Name` value.
-
-> [!TIP]
-> You can also use the `az iot ops device show` and `az iot ops device create` commands to view and create devices.
-
-## Import and export assets
-
-Use the **Import** and **Export** buttons to import or export an asset in the operations experience:
-
-:::image type="content" source="media/howto-manage-assets-devices/export-import-assets.png" alt-text="Screenshot showing the options to import and export an asset." lightbox="media/howto-manage-assets-devices/export-import-assets.png":::
-
-The JSON file that you export contains the asset definition. You can use this file to import the asset into another instance of Azure IoT Operations or modify it to create a new asset in the current instance. The following JSON example shows an example import file to use to create a thermostat asset:
-
-```yml
-{
-  "name": "thermostat",
-  "type": "microsoft.deviceregistry/assets",
-  "location": "<your location>",
-  "extendedLocation": {
-    "type": "CustomLocation",
-    "name": "/subscriptions/<your subscription id>/resourceGroups/<your resource group>/providers/Microsoft.ExtendedLocation/customLocations/<your custom location>"
-  },
-  "properties": {
-    "enabled": true,
-    "displayName": "thermostat",
-    "description": "A simulated thermostat asset",
-    "assetEndpointProfileRef": "opc-ua-connector-1",
-    "version": 1,
-    "attributes": {
-      "batch": "102",
-      "customer": "Contoso",
-      "equipment": "Boiler",
-      "isSpare": "true",
-      "location": "Seattle"
-    },
-    "defaultDatasetsConfiguration": "{\"publishingInterval\":1000,\"samplingInterval\":1000,\"queueSize\":1}",
-    "defaultEventsConfiguration": "{\"publishingInterval\":1000,\"queueSize\":1}",
-    "defaultTopic": {
-      "path": "azure-iot-operations/data/thermostat",
-      "retain": "Never"
-    },
-    "datasets": [
-      {
-        "name": "default",
-        "dataPoints": [
-          {
-            "name": "temperature",
-            "dataSource": "ns=3;s=SpikeData",
-            "observabilityMode": "None",
-            "dataPointConfiguration": "{}"
-          }
-        ]
-      }
-    ]
-  },
-  "apiVersion": "2024-11-01"
-}
-```
-
-> [!TIP]
-> Export an existing device to discover the `extendedLocation Name` value.
-
-> [!TIP]
-> You can also use the `az iot ops asset show` and `az iot ops asset create` commands to view and create devices.
-
 ## Notifications
 
 Whenever you make a change to a resource in the operations experience, you see a notification that reports the status of the operation: