Merge pull request #196957 from v-krishnag/dataref

Dataref

Author: v-regandowner

articles/iot-central/.openpublishing.redirection.iot-central.json

@@ -150,6 +150,11 @@
       "redirect_url": "/azure/iot-central/core/overview-iot-central-admin#create-applications",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/iot-central/core/howto-export-data.md",
+      "redirect_url": "/articles/iot-central/core/howto-export-to-blob-storage",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/iot-central/concepts-architecture.md",
       "redirect_url": "/azure/iot-central/core/concepts-architecture/",

articles/iot-central/TOC.yml

@@ -174,17 +174,27 @@
         - name: Use rules and workflows to integrate with other services
           href: core/howto-configure-rules-advanced.md
         - name: Export data to cloud destinations
-          href: core/howto-export-data.md
-        - name: Export data to cloud destinations (legacy)
-          href: core/howto-export-data-legacy.md
-        - name: Troubleshoot data export
-          href: core/troubleshoot-data-export.md
+          items:
+            - name: Export to Blob Storage
+              href: core/howto-export-to-blob-storage.md
+            - name: Export to Service Bus
+              href: core/howto-export-to-service-bus.md
+            - name: Export to Event Hubs
+              href: core/howto-export-to-event-hubs.md
+            - name: Export to Azure Data Explorer
+              href: core/howto-export-to-azure-data-explorer.md
+            - name: Export to a webhook
+              href: core/howto-export-to-webhook.md
+            - name: Export data to cloud destinations (legacy)
+              href: core/howto-export-data-legacy.md           
+            - name: Transform data internally for export
+              href: core/howto-transform-data-internally.md
+            - name: Troubleshoot data export
+              href: core/troubleshoot-data-export.md
         - name: Export data and visualize with Databricks
           href: core/howto-create-custom-analytics.md
         - name: Transform data internally on ingress
           href: core/howto-map-data.md
-        - name: Transform data internally for export
-          href: core/howto-transform-data-internally.md
         - name: Transform data externally
           href: core/howto-transform-data.md
         - name: Connect other clouds with device bridge

articles/iot-central/core/concepts-architecture.md

@@ -85,7 +85,8 @@ Reasons to export data include:
 
 ### Storage and analysis
 
-For long-term storage and control over archiving and retention policies, you can [continuously export your data](howto-export-data.md) to other storage destinations. Use of separate storage also lets you use other analytics tools to derive insights and view the data in your solution.
+For long-term storage and control over archiving and retention policies, you can [continuously export your data](howto-export-to-blob-storage.md).
+ to other storage destinations. Use of separate storage also lets you use other analytics tools to derive insights and view the data in your solution.
 
 ### Business automation
 

articles/iot-central/core/concepts-telemetry-properties-commands.md

@@ -27,7 +27,7 @@ The article doesn't describe every possible type of telemetry, property, and com
 Each example shows a snippet from the device model that defines the type and example JSON payloads to illustrate how the device should interact with the IoT Central application.
 
 > [!NOTE]
-> IoT Central accepts any valid JSON but it can only be used for visualizations if it matches a definition in the device model. You can export data that doesn't match a definition, see [Export IoT data to destinations in Azure](howto-export-data.md).
+> IoT Central accepts any valid JSON but it can only be used for visualizations if it matches a definition in the device model. You can export data that doesn't match a definition, see  [Export IoT data to cloud destinations using Blob Storage](howto-export-to-blob-storage.md).
 
 The JSON file that defines the device model uses the [Digital Twin Definition Language (DTDL) v2](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/dtdlv2.md).
 

articles/iot-central/core/howto-connect-secure-vnet.md

@@ -21,7 +21,7 @@ Currently, it's not possible to connect an IoT Central application directly to V
 
 - An IoT Central application. To learn more, see [Create an IoT Central application](howto-create-iot-central-application.md).
 
-- Data export configured in your IoT Central application to send device data to a destination such as Azure Blob Storage, Azure Event Hubs, or Azure Service Bus. The destination is configured to use a managed identity. To learn more, see [Export IoT data to cloud destinations using data export](howto-export-data.md).
+- Data export configured in your IoT Central application to send device data to a destination such as Azure Blob Storage, Azure Event Hubs, or Azure Service Bus. The destination is configured to use a managed identity. To learn more, see  [Export IoT data to cloud destinations using Blob Storage](howto-export-to-blob-storage.md).
 
 ## Configure the destination service
 

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

