Skip to content

Commit 0fdd36b

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/defender-docs-pr into log-collection
2 parents 41311d0 + d6f268e commit 0fdd36b

File tree

154 files changed

+410
-728
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

154 files changed

+410
-728
lines changed

.github/workflows/AutoLabelAssign.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,11 +30,11 @@ jobs:
3030
with:
3131
PayloadJson: ${{ needs.download-payload.outputs.WorkflowPayload }}
3232
AutoAssignUsers: 1
33-
AutoAssignReviewers: 1
33+
AutoAssignReviewers: 0
3434
AutoLabel: 1
3535
ExcludedUserList: '["user1", "user2"]'
3636
ExcludedBranchList: '["branch1", "branch2"]'
3737
secrets:
3838
AccessToken: ${{ secrets.GITHUB_TOKEN }}
3939
PrivateKey: ${{ secrets.M365_APP_PRIVATE_KEY }}
40-
ClientId: ${{ secrets.M365_APP_CLIENT_ID }}
40+
ClientId: ${{ secrets.M365_APP_CLIENT_ID }}

.openpublishing.redirection.defender-endpoint.json

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -159,6 +159,11 @@
159159
"source_path": "defender-endpoint/mde-linux-arm.md",
160160
"redirect_url": "/defender-endpoint/microsoft-defender-endpoint-linux",
161161
"redirect_document_id": false
162-
}
162+
},
163+
{
164+
"source_path": "defender-endpoint/contact-support.md",
165+
"redirect_url": "/defender-xdr/contact-defender-support",
166+
"redirect_document_id": false
167+
},
163168
]
164169
}

defender-endpoint/contact-support.md

Lines changed: 0 additions & 91 deletions
This file was deleted.

defender-endpoint/indicators-overview.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -50,11 +50,11 @@ A false positive (FP) refers to a false positive in Microsoft's threat intellige
5050

5151
You can use IP and URL/Domain indicators to manage site access.
5252

53-
To block connections to an IP address, type the IPv4 address in dotted-quad form (e.g. `8.8.8.8`). For IPv6 addresses, specify all 8 segments (e.g. `2001:4860:4860:0:0:0:0:8888`). Note that wildcards and ranges are not supported.
53+
To block connections to an IP address, type the IPv4 address in dotted-quad form (for example, `8.8.8.8`). For IPv6 addresses, specify all eight segments (for example, `2001:4860:4860:0:0:0:0:8888`). Note that wildcards and ranges aren't supported.
5454

55-
To block connections to a domain and any of its subdomains, specify the domain (e.g. `example.com`). This indicator will match `example.com` as well as `sub.example.com` and `anything.sub.example.com`.
55+
To block connections to a domain and any of its subdomains, specify the domain (for example, `example.com`). This indicator matches `example.com` as well as `sub.example.com` and `anything.sub.example.com`.
5656

57-
To block a specific URL path, specify the URL path (e.g. `https://example.com/block`). This indicator will match resources under the `/block` path on `example.com`. Note that HTTPS URL paths will only be matched in Microsoft Edge; HTTP URL paths can be matched in any browser.
57+
To block a specific URL path, specify the URL path (for example, `https://example.com/block`). This indicator matches resources under the `/block` path on `example.com`. Note that HTTPS URL paths will only be matched in Microsoft Edge; HTTP URL paths can be matched in any browser.
5858

5959
You can also create IP and URL indicators to unblock users from a SmartScreen block or selectively bypass web content filtering blocks of sites that you'd like to allow to load. For example, consider a case where you have web content filtering set to block all social media websites. However, the marketing team has a requirement to use a specific social media site to monitor their ad placements. In this case, you can unblock the specific social media site by creating a domain Allow indicator and assigning it to the marketing team's device group.
6060

@@ -143,17 +143,17 @@ The functionality of preexisting IoCs doesn't change. However, the indicators ar
143143
The IoC API schema and the threat IDs in Advanced Hunting are updated to align with the renaming of the IoC response actions. The API scheme changes apply to all IoC Types.
144144

