Skip to content

Commit 419c7a9

Browse files
authored
Merge pull request #196582 from dominicbetts/central-export-vnet
IoT Central add secure VNet details
2 parents 1fa5fd8 + abe4e40 commit 419c7a9

File tree

7 files changed

+74
-16
lines changed

7 files changed

+74
-16
lines changed

articles/iot-central/TOC.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -233,8 +233,10 @@
233233
href: core/howto-manage-iot-central-from-cli.md
234234
- name: Manage from CSP portal
235235
href: core/howto-create-and-manage-applications-csp.md
236-
- name: Create a private endpoint
236+
- name: Create a private endpoint for devices
237237
href: core/howto-create-private-endpoint.md
238+
- name: Export to a secure VNET
239+
href: core/howto-connect-secure-vnet.md
238240
- name: Reference
239241
items:
240242
- name: Azure CLI
Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
---
2+
title: Export IoT Central data to a secure VNet | Microsoft Docs
3+
description: Learn how to use IoT Central data export to send data to a destination in a secure VNet. Data export destinations include Azure Blob Storage, Azure Event Hubs, and Azure Service Bus Messaging.
4+
author: dominicbetts
5+
ms.author: dobett
6+
ms.date: 04/25/2022
7+
ms.topic: how-to
8+
ms.service: iot-central
9+
services: iot-central
10+
11+
# Administrator
12+
---
13+
14+
# Export data to a secure destination on an Azure Virtual Network
15+
16+
Data export in IoT Central lets you continuously stream device data to destinations such as Azure Blob Storage, Azure Event Hubs, Azure Service Bus Messaging. You may choose to lock down these destinations by using an Azure Virtual Network (VNet) and private endpoints.
17+
18+
Currently, it's not possible to connect an IoT Central application directly to VNet for data export. However, because IoT Central is a trusted Azure service, it's possible to configure an exception to the firewall rules and connect to a secure destination on a VNet. In this scenario, you typically use a managed identity to authenticate and authorize with the destination.
19+
20+
## Prerequisites
21+
22+
- An IoT Central application. To learn more, see [Create an IoT Central application](howto-create-iot-central-application.md).
23+
24+
- 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).
25+
26+
## Configure the destination service
27+
28+
To configure Azure Blob Storage to use a VNet and private endpoint see:
29+
30+
- [Configure Azure Storage firewalls and virtual networks](../../storage/common/storage-network-security.md?toc=%2Fazure%2Fstorage%2Fblobs%2Ftoc.json)
31+
- [Private endpoints for your storage account](../../storage/common/storage-private-endpoints.md)
32+
33+
To configure Azure Event Hubs to use a VNet and private endpoint see:
34+
35+
- [Allow access to Azure Event Hubs namespaces from specific virtual networks](../../event-hubs/event-hubs-service-endpoints.md)
36+
- [Allow access to Azure Event Hubs namespaces via private endpoints](../../event-hubs/private-link-service.md)
37+
38+
To configure Azure Service Bus Messaging to use a VNet and private endpoint see:
39+
40+
- [Allow access to Azure Service Bus namespace from specific virtual networks](../../service-bus-messaging/service-bus-service-endpoints.md)
41+
- [Allow access to Azure Service Bus namespaces via private endpoints](../../service-bus-messaging/private-link-service.md)
42+
43+
## Configure the firewall exception
44+
45+
To allow IoT Central to connect to a destination on a VNet, enable a firewall exception on the VNet to allow connections from trusted Azure services.
46+
47+
To configure the exception in the Azure portal for Azure Blob Storage, navigate to **Networking > Firewalls and virtual networks**. Then select **Allow Azure services on the trusted services list to access this storage account.**:
48+
49+
:::image type="content" source="media/howto-connect-secure-vnet/blob-storage-exception.png" alt-text="Screenshot from Azure portal that shows firewall exception for Azure Blob Storage virtual network.":::
50+
51+
To configure the exception in the Azure portal for Azure Event Hubs, navigate to **Networking > Public access**. Then select **Yes** to allow trusted Microsoft services to bypass this firewall:
52+
53+
:::image type="content" source="media/howto-connect-secure-vnet/event-hubs-exception.png" alt-text="Screenshot from Azure portal that shows firewall exception for Azure Event Hubs virtual network.":::
54+
55+
To configure the exception in the Azure portal for Azure Service Bus, navigate to **Networking > Public access**. Then select **Yes** to allow trusted Microsoft services to bypass this firewall:
56+
57+
:::image type="content" source="media/howto-connect-secure-vnet/service-bus-queue-exception.png" alt-text="Screenshot from Azure portal that shows firewall exception for Azure Service Bus virtual network.":::
58+
59+
## Next steps
60+
61+
Now that you've learned how to export data to a destination locked down on a VNet, here's the suggested next step:
62+
63+
> [!div class="nextstepaction"]
64+
> [Administer your application](howto-administer.md).

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