@@ -96,4 +96,4 @@ Select the ellipsis, for more chart controls:
 
 ## Next steps
 
-Now that you've learned how to visualize your data with the built-in analytics capabilities, a suggested next step is to learn how to [Export IoT data to cloud destinations using data export](howto-export-data.md).
+Now that you've learned how to visualize your data with the built-in analytics capabilities, a suggested next step is to learn how to [Export IoT data to cloud destinations using Blob Storage](howto-export-to-blob-storage.md).

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

@@ -14,7 +14,7 @@ ms.custom: contperf-fy22q2
 
 Organizations let you define a hierarchy that you use to manage which users can see which devices in your IoT Central application. The user's role determines their permissions over the devices they see, and the experiences they can access. Use organizations to implement a multi-tenanted application.
 
-Organizations is an optional feature that gives you more control over the [users and roles](howto-manage-users-roles.md) in your application.
+Organizations are an optional feature that gives you more control over the [users and roles](howto-manage-users-roles.md) in your application.
 
 Organizations are hierarchical:
 
@@ -59,7 +59,7 @@ When you create a new device in your application, assign it to an organization i
 
 To assign or reassign an existing device to an organization, select the device in the device list and then select **Organization**:
 
-:::image type="content" source="media/howto-create-organization/change-device-organization.png" alt-text="Screenshot that shows how change the organization a device is associated with." lightbox="media/howto-create-organization/change-device-organization.png":::
+:::image type="content" source="media/howto-create-organization/change-device-organization.png" alt-text="Screenshot that shows how to change the organization a device is associated with." lightbox="media/howto-create-organization/change-device-organization.png":::
 
 > [!TIP]
 > You can see which organization a device belongs to in the device list. Use the filter tool in the device list to show devices in a particular organization.
@@ -153,9 +153,10 @@ When you start adding organizations, all existing devices, users, and experience
 The following limits apply to organizations:
 
 - The hierarchy can be no more than five levels deep.
-- The total number of organization cannot be more than 200. Each node in the hierarchy counts as an organization.
+- The total number of organizations can't be more than 200. Each node in the hierarchy counts as an organization.
 
 
 ## Next steps
 
-Now that you've learned how to manage Azure IoT Central organizations, the suggested next step is learn how to [Export IoT data to cloud destinations using data export](howto-export-data.md).
+Now that you've learned how to manage Azure IoT Central organizations, the suggested next step is to learn how to  [Export IoT data to cloud destinations using Blob Storage](howto-export-to-blob-storage.md).
+

articles/iot-central/core/howto-export-data-legacy.md

@@ -10,7 +10,7 @@ ms.service: iot-central
 ---
 # Export IoT data to cloud destinations using data export (legacy)
 
-The legacy data export (classic) feature is now deprecated and you should plan to migrate to the new [data export feature](howto-export-data.md). The legacy data export lacks important capabilities such as the availability of different data types, filtering, and message transformation. See the following table for a comparison of legacy data export with new data export:
+The legacy data export (classic) feature is now deprecated and you should plan to migrate to the new [data export feature](howto-export-to-blob-storage.md). The legacy data export lacks important capabilities such as the availability of different data types, filtering, and message transformation. See the following table for a comparison of legacy data export with new data export:
 
 | Capability  | Legacy data export (classic) | New data export |
 | :------------- | :---------- | :----------- |
@@ -69,7 +69,7 @@ In the new data export, you can create a destination and reuse it across differe
 >
 > - Legacy data exports (classic) are scheduled to be retired. Migrate any legacy data exports to new exports
 > 
-> - For information about the latest data export features, see [Export IoT data to cloud destinations using data export](./howto-export-data.md).
+> - For information about the latest data export features, see  [Export IoT data to cloud destinations using Blob Storage](howto-export-to-blob-storage.md).
 
 
 This article describes how to use the data export feature in Azure IoT Central. This feature lets you export your data continuously to **Azure Event Hubs**, **Azure Service Bus**, or **Azure Blob storage** instances. Data export uses the JSON format and can include telemetry, device information, and device template information. Use the exported data for: