Skip to content

Commit 94455b5

Browse files
committed
fix links and wording
1 parent 61cb4a2 commit 94455b5

File tree

3 files changed

+14
-22
lines changed

3 files changed

+14
-22
lines changed

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

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ For more information, see:
7474

7575
This procedure describes how to add a Defender for IoT plan for OT networks to an Azure subscription.
7676

77-
**To onboard Defender for IoT plan for OT networks:**
77+
**To onboard a Defender for IoT plan for OT networks:**
7878

7979
1. In the Azure portal, go to **Defender for IoT** > **Pricing**.
8080

@@ -92,21 +92,19 @@ This procedure describes how to add a Defender for IoT plan for OT networks to a
9292

9393
- **Committed devices**. If you selected a monthly or annual commitment, enter the number of assets you'll want to monitor. If you selected a trial, this section doesn't appear as you have a default of 1000 devices.
9494

95-
For example:
96-
97-
:::image type="content" source="media/how-to-manage-subscriptions/onboard-plan-2.png" alt-text="Screenshot of adding a plan for OT networks to your subscription.":::
95+
For example:
9896

99-
1. Select the **I accept the terms** checkbox, and then select **Save**.
97+
:::image type="content" source="media/how-to-manage-subscriptions/onboard-plan-2.png" alt-text="Screenshot of adding a plan for OT networks to your subscription.":::
10098

99+
1. Select **I accept the terms** option, and then select **Save**.
101100

102-
Your new plan is shown under the associated subscription in the **Plans** grid on the **Pricing** page.
101+
Your OT networks plan will be shown under the associated subscription in the **Plans** grid.
103102

104103
## Add a Defender for IoT plan for Enterprise IoT networks to an Azure subscription
105104

106-
Onboard a Defender for IoT plan for Enterprise IoT networks from Microsoft Defender for Endpoint. For more information, see [Onboard Microsoft Defender for IoT](/microsoft-365/security/defender-endpoint/enable-microsoft-defender-for-iot-integration).
107-
108-
Defender for IoT plans for Enterprise IoT networks are also displayed in the Azure portal, under the associated subscription on the **Defender for IoT** > **Pricing** page.
105+
Onboard your Defender for IoT plan for Enterprise IoT networks in the Defender for Endpoint portal. For more information, see [Onboard Microsoft Defender for IoT](/microsoft-365/security/defender-endpoint/enable-microsoft-defender-for-iot-integration) in the Defender for Endpoint documentation.
109106

107+
Once you've onboarded a plan for Enterprise IoT networks from Defender for Endpoint, you'll see the plan in Defender for IoT in the Azure portal, under the associated subscription in the **Plans** grid, on the **Defender for IoT** > **Pricing** page.
110108

111109
For more information, see [Manage your subscriptions](how-to-manage-subscriptions.md).
112110

articles/defender-for-iot/organizations/how-to-activate-and-set-up-your-on-premises-management-console.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ After you sign in for the first time, you need to activate the on-premises manag
4646

4747
:::image type="content" source="media/how-to-manage-sensors-from-the-on-premises-management-console/multiple-subscriptions.png" alt-text="Screenshot that shows selecting multiple subscriptions." lightbox="media/how-to-manage-sensors-from-the-on-premises-management-console/multiple-subscriptions.png":::
4848

49-
If you haven't already onboarded Defender for IoT to a subscription, see [Onboard a Defender for IoT plan for OT networks to a subscription](how-to-manage-subscriptions.md#onboard-a-defender-for-iot-plan-for-ot-networks-to-a-subscription).
49+
If you haven't already onboarded Defender for IoT to a subscription, see [Onboard a Defender for IoT plan for OT networks](how-to-manage-subscriptions.md#onboard-a-defender-for-iot-plan-for-ot-networks).
5050

5151
> [!Note]
5252
> If you delete a subscription, you must upload a new activation file to the on-premises management console that was affiliated with the deleted subscription.
@@ -67,7 +67,7 @@ After activating an on-premises management console, you'll need to apply new act
6767

6868
|Location |Activation process |
6969
|---------|---------|
70-
|**On-premises management console** | Apply a new activation file on your on-premises management console if you've [modified the number of committed devices](how-to-manage-subscriptions.md#edit-a-plan) in your subscription. |
70+
|**On-premises management console** | Apply a new activation file on your on-premises management console if you've [modified the number of committed devices](how-to-manage-subscriptions.md#edit-a-plan-for-ot-networks) in your subscription. |
7171
|**Cloud-connected sensors** | Cloud-connected sensors remain activated for as long as your Azure subscription with your Defender for IoT plan is active. <br><br>However, you'll also need to apply a new activation file when [updating your sensor software](update-ot-software.md#download-and-apply-a-new-activation-file) from a legacy version to version 22.2.x. |
7272
| **Locally-managed** | Apply a new activation file to locally-managed sensors every year. After a sensor's activation file has expired, the sensor will continue to monitor your network, but you'll see a warning message when signing in to the sensor. |
7373

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

