Now that the September 2021 Cumulative Updates (CUs) for Exchange Server 2019 and Exchange Server 2016 have been released, customers around the world now have access to a new security feature in Exch...
Updated Oct 01, 2021
Version 1.0
Blog Post
error for Mitigation Service :
id : 1008
An unexpected exception occurred. Diagnostic information:
Exception encountered while fetching mitigations : System.Exception: This XML is not deemed safe to consume since Response xml's signing cert is invalid or not from microsoft
bei Microsoft.Exchange.Mitigation.Service.Common.SignatureVerifierUtils.ThrowIfIntegrityChecksFail(SafeXmlDocument xmlDoc)
bei Microsoft.Exchange.Mitigation.Service.Common.SignatureVerifierUtils.GetValidatedDocumentWithoutSignature(SafeXmlDocument xmlDoc)
bei Microsoft.Exchange.Mitigation.Service.Common.Utils.FetchDataFromXmlStream[T](Stream stream)
bei Microsoft.Exchange.Mitigation.Service.Common.Utils.FetchMitigationsFromUrl[T](String url, RemoteCertificateValidationCallback certValidationCallback, X509Certificate clientAuthCert, Boolean isResponseJson)
bei Microsoft.Exchange.Mitigation.Service.MitigationCloudServiceV2.FetchMitigations()
bei Microsoft.Exchange.Mitigation.Service.Mitigations.MitigationEngine.FetchAndApplyMitigation()
id 4999
Watson report about to be sent for process id: 5824, with parameters: E12IIS, c-RTL-AMD64, 15.01.2375.007, M.E.Mitigation.Service, M.E.Mitigation.Service, M.E.M.S.C.SignatureVerifierUtils.GetValidatedDocumentWithoutSignature, System.Exception, 9784-dumptidset, 15.01.2375.007.
ErrorReportingEnabled: False
The mitigation Test is ok :
[PS] C:\Program Files\Microsoft\Exchange Server\V15\scripts>.\Test-MitigationServiceConnectivity.ps1
Result: Success.
Message: The Mitigation Service endpoint is accessible from this computer.
what's the Problem ?