← Blog

Microsoft 365 connectivity report: practical steps for New Zealand businesses

A report of users being unable to connect to multiple Microsoft 365 services has not been independently verified in public Microsoft documentation. Here is how New Zealand businesses can check their tenant status, communicate during disruption, and avoid unnecessary configuration changes.

Published 13/11/2026 · EdgePoint IT Solutions

Illustration: laptop office
AI-generated illustration · OpenAI

What is known

A report has indicated that users may be unable to connect to multiple Microsoft 365 services. However, the available official public sources do not confirm an incident ID, affected services, New Zealand impact, subscription scope, cause, workaround or restoration timeframe.

This does not mean the report is incorrect. Microsoft notes that tenant-authenticated Service Health information is more accurate than its public status information because it recognises the tenant and services being managed. Microsoft 365 incident readiness guidance

Before communicating an outage internally or making technical changes, confirm what is occurring in your own Microsoft 365 tenant.

Check Microsoft 365 Service Health first

Microsoft identifies Health > Service health in the Microsoft 365 admin centre as the primary location for tenant-specific incident information. The page can show active incidents, affected services, estimated start times, user impact, status updates and resolved issue history. Service Support and Helpdesk administrators can view this information. Microsoft’s Service Health guidance

Ask an authorised administrator to record:

  • the incident ID
  • the Microsoft 365 services listed as affected
  • the stated user impact
  • the estimated incident start time
  • Microsoft’s latest update or mitigation advice
  • whether the issue appears limited to particular users, locations, devices or applications.

If Service Health does not show a matching incident, Microsoft advises using Report an issue in Service Health or opening a support request. If an incident is already listed, Service Health should contain Microsoft’s latest recovery and mitigation updates. Microsoft 365 incident readiness guidance

Use the public status page only as a fallback

If an active issue prevents access to the Microsoft 365 admin centre or Service Health, Microsoft directs organisations to its public status page at status.cloud.com. Microsoft also cautions that the authenticated Service Health view is the more accurate source for a specific tenant. Microsoft 365 incident readiness guidance

For a business, this distinction matters: a public status page may not reflect the exact services, region or configuration relevant to your organisation.

Avoid assuming the cause

A multi-service connectivity issue can affect email, meetings, files, collaboration and administration, depending on which services are involved. But the cause should not be assumed.

Microsoft’s monitoring guidance distinguishes between issues involving Microsoft infrastructure, third-party dependencies and customer-controlled infrastructure. Microsoft 365 monitoring guidance

Until the scope is clear, avoid making broad changes to DNS, identity settings, firewalls or endpoint configurations. First, check whether the problem is consistent across:

  • office and remote locations
  • wired and wireless connections
  • different internet providers
  • browser and desktop applications
  • different user accounts and devices.

This can help separate a tenant or service issue from a local network, device or configuration problem.

Keep business operations moving

For New Zealand organisations, the priority during a cloud-service disruption is maintaining business continuity. The National Cyber Security Centre recommends response planning and testing for system and service failures, including cloud services. NCSC response planning guidance

Practical actions may include:

  1. Activate an agreed communication channel. Use mobile calls, SMS or another pre-agreed method if normal collaboration tools are unavailable.
  2. Assign clear roles. Identify who is checking Service Health, who is communicating with staff, and who is recording operational impact.
  3. Prioritise critical work. Identify time-sensitive customer communications, payments, bookings, service delivery or regulatory obligations that may need an alternative process.
  4. Record evidence. Keep timestamps, screenshots, error messages, affected users and disrupted business processes for escalation and later review.
  5. Provide measured updates. Tell staff what is confirmed, what is still being investigated and when the next update will be provided.

The NCSC advises organisations to have backup communication methods and clear responsibilities in place for disruptions. NCSC guidance on communicating under pressure

Review after service is restored

Once normal service has returned, review the incident while details are still available. Consider:

  • Which business processes were disrupted?
  • Did staff know where to find updates?
  • Were alternative communications effective?
  • Did the organisation have clear decision-makers and escalation contacts?
  • Are there manual procedures that should be documented for future cloud-service disruption?

A tested response plan can help reduce confusion when a service failure affects day-to-day operations. NCSC response planning guidance

A note on this reported event

The supplied report and timestamp have not been independently verified through publicly indexed official Microsoft documentation. Businesses should confirm their tenant’s live Service Health status before treating the event as a Microsoft-wide, New Zealand-wide, Business-plan-specific or Enterprise-plan-specific outage.

This draft requires human review before publication, including confirmation of any live incident ID, affected services and Microsoft-provided guidance.

Frequently asked questions

Where can we check whether Microsoft 365 is affecting our organisation?

An authorised administrator can check Health > Service health in the Microsoft 365 admin centre. Microsoft says this tenant-specific view can show active incidents, affected services, user impact, updates and resolved issue history.

What should we do if Microsoft 365 Service Health is unavailable?

Microsoft advises using its public status page as a fallback when an active issue prevents access to the Microsoft 365 admin centre or Service Health. The authenticated Service Health view remains the more accurate source for the tenant when it is available.

Should we change DNS, firewall or identity settings during a Microsoft 365 connectivity issue?

Not before confirming the scope of the issue. Check whether the problem affects different users, locations, networks, devices and applications first, because Microsoft monitoring guidance distinguishes between Microsoft infrastructure, third-party dependencies and customer-controlled infrastructure.

How can a business communicate if Microsoft 365 collaboration tools are unavailable?

Use pre-agreed alternatives such as mobile calls, SMS or another backup communication channel. NCSC guidance also recommends clear roles and communication plans for service disruptions.