TMU Resources

Moving to Microsoft Sentinel: What NHS Organisations Need to Consider

Written by Milla Ross | Nov 20, 2026, 12:34:54 PM

For NHS organisations, the conversation around Microsoft Sentinel is changing.

The question is increasingly less about whether cloud-native security operations have a role to play, and more about how organisations can make the transition in a way that improves visibility, supports existing teams and avoids carrying the limitations of a legacy SIEM into a new platform.

That matters because replacing a SIEM is not simply a technology change.

It can affect how security data is collected, which threats teams can see, how incidents are investigated, how different IT functions work together and how security operations connect with the wider NHS environment.


The short version for busy readers

Moving to Microsoft Sentinel should start with the security outcomes your organisation needs, not the technology you are replacing. For NHS organisations, that means understanding your existing data, integrations and Microsoft estate, deciding what visibility you need, and being realistic about the resource required to operate and optimise the platform.


Table of contents

Why Sentinel is becoming a bigger NHS conversation

Cyber security within the NHS increasingly relies on organisations being able to see threats across complex and highly connected environments.

Endpoints are only part of that picture.

Security teams may need visibility across identities, Microsoft 365, cloud environments, servers, networking, applications and third-party technologies, while also working within wider regional and national security arrangements.

For NHS organisations considering Sentinel, this creates an important distinction.

The objective should not simply be to replace one SIEM with another. It should be to decide what security visibility the organisation needs and what operating model will allow teams to use that information effectively.

 That makes the move to Sentinel as much an operational decision as a technical one. 

 

 

Start with the security outcome, not the SIEM

A SIEM migration can easily become a technology project.

Which connectors are required? How much data needs to move? Which rules need recreating? What needs integrating?

Those questions matter, but they should not be the starting point.

Before considering the architecture, NHS organisations should be clear about what they are trying to improve.

For example:

  • Where do security teams currently lack visibility?
  • Which incidents are difficult or time-consuming to investigate?
  • Which systems, identities and services are most critical?
  • Where are analysts dealing with unnecessary alert volume or manual work?
  • What information needs to be available during an incident?
  • How does the organisation need to work with wider NHS security teams?

Otherwise, there is a risk of recreating the existing SIEM environment on a different platform without addressing the underlying problem. 

Understand what visibility you actually need

 An NHS environment rarely consists of Microsoft technology alone.

A Trust may be using Microsoft Defender across parts of its environment while also operating network security tools, infrastructure platforms, clinical or specialist systems and third-party security technologies.

The SIEM needs to provide useful visibility across that environment.

The question is therefore not simply:

"What can we connect to Sentinel?"

It is:

"Which signals do our security teams need to detect, investigate and respond to the threats that matter?"

The distinction is important.

Connecting every available data source can increase volume and complexity without necessarily improving security. Leaving important systems outside the security picture can create equally significant blind spots.

The right starting point is understanding where the important signals sit today, where visibility is missing and how those signals should support detection and investigation. 

 

Decide what data is worth bringing with you

 A migration also creates an opportunity to question assumptions that have built up over time.

Legacy SIEM environments can contain years of rules, logs, integrations and historic data. It can be tempting to move everything simply because it already exists.

But migration should not automatically mean replication.

Ask:

  • Which log sources genuinely contribute to detection and investigation?
  • Which information needs immediate analysis?
  • What needs longer-term retention?
  • Which historic rules are still relevant?
  • Which integrations still serve a clear security purpose?
  • Is historical SIEM data valuable enough to justify migrating it?

The objective is not to reproduce the old environment as closely as possible.It is to build a security data strategy around what the organisation needs now. 

Look at the Microsoft environment you already have

For NHS organisations with significant Microsoft estates, Sentinel should be looked at as part of the wider security architecture rather than as an isolated SIEM.

Identity, endpoints, cloud services and Microsoft 365 can all provide security signals. Sentinel can then bring those signals together with information from appropriate third-party sources.This matters because the value of a SIEM does not come from collecting data alone.

It comes from helping security teams connect signals that would otherwise sit separately.

An identity event may appear relatively insignificant on its own. The same event combined with unusual endpoint activity, network information or a related security alert can provide analysts with much more useful context.