Lines changed: 3 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -328,11 +328,7 @@ To configure the permissions:
328328
329329
1. Select **Save**. The managed identity for your IoT Central application is now configured.
330330
331-
To further secure your event hub and only allow access from trusted services with managed identities, see:
332-
333-
- [Allow access to Azure Event Hubs namespaces using private endpoints](../../event-hubs/private-link-service.md)
334-
- [Trusted Microsoft services](../../event-hubs/private-link-service.md#trusted-microsoft-services)
335-
- [Allow access to Azure Event Hubs namespaces from specific virtual networks](../../event-hubs/event-hubs-service-endpoints.md)
331+
To further secure your event hub and only allow access from trusted services with managed identities, see [Export data to a secure destination on an Azure Virtual Network](howto-connect-secure-vnet.md).
336332
337333
To create the Event Hubs destination in IoT Central on the **Data export** page:
338334
@@ -403,11 +399,7 @@ To configure the permissions:
403399
404400
1. Select **Save**. The managed identity for your IoT Central application is now configured.
405401
406-
To further secure your queue or topic and only allow access from trusted services with managed identities, see:
407-
408-
- [Allow access to Azure Service Bus namespaces using private endpoints](../../service-bus-messaging/private-link-service.md)
409-
- [Trusted Microsoft services](../../service-bus-messaging/private-link-service.md#trusted-microsoft-services)
410-
- [Allow access to Azure Service Bus namespace from specific virtual networks](../../service-bus-messaging/service-bus-service-endpoints.md)
402+
To further secure your queue or topic and only allow access from trusted services with managed identities, see [Export data to a secure destination on an Azure Virtual Network](howto-connect-secure-vnet.md).
411403
412404
To create the Service Bus destination in IoT Central on the **Data export** page:
413405
@@ -482,11 +474,7 @@ To configure the permissions:
482474
> [!TIP]
483475
> This role assignment isn't visible in the list on the **Azure role assignments** page.
484476
485-
To further secure your blob container and only allow access from trusted services with managed identities, see:
486-
487-
- [Use private endpoints for Azure Storage](../../storage/common/storage-private-endpoints.md)
488-
- [Authorize access to blob data with managed identities for Azure resources](../../storage/blobs/authorize-managed-identity.md)
489-
- [Configure Azure Storage firewalls and virtual networks](../../storage/common/storage-network-security.md?toc=%2Fazure%2Fstorage%2Fblobs%2Ftoc.json)
477+
To further secure your blob container and only allow access from trusted services with managed identities, see [Export data to a secure destination on an Azure Virtual Network](howto-connect-secure-vnet.md).
490478
491479
To create the Blob Storage destination in IoT Central on the **Data export** page:
492480
96.1 KB
Loading
86.9 KB
Loading
78.6 KB
Loading

articles/iot-central/core/overview-iot-central-security.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -86,6 +86,10 @@ To learn more, see:
8686
- [Configure a managed identity in the Azure portal](howto-manage-iot-central-from-portal.md#configure-a-managed-identity)
8787
- [Configure a managed identity using the Azure CLI](howto-manage-iot-central-from-cli.md#configure-a-managed-identity)
8888

89+
## Connect to a destination on a secure virtual network
90+
91+
Data export in IoT Central lets you continuously stream device data to destinations such as Azure Blob Storage, Azure Event Hubs, Azure Service Bus Messaging. You may choose to lock down these destinations by using an Azure Virtual Network (VNet) and private endpoints. To enable IoT Central to connect to a destination on a secure VNet, configure a firewall exception. To learn more, see [Export data to a secure destination on an Azure Virtual Network](howto-connect-secure-vnet.md).
92+
8993
## Next steps
9094

9195
Now that you've learned about security in your Azure IoT Central application, the suggested next step is to learn about [Manage users and roles](howto-manage-users-roles.md) in Azure IoT Central.

0 commit comments

Comments
 (0)