Combine troubleshooting guides

dominicbetts · dominicbetts · commit a2a75e075b86 · 2024-02-06T14:35:00.000Z
diff --git a/articles/iot-central/.openpublishing.redirection.iot-central.json b/articles/iot-central/.openpublishing.redirection.iot-central.json
@@ -1379,6 +1379,16 @@
       "source_path_from_root": "/articles/iot-central/core/howto-connect-eflow.md",
       "redirect_url": "/azure/iot-edge/iot-edge-for-linux-on-windows/",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/iot-central/core/troubleshoot-data-export.md",
+      "redirect_url": "/azure/iot-central/core/troubleshooting/",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/iot-central/core/troubleshoot-connection.md",
+      "redirect_url": "/azure/iot-central/core/troubleshooting/",
+      "redirect_document_id": true
     }
   ]
 }
diff --git a/articles/iot-central/TOC.yml b/articles/iot-central/TOC.yml
@@ -132,8 +132,6 @@
           href: core/howto-manage-deployment-manifests.md
         - name: Connect devices through an IoT Edge transparent gateway
           href: core/how-to-connect-iot-edge-transparent-gateway.md
-        - name: Prepare and connect an IoT Edge for Linux on Windows device 
-          href: core/howto-connect-eflow.md
         - name: Prepare and connect an Azure Sphere DevKit
           href: /azure-sphere/app-development/setup-iot-central
         - name: Prepare and connect a RuuviTag device
@@ -142,8 +140,6 @@
           href: core/howto-connect-rigado-cascade-500.md
         - name: Monitor device connectivity using Azure CLI
           href: core/howto-monitor-devices-azure-cli.md
-        - name: Troubleshoot device connections
-          href: core/troubleshoot-connection.md
     - name: View and analyze device data
       items:
         - name: Build analytics queries
@@ -166,8 +162,6 @@
       items:
         - name: Configure rules
           href: core/howto-configure-rules.md
-        - name: Create custom rules
-          href: core/howto-create-custom-rules.md
         - name: Use rules and workflows to integrate with other services
           href: core/howto-configure-rules-advanced.md
         - name: Export data to cloud destinations
@@ -184,8 +178,6 @@
               href: core/howto-export-to-webhook.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
@@ -251,6 +243,8 @@
           href: core/howto-create-private-endpoint.md
         - name: Export to a secure VNET
           href: core/howto-connect-secure-vnet.md
+    - name: Troubleshooting
+      href: core/troubleshooting.md
 - name: Reference
   items:
   - name: Azure CLI
diff --git a/articles/iot-central/core/concepts-device-implementation.md b/articles/iot-central/core/concepts-device-implementation.md
@@ -126,7 +126,7 @@ If the device gets any of the following errors when it connects, it should use a
 - Operator blocked device.
 - Internal error 500 from the service.
 
-To learn more about device error codes, see [Troubleshooting device connections](troubleshoot-connection.md).
+To learn more about device error codes, see [Troubleshooting device connections](troubleshooting.md).
 
 To learn more about implementing automatic reconnections, see [Manage device reconnections to create resilient applications](../../iot-develop/concepts-manage-device-reconnections.md).
 
diff --git a/articles/iot-central/core/howto-export-to-azure-data-explorer.md b/articles/iot-central/core/howto-export-to-azure-data-explorer.md
@@ -178,7 +178,7 @@ To create the Azure Data Explorer destination in IoT Central on the **Data expor
 
     :::image type="content" source="media/howto-export-data/export-destination-managed.png" alt-text="Screenshot of Azure Data Explorer export destination that uses a managed identity.":::
 
-If you don't see data arriving in your destination service, see [Troubleshoot issues with data exports from your Azure IoT Central application](troubleshoot-data-export.md).
+If you don't see data arriving in your destination service, see [Troubleshoot issues with data exports from your Azure IoT Central application](troubleshooting.md).
 
 ---
 
diff --git a/articles/iot-central/core/howto-export-to-blob-storage.md b/articles/iot-central/core/howto-export-to-blob-storage.md
@@ -138,7 +138,7 @@ To create the Blob Storage destination in IoT Central on the **Data export** pag
 
 1. Select **Save**.
 
-If you don't see data arriving in your destination service, see [Troubleshoot issues with data exports from your Azure IoT Central application](troubleshoot-data-export.md).
+If you don't see data arriving in your destination service, see [Troubleshoot issues with data exports from your Azure IoT Central application](troubleshooting.md).
 
 ---
 
diff --git a/articles/iot-central/core/howto-export-to-event-hubs.md b/articles/iot-central/core/howto-export-to-event-hubs.md
@@ -112,7 +112,7 @@ To create the Event Hubs destination in IoT Central on the **Data export** page:
 
 1. Select **Save**.
 
-If you don't see data arriving in your destination service, see [Troubleshoot issues with data exports from your Azure IoT Central application](troubleshoot-data-export.md).
+If you don't see data arriving in your destination service, see [Troubleshoot issues with data exports from your Azure IoT Central application](troubleshooting.md).
 
 ---
 
