Skip to content

Commit 3b7b147

Browse files
Merge pull request #222321 from pritamso/Broken-link-fix-batamig
Broken link fixed
2 parents 5571088 + bc78423 commit 3b7b147

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -328,7 +328,7 @@ You'll need an SMTP mail server configured to enable email alerts about disconne
328328

329329
**Prerequisites**:
330330

331-
Make sure you can reach the SMTP server from the [sensor's management port](/best-practices/understand-network-architecture).
331+
Make sure you can reach the SMTP server from the [sensor's management port](/azure/defender-for-iot/organizations/best-practices/understand-network-architecture).
332332

333333
**To configure an SMTP server on your sensor**:
334334

articles/defender-for-iot/organizations/iot-advanced-threat-monitoring.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -321,19 +321,19 @@ This playbook updates the incident severity according to the importance level of
321321
## Next steps
322322

323323
> [!div class="nextstepaction"]
324-
> [Visualize data](/azure/sentinel/get-visibility.md)
324+
> [Visualize data](/azure/sentinel/get-visibility)
325325
326326
> [!div class="nextstepaction"]
327-
> [Create custom analytics rules](/azure/sentinel/detect-threats-custom.md)
327+
> [Create custom analytics rules](/azure/sentinel/detect-threats-custom)
328328
329329
> [!div class="nextstepaction"]
330-
> [Investigate incidents](/sentinel/investigate-cases)
330+
> [Investigate incidents](/azure/sentinel/investigate-cases)
331331
332332
> [!div class="nextstepaction"]
333-
> [Investigate entities](/azure/sentinel/entity-pages.md)
333+
> [Investigate entities](/azure/sentinel/entity-pages)
334334
335335
> [!div class="nextstepaction"]
336-
> [Use playbooks with automation rules](/azure/sentinel/tutorial-respond-threats-playbook.md)
336+
> [Use playbooks with automation rules](/azure/sentinel/tutorial-respond-threats-playbook)
337337
338338
For more information, see our blog: [Defending Critical Infrastructure with the Microsoft Sentinel: IT/OT Threat Monitoring Solution](https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/defending-critical-infrastructure-with-the-microsoft-sentinel-it/ba-p/3061184)
339339

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Before you start, make sure you have the following requirements on your workspac
3131
- A Defender for IoT plan on your Azure subscription with data streaming into Defender for IoT. For more information, see [Quickstart: Get started with Defender for IoT](getting-started.md).
3232

3333
> [!IMPORTANT]
34-
> Currently, having both the Microsoft Defender for IoT and the [Microsoft Defender for Cloud](/azure/sentinel/data-connectors-reference.md#microsoft-defender-for-cloud) data connectors enabled on the same Microsoft Sentinel workspace simultaneously may result in duplicate alerts in Microsoft Sentinel. We recommend that you disconnect the Microsoft Defender for Cloud data connector before connecting to Microsoft Defender for IoT.
34+
> Currently, having both the Microsoft Defender for IoT and the [Microsoft Defender for Cloud](/azure/sentinel/data-connectors-reference#microsoft-defender-for-cloud) data connectors enabled on the same Microsoft Sentinel workspace simultaneously may result in duplicate alerts in Microsoft Sentinel. We recommend that you disconnect the Microsoft Defender for Cloud data connector before connecting to Microsoft Defender for IoT.
3535
>
3636
3737
## Connect your data from Defender for IoT to Microsoft Sentinel
@@ -48,7 +48,7 @@ Start by enabling the **Defender for IoT** data connector to stream all your Def
4848

4949
If you've made any connection changes, it can take 10 seconds or more for the **Subscription** list to update.
5050

51-
For more information, see [Connect Microsoft Sentinel to Azure, Windows, Microsoft, and Amazon services](/azure/sentinel/connect-azure-windows-microsoft-services.md).
51+
For more information, see [Connect Microsoft Sentinel to Azure, Windows, Microsoft, and Amazon services](/azure/sentinel/connect-azure-windows-microsoft-services).
5252

5353
## View Defender for IoT alerts
5454

@@ -167,5 +167,5 @@ For more information, see:
167167
- [Tutorial: Investigate and detect threats for IoT devices](iot-advanced-threat-monitoring.md)
168168
- [Defending Critical Infrastructure with the Microsoft Sentinel: IT/OT Threat Monitoring Solution](https://techcommunity.microsoft.com/t5/microsoft-sentinel-blog/defending-critical-infrastructure-with-the-microsoft-sentinel-it/ba-p/3061184)
169169
- [Microsoft Defender for IoT solution](https://azuremarketplace.microsoft.com/marketplace/apps/azuresentinel.azure-sentinel-solution-unifiedmicrosoftsocforot?tab=Overview)
170-
- [Microsoft Defender for IoT data connector](/azure/sentinel/data-connectors-reference.md#microsoft-defender-for-iot)
170+
- [Microsoft Defender for IoT data connector](/azure/sentinel/data-connectors-reference#microsoft-defender-for-iot)
171171

0 commit comments

Comments
 (0)