Skip to content

Commit fbeeb7c

Browse files
authored
Merge pull request #206766 from batamig/patch-222
1000 > 100
2 parents 24c152f + 93735d9 commit fbeeb7c

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ This procedure describes how to add a Defender for IoT plan for OT networks to a
8787

8888
- **Number of sites** (for annual commitment only). Enter the number of committed sites.
8989

90-
- **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.
90+
- **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 100 devices.
9191

9292
For example:
9393

@@ -183,4 +183,4 @@ Business considerations may require that you apply your existing IoT sensors to
183183

184184
- [Create an additional Azure subscription](../../cost-management-billing/manage/create-subscription.md)
185185

186-
- [Upgrade your Azure subscription](../../cost-management-billing/manage/upgrade-azure-subscription.md)
186+
- [Upgrade your Azure subscription](../../cost-management-billing/manage/upgrade-azure-subscription.md)

articles/defender-for-iot/organizations/pre-deployment-checklist.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ Review your industrial network architecture to define the proper location for th
4848
> [!NOTE]
4949
> The Defender for IoT appliance should be connected to a lower-level switch that sees the traffic between the ports on the switch.
5050
51-
1. **Committed devices** - Provide the approximate number of network devices that will be monitored. You'll need this information when onboarding your subscription to Defender for IoT in the Azure portal. During the onboarding process, you'll be prompted to enter the number of devices in increments of 1000. For more information, see [What is a Defender for IoT committed device?](architecture.md#what-is-a-defender-for-iot-committed-device)
51+
1. **Committed devices** - Provide the approximate number of network devices that will be monitored. You'll need this information when onboarding your subscription to Defender for IoT in the Azure portal. During the onboarding process, you'll be prompted to enter the number of devices in increments of 100. For more information, see [What is a Defender for IoT committed device?](architecture.md#what-is-a-defender-for-iot-committed-device)
5252

5353
1. **(Optional) Subnet list** - Provide a subnet list for the production networks and a description (optional).
5454

0 commit comments

Comments
 (0)