Blog Post

Microsoft Security Community Blog
5 MIN READ

Planning your move to Microsoft Defender portal for all Microsoft Sentinel customers

TomerBrand's avatar
TomerBrand
Icon for Microsoft rankMicrosoft
Jul 01, 2025

In November 2023, Microsoft announced our strategy to unify security operations by bringing the best of XDR and SIEM together. Our first step was bringing Microsoft Sentinel into the Microsoft Defender portal, giving teams a single, comprehensive view of incidents, reducing queue management, enriching threat intel, streamlining response and enabling SOC teams to take advantage of Gen AI in their day-to-day workflow. Since then, considerable progress has been made with thousands of customers using this new unified experience; to enhance the value customers gain when using Sentinel in the Defender portal, multi-tenancy and multi-workspace support was added to help customers with more sophisticated deployments.

Our mission is to unify security operations by bringing all your data, workflows, and people together to unlock new capabilities and drive better security outcomes. As a strong example of this, last year we added extended posture management, delivering powerful posture insights to the SOC team. This integration helps build a closed-loop feedback system between your pre- and post-breach efforts. Exposure Management is just one example. By bringing everything together, we can take full advantage of AI and automation to shift from a reactive to predictive SOC that anticipates threats and proactively takes action to defend against them.

Beyond Exposure Management, Microsoft has been constantly innovating in the Defender experience, adding not just SIEM but also Security Copilot. The Sentinel experience within the Defender portal is the focus of our innovation energy and where we will continue to add advanced Sentinel capabilities going forward.

Onboarding to the new unified experience is easy and doesn’t require a typical migration. Just a few clicks and permissions. Customers can continue to use Sentinel in the Azure portal while it is available even after choosing to transition. 

Today, we’re announcing that we are moving to the next phase of the transition with a target to retire the Azure portal for Microsoft Sentinel by July 1, 2026.  Customers not yet using the Defender portal should plan their transition accordingly.

 

Microsoft Sentinel in the Microsoft Defender portal

“Really amazing to see that coming, because cross querying with tables in one UI is really cool! Amazing, big step forward to the unified [Defender] portal.” 

Glueckkanja AG 

“The biggest benefit of a unified security operations solution (Microsoft Sentinel + Microsoft Defender XDR) has been the ability to combine data in Defender XDR with logs from third party security tools. Another advantage developed has been to eliminate the need to switch between Defender XDR and Microsoft Sentinel portals, now having a single pane of glass, which the team has been wanting for some years.” 

Robel Kidane, Group Information Security Manager, Renishaw PLC 

Delivering the SOC of the future

Unifying threat protection, exposure management and security analytics capabilities in one pane of glass not only streamlines the user experience, but also enables Sentinel customers to realize security outcomes more efficiently: 

  • Analyst efficiency: A single portal reduces context switching, simplifies workflows, reduces training overhead, and improves team agility. 
  • Integrated insights: SOC-focused case management, threat intelligence, incident correlation, advanced hunting, exposure management, and a prioritized incident queue enriched with business and sensitivity context—enabling faster, more informed detection and response across all products.
  • SOC optimization: Security controls that can be adjusted as threats and business priorities change to control costs and provide better coverage and utilization of data, thus maximizing ROI from the SIEM. 
What’s next: Preparing for the retirement of the Sentinel Experience in the Azure Portal

Microsoft is committed to supporting every single customer in making that transition over the next 12 months. Beginning July 1, 2026, Sentinel users will be automatically redirected to the Defender portal. 

After helping thousands of customers smoothly make the transition, we recommend that security teams begin planning their migration and change management now to ensure continuity and avoid disruption. While the technical process is very straightforward, we have found that early preparation allows time for workflow validation, training, and process alignment to take full advantage of the new capabilities and experience.

Tips for a Successful Migration to Microsoft Defender

1. Leverage Microsoft’s help:

Leverage Microsoft documentation, instructional videos, guidance, and in-product support to help you be successful. A good starting point is the documentation on Microsoft Learn. 

 

2. Plan early:

Engage stakeholders early including SOC and IT Security leads, MSSPs, and compliance teams to align on timing, training and organizational needs. Make sure you have an actionable timeline and agreement in the organization around when you can prioritize this transition to ensure access to the full potential of the new experience.

 

3. Prepare your environment:

Plan and design your environment thoroughly. This includes understanding the prerequisites for onboarding Microsoft Sentinel workspaces, reviewing and deciding on access controls, and planning the architecture of your tenant and workspace. Proper planning will ensure a smooth transition and help avoid any disruptions to your security operations.

 

4. Leverage Advanced Threat Detection:

The Defender portal offers enhanced threat detection capabilities with advanced AI and machine learning for Microsoft Sentinel. Make sure to leverage these features for faster and more accurate threat detection and response. This will help you identify and address critical threats promptly, improving your overall security posture.

 

5. Utilize Unified Hunting and Incident Management:

Take advantage of the enhanced hunting, incident, and investigation capabilities in Microsoft Defender. This provides a comprehensive view for more efficient threat detection and response. By consolidating all security incidents, alerts, and investigations into a single unified interface, you can streamline your operations and improve efficiency.

6. Optimize Cost and Data Management

The Defender portal offers cost and data optimization features, such as SOC Optimization and Summary Rules. Make sure to utilize these features to optimize your data management, reduce costs, and increase coverage and SIEM ROI. This will help you manage your security operations more effectively and efficiently.

