Blog Post

Microsoft Defender XDR Blog
5 MIN READ

Monthly news - July 2026

HeikeRitter's avatar
HeikeRitter
Icon for Microsoft rankMicrosoft
Jul 01, 2026

Microsoft Defender
Monthly news - July 2026 Edition

This is our monthly "What's new" blog post, summarizing product updates and various new assets we released over the past month across our Defender products. In this edition, we are looking at all the goodness from June 2026. We are now including news related to Defender for Cloud in the Defender portal. For all other Defender for Cloud news, have a look at the dedicated Defender for Cloud Monthly News here. 

🚀 New Virtual Ninja Show episode:

Weekly Security News: We publish a short 1ish minute video every week with updates across our Microsoft Security stack. Subscribe to our YouTube channel, so you don't miss the next episode. 

Actionable threat insights (find all of them here)

Microsoft Defender

  • Two Workbooks capabilities in the unified Microsoft Defender portal moved to GA:
    • Advanced Hunting connector - build custom dashboards directly on top of Advanced Hunting (XDR) dat. Query XDR tables and visualize them in Workbooks for richer investigations and reports.
    • Workspace filter / multi-workspace experience - scope and filter workbooks by workspace, with workspace selection integrated into the workbook itself rather than relying on the global selector.
  • MTO Tenant Groups let MSSPs and large enterprises organize their multitenant view in Microsoft Defender by grouping tenants logically (e.g., by region, business unit, or customer cohort). Learn more here. 
  • Custom Detections support in Microsoft Sentinel Repositories. Custom Detections can now be managed as code in Microsoft Sentinel Repositories, the same way customers already manage analytic rules, playbooks, parsers and workbooks. Detection engineers connect a GitHub or Azure DevOps repo to their workspace; Custom Detections placed in the repo are reconciled on every commit. A standalone Bicep path via the Microsoft Security Bicep extension lets teams deploy from any CI/CD pipeline (ADO Pipelines, GitHub Actions, custom runners).

  • (General Availability) The following advanced hunting schema tables are now generally available:

    • The CloudAuditEvents table contains information about cloud audit events for various cloud platforms protected by the organization's Defender for Cloud.

    • The CloudDnsEvents table contains information about DNS activity events from cloud infrastructure environments.

    • The CloudProcessEvents table contains information about process events in multicloud hosted environments.

  • (Public Preview) The AgentsInfo table in advanced hunting is now available in preview. The AIAgentsInfo table is transitioning to this new table, which provides a unified schema that supports agent inventory and governance for all agent types, including Copilot Studio, Microsoft Foundry, Microsoft 365 Copilot, third-party, and endpoint-discovered agents. Microsoft Agent 365 customers should use the AgentsInfo table today. The AIAgentsInfo table remains accessible until July 1, 2026. Update your queries to use AgentsInfo before this date. For more information, see Advanced hunting schema - Naming changes.

  • For all other Sentinel News, have a look at the "What's new in Microsoft Sentinel blog post - June edition"

 

Identity Security

  • (Public Preview) The Identity Security dashboard now includes a new Human identities card that shows your human identities by source (Entra ID, SaaS, and on-premises), giving you a single view of where your human identities live. For more information, see Identity Security dashboard.
Identity Security dashboard overview
  • (Public Preview) On the Coverage and maturity page, the Review and improve coverage side panel for SaaS Identities now includes an Observed column and a Show Only Observed Applications toggle. By default, the panel shows only SaaS applications detected in your environment. Turn off the toggle to see other supported SaaS applications you can onboard to expand your identity coverage. For more information, see Coverage and maturity.
  • New alerts were added to the Defender for Identity security alerts related to Microsoft Entra ID, Active Directory as well as other identity providers. For a full list of those new alerts, check out our documentation.

  • Recent ShinyHunters attacks on Salesforce show how OAuth tokens and connected apps are being weaponized to bypass MFA at scale. The upgraded Salesforce connector for Defender for Cloud Apps helps detect these attacks faster, with richer connected-app context and investigation-ready signals. Customers already using the connector are advised to enable the additional events in the Salesforce console for tighter protection, and eligible customers not yet using it are advised to connect Salesforce. Learn more.

 

Microsoft Defender for Endpoint / Microsoft Defender Vulnerability Management

  • (Public Preview) Local AI agent discovery: as part of the Defender AI agents experience, Microsoft Defender now automatically discovers supported local AI agents running on onboarded Windows & macOS devices. Discovered agents appear as assets in the AI agent inventory, exposure map, and advanced hunting, giving security teams visibility into local AI agent usage across the organization. For more information, see Discover local AI agents.

    AI Assets page

     

  • (Preview) Local AI agent runtime protection on Windows endpoints is now available in public preview. Microsoft Defender inspects the agent loop (user prompts, tool calls, and tool responses) and can block risky activity before it executes, helping stop prompt injection and unsafe agent actions at the device level. Blocked and audited events appear as alerts in Microsoft Defender to support incident correlation and investigation workflows.

  • The new version of the Defender deployment tool for Windows streamlines onboarding and enhances security by:

    • Bundling the onboarding package directly into the tool's executable.

    • Generating a key during deployment package creation that is required for running the tool.

    • Enabling users to configure an expiry date for the package to reduce the risk of unauthorized use.
      In addition:

    • You have the option of downloading the package as either an .exe or a .zip file, whichever best suits your organization's needs.

    • A new Deployment packages page in the Defender portal facilitates management of downloaded packages by providing centralized visibility into all the packages and their current status.

  • Now generally available: Selective Response Actions enables organizations to tailor high-impact security operations on devices during onboarding. It provides precise control over how response actions are applied on Tier-0 systems and other high-value assets, helping maintain operational stability while delivering strong protection.

    Enable selective response actions

     

  • The new exposure score model in Defender Vulnerability Management is now generally available. This model improves risk prioritization and recommendation impact accuracy by incorporating exploit prediction data (EPSS) and asset context factors such as internet-facing status and criticality. More details here. 

  • Microsoft Secure Score now includes the Reduce unnecessary inbound internet exposure on internet-facing devices recommendation, which helps identify devices that are accessible from the public internet and may represent unnecessary attack surface. This recommendation provides centralized visibility into internet-facing devices across the environment.

  • Many predefined SaaS application classification rules were added to the critical assets list. Have a look at our documentation for the full list. These classifications require onboarding to Microsoft Defender for Cloud Apps.

