Zero Trust Network Access (ZTNA)

Are you looking for information about ZTNA of Microsoft Azure and Microsoft 365? In this archive you will find all our posts about ZTNA.

  • Microsoft 365,  Microsoft Azure

    Microsoft Entra Private Access: Secure Access for External Users to Internal Resources

    7. March 2026 /

    Connecting external users to internal resources has traditionally been implemented using VPN. While this approach provides network connectivity, it does not consistently align with Zero Trust principles. With the external user access capability in Microsoft Entra Global Secure Access, external identities can now be integrated into existing Microsoft Entra Private Access configurations. Microsoft Entra Private Access External Users authenticate with their own identity and device and intentionally switch to the resource tenant within the Global Secure Access Client. During this tenant switch, a Private Access tunnel is established that restricts connectivity exclusively to explicitly published internal applications.

    ⟶
  • Microsoft 365,  Microsoft Azure

    Microsoft Entra Private Access BYOD: Access Internal Resources with Entra Registered Devices

    13. February 2026 /

    Until now, access to internal resources through Microsoft Entra Private Access was limited to managed devices that were either Microsoft Entra joined or Microsoft Entra hybrid joined. With the introduction of Microsoft Entra Private Access BYOD support, this limitation has been removed. Microsoft Entra registered devices can now access internal resources through Microsoft Entra Private Access, extending secure access to scenarios beyond fully managed devices.

    ⟶
  • Microsoft 365,  Microsoft Azure

    Intelligent Local Access in Microsoft Entra Global Secure Access

    6. February 2026 /

    Intelligent Local Access (ILA) addresses a core limitation of Microsoft Entra Global Secure Access: ensuring that local network traffic is handled locally. By default, Microsoft Entra Global Secure Access forwards traffic based on configured traffic forwarding profiles through the cloud-based Security Service Edge (SSE), even when the destination resides within the local network. This approach guarantees that security policies and access controls are enforced consistently at all times. As a result, local resources such as file shares or applications are routed through the cloud-based Security Service Edge (SSE), despite a direct local connection being available. The extended network path introduces additional latency and negatively impacts overall access performance.

    ⟶
  • Microsoft Azure

    Microsoft Entra ID: Admin Consent Workflow for Secure Application Permissions

    2. June 2025 /

    The Admin Consent Workflow in Microsoft Entra ID is a feature designed to manage user consent for enterprise application permissions. It allows administrators to review, approve, or deny permission requests before access is granted. Instead of allowing users to grant extensive permissions directly, the Admin Consent Workflow ensures that only authorized applications can access sensitive data. For instance, an application might request permission to access a user’s profile or read the contents of their mailbox. By introducing this workflow, organizations can effectively enforce the principle of least privilege and reduce the risk of unintentional data exposure.

    ⟶