Skip to content

Commit a4ce880

Browse files
committed
Remove import export
1 parent 1643f44 commit a4ce880

File tree

3 files changed

+0
-95
lines changed

3 files changed

+0
-95
lines changed

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

Lines changed: 0 additions & 95 deletions
Original file line numberDiff line numberDiff line change
@@ -65,101 +65,6 @@ After you select your instance, the operations experience displays the **Overvie
6565

6666
:::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":::
6767

68-
## Import and export devices
69-
70-
Use the **Import** and **Export** buttons to import or export a device in the operations experience:
71-
72-
:::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":::
73-
74-
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:
75-
76-
```yml
77-
{
78-
"name": "<your device name>",
79-
"type": "microsoft.deviceregistry/assetendpointprofiles",
80-
"location": "<your location>",
81-
"extendedLocation": {
82-
"type": "CustomLocation",
83-
"name": "/subscriptions/<your subscription id>/resourceGroups/<your resource group>/providers/Microsoft.ExtendedLocation/customLocations/<your custom location>"
84-
},
85-
"properties": {
86-
"targetAddress": "<your target address>",
87-
"endpointProfileType": "Microsoft.OpcUa",
88-
"additionalConfiguration": "{\"runAssetDiscovery\":true}",
89-
"authentication": {
90-
"method": "Anonymous"
91-
}
92-
},
93-
"apiVersion": "2024-11-01"
94-
}
95-
```
96-
97-
> [!TIP]
98-
> Export an existing device to discover the `extendedLocation Name` value.
99-
100-
> [!TIP]
101-
> You can also use the `az iot ops device show` and `az iot ops device create` commands to view and create devices.
102-
103-
## Import and export assets
104-
105-
Use the **Import** and **Export** buttons to import or export an asset in the operations experience:
106-
107-
:::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":::
108-
109-
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:
110-
111-
```yml
112-
{
113-
"name": "thermostat",
114-
"type": "microsoft.deviceregistry/assets",
115-
"location": "<your location>",
116-
"extendedLocation": {
117-
"type": "CustomLocation",
118-
"name": "/subscriptions/<your subscription id>/resourceGroups/<your resource group>/providers/Microsoft.ExtendedLocation/customLocations/<your custom location>"
119-
},
120-
"properties": {
121-
"enabled": true,
122-
"displayName": "thermostat",
123-
"description": "A simulated thermostat asset",
124-
"assetEndpointProfileRef": "opc-ua-connector-1",
125-
"version": 1,
126-
"attributes": {
127-
"batch": "102",
128-
"customer": "Contoso",
129-
"equipment": "Boiler",
130-
"isSpare": "true",
131-
"location": "Seattle"
132-
},
133-
"defaultDatasetsConfiguration": "{\"publishingInterval\":1000,\"samplingInterval\":1000,\"queueSize\":1}",
134-
"defaultEventsConfiguration": "{\"publishingInterval\":1000,\"queueSize\":1}",
135-
"defaultTopic": {
136-
"path": "azure-iot-operations/data/thermostat",
137-
"retain": "Never"
138-
},
139-
"datasets": [
140-
{
141-
"name": "default",
142-
"dataPoints": [
143-
{
144-
"name": "temperature",
145-
"dataSource": "ns=3;s=SpikeData",
146-
"observabilityMode": "None",
147-
"dataPointConfiguration": "{}"
148-
}
149-
]
150-
}
151-
]
152-
},
153-
"apiVersion": "2024-11-01"
154-
}
155-
```
156-
157-
> [!TIP]
158-
> Export an existing device to discover the `extendedLocation Name` value.
159-
160-
> [!TIP]
161-
> You can also use the `az iot ops asset show` and `az iot ops asset create` commands to view and create devices.
162-
16368
## Notifications
16469

16570
Whenever you make a change to a resource in the operations experience, you see a notification that reports the status of the operation:

0 commit comments

Comments
 (0)