Blog Post

Microsoft Entra Blog
3 MIN READ

Why identity needs network insight to make Zero Trust work

Mohammad_Zmaili's avatar
Oct 27, 2026

See how Microsoft Entra connects identity, traffic, and session signals to apply smarter Zero Trust controls across internet and private access.

Your users sign in successfully—and then what? The session can be hijacked, device posture can degrade, and traffic to non-federated SaaS and AI apps can slip past the identity controls you trust to protect them. That’s the gap admins see every day: identity tells you who, but not what’s happening across the network during the session—and it’s why identity alone can’t carry Zero Trust on its own.

Most Zero Trust strategies start with identity—and for good reason. Identity is the control point for authenticating users and granting access. But identity by itself can’t address every evolving risk. Today, users connect from anywhere, on any device, and interact with thousands of apps across cloud, AI, internet, and private networks. The gap between identity and network security creates blind spots that attackers can exploit.

Microsoft’s approach is clear: identity is most effective when it operates with full awareness of the network. That’s why Microsoft Entra brings identity and network protections together in a unified architecture designed for modern Zero Trust security.

Why identity alone is not enough

Traditional access decisions often stop at sign-in and rely on credentials plus multifactor authentication. This works for many scenarios—but not all. In practice, a session that looks low-risk at sign-in can turn risky minutes later, and unmanaged traffic to AI tools and non-federated SaaS apps creates blind spots your identity policies weren’t designed to cover Why? Because threats don’t disappear after a successful sign-in:

  • Risk changes dynamically: A user’s session can be hijacked, or device posture can deteriorate mid-session.
  • Blind spots in traffic: Connections to non-federated SaaS apps or AI services often bypass identity controls.
  • Static policies fail: Network contexts like location or traffic path often go unchecked.

Zero Trust isn’t just about verifying identity at the front door—it’s about making continuous, adaptive decisions that factor in identity, device, network conditions, and session context together.

How Microsoft Entra unifies identity and network signals

Microsoft brings these controls together through a single security architecture anchored by Microsoft Entra ID, Conditional Access, continuous access evaluation, and Global Secure Access, including Microsoft Entra Internet Access and Microsoft Entra Private Access.

Key principles

  • Conditional Access as a unified engine
    Access decisions no longer evaluate identity alone—they also factor in device compliance, location, trusted network, and contextual signals.
  • Global Secure Access as integrated traffic enforcement
    Microsoft Entra Internet Access applies Conditional Access controls to internet destinations and SaaS apps, including those that aren’t federated with Microsoft Entra ID.
  • Continuous enforcement with continuous access evaluation
    Sessions can be revoked instantly when conditions change—for example, when a user account is disabled or risk increases.

This approach closes the visibility gaps between identity and network layers without reintroducing legacy network perimeters. The result: a dynamic system that continuously evaluates risk and enforces Zero Trust everywhere users work.

What this delivers

  • Stronger security foundation: Identity decisions informed by network and device context help detect and block threats early.
  • Granular, unified policy control: One Conditional Access framework for internet, SaaS, and private app traffic—no need to maintain separate systems.
  • Faster response: Continuous policy evaluation enables real-time revocation of risky sessions without manual intervention.

This isn’t just authentication. It’s identity-driven networking, where every decision considers who the user is, what device they’re using, where traffic is going, and how risk changes during the session.

Get started

Start by reviewing where your current access policies end—and where network visibility needs to extend them.

  • Review your Conditional Access policies and incorporate device compliance and location conditions.
  • Extend those policies to internet and private app connectivity using Microsoft Entra Internet Access and Private Access.
  • Enable Continuous Access Evaluation for dynamic, session-aware protection.

Now is the time to close the gap between identity and network visibility. Start by reviewing your Conditional Access policies, extending those controls to internet and private app traffic, and enabling continuous access evaluation so your Zero Trust strategy can adapt in real time as risk changes.

- Mohammad Zmaili, (SENIOR PRODUCT MANAGER )

Mohammad Zmaili | LinkedIn

-Sule Tatar, ( SENIOR PRODUCT MARKETING MANAGER)

Sule Tatar | LinkedIn

 

Additional resources

 

Learn more about Microsoft Entra

Prevent identity attacks, ensure least privilege access, unify access controls, and improve the experience for users with comprehensive identity and network access solutions across on-premises and clouds.

Updated Oct 26, 2026
Version 1.0

2 Comments

  • Clear summary of why a sign-in check alone is not enough. Two practical points that might be worth adding to the get started list:

     

    • Device compliance in Conditional Access is only as fresh as the compliance data behind it. Intune evaluates on a schedule and at check-in, and as far as I know device posture changes are not a continuous access evaluation trigger the way account disabled or high user risk are. So a device that degrades mid-session can still count as compliant until the next evaluation. It is worth knowing the real evaluation interval in your environment.
    • The other half is what happens after a policy blocks a device. When posture fails (BitLocker suspended, firewall off, a missing patch), the user stays blocked until someone fixes the device, so the time to remediate decides how disruptive Zero Trust feels. Intune remediations cover part of this, and endpoint tools that can run the fix right away and report the result are another option. TFalke is one example (disclosure: I work on it): an AI agent diagnoses the device and fixes it with a command that an operator approves first.

    Tracking time blocked per user, and not only the number of blocked sessions, would show whether the controls are working or just creating tickets.

    • WinEndpointOps's avatar
      WinEndpointOps
      Iron Contributor

      A correction to my first point above. Since I wrote it, Microsoft's October Intune what's new post explains that supported Windows devices now detect changes to key security settings locally (for example the firewall being turned off or antivirus health changing) and request an early check-in, so compliance can be reevaluated without waiting for the scheduled one. So the delay I described is shorter than I made it sound, for those settings and on supported Windows devices. My point about the time to fix the device afterwards still stands, but please read the compliance part with that update in mind.