145145
> [!NOTE]
146-
> There is a limit of 15,000 indicators per tenant. Increases to this limit are not supported.
146+
> There's a limit of 15,000 indicators per tenant. Increases to this limit aren't supported.
147147
>
148-
> File and certificate indicators do not block [exclusions defined for Microsoft Defender Antivirus](/windows/security/threat-protection/microsoft-defender-antivirus/configure-exclusions-microsoft-defender-antivirus). Indicators are not supported in Microsoft Defender Antivirus when it is in passive mode.
148+
> File and certificate indicators don't block [exclusions defined for Microsoft Defender Antivirus](/windows/security/threat-protection/microsoft-defender-antivirus/configure-exclusions-microsoft-defender-antivirus). Indicators aren't supported in Microsoft Defender Antivirus when it is in passive mode.
149149
>
150150
> The format for importing new indicators (IoCs) has changed according to the new updated actions and alerts settings. We recommend downloading the new CSV format that can be found at the bottom of the import panel.
151151
>
152-
> If indicators are synced to the Microsoft Defender portal from Microsoft Defender for Cloud Apps for sanctioned or unsanctioned applications, the `Generate Alert` option is enabled by default in the Microsoft Defender portal. If you try to clear the `Generate Alert` option for Defender for Endpoint, it is re-enabled after some time because the Defender for Cloud Apps policy overrides it.
152+
If indicators are synced to the Defender portal from Microsoft Defender for Cloud Apps for sanctioned or unsanctioned applications, the settings are overwritten when synced to Microsoft Defender portal. The `Generate Alert` option is enabled by default in the Microsoft Defender portal for unsanctioned applications. If you try to clear the `Generate Alert` option for Defender for Endpoint, it's re-enabled after some time because the Defender for Cloud Apps policy overrides it. Sanctioned or allowed applications the value is set to not `Generate Alert` .
153153

154154
## Known issues and limitations
155155

156-
Microsoft Store apps cannot be blocked by Microsoft Defender because they're signed by Microsoft.
156+
Microsoft Store apps can't be blocked by Microsoft Defender because they're signed by Microsoft.
157157

158158
Customers might experience issues with alerts for IoCs. The following scenarios are situations where alerts aren't created or are created with inaccurate information.
159159

defender-endpoint/ios-whatsnew.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Want to experience Microsoft Defender for Endpoint? [Sign up for a free trial.](
3333

3434
| Build| 1.1.70230101|
3535
| -------- | -------- |
36-
| Release Date |October 30, 2025|
36+
| Release Date |October 28, 2025|
3737

3838
**What's New**
3939

defender-endpoint/linux-install-manually.md

Lines changed: 2 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: install-set-up-deploy
1616
ms.subservice: linux
1717
search.appverid: met150
18-
ms.date: 08/11/2025
18+
ms.date: 11/03/2025
1919
---
2020

2121
# Deploy Microsoft Defender for Endpoint on Linux manually
@@ -492,27 +492,7 @@ Download the onboarding package from the [Microsoft Defender portal](https://sec
492492

493493
## Defender for Endpoint package external package dependencies
494494

495-
The following external package dependencies exist for the `mdatp` package:
496-
497-
- The mdatp RPM package requires `glibc >= 2.17`
498-
- For DEBIAN the mdatp package requires `libc6 >= 2.23`
499-
- For Mariner the mdatp package requires `attr`, `diffutils`, `libacl`, `libattr`, `libselinux-utils`, `selinux-policy`, `policycoreutils`
500-
501-
> [!NOTE]
502-
> Beginning with version `101.24082.0004`, Defender for Endpoint on Linux no longer supports the `Auditd` event provider. We're transitioning completely to the more efficient eBPF technology.
503-
> If eBPF isn't supported on your machines, or if there are specific requirements to remain on Auditd, and your machines are using Defender for Endpoint on Linux version `101.24072.0001` or lower, the following other dependencies on the auditd package exist for mdatp:
504-
> - The mdatp RPM package requires `audit`, `semanage`.
505-
> - For DEBIAN, the mdatp package requires `auditd`.
506-
> - For Mariner, the mdatp package requires `audit`.
507-
> For version older than `101.25032.0000`:
508-
> - RPM package needs: `mde-netfilter`, `pcre`
509-
> - DEBIAN package needs: `mde-netfilter`, `libpcre3`
510-
> - The `mde-netfilter` package also has the following package dependencies:
511-
- For DEBIAN, the mde-netfilter package requires `libnetfilter-queue1` and `libglib2.0-0`
512-
- For RPM, the mde-netfilter package requires `libmnl`, `libnfnetlink`, `libnetfilter_queue`, and `glib2`
513-
> Beginning with version `101.25042.0003`, uuid-runtime is no longer required as an external-dependency.
514-
515-
If the Microsoft Defender for Endpoint installation fails due to missing dependencies errors, you can manually download the prerequisite dependencies.
495+
For information, see [Prerequisites for Microsoft Defender for Endpoint on Linux: External package dependency](./mde-linux-prerequisites.md#external-package-dependency).
516496

517497
## Troubleshoot installation issues
518498

0 commit comments

Comments
 (0)