Updated Jul 01, 2026
Version 1.0

6 Comments

  • Where can we read up on the following news point (only visible in this blogg):

    • Custom Detections support in Microsoft Sentinel Repositories. Custom Detections can now be managed as code in Microsoft Sentinel Repositories, the same way customers already manage analytic rules, playbooks, parsers and workbooks. Detection engineers connect a GitHub or Azure DevOps repo to their workspace; Custom Detections placed in the repo are reconciled on every commit. A standalone Bicep path via the Microsoft Security Bicep extension lets teams deploy from any CI/CD pipeline (ADO Pipelines, GitHub Actions, custom runners).

    I tried making a new Azure DevOps connecting and the powershell script that is automatically created has no support for Custom Detections. (This script should be available on your github btw, would be great to see if any updates are made to it!). Also, https://learn.microsoft.com/en-us/azure/sentinel/ci-cd-custom-content#how-microsoft-sentinel-repositories-work states no support for custom detections yeat. And there is no template for Custom Detections for ci-cd pipelines.  I have built my own using webextensions and can deploy them in xdr portal, but those (json/yaml) did not work in the devops ci-cd.

    So some more information on this would be great :)

    • HeikeRitter's avatar
      HeikeRitter
      Icon for Microsoft rankMicrosoft

      Found this, please let me know if it helps and sorry for the delay (did see your comment :( )

      Custom detection rules support in Microsoft Sentinel Repositories (Preview)

      You can now manage custom detection rules as code in your GitHub or Azure DevOps repository using the Microsoft Security BICEP extension. Sync custom detection rules to Microsoft Sentinel using the Repositories feature, or deploy them directly using BICEP CLI. For more information, see Deploy custom detection rules as code.

      • Internetguy441's avatar
        Internetguy441
        Brass Contributor

        Hello!
        Thanks for your reply, appreciated.
        That clears up one thing: How to create the Bicep file (*.bicep) and that our Repository now needs to add the bicepsettings.json file in root and with the extension added. So this introduces a complete new file (bicep). No other resource has been in bicep before for Azure DevOps (or github) repository connections:  

        https://learn.microsoft.com/en-us/azure/sentinel/ci-cd-custom-content#plan-your-repository-content

        Thats ok, but when i started reading up on bicep, apprently the Repository connection have to be newer then 1 November 2024 as stated here:

        https://learn.microsoft.com/en-us/azure/sentinel/ci-cd?tabs=github

        "This procedure describes how to remove the connection to a source control repository from Microsoft Sentinel. In order to use Bicep files, your repository connection must be newer than November 1, 2024. Use this procedure to remove the connection and recreate it in order to update the connection."

        Working in a MSSP with around 25-75 connections, many of which are created before that date, this becomes a massive undertaking. We where reassured in many other blogposts and partner programs that only editing the existing connections where enough to get the full support (And custom detections files will start to appear in content hub in sentinel). Im starting to feel what i feared, a huge undertaking starting this fall to recreate all our connections and introduce the bicep extension support to Azure DevOps. (i would LOVE not to use bicep, ARM is already natively supported).

        I also did a new fresh connection, as i had a gut feeling that the *.ps1 deployment file that is generated when a new connection is set up (that still dosent work correctly with workingdirectories btw) had some new items in them, for both bicep AND custom detections - and yes, it had.... I have rewritten the whole file by hand to support proper versioning, renaming of workbooks AND workingdirectories for customers (biggest issue with default ps1 was that a full deployment is forced as soon as you change any customer folder, making a full redployment taking 20-30min per customer on ANY minor change). Now i need to spend a few days diffing the files to add the new custom detection items... Would be GREAT if these infrastructure files that are generated upon such connections would be publicly available and maintained by Microsoft - that would be awesome and great (then i dont need to redeploy/connect a tenant to see them).


        Thank you <3 , i will try all these when vacation starts to wind down, this is a massive undertaking but i think i have the basis to begin exploring both Bicep support, but also custom detections (i have built a firefox extension that can handle mass deployment of custom detections). But i will have to convert that to support a bicep EXPORT :)

        Thanks again, appreciated coming back to me!!

    • thomasdauner1's avatar
      thomasdauner1
      Copper Contributor

      Same here - further information would be great on how to use Bicep to deploy custom detections for the Defender XDR.

  • LearnToday's avatar
    LearnToday
    Copper Contributor

    Great to see the continued push toward a unified security experience. Bringing Defender for Cloud visibility directly into the Defender portal is a massive win for reducing portal fatigue and streamlining SOC workflows.