Lines changed: 5 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -65,9 +65,7 @@ We recommend making an initial estimate of your committed devices when onboardin
6565

6666
If you are also a Defender for Endpoint customer, you can identify devices managed by Defender for Endpoint in the Defender for Endpoint **Device inventory** page. In the **Endpoints** tab, filter for devices by **Onboarding status**. For more information, see [Defender for Endpoint Device discovery overview](/microsoft-365/security/defender-endpoint/device-discovery).
6767

68-
After you've set up your network sensor and have full visibility into all devices, you can [edit your plan](#edit-a-plan) to update the number of committed devices as needed.
69-
70-
<!--do we need the words 'to a subscription' in this heading?-->
68+
After you've set up your network sensor and have full visibility into all devices, you can [Edit a plan](#edit-a-plan-for-ot-networks) to update the number of committed devices as needed.
7169

7270
## Onboard a Defender for IoT plan for OT networks
7371

@@ -91,16 +89,14 @@ This procedure describes how to add a Defender for IoT plan for OT networks to a
9189

9290
- **Committed devices**. If you selected a monthly or annual commitment, enter the number of assets you'll want to monitor. If you selected a trial, this section doesn't appear as you have a default of 1000 devices.
9391

92+
For example:
9493

9594
:::image type="content" source="media/how-to-manage-subscriptions/onboard-plan-2.png" alt-text="Screenshot of adding a plan for OT networks to your subscription.":::
9695

97-
1. Select **I accept the terms**, and then select **Save**.
98-
96+
1. Select the **I accept the terms** option, and then select **Save**.
9997

10098
Your OT networks plan will be shown under the associated subscription in the **Plans** grid.
10199

102-
<!--same here do we need the words 'to a subscription' in this heading?-->
103-
104100
## Onboard a Defender for IoT plan for Enterprise IoT networks
105101

106102
Onboard your Defender for IoT plan for Enterprise IoT networks in the Defender for Endpoint portal. For more information, see [Onboard Microsoft Defender for IoT](/microsoft-365/security/defender-endpoint/enable-microsoft-defender-for-iot-integration) in the Defender for Endpoint documentation.
@@ -133,14 +129,12 @@ For example, you may have more devices that require monitoring if you're increas
133129

134130
1. Select the **I accept the terms** option, and then select **Save**.
135131

136-
137132
Changes to your plan will take effect one hour after confirming the change. Billing for these changes will be reflected at the beginning of the month following confirmation of the change.
138133

139134
> [!NOTE]
140135
> **For an on-premises management console:**
141136
After any changes are made, you will need to upload a new activation file to your on-premises management console. The activation file reflects the new number of committed devices. For more information, see [Upload an activation file](how-to-manage-the-on-premises-management-console.md#upload-an-activation-file).
142137

143-
144138
## Cancel a Defender for IoT plan from a subscription
145139

146140
You may need to cancel a Defender for IoT plan from your Azure subscription, for example, if you need to work with a new payment entity. Your changes take effect one hour after confirmation. Your upcoming monthly bill will reflect this change.
@@ -169,9 +163,9 @@ Business considerations may require that you apply your existing IoT sensors to
169163

170164
1. Onboard a new plan to the new subscription you want to use. For more information, see:
171165

172-
[Onboard a plan for OT networks](#onboard-a-defender-for-iot-plan-for-ot-networks-to-a-subscription) in the Azure portal
166+
[Onboard a plan for OT networks](#onboard-a-defender-for-iot-plan-for-ot-networks) in the Azure portal
173167

174-
[Onboard a plan for Enterprise IoT networks](#onboard-a-defender-for-iot-plan-for-enterprise-iot-networks-to-a-subscription) in Defender for Endpoint
168+
[Onboard a plan for Enterprise IoT networks](#onboard-a-defender-for-iot-plan-for-enterprise-iot-networks) in Defender for Endpoint
175169

176170
1. Register your sensors under the new subscription. For more information, see [Set up an Enterprise IoT sensor](tutorial-getting-started-eiot-sensor.md#set-up-an-enterprise-iot-sensor).
177171

0 commit comments

Comments
 (0)