Skip to content

Commit 91c9a13

Browse files
Merge pull request #4920 from MicrosoftDocs/main
[AutoPublish] main to live - 09/03 10:29 PDT | 09/03 22:59 IST
2 parents 6cb2af8 + 1a67cbf commit 91c9a13

File tree

4 files changed

+14
-11
lines changed

4 files changed

+14
-11
lines changed

ATPDocs/remove-inactive-service-account.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ ms.topic: how-to
66
#customer intent: As a security administrator, I want to improve security posture in my organization by removing inactive service accounts
77
---
88

9-
# Security Assessment: Remove Inactive Service Accounts (Preview)
9+
# Security Assessment: Remove Stale Service Accounts (Preview)
1010

11-
This recommendation lists Active Directory service accounts detected as inactive (stale) within the past 90 days.
11+
This recommendation lists Active Directory service accounts detected as stale within the past 90 days.
1212

13-
## Why do inactive service accounts pose a risk?
13+
## Why do stale service accounts pose a risk?
1414

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.
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. Stale 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.
1616

1717
This exposure creates several risks:
1818

@@ -25,10 +25,9 @@ This exposure creates several risks:
2525

2626
To use this security assessment effectively, follow these steps:
2727

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.
28+
1. Review the recommended action at [https://security.microsoft.com/securescore?viewid=actions ](https://security.microsoft.com/securescore?viewid=actions) for Remove stale service account.
3029

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":::
30+
1. Review the list of exposed entities to discover which of your service accounts are stale and have not performed any login activity in the last 90 days.
3231

3332
1. Take appropriate actions on those entities by removing the service account. For example:
3433

ATPDocs/whats-new.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -42,11 +42,11 @@ Previously, Defender for Identity tenants received Entra ID risk level in the Id
4242

4343
For UEBA tenants without a Microsoft Defender for Identity license, synchronization of Entra ID risk level to the IdentityInfo table remains unchanged.
4444

45-
### New security assessment: Remove inactive service accounts (Preview)
45+
### New security assessment: Remove stale service accounts (Preview)
4646

47-
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 90 days, to help you mitigate security risks associated with unused accounts.
47+
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 stale for the past 90 days, to help you mitigate security risks associated with unused accounts.
4848

49-
For more information, see: [Security Assessment: Remove Inactive Service Accounts (Preview)](remove-inactive-service-account.md)
49+
For more information, see: Security Assessment: [Remove Stale Service Accounts (Preview)](/defender-for-identity/remove-inactive-service-account)
5050

5151
### New Graph based API for response actions (preview)
5252

defender-office-365/outbound-spam-protection-about.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ ms.custom:
1919
- seo-marvel-apr2020
2020
description: Admins can learn about the outbound spam controls in Microsoft 365, and what to do if you need to send mass mailings.
2121
ms.service: defender-office-365
22-
ms.date: 07/07/2025
22+
ms.date: 09/03/2025
2323
appliesto:
2424
- ✅ <a href="https://learn.microsoft.com/defender-office-365/eop-about" target="_blank">Default email protections for cloud mailboxes</a>
2525
- ✅ <a href="https://learn.microsoft.com/defender-office-365/mdo-about#defender-for-office-365-plan-1-vs-plan-2-cheat-sheet" target="_blank">Microsoft Defender for Office 365 Plan 1 and Plan 2</a>
@@ -34,6 +34,9 @@ In all organizations with cloud mailboxes, we take managing outbound spam seriou
3434

3535
This article describes the controls and notifications that are designed to help prevent outbound spam, and what you can do if you need to send mass mailings.
3636

37+
> [!TIP]
38+
> If you're an end-user and your email is blocked or fails to send due to outbound spam protection, you receive a non-delivery report (also known as an NDR or bounce message). This behavior is expected. Only admins can review and resolve these issues, so contact your email admin for assistance.
39+
3740
## What admins can do to control outbound spam
3841

3942
- **Use built-in notifications**: When a user exceeds [sending limits of the service](/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#sending-limits-across-office-365-options) or [outbound spam policies](outbound-spam-policies-configure.md) and is restricted from sending email, the default alert policy named **User restricted from sending email** sends email notifications to members of the **TenantAdmins** group (**Global Administrator** members). To configure who else receives these notifications, see [Verify the alert settings for restricted users](outbound-spam-restore-restricted-users.md#verify-the-alert-settings-for-restricted-users). Also, the default alert policies named **Email sending limit exceeded** and **Suspicious email sending patterns detected** send email notifications to members of the **TenantAdmins** group (**Global Administrator** members). For more information about alert policies, see [Alert policies in the Microsoft Defender portal](alert-policies-defender-portal.md).

exposure-management/predefined-classification-rules-and-levels.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,7 @@ Current asset types are:
3131
| Classification | Asset type | Default criticality level | Description |
3232
| -------------------------- | ---------- | ------------------------- | ------------------------------------------------------------ |
3333
| Microsoft Entra ID Connect | Device | High | The Microsoft Entra ID Connect server is responsible for syncing on-premises directory data and passwords to the Microsoft Entra ID tenant. Compromise could disrupt identity synchronization, leading to authentication issues and potential security breaches. |
34+
| Microsoft Entra ID Cloud Sync | Device | High | The Microsoft Entra ID Cloud Sync agent is responsible for syncing on-premises directory data to the Microsoft Entra ID tenant using lightweight infrastructure. Compromise could disrupt identity synchronization, leading to authentication issues and potential security breaches. |
3435
| ADCS | Device | High | The ADCS server allows administrators to fully implement a public key infrastructure (PKI) and issue digital certificates for securing multiple network resources. Compromise could undermine SSL encryption, user authentication, and secure email, leading to significant security vulnerabilities. |
3536
| ADFS | Device | High | The ADFS server provides users with single sign-on access to systems and applications across organizational boundaries. It uses a claims-based access control authorization model to maintain application security and implement federated identity. Compromise could lead to unauthorized access and data breaches. |
3637
| Backup | Device | Medium | The Backup server is responsible for safeguarding data through regular backups, ensuring data protection and disaster recovery readiness. Compromise could result in data loss and hinder disaster recovery efforts, affecting business continuity. |

0 commit comments

Comments
 (0)