Skip to content

Commit 13e506c

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/defender-docs-pr into WI451232-okta-public-preview-unified-connector
2 parents c6ef574 + 155d3e3 commit 13e506c

File tree

64 files changed

+479
-136
lines changed

Some content is hidden

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

64 files changed

+479
-136
lines changed

.openpublishing.redirection.defender-xdr.json

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,5 @@
11
{
22
"redirections": [
3-
{
4-
"source_path": "microsoft-365/security/defender/advanced-hunting-IdentityEvents-table.md",
5-
"redirect_url": "/defender-xdr/advanced-hunting-identityevents-table",
6-
"redirect_document_id": false
7-
},
83
{
94
"source_path": "defender-xdr/microsoft-365-security-center-defender-cloud-apps.md",
105
"redirect_url": "/defender-cloud-apps/microsoft-365-security-center-defender-cloud-apps",
456 KB
Loading
Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
---
2+
title: 'Security Assessment: Remove Inactive Service Account (Preview)'
3+
description: Learn how to identify and address inactive Active Directory service accounts to mitigate security risks and improve your organization's security posture.
4+
ms.date: 08/17/2025
5+
ms.topic: how-to
6+
#customer intent: As a security administrator, I want to improve security posture in my organization by removing inactive service accounts
7+
---
8+
9+
# Security Assessment: Remove Inactive Service Accounts (Preview)
10+
11+
This recommendation lists Active Directory service accounts detected as inactive (stale) within the past 180 days.
12+
13+
## Why do inactive service accounts pose a risk?
14+
15+
Unused service accounts create significant security risks, as some of them can carry elevated privileges. If attackers gain access, the result can be substantial damage. Dormant service accounts might retain high or legacy permissions. When compromised, they provide attackers with discreet entry points into critical systems, granting far more access than a standard user account.
16+
17+
This exposure creates several risks:
18+
19+
- Unauthorized access to sensitive applications and data.
20+
21+
- Lateral movement across the network without detection.
22+
23+
24+
## How do I use this security assessment to improve my organizational security posture?
25+
26+
To use this security assessment effectively, follow these steps:
27+
28+
1. Review the recommended action at [https://security.microsoft.com/securescore?viewid=actions ](https://security.microsoft.com/securescore?viewid=actions ) for Remove inactive service account.
29+
1. Review the list of exposed entities to discover which of your service account is inactive.
30+
31+
:::image type="content" source="media/okta-integration/remove-inactive-service-accounts.png" alt-text="Screenshot that shows the recommendation action to remove inactive service accounts." lightbox="media/okta-integration/remove-inactive-service-accounts.png":::
32+
33+
1. Take appropriate actions on those entities by removing the service account. For example:
34+
35+
- **Disable the account:** Prevent any usage by disabling the account identified as exposed.
36+
37+
- **Monitor for impact:** Wait several weeks and monitor for operational issues, such as service disruptions or errors.
38+
39+
- **Delete the account:** If no issues are observed, delete the account and fully remove its access.
40+
41+
> [!NOTE]
42+
> Assessments are updated in near real time, and scores and statuses are updated every 24 hours. The list of impacted entities is updated within a few minutes of your implementing the recommendations. The status might take time until it's marked as **Completed**.
43+
44+
## Related articles
45+
46+
- [Learn more about Microsoft Secure Score](/defender-xdr/microsoft-secure-score)

ATPDocs/toc.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -255,10 +255,12 @@ items:
255255
href: security-assessment-clear-text.md
256256
- name: LAPS usage assessment
257257
href: security-assessment-laps.md
258-
- name: Riskiest lateral movement paths
259-
href: security-assessment-riskiest-lmp.md
260258
- name: Remove discoverable passwords in Active Directory account attributes
261259
href: remove-discoverable-passwords-active-directory-account-attributes.md
260+
- name: Remove inactive service accounts
261+
href: remove-inactive-service-account.md
262+
- name: Riskiest lateral movement paths
263+
href: security-assessment-riskiest-lmp.md
262264
- name: Unsecure Kerberos delegation assessment
263265
href: security-assessment-unconstrained-kerberos.md
264266
- name: Unsecure SID History attributes

ATPDocs/whats-new.md

Lines changed: 23 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,27 @@ Microsoft Defender for Identity supports the [Unified connectors](/azure/sentine
3232
For more information see: [Connect Okta to Microsoft Defender for Identity (Preview)](okta-integration.md)
3333

3434

35-
## New security posture assessment: Remove discoverable passwords in Active Directory account attributes (Preview)
35+
### New security assessment: Remove inactive service accounts (Preview)
36+
37+
Microsoft Defender for Identity now includes a new security assessment that helps you identify and remove inactive service accounts in your organization. This assessment lists Active Directory service accounts that have been inactive (stale) for the past 180 days, to help you mitigate security risks associated with unused accounts.
38+
39+
For more information, see: [Security Assessment: Remove Inactive Service Accounts (Preview)](remove-inactive-service-account.md)
40+
41+
### New Graph based API for response actions (preview)
42+
43+
We’re excited to announce a new Graph-based API for initiating and managing remediation actions in Microsoft Defender for Identity.
44+
45+
This capability is currently in preview and available in API Beta version.
46+
47+
For more information, see [Managing response actions through Graph API](/graph/api/resources/security-identityaccounts?view=graph-rest-beta&preserve-view=true).
48+
49+
### Identity scoping is now generally available (GA)
50+
51+
Identity scoping is now generally available across all environments. Organizations can now define and refine the scope of MDI monitoring and gain granular control over which entities and resources are included in security analysis.
52+
53+
For more information, see [Configure scoped access for Microsoft Defender for Identity](configure-scoped-access.md).
54+
55+
### New security posture assessment: Remove discoverable passwords in Active Directory account attributes (Preview)
3656

3757
The new security posture assessment highlights unsecured Active Directory attributes that contain passwords or credential clues and recommends steps to remove them, helping reduce the risk of identity compromise.
3858

@@ -53,11 +73,11 @@ Improved detection logic to include scenarios where accounts were locked during
5373

5474
## July 2025
5575

56-
**Expanded coverage in ITDR deployment health widget**
76+
### Expanded coverage in ITDR deployment health widget
5777

5878
The Identity Threat Detection and Response (ITDR) deployment health widget now provides visibility into the deployment status of additional server types. Previously, it only reflected the status for Active Directory domain controllers. With this update, the widget also includes deployment status for ADFS, ADCS, and Microsoft Entra Connect servers - making it easier to track and ensure full sensor coverage across all supported identity infrastructure.
5979

60-
**Time limit added to Recommended test mode**
80+
### Time limit added to Recommended test mode
6181

6282
Recommended test mode configuration on the [Adjust alert thresholds page](/defender-for-identity/advanced-settings), now requires you to set an expiration time (up to 60 days) when enabling it. The end time is shown next to the toggle while test mode is active. For customers who already have Recommended test mode enabled, a 60-day expiration is automatically applied.
6383

CloudAppSecurityDocs/investigate-anomaly-alerts.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,6 @@ ms.topic: how-to
88
# How to investigate anomaly detection alerts
99

1010

11-
1211
Microsoft Defender for Cloud Apps provides security detections and alerts for malicious activities. The purpose of this guide is to provide you with general and practical information on each alert, to help with your investigation and remediation tasks. Included in this guide is general information about the conditions for triggering alerts. However, it's important to note that since anomaly detections are nondeterministic by nature, they're only triggered when there's behavior that deviates from the norm. Finally, some alerts might be in preview, so regularly review the official documentation for updated alert status.
1312

1413
> [!IMPORTANT]

CloudAppSecurityDocs/protect-salesforce.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ You can use the following built-in policy templates to detect and notify you abo
5555

5656
| Type | Name |
5757
| ---- | ---- |
58-
| Built-in anomaly detection policy | [Activity from anonymous IP addresses](anomaly-detection-policy.md#activity-from-anonymous-ip-addresses)<br />[Activity from infrequent country](anomaly-detection-policy.md#activity-from-infrequent-country)<br />[Activity from suspicious IP addresses](anomaly-detection-policy.md#activity-from-suspicious-ip-addresses)<br />[Impossible travel](anomaly-detection-policy.md#impossible-travel)<br />[Activity performed by terminated user](anomaly-detection-policy.md#activity-performed-by-terminated-user) (requires Microsoft Entra ID as IdP)<br />[Multiple failed login attempts](anomaly-detection-policy.md#multiple-failed-login-attempts)<br />[Unusual administrative activities](anomaly-detection-policy.md#unusual-activities-by-user)<br />[Unusual file deletion activities](anomaly-detection-policy.md#unusual-activities-by-user)<br />[Unusual file share activities](anomaly-detection-policy.md#unusual-activities-by-user)<br />[Unusual impersonated activities](anomaly-detection-policy.md#unusual-activities-by-user)<br />[Unusual multiple file download activities](anomaly-detection-policy.md#unusual-activities-by-user) |
58+
| Built-in anomaly detection policy | [Activity from anonymous IP addresses](anomaly-detection-policy.md#activity-from-anonymous-ip-addresses)<br />[Activity from infrequent country](anomaly-detection-policy.md#activity-from-infrequent-country)<br />[Activity from suspicious IP addresses](anomaly-detection-policy.md#activity-from-suspicious-ip-addresses)<br />[Impossible travel](anomaly-detection-policy.md#impossible-travel)<br />[Activity performed by terminated user](anomaly-detection-policy.md#activity-performed-by-terminated-user) (requires Microsoft Entra ID as IdP)<br />[Multiple failed login attempts](anomaly-detection-policy.md#multiple-failed-login-attempts)<br />[Unusual administrative activities](anomaly-detection-policy.md#unusual-activities-by-user)<br />[Unusual file deletion activities](anomaly-detection-policy.md#unusual-activities-by-user) (Temporarily not supported due to limitation in Salesforce API)<br />[Unusual file share activities](anomaly-detection-policy.md#unusual-activities-by-user)<br />[Unusual impersonated activities](anomaly-detection-policy.md#unusual-activities-by-user)<br />[Unusual multiple file download activities](anomaly-detection-policy.md#unusual-activities-by-user) |
5959
| Activity policy template | Logon from a risky IP address<br />Mass download by a single user|
6060
| File policy template | Detect a file shared with an unauthorized domain<br />Detect a file shared with personal email addresses|
6161

defender-endpoint/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -267,6 +267,8 @@
267267
items:
268268
- name: Installer script based deployment
269269
href: linux-installer-script.md
270+
- name: Enabling deployment to a custom location
271+
href: linux-custom-location-installation.md
270272
- name: Ansible based deployment
271273
href: linux-install-with-ansible.md
272274
- name: Chef based deployment

defender-endpoint/api/run-advanced-query-api.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.topic: reference
1616
ms.subservice: reference
1717
ms.custom: api
1818
search.appverid: met150
19-
ms.date: 12/18/2020
19+
ms.date: 08/18/2025
2020
---
2121

2222
# Advanced hunting API
@@ -105,13 +105,11 @@ POST https://api.securitycenter.microsoft.com/api/advancedqueries/run
105105
```
106106

107107
```json
108+
108109
{
109-
"Query":"DeviceProcessEvents
110-
|where InitiatingProcessFileName =~ 'powershell.exe'
111-
|where ProcessCommandLine contains 'appdata'
112-
|project Timestamp, FileName, InitiatingProcessFileName, DeviceId
113-
|limit 2"
110+
"Query":"DeviceProcessEvents |where InitiatingProcessFileName =~ 'powershell.exe' |where ProcessCommandLine contains 'appdata'|project Timestamp, FileName, InitiatingProcessFileName, DeviceId|limit 2"
114111
}
112+
115113
```
116114

117115
### Response example

0 commit comments

Comments
 (0)