Merge branch 'main' into diannegali-copilotrai

Author: diannegali

.github/workflows/StaleBranch.yml

@@ -5,9 +5,9 @@ permissions:
 
 on:
   schedule:
-    - cron: "0 */12 * * *"
+    - cron: "0 9 1 * *"
 
-  workflow_dispatch:
+  # workflow_dispatch:
 
 
 jobs:
@@ -21,6 +21,6 @@ jobs:
                               "ExampleBranch1",
                               "ExampleBranch2"
                              ]'
-        ReportOnly: true
+        ReportOnly: false
     secrets:
         AccessToken: ${{ secrets.GITHUB_TOKEN }}

.openpublishing.redirection.defender-cloud-apps.json

@@ -1004,6 +1004,11 @@
       "source_path": "CloudAppSecurityDocs/file-filters.md",
       "redirect_url": "/defender-cloud-apps/data-protection-policies",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "CloudAppSecurityDocs/troubleshooting-api-connectors-using-error-messages.md",
+      "redirect_url": "/defender-cloud-apps/troubleshooting-api-connectors-errors",
+      "redirect_document_id": true
     }
   ]
 }

.openpublishing.redirection.defender-endpoint.json

@@ -119,6 +119,11 @@
       "source_path": "defender-endpoint/linux-schedule-scan-mde.md",
       "redirect_url": "/defender-endpoint/schedule-antivirus-scan-crontab",
       "redirect_document_id": true
+    },
+    {
+      "source_path": "defender-endpoint/non-windows.md",
+      "redirect_url": "/defender-endpoint/microsoft-defender-endpoint",
+      "redirect_document_id": true
     } 
   ]
 }

ATPDocs/docfx.json

@@ -38,9 +38,9 @@
       "breadcrumb_path": "/azure-advanced-threat-protection/bread/toc.json",
       "searchScope": ["Defender for Identity"],
       "titleSuffix": "Microsoft Defender for Identity",
-      "author": "batamig",
-      "manager": "batamig",
-      "ms.author": "bagol",
+      "author": "AbbyMSFT",
+      "manager": "AbbyMSFT",
+      "ms.author": "abbyweisberg",
       "ms.collection": "M365-security-compliance",
       "ms.service": "microsoft-defender-for-identity",
       "uhfHeaderId": "MSDocsHeader-MicrosoftDefender",

ATPDocs/identity-inventory.md

@@ -36,13 +36,16 @@ There are several options you can choose from to customize the identities list v
 
 - Apply filters.
 
-- Search for an identity by name or full UPN, Sid and Object ID. 
+- Search for an identity by name or full UPN, SID and Object ID. 
 
 - Export the list to a CSV file.
 
 - Copy list link with the included filters configured. 
 
-## ![A screenshot of identity inventory page.](media/identity-inventory/inventory11.png)  
+> [!NOTE]
+> When exporting the identities list to a CSV file, a maximum of 5,000 identities are displayed.
+
+## ![A screenshot of identity inventory page.](media/identity-inventory/inventory11.png)
 
 ### Identity details 
 
@@ -120,8 +123,7 @@ You can use this information to help you prioritize devices for security posture
 
 ### Navigate to the Identity inventory page
 
