Live  /  ESET  /  Incident

ESET: ESET PROTECT's Integration with Microsoft services is not possible.

ESET · eset.comMinor incidentResolved2026-10-01 08:06 UTC
Public — what happened

Summary

ESET said that connecting its ESET PROTECT product with Microsoft services was not working, with users who were sent to Microsoft to grant consent getting an error saying a connector could not be created. The company began investigating on September 24, 2026 at 23:08 UTC. On September 28, ESET said it had received only a single report and that the problem appeared limited to one customer, with no sign of wider impact, and it moved the incident to monitoring. ESET did not name a cause, and the incident was marked resolved on October 1, 2026.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach ESET against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for ESET: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the ESET report →

More from ESET

Covered in The Squid’s Ink, Week 40, 2026, our weekly internet health report.

The full archive is on the ESET status & history page.

Related: ESET status & history. SquidGrid is not affiliated with ESET.