Before migrating, NHS organisations should therefore map the security capabilities they already have, understand where there is overlap and identify where Sentinel could close genuine visibility gaps. 

Do not underestimate the operational change

Technology is only one part of a successful SIEM migration.

Sentinel can change how security teams investigate incidents, build detections, manage data and work with colleagues across infrastructure, networking, identity and cloud teams.

That creates questions beyond deployment:

  • Who owns the platform?
  • Who will create and maintain analytics rules?
  • How will detections be tuned?
  • What happens when an alert is generated?
  • Which teams need access to the resulting information?
  • How will the environment continue to evolve as threats and infrastructure change?

These decisions determine whether the organisation simply has a functioning SIEM or a security operations capability that continues to improve. 

Plan for skills and capacity, not just technology

This is particularly important for NHS organisations where security teams are already balancing operational demands, transformation programmes and constrained resources.

Implementing Sentinel does not remove the need for skilled people.

Someone still needs to understand the data, investigate incidents, tune detections, develop new use cases and make decisions about how the platform evolves.

The skills question therefore needs to be considered early.

Ask whether your existing team has the time and specialist capability needed to operate the environment effectively. If not, decide where external expertise, additional capacity or managed support could strengthen the internal team.

The goal should be to add capability without creating unnecessary dependency.

What Royal Cornwall Hospitals NHS Trust learnt from moving to Sentinel

Royal Cornwall Hospitals NHS Trust provides a useful example of why these decisions matter.

The Trust moved from Splunk to Microsoft Sentinel as it looked for greater flexibility, visibility and operational efficiency from its security operations.

Rather than simply recreating its previous environment, the Trust worked with Trustmarque Ultima to consider the value of different log types and how that information should be handled within Sentinel.

The Trust also made the decision not to migrate large volumes of historic SIEM data where the complexity involved would have outweighed the likely value.

The move subsequently gave the security team greater flexibility for threat detection and investigation, while consolidated alerting improved visibility across the environment.

The impact also extended beyond thecyber security team. Greater access to security information supported closer collaboration with networking and infrastructure colleagues, helping different teams use the same information to understand activity across the wider IT environment.

That is the more important lesson from a Sentinel migration.

The objective is not simply to change SIEM platforms. It is to create a security operating model that gives teams better information and helps them act on it. 

Six questions to ask before moving to Microsoft Sentinel

 Before making a decision, NHS organisations should be able to answer six practical questions. 

 

Want to understand what Sentinel could mean for your organisation?

In January, Trustmarque Ultima will be hosting a webinar exploring Microsoft Sentinel specifically for NHS organisations.

Rather than a product demonstration, the session will look at the practical considerations behind adopting Sentinel, from data and visibility to migration, skills and operating models.

Pre-register for our Microsoft Sentinel webinar to be among the first to receive the session details and registration information.

 

Frequently Asked Questions (FAQs)

Is Microsoft Sentinel suitable for NHS organisations?
Sentinel can support NHS security operations, particularly where organisations already have significant Microsoft estates. Suitability still depends on the organisation's data requirements, existing technology, integrations, security operating model and internal capabilities.

Do we need to migrate all of our existing SIEM data to Sentinel?
Not necessarily. Organisations should assess the security, operational and compliance value of historical data against the complexity and cost of migrating it. Royal Cornwall Hospitals NHS Trust chose not to migrate large volumes of historic SIEM data where the effort required would have outweighed the expected value.

Can Microsoft Sentinel integrate with non-Microsoft technology?
Yes. Sentinel can ingest security information from Microsoft and appropriate third-party sources. Organisations should prioritise the integrations that provide meaningful detection and investigation value rather than connecting systems simply because the data is available.

Does moving to Sentinel remove the need for specialist security skills?
No. Successful security operations still require people who can manage data, detections, investigations, tuning and ongoing optimisation. Organisations should consider internal capacity and skills alongside the technology decision.

Should an NHS organisation move from Splunk or another SIEM to Microsoft Sentinel?
There is no universal answer. The decision should be based on your current SIEM's performance, data requirements, integrations, Microsoft estate, operating costs, available skills and the security outcomes your organisation needs to achieve.