Glassbreak and Hudu: Independent MSP Recovery

Hudu and Glassbreak solve different jobs. An MSP can continue using Hudu as its normal documentation environment while placing the small, critical emergency set in Glassbreak.

What belongs in the emergency layer

• Who declares and leads the incident.
• How responders communicate without the normal collaboration suite.
• How emergency client access is approved and recovered.
• Which clients and services depend on the failed vendor.
• Which manual workarounds are authorised.
• How exercise and incident evidence is retained.

The goal is not to duplicate every asset and process. It is to retain enough trusted information to make the next emergency decision when the everyday path is unavailable.

Prove independence

A tabletop should begin without an active Hudu, primary identity-provider, or normal vault session. Verify that the team can establish communications, locate the affected client, recover controlled access, execute the first response steps, and create a reviewable record.

See the MSP vendor-failure readiness workflow, then run the free Microsoft 365 outage assessment.