-Use relative links instead of absolute links. 
-In the Defender XDR portal at [https://security.microsoft.com](https://security.microsoft.com), go to Assets > Identities. Or, to navigate directly to the [identity inventory](/defender-for-identity/identity-inventory) page.
+In the Defender XDR portal at [https://security.microsoft.com](https://security.microsoft.com), go to **Assets** > **Identities**. Or, to navigate directly to the [identity inventory](/defender-for-identity/identity-inventory) page.
 
 ### Related Articles
 

ATPDocs/media/Screenshot-of-the-connections-page.png

@@ -0,0 +1,103 @@
+---
+title: Service Account Discovery
+description: The Service Accounts page provides a centralized location for customers to view and manage identity information across their environment, ensuring optimal visibility and a comprehensive experience.
+ms.topic: conceptual
+ms.date: 03/25/2025
+---
+
+# Investigate and protect Service Accounts | Microsoft Defender for Identity
+
+### What are Service Accounts?
+
+Service accounts are specialized identities within Active Directory used to run applications, services, and automated tasks. These accounts often require elevated privileges to perform their designated job. However, because they can't authenticate in the same way as human accounts, they typically don't benefit from the increased security of modern authentication methods like MFA (multifactor authentication). Given their potential elevated privilege and the inherent limitations of the access policies that govern them, careful management and monitoring are crucial to ensure they don't become a security vulnerability.
+
+Service accounts are classified into several types:
+
+- gMSA (Group Managed Service Accounts): gMSAs provide a single identity solution for multiple services that require mutual authentication across multiple servers, as they allow Windows to handle password management, reducing administrative overhead.
+- sMSA (Managed Service Accounts): Designed for individual services on a single server rather than groups.
+- User Account: These standard user accounts are typically used for interactive logins but can also be configured to run services.
+
+The auto discovery feature quickly identifies gMSA and sMSA accounts as well as user accounts within Active Directory that meet specific criteria and classifies them as service accounts. These accounts are then highlighted and presented, along with relevant information including insights into recent authentications and the sources and destinations of those interactions, as part of a dedicated inventory within the Defender experience. This helps you better understand the accounts' purpose so you can more easily spot anomalous activity and understand its implications.
+
+Service account types are displayed in the Identity Info table within Advanced Hunting.
+
+## Service accounts page
+
+#### Navigate to the Service accounts page
+
+In the Defender XDR portal at [https://security.microsoft.com](https://security.microsoft.com), go to Identities > Service Accounts.
+
+The following image depicts the Service accounts page:
+
+:::image type="content" source="media/service-accounts-page.png" alt-text="Screenshot of the Service accounts page in the Defender portal." lightbox="media/service-accounts-page.png":::
+
+### Customize the page view
+
+There are several options you can choose from to customize the identities list view. On the top navigation you can:
+
+- Add or remove columns.
+
+- Apply filters.
+
+- Export the list to a CSV file.
+
+- Sort and filter the Service accounts list.
+
+> [!NOTE]
+> When exporting the service accounts list to a CSV file, a maximum of 2,000 service accounts are displayed.
+
+### Service account details
+
+- Total: The total number of service accounts listed.
+
+- Managed: The total number of service accounts that are gMSA (Group Managed Service Accounts) or sMSA (Managed Service Accounts).
+
+- User: The total number of standard user accounts used for interactive logins or configured to run services.
+
+- Critical: The total number of service accounts identified as critical.
+
+You can use the sort and filter functionality on each service account tab to get a more focused view.
+
+| Service account details   |  Description |
+|---------|---------|
+|**Display name** | The full name of the service account as shown in the directory.
+|**SID**     | The Security Identifier, a unique value used to identify the identity in Active Directory.         |
+|**Domain**    | The Active Directory domain to which the identity belongs.         |
+|**Type**    | Specifies if the service account is gMSA (Group Managed Service Accounts), sMSA (Managed Service Accounts) or a user account.         |
+|**Criticality level**     | Indicates the critical level of the service account, ranging from low to very high.         |
+|**Tags**    | Sensitive or Honey Token        |
+|**Auth protocols**   | Lists the available methods for verifying user identities, for example, Kerberos and NTLM (New Technology LAN Manager).         |
+|**Sources**     |  The number of potential source logins.        |
+|**Destinations**    | When a service account is trying to access a destination server, the request is directed to the target system, which can include a number of resources on that server. These resources might be a database, a file server, or other services hosted on the server.        |
+|**Connections**   | The number of unique connections made between sources and destinations.         |
+|**Created**    |The timestamp when the service account was first created.         |
+|**Last updated**    | The timestamp of the most recent update to the service account.        |
+|
+
+### Connections
+
+
+For a deeper dive into what's happening in your service account click on the domain name to see the following information:
+
+When you investigate a specific Service account, you'll see the following details under the connections tab:
+
+:::image type="content" source="media/Screenshot-of-the-connections-page.png" alt-text="Screenshot of the connections page." lightbox="media/Screenshot-of-the-connections-page.png":::
+
+|Service account connection details  |Description |
+|---------|---------|
+|Source  |  Where the network traffic or request originates from.       |
+|Source type    | What kind of device or system is initiating the request. For example, server, workstation or domain controller.        |
+|Source risk   | Identicates the risk posed to the source from no risk to high risk.         |
+|Destination   | Where the request is being directed to. The target system that the service account is trying to access. For example, when trying to access a destination server, there can be multiple resources on that server (for example, a database and a file-server).        |
+|Destination type    | Server, Workstation, or Domain controller.         |
+|Auth protocols   | Kerberos and NTLM        |
+|Service Class     | The services within a network that define the type of service being provided, often used for authentication and resource management. These include: Lightweight Directory Access Protocol (LDAP), Common Internet File System (CIFS), Remote Procedure Call (RPC), Remote Procedure Call Subsystem (RPCSS), "HTTP," Terminal Services (TERMSRV), and "HOST"        |
+|Count | How many sign in events occurred over this connection in the last 180 days.
+Last seen   | The date and time of the most recent sign in event over this connection.        |
+
+
+
+For more information about the following tabs, **Overview**, **Incidents and alerts**,**Observed in organization**, **Timeline**, and **Attack paths**, see: [Investigate assets](/defender-for-identity/investigate-assets#identity-details).
+
+
+If you run into any problems, we're here to help. To get assistance or support for your product issue, see how to open a support ticket at [Microsoft Defender for Identity support](support.md).

ATPDocs/media/service-accounts-page.png

@@ -128,6 +128,8 @@ items:
       href: identity-inventory.md
     - name: Investigate assets
       href: investigate-assets.md
+    - name: Service accounts
+      href: service-account-discovery.md
   - name: Lateral movement paths
     items:
     - name: Understand and investigate lateral movement paths

ATPDocs/service-account-discovery.md

@@ -224,7 +224,7 @@ Suggested possible workarounds:
 
 ## VMware virtual machine sensor issue
 
-If you have a Defender for Identity sensor on VMware virtual machines, you might receive one or both of the following health alerts **Some network traffic is not being analyzed** and **Network configuratuin mismatch for sensors running on VMware**. This can happen because of a configuration mismatch in VMware.
+If you have a Defender for Identity sensor on VMware virtual machines, you might receive one or both of the following health alerts **Some network traffic is not being analyzed** and **Network configuration mismatch for sensors running on VMware**. This can happen because of a configuration mismatch in VMware.
 
 To resolve the issue:
 
@@ -422,7 +422,7 @@ Uninstall the certificate management client, install the Defender for Identity s
 
 >[!NOTE]
 >
->The self-signed certificate is renewed every 2 years, and the auto-renewal process might fail if the certificate management client prevents the self-signed certificate creation.
+> The self-signed certificate is renewed every 2 years, and the auto-renewal process might fail if the certificate management client prevents the self-signed certificate creation.
 > This will cause the sensor to stop communicating with the backend, which will require a sensor reinstallation using the workaround mentioned above.
 
 ## Sensor installation fails due to network connectivity issues
@@ -445,7 +445,6 @@ For more information, see [Run a silent installation with a proxy configuration]
 
 > [!IMPORTANT]
 > Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that aren't present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
->
 
 ## Sensor service couldn't run and remains in Starting state
 
@@ -486,6 +485,22 @@ The issue can come up when a Defender for Identity workspace license expires and
    - "Azure ATP workspaceName Users" -> "Azure ATP workspaceName Users - old"
 1. Then you can go back in the [Microsoft Defender portal](https://security.microsoft.com), to the [Settings](https://security.microsoft.com/securitysettings) -> [Identities](https://security.microsoft.com/settings/identities) section to create the new workspace for Defender for Identity.
 
+## Entra Connect sensor experiences loss of database permissions following the update to Microsoft Entra Connect 
+
+**Cause:**
+
+Updating Microsoft Entra Connect may cause the Entra Connect sensor to lose previously configured database permissions. To investigate, check the Microsoft Defender logs for relevant indicators. Refer to [Troubleshooting Microsoft Defender for Identity sensor using the Defender for Identity logs](troubleshooting-using-logs.md) for log locations and further details.
+
+Sample logs that may indicate the issue:
+
+`GetEntraConnectGlobalSettingsAsync GetEntraConnectGlobalSettingsAsync failed. Exception - The EXECUTE permission was denied on the object 'mms_get_globalsettings', database Contoso', schema 'dbo'`
+
+`GetEntraConnectConnectivityParametersAsync GetEntraConnectConnectivityParametersAsync failed. Exception - The EXECUTE permission was denied on the object 'mms_get_connectors', database Contoso, schema 'dbo'`
+
+**Resolution:**
+
+If permissions need to be reconfigured, please follow the steps outlined in this [guide](deploy/active-directory-federation-services.md).
+
 ## Next steps
 
 - [Defender for Identity prerequisites](deploy/prerequisites.md)