Bastion Cyber Threat Brief | October 25, 2026: ConnectWise Cloud Backup Incident Requires Microsoft 365 Tenant Review

Executive takeaway
ConnectWise’s October 24 update says the company identified unauthorized access to application credentials associated with Cloud Backup, formerly SkyKick. ConnectWise is restoring service in a controlled sequence, but it tells partners to keep affected application connections disabled and review individual Microsoft 365 environments. This is a new status update on an incident first disclosed October 16—not a claim that the incident began this weekend. ConnectWise Trust Center
What happened and when
The official advisory was first published October 16 at 17:47 UTC and was last updated October 24 at 14:00 UTC. ConnectWise says certificate rotation, testing and validation are part of its restoration work. It is targeting phased partner onboarding beginning October 26, subject to successful checks, with backup-restoration access expected before full re-enrollment. Those dates are conditional targets, not guarantees. Latest incident update
ConnectWise says existing backup archives remain encrypted, isolated and preserved, with no indication those archives were compromised. It also says it has no indication that other ConnectWise products or services were affected. These are the vendor’s current findings; they do not independently establish that every partner or customer tenant is unaffected. Vendor statement and limits
Who should pay attention
The update is relevant to partners and customers that use Cloud Backup, including environments still known by the former SkyKick name. ConnectWise’s technical guide is written for authorized Microsoft 365 administrators, security teams and incident responders reviewing both partner tenants and managed customer tenants, including dormant tenants. Technical investigation and remediation guide
Why a business should care
Bastion analysis: Restoring a vendor service does not complete the customer-side investigation. Managed service providers, SaaS firms and growing businesses should assign a named owner for each tenant review and should not treat the reported integrity of stored backup archives as proof that the live Microsoft 365 tenant is clear.
Practical defensive next steps
Keep affected application connections disabled until ConnectWise provides service-specific restoration instructions.
Inventory every partner and managed customer tenant, including dormant tenants, and record who owns each review.
Preserve available Entra sign-in and directory-audit evidence, plus relevant Microsoft Purview audit data, before remediation where practical. Do not delay urgent containment.
Review application identities, credentials, owners, permissions and consent grants; also examine privileged-role changes, Conditional Access changes, Exchange rules and forwarding for unauthorized activity.
Treat an IP address or user-agent match as an investigative lead, not proof of compromise or data access. Escalate confirmed unauthorized credentials, privileged assignments or access through the organization’s incident-response process.
After ConnectWise authorizes restoration, verify workload connections and successful backup jobs, then document the last successful recovery point and any protection gap.
Limits and verification
ConnectWise’s guide says completing its workflow does not by itself prove that a tenant was unaffected or authorize reconnection. This brief does not establish confirmed downstream compromise, identify a threat actor, or claim that any reader was affected. Review the full technical guide
Original disclosure: October 16, 2026, 17:47 UTC. Latest vendor update reviewed: October 24, 2026, 14:00 UTC. Technical guide dated October 18, 2026. Verified as of October 25, 2026, 8:09:09 a.m. Eastern.

Comments