diff --git a/articles/iot-central/core/howto-export-to-service-bus.md b/articles/iot-central/core/howto-export-to-service-bus.md
@@ -116,7 +116,7 @@ To create the Service Bus destination in IoT Central on the **Data export** page
 
 1. Select **Save**.
 
-If you don't see data arriving in your destination service, see [Troubleshoot issues with data exports from your Azure IoT Central application](troubleshoot-data-export.md).
+If you don't see data arriving in your destination service, see [Troubleshoot issues with data exports from your Azure IoT Central application](troubleshooting.md).
 
 ---
 
diff --git a/articles/iot-central/core/howto-faq.yml b/articles/iot-central/core/howto-faq.yml
@@ -107,7 +107,7 @@ sections:
       - question: |
           How do I check for credential issues if a device isn't connecting to my IoT Central application?
         answer: |
-          The [Troubleshoot why data from your devices isn't showing up in Azure IoT Central](troubleshoot-connection.md) includes steps to diagnose connectivity issues for devices.
+          The [Troubleshoot why data from your devices isn't showing up in Azure IoT Central](troubleshooting.md) includes steps to diagnose connectivity issues for devices.
 
       - question: |
           How do I unblock a device?
diff --git a/articles/iot-central/core/howto-monitor-devices-azure-cli.md b/articles/iot-central/core/howto-monitor-devices-azure-cli.md
@@ -85,4 +85,4 @@ az iot central device twin show --app-id <app-id> --device-id <device-id>
 
 ## Next steps
 
-A suggested next step is to learn [Troubleshoot why data from your devices isn't showing up in Azure IoT Central](troubleshoot-connection.md).
+A suggested next step is to learn [Troubleshoot why data from your devices isn't showing up in Azure IoT Central](troubleshooting.md).
diff --git a/articles/iot-central/core/media/troubleshooting/export-error.png b/articles/iot-central/core/media/troubleshooting/export-error.png
diff --git a/articles/iot-central/core/media/troubleshooting/raw-data-view.png b/articles/iot-central/core/media/troubleshooting/raw-data-view.png
diff --git a/articles/iot-central/core/overview-iot-central-operator.md b/articles/iot-central/core/overview-iot-central-operator.md
@@ -104,7 +104,7 @@ To automate device management tasks, you can use:
 
 ## Troubleshoot and remediate device issues
 
-The [troubleshooting guide](troubleshoot-connection.md) helps you to diagnose and remediate common issues. You can use the **Devices** page to block devices that appear to be malfunctioning until the problem is resolved.
+The [troubleshooting guide](troubleshooting.md) helps you to diagnose and remediate common issues. You can use the **Devices** page to block devices that appear to be malfunctioning until the problem is resolved.
 
 ## Next steps
 
diff --git a/articles/iot-central/core/overview-iot-central-solution-builder.md b/articles/iot-central/core/overview-iot-central-solution-builder.md
@@ -125,7 +125,6 @@ You can use the data export and rules capabilities in IoT Central to integrate w
 - [Export IoT data to cloud destinations using Blob Storage](howto-export-to-blob-storage.md).
 - [Transform data for IoT Central](howto-transform-data.md)
 - [Use workflows to integrate your Azure IoT Central application with other cloud services](howto-configure-rules-advanced.md)
-- [Extend Azure IoT Central with custom rules using Stream Analytics, Azure Functions, and SendGrid](howto-create-custom-rules.md)
 - [Extend Azure IoT Central with custom analytics using Azure Databricks](howto-create-custom-analytics.md)
 
 ## Integrate with companion applications
diff --git a/articles/iot-central/core/troubleshoot-data-export.md b/articles/iot-central/core/troubleshoot-data-export.md
diff --git a/articles/iot-central/core/troubleshooting.md b/articles/iot-central/core/troubleshooting.md
@@ -1,30 +1,20 @@
 ---
-title: Troubleshoot device connections to Azure IoT Central
-description: Troubleshoot and resolve why you're not seeing data from your devices in your IoT Central application
+title: Troubleshooting in Azure IoT Central
+description: Troubleshoot and resolve issues with device connections and data export configurations in your IoT Central application
 services: iot-central
 author: dominicbetts
 ms.author: dobett
-ms.date: 05/22/2023
+ms.date: 02/06/2024
 ms.topic: troubleshooting
 ms.service: iot-central
 ms.custom: device-developer, devx-track-azurecli
 
 #Customer intent: As a device developer, I want to understand why data from my devices isn't showing up in IoT Central, and the steps I can take to rectify the issue.
 ---
 
-# Troubleshoot why data from your devices isn't showing up in Azure IoT Central
+# Troubleshooting in Azure IoT Central
 
-This document helps you determine why the data your devices are sending to IoT Central isn't showing up in the application.
-
-There are two main areas to investigate:
-
-- Device connectivity issues
-  - Authentication issues such as the device has invalid credentials
-  - Network connectivity issues
-  - Device isn't approved, or blocked
-- Device payload shape issues
-
-This troubleshooting guide focuses on device connectivity issues and device payload shape issues.
+This article includes troubleshooting guidance for device connectivity issues and data export configuration issues in your IoT Central applications.
 
 ## Device connectivity issues
 
@@ -232,7 +222,7 @@ The validation commands also report an error if the same telemetry name is defin
 
 If you prefer to use a GUI, use the IoT Central **Raw data** view to see if something isn't being modeled.
 
-:::image type="content" source="media/troubleshoot-connection/raw-data-view.png" alt-text="Screenshot of Raw Data view" lightbox="media/troubleshoot-connection/raw-data-view.png":::
+:::image type="content" source="media/troubleshooting/raw-data-view.png" alt-text="Screenshot that shows the raw data view in an IoT Central application." lightbox="media/troubleshooting/raw-data-view.png":::
 
 When you've detected the issue, you may need to update device firmware, or create a new device template that models previously unmodeled data.
 
@@ -248,6 +238,42 @@ You can't use the validate commands or the **Raw data** view in the UI to detect
 
 To display telemetry from components hosted in IoT Edge modules correctly, use [IoT Edge version 1.2.4](https://github.com/Azure/azure-iotedge/releases/tag/1.2.4) or later. If you use an earlier version, telemetry from components in IoT Edge modules displays as *_unmodeleddata*.
 
+## Data export managed identity issues
+
+You're using a managed identity to authorize the connection to an export destination. Data isn't arriving at the export destination.
+
+Before you configure or enable the export destination, make sure that you complete the following steps:
+
+- Enable the managed identity for the IoT Central application. To verify that the managed identity is enabled, go to the **Identity** page for your application in the Azure portal or use the following CLI command:
+
+    ```azurecli
+    az iot central app identity show --name {your app name} --resource-group {your resource group name}
+    ```
+
+- Configure the permissions for the managed identity. To view the assigned permissions, select **Azure role assignments** on the **Identity** page for your app in the Azure portal or use the `az role assignment list` CLI command. The required permissions are:
+
+    | Destination | Permission |
+    |-------------|------------|
+    | Azure Blob storage | Storage Blob Data Contributor |
+    | Azure Service Bus | Azure Service Bus Data Sender |
+    | Azure Event Hubs | Azure Event Hubs Data Sender |
+    | Azure Data Explorer | Admin |
+
+    If the permissions were not set correctly before you created the destination in your IoT Central application, try removing the destination and then adding it again.
+
+- Configure any virtual networks, private endpoints, and firewall policies.
+
+> [!NOTE]
+> If you're using a managed identity to authorize the connection to an export destination, IoT Central doesn't export data from simulated devices.
+
+To learn more, see [Export data](howto-export-data.md?tabs=managed-identity).
+
+## Data export destination connection issues
+
+The export definition page shows information about failed connections to the export destination:
+
+:::image type="content" source="media/troubleshooting/export-error.png" alt-text="Screenshot that shows an example export error.":::
+
 ## Next steps
 
 If you need more help, you can contact the Azure experts on the [Microsoft Q&A and Stack Overflow forums](https://azure.microsoft.com/support/community/). Alternatively, you can file an [Azure support ticket](https://portal.azure.com/#create/Microsoft.Support).

Original file line number	Diff line number	Diff line change
`@@ -1379,6 +1379,16 @@`
`1379`	`1379`	`"source_path_from_root": "/articles/iot-central/core/howto-connect-eflow.md",`
`1380`	`1380`	`"redirect_url": "/azure/iot-edge/iot-edge-for-linux-on-windows/",`
`1381`	`1381`	`"redirect_document_id": false`
	`1382`	`+ },`
	`1383`	`+ {`
	`1384`	`+ "source_path_from_root": "/articles/iot-central/core/troubleshoot-data-export.md",`
	`1385`	`+ "redirect_url": "/azure/iot-central/core/troubleshooting/",`
	`1386`	`+ "redirect_document_id": false`
	`1387`	`+ },`
	`1388`	`+ {`
	`1389`	`+ "source_path_from_root": "/articles/iot-central/core/troubleshoot-connection.md",`
	`1390`	`+ "redirect_url": "/azure/iot-central/core/troubleshooting/",`
	`1391`	`+ "redirect_document_id": true`
`1382`	`1392`	`}`
`1383`	`1393`	`]`
`1384`	`1394`	`}`
Original file line number	Diff line number	Diff line change
`@@ -85,4 +85,4 @@ az iot central device twin show --app-id <app-id> --device-id <device-id>`
`85`	`85`
`86`	`86`	`## Next steps`
`87`	`87`
`88`		`-A suggested next step is to learn [Troubleshoot why data from your devices isn't showing up in Azure IoT Central](troubleshoot-connection.md).`
	`88`	`+A suggested next step is to learn [Troubleshoot why data from your devices isn't showing up in Azure IoT Central](troubleshooting.md).`