Skip to content

Commit 155ef98

Browse files
Merge pull request #292327 from tarTech23/cmdelot
cm deletion from ot
2 parents 7188fa3 + b40a371 commit 155ef98

File tree

6 files changed

+8
-12
lines changed

6 files changed

+8
-12
lines changed

articles/defender-for-iot/organizations/best-practices/plan-corporate-monitoring.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ For more information, see:
7474

7575
For cloud-connected sensors, determine how you'll be connecting each OT sensor to Defender for IoT in the Azure cloud, such as what sort of proxy you might need. For more information, see [Methods for connecting sensors to Azure](../architecture-connections.md).
7676

77-
If you're working in an air-gapped or hybrid environment and will have multiple, locally-managed OT network sensors, you may want to plan to deploy an on-premises management console to configure your settings and view data from a central location. For more information, see the [Air-gapped OT sensor management deployment path](../ot-deploy/air-gapped-deploy.md).
77+
If you're working in an air-gapped or hybrid environment and will have multiple, locally-managed OT network sensors, see the [Air-gapped OT sensor management deployment path](../ot-deploy/air-gapped-deploy.md).
7878

7979
## Plan on-premises SSL/TLS certifications
8080

articles/defender-for-iot/organizations/integrations/send-cloud-data-to-partners.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ relatedContent:
121121
url: ../integrate-overview.md
122122
# Next steps
123123

124-
#This article describes how to forward alerts generated by cloud-connected sensors only. If you're working on-premises, such as in air-gapped environments, you may be able to create a forwarding alert rule to forward alert data directly from an OT sensor or on-premises management console.
124+
#This article describes how to forward alerts generated by cloud-connected sensors only. If you're working on-premises, such as in air-gapped environments, you may be able to create a forwarding alert rule to forward alert data directly from an OT sensor.
125125

126126
#> [!div class="nextstepaction"]
127127
#> [Integrations with Microsoft and partner services](../integrate-overview.md).

articles/defender-for-iot/organizations/ot-deploy/create-learned-baseline.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Creating your baseline of OT alerts can take anywhere from a few days to several
3333

3434
## Prerequisites
3535

36-
You can perform the procedures in this article from the Azure portal, an OT sensor, or an on-premises management console.
36+
You can perform the procedures in this article from the Azure portal or an OT sensor.
3737

3838
Before you start, make sure that you have:
3939

articles/defender-for-iot/organizations/ot-deploy/create-ssl-certificates.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
title: Create SSL/TLS certificates for OT appliances - Microsoft Defender for IoT
3-
description: Learn how to create SSL/TLS certificates for use with Microsoft Defender for IOT OT sensors and on-premises management consoles.
3+
description: Learn how to create SSL/TLS certificates for use with Microsoft Defender for IOT OT sensors.
44
ms.date: 01/17/2023
55
ms.topic: install-set-up-deploy
66
---
77

88
# Create SSL/TLS certificates for OT appliances
99

10-
This article is one in a series of articles describing the [deployment path](../ot-deploy/ot-deploy-path.md) for OT monitoring with Microsoft Defender for IoT, and describes how to create CA-signed certificates to use with Defender for IoT on-premises appliances, including both OT sensors and [on-premises management consoles](air-gapped-deploy.md).
10+
This article is one in a series of articles describing the [deployment path](../ot-deploy/ot-deploy-path.md) for OT monitoring with Microsoft Defender for IoT, and describes how to create CA-signed certificates to use with Defender for IoT on-premises OT sensor appliances.
1111

1212
:::image type="content" source="../media/deployment-paths/progress-plan-and-prepare.png" alt-text="Diagram of a progress bar with Plan and prepare highlighted." border="false" lightbox="../media/deployment-paths/progress-plan-and-prepare.png":::
1313

@@ -163,7 +163,6 @@ If these tests fail, review [certificate file requirements](../best-practices/ce
163163
Self-signed certificates are available for use in testing environments after installing Defender for IoT OT monitoring software. For more information, see:
164164

165165
- [Create and deploy self-signed certificates on OT sensors](../how-to-manage-individual-sensors.md#manage-ssltls-certificates)
166-
- [Create and deploy self-signed certificates on on-premises management consoles](../legacy-central-management/how-to-manage-the-on-premises-management-console.md#manage-ssltls-certificates)
167166

168167
## Next steps
169168

articles/defender-for-iot/organizations/ot-deploy/ot-deploy-path.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -44,9 +44,6 @@ Plan basic details about your monitoring system, such as:
4444

4545
For more information, see [Plan your OT monitoring system with Defender for IoT](../best-practices/plan-corporate-monitoring.md).
4646

47-
> [!TIP]
48-
> If you're using several locally managed sensors, you may also want to deploy an [on-premises management console](air-gapped-deploy.md) for central visibility and management.
49-
>
5047
### Prepare for an OT site deployment
5148

5249
Define additional details for each site planned in your system, including:
@@ -98,7 +95,7 @@ For more information, see:
9895

9996
Configure any firewall rules to ensure that your OT sensor appliances will be able to access Defender for IoT on the Azure cloud. If you're planning to connect via a proxy, you'll configure those settings only after installing your sensor.
10097

101-
Skip this step for any OT sensor that is planned to be air-gapped and managed locally, either directly on the sensor console, or via an [on-premises management console](air-gapped-deploy.md).
98+
Skip this step for any OT sensor that is planned to be air-gapped and managed locally directly on the sensor console.
10299

103100
For more information, see [Provision OT sensors for cloud management](provision-cloud-management.md).
104101

@@ -134,7 +131,7 @@ If you've decided to use a proxy to connect your sensors to the cloud, set up yo
134131
Skip this step in the following situations:
135132

136133
- For any OT sensor where you're connecting directly to Azure, without a proxy
137-
- For any sensor that is planned to be air-gapped and managed locally, either directly on the sensor console, or via an [on-premises management console](air-gapped-deploy.md).
134+
- For any sensor that is planned to be air-gapped and managed locally directly on the sensor console.
138135

139136
### Configure optional settings
140137

articles/defender-for-iot/organizations/ot-deploy/post-install-validation-ot-software.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ For more information, see [Check system health](../how-to-troubleshoot-sensor.md
107107

108108
## Next steps
109109

110-
For more information, see [Troubleshoot the sensor](../how-to-troubleshoot-sensor.md) and [Troubleshoot the on-premises management console](../legacy-central-management/how-to-troubleshoot-on-premises-management-console.md).
110+
For more information, see [Troubleshoot the sensor](../how-to-troubleshoot-sensor.md).
111111

112112
> [!div class="step-by-step"]
113113
> [« Install OT monitoring software on OT sensors](install-software-ot-sensor.md)

0 commit comments

Comments
 (0)