Paper notebook, phone and parcels on a small business workbench

Dynamic Uplift · Outage readiness

When things go wrong,
keep business moving.

Microsoft 365 goes quiet. A cloud service stops. Your team still has customers to help. An outage does not have to stop the whole working day.

Know what is affected, switch to a safe fallback and keep people informed. A few simple initiatives can make a real difference.

Free Business Selfie assessment. No sign up needed.

When an outage happens

Check. Adapt. Keep people informed.

01 · Confirm the impact

Check the provider's status and your own affected services. Record the incident reference and follow official updates. An outage alone is not evidence of a cyber attack.

02 · Use a safe fallback

Prioritise essential customer work. Use your approved backup channel and manual process. Do not disable security or move sensitive information into unapproved tools.

03 · Update and recover

Name one person to update staff and customers. Once service returns, check access and reconcile work captured during the outage before closing the incident.

Official provider pages open in a new tab. This page does not monitor live outages. Public status pages may not show every issue affecting your organisation.

Find recovery guides and best practices

Less drama.
A little more preparation.

Business resilience is not only about disasters. It is knowing what matters, having another way to work and helping your people respond calmly when the day changes.

During an outage, small choices matter

Small actions. A real difference.

You cannot control every interruption. You can give your business a better way to respond.

Email and Teams are unavailable. Orders are still coming in.

Without a fallback

The team waits for systems to return. Customers are left wondering.

Business resilience

With a little preparation

The shop keeps taking phone orders using a printed form, an offline template or an approved alternative such as Google Docs, if it is available. Each order gets a reference, callback number, item, quantity and collection time. The manager contacts staff by SMS or another agreed channel. When systems return, one person transfers the orders and checks for duplicates.

Choose and test a fallback your team can access without Microsoft: paper, a saved offline file or another provider with an independent sign in. Keep records secure. Never record card details or send customer information by SMS.

What else are you not doing?

Take the free Resilience Selfie

About 5 to 7 minutes. No credit card. No account needed.

Illustrative scenario, not a live incident report. Check which services are actually affected: one Microsoft service being unavailable does not mean every service has stopped.

Five practical initiatives

A fallback, not a filing cabinet.

01

Know what matters first

Identify critical business processes

Not everything needs to keep running at once. Pick the work your customers depend on, who owns it and what it needs to continue.

Start small: list your three most important customer activities.

02

Give the work another way

Develop manual operating procedures

A paper order sheet or an approved phone process can buy you breathing room. Write down a safe fallback before anyone needs it.

Start small: make one order sheet you can use without your usual system.

03

Try it before you need it

Test business continuity with a simulated outage

Talk through a morning without your usual tools. Then safely test one fallback. Find the missing step while customers are not waiting.

Start small: run a short practice without interrupting live services.

04

Keep the conversation going

Establish alternative staff communications

If work email or chat stops, where will everyone meet? Agree an approved alternative, who sends updates and what is safe to share.

Start small: agree one backup channel that everyone can access.

05

Make the right people reachable

Create an emergency contact directory

You should not need a working inbox to call your supplier or team. Keep essential contacts secure, current and accessible independently.

Start small: check that two authorised people can reach the contact list.

Choose fallbacks that suit your business and its safety, privacy and customer obligations. A workaround should not bypass essential controls.

Official resources

Recovery guides, not guesswork.

Start with Microsoft's service checks and practical workarounds. Use the wider cloud guidance with your technology provider to prepare, recover and practise for next time.

Microsoft logo

Microsoft · During an outage

Check Microsoft 365 service health

Confirm known issues and read updates for your organisation before spending time troubleshooting. The detailed dashboard needs an authorised administrator account.

What DU thinks

Check the affected service before changing anything. A provider outage is not a reason to reset every device or switch off security.

Read official guide
Microsoft logo

Microsoft · Keep work moving

Work around Microsoft 365 interruptions

Explore Microsoft's practical alternatives for unavailable email, Teams meetings and files. Choose only options that still work and meet your security requirements.

What DU thinks

A workaround must work without the failed dependency. Test access in advance and keep the same privacy and approval rules.

Read official guide
Microsoft logo

Microsoft · Before the next outage

Build a Microsoft 365 continuity plan

Map the business work that depends on Microsoft 365, decide what matters most and validate your fallback arrangements with your team.

What DU thinks

Start with customer work, not a list of software. Give each essential activity an owner, a fallback and a clear point at which it must pause.

Read official guide
Google Cloud logo

Google Cloud · Respond and recover

Handle a cloud outage step by step

Follow a structured approach: verify the issue, investigate its impact, report it, resolve it and review what happened. Useful for your technology team or provider.

What DU thinks

Give one person ownership of the response and one shared incident record. Separate restoring service from keeping customers informed.

Read official guide
Amazon Web Services logo

Amazon Web Services · Plan recovery

Choose a tested recovery strategy

Technical guidance on backup and restore, standby systems and recovery options. Ask your provider which approach fits your downtime and data loss needs.

What DU thinks

Buy the recovery capability your business actually needs. Ask your provider to demonstrate the agreed restoration time and data recovery point.

Read official guide
Google Cloud logo

Google Cloud · Practise recovery

Test that recovery actually works

Guidance for safely testing backup restoration, rollback and switching to an alternative location. Your technology team should agree the scope before testing.

What DU thinks

A successful backup message is not proof of recovery. Test that restored information is usable and that the people doing the work can access it.

Read official guide

These are external publisher resources, not Dynamic Uplift recovery services or partner endorsements. Technical recovery steps depend on your setup. Confirm them with an authorised administrator or provider.

Your next useful step

What would help your business keep moving?

Take the free Business Resilience Selfie in about 5 to 7 minutes, at your own pace. See the practices you report having in place and the gaps worth exploring. Create an account only when you are ready to build an Action Plan.