Suspicious DNS activity was observed, originating from {0} (which is not a DNS server). The query was for {1} (type {2}). The response was {3}.
successfully authenticated from {1} against {2} using an unusual protocol implementation. This may be a result of malicious ...
Successfully updated the {0}. Restart the FIM CM IIS worker process and the FIM CM Update service for changes to take effect. ...
Suspicious account enumeration activity using Kerberos protocol, originating from {0}, was detected. The attacker performed ...
Suspicious account enumeration activity using the Kerberos protocol, originating from {0}, was observed and successfully ...
Suspicious DNS activity was observed, originating from {0} (which is not a DNS server). The query was for {1} (type {2}). ...
Synchronization cannot continue. Recurring synchronization will not start until a Synchronize Now has been completed successfully. ...
Synchronization has been stopped. Your company has exceeded the number of objects that can be synchronized. Contact Technical ...
Synchronization is currently disabled. Before a synchronization can occur, you must enable the Azure Active Directory Sync ...
Synchronization items were modified which requires a full Active Directory synchronization. Click OK to synchronize now. ...