Unleash the full potential of your Security team 

The unified SecOps experience available in the Defender portal is designed to support the evolving needs of modern SOCs. The Defender portal is not just a new home for Microsoft Sentinel - it’s a foundation for integrated, AI-driven security operations.

We’re committed to helping you make this transition smoothly and confidently. If you haven’t already joined the thousands of security organizations that have done so, now is the time to begin.

Resources
Updated Jul 03, 2025
Version 3.0

21 Comments

  • 1357924680's avatar
    1357924680
    Brass Contributor

    I understand the appeal of the illusive "single pane of glass" for IT Security tools, but the amount of bugs / issues in Defender XDR is frustrating and is hopefully being taken into consideration. The number of tickets we have to open for issues in Defender XDR is only increasing, while I can't even remember the last time I opened a ticket for Sentinel; Sentinel just works. 

    Let's just be honest here, Microsoft's track record with product portal consolidations is simply not good. Please stop making changes for the sake of change and consider giving customers the option to leave the management of Sentinel in Azure or prioritize stabilizing Defender XDR. 

  • GernotBaar's avatar
    GernotBaar
    Copper Contributor

    It all seems like a bit of a mess at the moment when you connect Sentinel to Defender, surely Microsoft should have also considered to add permission management for Sentinel access to the Defender portal as well at the same time as the connect feature. It seem very silly that you have to use the roles in azure to to control the Sentinel access.
    We have also noticed that once Sentinel is connected and Incidents are in the Defender Portal it completely ignores the Sentinel Incident grouping configuration and keep adding unless the Incident is closed...
    I like the idea to have one portal, but in reality it will never be one portal if some configuration aspects are needed in Azure like resource group and workspace...

  • DBoughton's avatar
    DBoughton
    Copper Contributor

    Please tell me you're planning on having an auto-refresh on the Defender incident page similar to that in Sentinel?

  • Lewisguy35's avatar
    Lewisguy35
    Copper Contributor

    Hey, will you be making the Defender portal a functional experience prior to this timeline? Dear god Microsoft, talk to an MSSP about this please... Consider that MSSPs are a large portion of your market currently and Defenders UI is a **bleep**ing uphill struggle.

    • 1357924680's avatar
      1357924680
      Brass Contributor

      My thoughts as well. Defender XDR is buggy, Sentinel is not. This seems like yet another Microsoft change for the sake of change. 

  • bjamin's avatar
    bjamin
    Copper Contributor

    How is this going to work for MSSPs who access Sentinels through Azure Lighthouse if GDAP is not supported?

  • BCoxSecureSky's avatar
    BCoxSecureSky
    Copper Contributor

    Is there yet a solution for companies using Azure Lighthouse to support multiple Sentinel instances?

  • kaloszer's avatar
    kaloszer
    Copper Contributor

    retire the Azure portal for Microsoft Sentinel

    Does this mean that all the resources will no longer reside in Azure? What happens to all Infrastructure-as-code (bicep) that deploys all the dependencies for Sentinel such as LAW/Sentinel enablement/DCR/DCE/Analytic rules/Hunts and others?

    Will logic apps still be possible to be called from XDR?  

    GDAP according to docs still say that 'GDAP Iisn't supported for Microsoft Sentinel data' - will that change? This is a blocker for MSPs' to actually migrate fully to the unified XDR platform.

    • bjamin's avatar
      bjamin
      Copper Contributor

      You will still need Lighthouse for CI/CD but B2B guest accounts for Sentinel access through Defender with users needing both Azure RBAC roles and tenant based permissions.

    • bjamin's avatar
      bjamin
      Copper Contributor

      We raised the MSSP access issue with Microsoft and had it escalated to the product group. The response was, traditional centralised MSSP access methods like GDAP and Lighthouse will no longer work for Sentinel access, B2B guest accounts with Defender and Sentinel permissions will need to be managed in every customer tenant.

      Needless to say, abandoning these centralised access methods is a huge blow to MSSPs and introduces a host of compliance and security challenges along with administrative overhead.

       

      • john66571's avatar
        john66571
        Iron Contributor

        Actually, we (as MSSP) do not use any of that. We always deploy everything in the customers environment so they own everything. Thats the right thing to do. And we manage everything through DevOps connection (or others through github) - such as Analytic rules, Workbook, Playbooks. But we still need to login in the customer tenant to do some configuration things, such as Azure policies for some of the connectors, checking costs, deploying MI's and granting them unique access. Also attaching them to specific playbooks and some other configuration related parts to resources in Azure. 

    • john66571's avatar
      john66571
      Iron Contributor

      I came here for this exact question - as a MSSP we deploy a lot of things through DevOps - and we manage resources (such as logic apps, connectors, Managed identities, DCR rules and much much more) which are locked down in a subscription. Then on top of that all the cost optimization. 

      If i understand correctly, all this will remain exactly the same - but then i dont understand the "big news" about this. Then the whole heart of Sentinel is STILL in azure portal. In Unified security operation platform (formley xdr) its only alerts, incident and some insight into the alerting logic/connectors etc. All the cost and resources will still be in Azure Portal, in a resourcegroup, controlled by rbac and entra roles. Yes?

      • Dean_Gross's avatar
        Dean_Gross
        Silver Contributor

        john66571​ FYI, I was in a meeting yesterday in which MSFT provided the following information about product naming, I realize that is does not address you fundamental question, I think you may find it of some help.