You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ATPDocs/troubleshooting-known-issues.md
+18-3Lines changed: 18 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -224,7 +224,7 @@ Suggested possible workarounds:
224
224
225
225
## VMware virtual machine sensor issue
226
226
227
-
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.
227
+
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.
228
228
229
229
To resolve the issue:
230
230
@@ -422,7 +422,7 @@ Uninstall the certificate management client, install the Defender for Identity s
422
422
423
423
>[!NOTE]
424
424
>
425
-
>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.
425
+
>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.
426
426
> This will cause the sensor to stop communicating with the backend, which will require a sensor reinstallation using the workaround mentioned above.
427
427
428
428
## Sensor installation fails due to network connectivity issues
@@ -445,7 +445,6 @@ For more information, see [Run a silent installation with a proxy configuration]
445
445
446
446
> [!IMPORTANT]
447
447
> 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.
448
-
>
449
448
450
449
## Sensor service couldn't run and remains in Starting state
451
450
@@ -486,6 +485,22 @@ The issue can come up when a Defender for Identity workspace license expires and
486
485
- "Azure ATP workspaceName Users" -> "Azure ATP workspaceName Users - old"
487
486
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.
488
487
488
+
## Entra Connect sensor experiences loss of database permissions following the update to Microsoft Entra Connect
489
+
490
+
**Cause:**
491
+
492
+
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.
493
+
494
+
Sample logs that may indicate the issue:
495
+
496
+
`GetEntraConnectGlobalSettingsAsync GetEntraConnectGlobalSettingsAsync failed. Exception - The EXECUTE permission was denied on the object 'mms_get_globalsettings', database Contoso', schema 'dbo'`
497
+
498
+
`GetEntraConnectConnectivityParametersAsync GetEntraConnectConnectivityParametersAsync failed. Exception - The EXECUTE permission was denied on the object 'mms_get_connectors', database Contoso, schema 'dbo'`
499
+
500
+
**Resolution:**
501
+
502
+
If permissions need to be reconfigured, please follow the steps outlined in this [guide](deploy/active-directory-federation-services.md).
503
+
489
504
## Next steps
490
505
491
506
- [Defender for Identity prerequisites](deploy/prerequisites.md)
0 commit comments