Update TCP port from 444 to 443 in troubleshooting guide#524
Conversation
|
@Tungsten66 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 35001bd: ✅ Validation status: passed
For more details, please refer to the build report. |
|
#assign:Dickson-Mwendia |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
|
@Tungsten66 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
There was a problem hiding this comment.
Pull request overview
Updates a troubleshooting step in the Defender for Identity known-issues guide to reference a different TCP port for localhost communication.
Changes:
- Changes the referenced localhost TCP port in the “Sensor failure communication error” resolution step (444 → 443).
| **Resolution:** | ||
|
|
||
| Make sure that communication isn't blocked for localhost, TCP port 444. To learn more about Microsoft Defender for Identity prerequisites, see [ports](prerequisites.md#required-ports). | ||
| Make sure that communication isn't blocked for localhost, TCP port 443. To learn more about Microsoft Defender for Identity prerequisites, see [ports](prerequisites.md#required-ports). |
|
This was fixed in https://github.com/MicrosoftDocs/defender-docs-pr/pull/8617 |
No description provided.