Cybersecurity

Your Backup Vendor's Key Got Stolen: What the ConnectWise Cloud Backup Incident Means for Microsoft 365 Offices

Updated Nov. 4, 2026: ConnectWise says phases 1–2 of Cloud Backup restoration are complete and phases 3–4 are partial. Partners still must re-authorize each Microsoft 365 tenant, verify new snapshots, and not re-enable old apps.

A conference table with an open laptop showing a generic checklist, a printed tenant review checklist with checkmarks, a legal pad and a coffee mug

Updated Nov. 4, 2026 (18:55 UTC). This version replaces our Oct. 28 update and keeps the background and checklist below.

Update, November 4, 2026: Phases 1–2 complete; phases 3–4 still partial

In its November 4 update (18:55 UTC), ConnectWise said restoration of Cloud Backup, formerly SkyKick, continues. Many partners have re-enrolled their tenants, and ConnectWise says it is focused on helping the remaining partners reconnect and resume protection.

Since the prior update, ConnectWise says Backup Health reporting, Export jobs, and Marketplace APIs have become available. Billing and other remaining capabilities are still being restored. ConnectWise still says: if you have not yet re-authorized your customer tenants, take action now — re-authorization is required to resume Microsoft 365 backups and restores.

  • Phase 1 complete — Backups and restores: Backup and restore capabilities are available for re-authorized Microsoft 365 tenants.
  • Phase 2 complete — Customer access and monitoring: The End-Customer Self-Service Portal and Backup Monitoring dashboards are available.
  • Phase 3 partially complete — Reporting and additional features: Backup Health reporting and Export jobs became available on November 3. Billing functionality, including the Billing API and Management portal billing reports, remains in progress.
  • Phase 4 partially available — Notifications: Core notifications are live. Additional notifications are being enabled gradually to reduce excessive alerts during recovery.
  • Additional service availability: Marketplace APIs restored November 3; Migrations restored October 28; SaaS Security and Cloud Automation fully restored (partners must reconnect Microsoft 365 and Azure integrations using ConnectWise's technical reconnection guidance). The platform backup dashboard is not yet fully restored.
  • Actions for partners (unchanged in substance): Sign in to the Cloud Services portal (reset password and complete MFA if using username/password; Microsoft 365 sign-in needs a tenant admin to consent to the new portal app). Re-authorize each Microsoft 365 tenant with ConnectWise Cloud Backup for M365. Verify that new snapshots complete successfully — re-authorization alone does not confirm backups are running. Snapshot history will reflect the gap between the last successful backup before the interruption and the first successful backup after service resumes.
  • Old apps stay off: "Do not re-enable previously disabled applications unless ConnectWise specifically instructs you to do so." Continue following published investigation guidance for your own and managed customer environments.

ConnectWise's FAQ as of this update says that as of November 4, all services have been restored except billing services (including APIs), some elements of the ConnectWise Platform Backup Dashboard, and notifications. We are summarizing the Trust Center wording only; we are not inventing encryption, PHI, payment-card, or customer-data-theft claims beyond what ConnectWise and Microsoft have published.

The attacker and the data question

On October 21, Microsoft said it assesses that Storm-0940, a group it describes as China-state-aligned, was responsible. ConnectWise says that, based on its evidence including Microsoft's threat intelligence, "it appears that a China state-aligned group was responsible." On October 26, Huntress said its telemetry is "consistent with Microsoft's findings, though we cannot verify it independently." Huntress also noted that Microsoft Graph reads are not recorded in the Entra audit log and that "no victim we know of had Graph activity logging enabled." In other words, logs may not show whether data was read in a given tenant. No source has confirmed customer data theft, and Microsoft says a successful sign-in "does not necessarily indicate" that data was accessed.

Background

ConnectWise suspended Cloud Backup (formerly SkyKick) on October 17. By October 18 it had also taken SaaS Security and Cloud Management offline as a precaution, because they are integrated with Cloud Backup. ConnectWise says it discovered the problem on October 14, then disabled seven application identities and revoked certificates. Huntress reported that the Cloud Backup credential was used from 144.172.64.128 on October 15, with sign-in activity in nearly 1,000 Entra tenants, more than 300 of them successful. Microsoft says the group attempted sign-ins to more than 2,250 tenants. In some environments, Microsoft says, the activity went on to change application credentials and make "changes involving identities, groups, and privileged roles." It warns those changes "can remain active as a backdoor" after the original app is fixed. Huntress says it saw no identity or group changes in the two tenants where it holds directory audit logs. Disabling the vendor apps stops new sign-ins, but it doesn't undo what was already changed.

The takeaway

Phases 1 and 2 are complete, but billing, some notifications, and the platform backup dashboard are still catching up. Have your IT provider re-authorize each tenant with the new app, not the old ones, then confirm new snapshots actually complete. Keep reviewing admin roles, app consents and sign-ins: a reconnected tenant isn't the same as a clean one.

Checklist for this week

  1. Reconnect with the new app only. Your IT provider resets its Cloud Services portal password, sets up MFA and re-authorizes each Microsoft 365 tenant with ConnectWise Cloud Backup for M365, following ConnectWise's linked instructions on its Trust Center. Keep the old disabled apps off: match on application ID, not display name, don't delete them, and don't re-enable them unless ConnectWise specifically says to.
  2. Keep going with the tenant review. ConnectWise says re-authorizing doesn't replace it. Search sign-in logs, including service-principal sign-ins, from at least October 13 (back to October 1 where records exist) for these published addresses: 144.172.64.128, .99 and .60, plus the three VPN addresses Microsoft lists for October 15–16: 187.15.88.186, 187.15.90.217 and 187.15.89.186. A match calls for investigation but doesn't by itself prove compromise. Review admin roles, app secrets and certificates, consents, Conditional Access changes, mail forwarding and inbox rules.
  3. Write your restore list. List the mailboxes, OneDrive accounts, SharePoint sites and Teams data you'd restore first, and the last good recovery point for each.
  4. Name who reconnects and who approves. Confirm your IT provider is watching the Trust Center and knows who signs off on re-authorizing each tenant.
  5. Verify new backups. Once backups are available for a tenant, confirm new snapshots complete successfully, since ConnectWise says re-authorization alone doesn't confirm backups have resumed. Then recheck for unexpected app credentials or roles.
  6. Cover the gap. Ask what stopgap protection is in place until backups resume for each tenant, and note the gap in snapshot history.

How Brotherly Technology can help

Brotherly Technology helps small businesses, law firms and accounting offices in Rome, Northwest Georgia and beyond review Microsoft 365 tenants after vendor incidents and plan backup continuity. If you want a second set of eyes on your restore plan, give us a call.

Sources

One accountable technology partner.

Tell us what's slowing your team down. We'll show you exactly how we'd fix it — no pressure, no jargon.

Book a Free Consultation
Book a Free Consultation