Skip to content

Commit b335d13

Browse files
committed
adding links to the portal
1 parent 4b4bfe0 commit b335d13

13 files changed

+36
-38
lines changed

articles/defender-for-iot/organizations/alerts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ For more information, see [Securing IoT devices in the enterprise](concept-enter
4545

4646
## Managing OT alerts in a hybrid environment
4747

48-
Users working in hybrid environments may be managing OT alerts in Defender for IoT on the Azure portal, the OT sensor, and an on-premises management console.
48+
Users working in hybrid environments may be managing OT alerts in [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, the OT sensor, and an on-premises management console.
4949

5050
Alert statuses are fully synchronized between the Azure portal and the OT sensor, and between the sensor and the on-premises management console. This means that regardless of where you manage the alert in Defender for IoT, the alert is updated in other locations as well.
5151

articles/defender-for-iot/organizations/concept-enterprise.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ While the number of IoT devices continues to grow, they often lack the security
1818
1919
## IoT security across Microsoft 365 Defender and Azure
2020

21-
Defender for IoT provides IoT security functionality across both the Microsoft 365 Defender and Azure portals using the following methods:
21+
Defender for IoT provides IoT security functionality across both the Microsoft 365 Defender and [Azure portals](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) using the following methods:
2222

2323
|Method |Description and requirements | Configure in ... |
2424
|---------|---------|---------|

articles/defender-for-iot/organizations/configure-sensor-settings-portal.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Define a new setting whenever you want to define a specific configuration for on
3737

3838
**To define a new setting**:
3939

40-
1. In Defender for IoT on the Azure portal, select **Sites and sensors** > **Sensor settings (Preview)**.
40+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select **Sites and sensors** > **Sensor settings (Preview)**.
4141

4242
1. On the **Sensor settings (Preview)** page, select **+ Add**, and then use the wizard to define the following values for your setting. Select **Next** when you're done with each tab in the wizard to move to the next step.
4343

@@ -62,7 +62,7 @@ Your new setting is now listed on the **Sensor settings (Preview)** page under i
6262

6363
**To view the current settings already defined for your subscription**:
6464

65-
1. In Defender for IoT on the Azure portal, select **Sites and sensors** > **Sensor settings (Preview)**
65+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select **Sites and sensors** > **Sensor settings (Preview)**
6666

6767
The **Sensor settings (Preview)** page shows any settings already defined for your subscriptions, listed by setting type. Expand or collapse each type to view detailed configurations. For example:
6868

articles/defender-for-iot/organizations/faqs-eiot.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Enterprise IoT is designed to help customers secure un-managed devices throughou
2929

3030
For more information, see [Onboard with Microsoft Defender for IoT](eiot-defender-for-endpoint.md).
3131

32-
- **In the Azure portal**: Defender for IoT customers can view their discovered IoT devices in the **Device inventory** page in Defender for IoT in the Azure portal. Register an Enterprise IoT network sensor, currently in **Public preview** to gain visibility to additional devices that aren't covered by Defender for Endpoint.
32+
- **In the Azure portal**: Defender for IoT customers can view their discovered IoT devices in the **Device inventory** page in [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) in the Azure portal. Register an Enterprise IoT network sensor, currently in **Public preview** to gain visibility to additional devices that aren't covered by Defender for Endpoint.
3333

3434
For more information, see [Enhance device discovery with an Enterprise IoT network sensor (Public preview)](eiot-sensor.md).
3535

@@ -82,7 +82,7 @@ To make any changes to an existing plan, you'll need to cancel your existing pla
8282

8383
To remove only Enterprise IoT from your plan, cancel your plan from Microsoft Defender for Endpoint. For more information, see [Cancel your Defender for IoT plan](/microsoft-365/security/defender-endpoint/enable-microsoft-defender-for-iot-integration#cancel-your-defender-for-iot-plan).
8484

85-
To cancel the plan and remove all Defender for IoT services from the associated subscription, cancel the plan in Defender for IoT in the Azure portal. For more information, see [Cancel your Enterprise IoT plan](manage-subscriptions-enterprise.md#cancel-your-enterprise-iot-plan).
85+
To cancel the plan and remove all Defender for IoT services from the associated subscription, cancel the plan in [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) in the Azure portal. For more information, see [Cancel your Enterprise IoT plan](manage-subscriptions-enterprise.md#cancel-your-enterprise-iot-plan).
8686

8787
## What happens when the 30-day trial ends?
8888

articles/defender-for-iot/organizations/getting-started.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ This procedure describes how to add a trial Defender for IoT plan for OT network
3737

3838
**To add your plan**:
3939

40-
1. In the Azure portal, go to **Defender for IoT** and select **Plans and pricing** > **Add plan**.
40+
1. In the Azure portal, go to [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) and select **Plans and pricing** > **Add plan**.
4141

4242
1. In the **Plan settings** pane, define the following settings:
4343

articles/defender-for-iot/organizations/how-to-manage-cloud-alerts.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ For more information, see [Azure user roles and permissions for Defender for IoT
3232

3333
## View alerts on the Azure portal
3434

35-
1. In Defender for IoT on the Azure portal, select the **Alerts** page on the left. By default, the following details are shown in the grid:
35+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select the **Alerts** page on the left. By default, the following details are shown in the grid:
3636

3737
| Column | Description
3838
|--|--|
@@ -93,7 +93,7 @@ Supported grouping options include *Engine*, *Name*, *Sensor*, *Severity*, and *
9393

9494
## Manage alert severity and status
9595

96-
We recommend that you update alert severity as soon as you've triaged an alert so that you can prioritize the riskiest alerts as soon as possible. Make sure to update your alert status once you've taken remediation steps so that the progress is recorded.
96+
We recommend that you update alert severity In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) in the Azure portal as soon as you've triaged an alert so that you can prioritize the riskiest alerts as soon as possible. Make sure to update your alert status once you've taken remediation steps so that the progress is recorded.
9797

9898
You can update both severity and status for a single alert or for a selection of alerts in bulk.
9999

@@ -136,7 +136,7 @@ Downloading the PCAP file can take several minutes, depending on the quality of
136136

137137
You may want to export a selection of alerts to a CSV file for offline sharing and reporting.
138138

139-
1. In Defender for IoT on the Azure portal, select the **Alerts** page on the left.
139+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select the **Alerts** page on the left.
140140

141141
1. Use the search box and filter options to show only the alerts you want to export.
142142

articles/defender-for-iot/organizations/how-to-manage-device-inventory-for-organizations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.topic: how-to
77

88
# Manage your device inventory from the Azure portal
99

10-
Use the **Device inventory** page in the Azure portal to manage all network devices detected by cloud-connected sensors, including OT, IoT, and IT. Identify new devices detected, devices that might need troubleshooting, and more.
10+
Use the **Device inventory** page in [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal to manage all network devices detected by cloud-connected sensors, including OT, IoT, and IT. Identify new devices detected, devices that might need troubleshooting, and more.
1111

1212
For more information, see [What is a Defender for IoT committed device?](architecture.md#what-is-a-defender-for-iot-committed-device).
1313

articles/defender-for-iot/organizations/how-to-manage-individual-sensors.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Select the link in each widget to drill down for more information in your sensor
3535

3636
### Validate connectivity status
3737

38-
Verify that your sensor is successfully connected to the Azure portal directly from the sensor's **Overview** page.
38+
Verify that your sensor is successfully connected to the Azure portal directly from the sensor's **Overview** page.
3939

4040
If there are any connection issues, a disconnection message is shown in the **General Settings** area on the **Overview** page, and a **Service connection error** warning appears at the top of the page in the :::image type="icon" source="media/how-to-manage-individual-sensors/bell-icon.png" border="false"::: **System Messages** area. For example:
4141

@@ -49,12 +49,11 @@ If there are any connection issues, a disconnection message is shown in the **Ge
4949

5050
:::image type="content" source="media/how-to-manage-individual-sensors/system-messages.png" alt-text="Screenshot of the system messages pane." lightbox="media/how-to-manage-individual-sensors/system-messages.png":::
5151

52-
5352
## Download software for OT sensors
5453

5554
You may need to download software for your OT sensor if you're [installing Defender for IoT software](ot-deploy/install-software-ot-sensor.md) on your own appliances, or [updating software versions](update-ot-software.md).
5655

57-
In Defender for IoT in the Azure portal, use one of the following options:
56+
In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) in the Azure portal, use one of the following options:
5857

5958
- For a new installation, select **Getting started** > **Sensor**. Select a version in the **Purchase an appliance and install software** area, and then select **Download**.
6059

@@ -366,7 +365,7 @@ You'll need an SMTP mail server configured to enable email alerts about disconne
366365

367366
**Prerequisites**:
368367

369-
Make sure you can reach the SMTP server from the [sensor's management port](./best-practices/understand-network-architecture.md).
368+
Make sure you can reach the SMTP server from the [sensor's management port](./best-practices/understand-network-architecture.md).
370369

371370
**To configure an SMTP server on your sensor**:
372371

articles/defender-for-iot/organizations/how-to-manage-the-on-premises-management-console.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,18 +13,19 @@ This article covers on-premises management console options like backup and resto
1313

1414
You may need to download software for your on-premises management console if you're [installing Defender for IoT software](ot-deploy/install-software-on-premises-management-console.md) on your own appliances, or [updating software versions](update-ot-software.md).
1515

16-
In Defender for IoT in the Azure portal, use one of the following options:
16+
In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) in the Azure portal, use one of the following options:
1717

18-
- For a new installation or standalone update, select **Getting started** > **On-premises management console**.
18+
- For a new installation or standalone update, select **Getting started** > **On-premises management console**.
1919

20-
- For a new installation, select a version in the **Purchase an appliance and install software** area, and then select **Download**.
20+
- For a new installation, select a version in the **Purchase an appliance and install software** area, and then select **Download**.
2121
- For an update, select your update scenario in the **On-premises management console** area and then select **Download**.
2222

2323
- If you're updating your on-premises management console together with connected OT sensors, use the options in the **Sites and sensors** page > **Sensor update (Preview)** menu.
2424

2525
[!INCLUDE [root-of-trust](includes/root-of-trust.md)]
2626

2727
For more information, see [Update Defender for IoT OT monitoring software](update-ot-software.md#update-an-on-premises-management-console).
28+
2829
## Upload an activation file
2930

3031
When you first sign in, an activation file for the on-premises management console is downloaded. This file contains the aggregate committed devices that are defined during the onboarding process. The list includes sensors associated with multiple subscriptions.

articles/defender-for-iot/organizations/how-to-work-with-threat-intelligence-packages.md

Lines changed: 10 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -27,15 +27,14 @@ To perform the procedures in this article, make sure that you have:
2727

2828
- Relevant permissions on the Azure portal and any OT network sensors or on-premises management console you want to update.
2929

30-
- **To download threat intelligence packages from the Azure portal**, you need access to the Azure portal as a [Security Reader](../../role-based-access-control/built-in-roles.md#security-reader), [Security Admin](../../role-based-access-control/built-in-roles.md#security-admin), [Contributor](../../role-based-access-control/built-in-roles.md#contributor), or [Owner](../../role-based-access-control/built-in-roles.md#owner) role.
30+
- **To download threat intelligence packages from the Azure portal**, you need access to the Azure portal as a [Security Reader](../../role-based-access-control/built-in-roles.md#security-reader), [Security Admin](../../role-based-access-control/built-in-roles.md#security-admin), [Contributor](../../role-based-access-control/built-in-roles.md#contributor), or [Owner](../../role-based-access-control/built-in-roles.md#owner) role.
3131

32-
- **To push threat intelligence updates to cloud-connected OT sensors from the Azure portal**, you need access to Azure portal as a [Security Admin](../../role-based-access-control/built-in-roles.md#security-admin), [Contributor](../../role-based-access-control/built-in-roles.md#contributor), or [Owner](../../role-based-access-control/built-in-roles.md#owner) role.
32+
- **To push threat intelligence updates to cloud-connected OT sensors from the Azure portal**, you need access to Azure portal as a [Security Admin](../../role-based-access-control/built-in-roles.md#security-admin), [Contributor](../../role-based-access-control/built-in-roles.md#contributor), or [Owner](../../role-based-access-control/built-in-roles.md#owner) role.
3333

34-
- **To manually upload threat intelligence packages to OT sensors or on-premises management consoles**, you need access to the OT sensor or on-premises management console as an **Admin** user.
34+
- **To manually upload threat intelligence packages to OT sensors or on-premises management consoles**, you need access to the OT sensor or on-premises management console as an **Admin** user.
3535

3636
For more information, see [Azure user roles and permissions for Defender for IoT](roles-azure.md) and [On-premises users and roles for OT monitoring with Defender for IoT](roles-on-premises.md).
3737

38-
3938
## View the most recent threat intelligence package
4039

4140
To view the most recent package delivered, in the Azure portal, select **Sites and sensors** > **Threat intelligence update (Preview)** > **Local update**.
@@ -54,13 +53,13 @@ Update threat intelligence packages on your OT sensors using any of the followin
5453

5554
### Automatically push updates to cloud-connected sensors
5655

57-
Threat intelligence packages can be automatically updated to *cloud connected* sensors as they're released by Defender for IoT.
56+
Threat intelligence packages can be automatically updated to *cloud connected* sensors as they're released by Defender for IoT.
5857

5958
Ensure automatic package update by onboarding your cloud connected sensor with the **Automatic Threat Intelligence Updates** option enabled. For more information, see [Onboard a sensor](tutorial-onboarding.md#onboard-and-activate-the-virtual-sensor).
6059

6160
**To change the update mode after you've onboarded your OT sensor**:
6261

63-
1. In Defender for IoT on the Azure portal, select **Sites and sensors**, and then locate the sensor you want to change.
62+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select **Sites and sensors**, and then locate the sensor you want to change.
6463
1. Select the options (**...**) menu for the selected OT sensor > **Edit**.
6564
1. Toggle on or toggle off the **Automatic Threat Intelligence Updates** option as needed.
6665

@@ -70,14 +69,14 @@ Your *cloud connected* sensors can be automatically updated with threat intellig
7069

7170
**To manually push updates to a single OT sensor**:
7271

73-
1. In Defender for IoT on the Azure portal, select **Sites and sensors**, and locate the OT sensor you want to update.
74-
1. Select the options (**...**) menu for the selected sensor and then select **Push Threat Intelligence update**.
72+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select **Sites and sensors**, and locate the OT sensor you want to update.
73+
1. Select the options (**...**) menu for the selected sensor and then select **Push Threat Intelligence update**.
7574

7675
The **Threat Intelligence update status** field displays the update progress.
7776

7877
**To manually push updates to multiple OT sensors**:
7978

80-
1. In Defender for IoT on the Azure portal, select **Sites and sensors**. Locate and select the OT sensors you want to update.
79+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select **Sites and sensors**. Locate and select the OT sensors you want to update.
8180
1. Select **Threat intelligence updates (Preview)** > **Remote update**.
8281

8382
The **Threat Intelligence update status** field displays the update progress for each selected sensor.
@@ -94,7 +93,7 @@ If you're also working with an on-premises management console, we recommend that
9493
9594
**To download threat intelligence packages**:
9695

97-
1. In Defender for IoT on the Azure portal, select **Sites and sensors** > **Threat intelligence update (Preview)** > **Local update**.
96+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select **Sites and sensors** > **Threat intelligence update (Preview)** > **Local update**.
9897

9998
1. In the **Sensor TI update** pane, select **Download** to download the latest threat intelligence file. For example:
10099

@@ -134,7 +133,7 @@ On each OT sensor, the threat intelligence update status and version information
134133

135134
For cloud-connected OT sensors, threat intelligence data is also shown in the **Sites and sensors** page. To view threat intelligence statues from the Azure portal:
136135

137-
1. In Defender for IoT on the Azure portal, select **Site and sensors**.
136+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select **Site and sensors**.
138137

139138
1. Locate the OT sensors where you want to check the threat intelligence statues.
140139

@@ -149,7 +148,6 @@ For cloud-connected OT sensors, threat intelligence data is also shown in the **
149148
> [!TIP]
150149
> If a cloud-connected OT sensor shows that a threat intelligence update has failed, we recommend that your check your sensor connection details. On the **Sites and sensors** page, check the **Sensor status** and **Last connected UTC** columns.
151150
152-
153151
## Next steps
154152

155153
For more information, see:

0 commit comments

Comments
 (0)