Skip to main content

Microsoft Intune Integration with ZTXGate

Microsoft Intune can contribute managed-device compliance information to ZTXGate access decisions.

That lets an organization combine who the user is, which device is enrolled, what Intune reports about that device, and which resource is being requested before access is allowed.

Use Intune Compliance as an Access Signal​

ZTXGate can use available Intune compliance information as part of resource policy in connected environments.

A policy can therefore require an enrolled endpoint to satisfy the required device posture before it reaches a sensitive application or service.

This is different from treating possession of valid credentials as sufficient proof of trust.

ZTXGate Enrollment and Intune Solve Different Problems​

ZTXGate enrolls devices individually so the access platform can identify and manage each endpoint.

Intune remains the device-management and compliance source.

ZTXGate enrollment  → which endpoint is requesting access
Intune posture       → what the management platform says about its state
ZTXGate policy       → whether that endpoint may reach this resource now

The two controls complement each other rather than duplicating the same function.

Continuous Policy Enforcement​

Device state is not static. ZTXGate can continue evaluating relevant policy conditions after access begins and revoke access when required conditions are no longer satisfied.

That allows Intune-derived posture to participate in an ongoing access decision instead of becoming a one-time gate at sign-in.

Combine Intune with Identity and Step-Up Authentication​

For sensitive resources, posture can be combined with other controls such as:

  • OIDC-authenticated user identity
  • SCIM-managed roles and lifecycle
  • individually enrolled device identity
  • time or network-location conditions
  • temporary or approved access windows
  • additional authentication, including integrated ZTXBAS when licensed

This makes Intune one input into a broader Zero Trust policy rather than the sole access decision.

Deployment Considerations​

The Intune integration requires connectivity to the Microsoft service it depends on. In a fully air-gapped ZTXGate deployment, external Intune posture is unavailable unless connectivity is deliberately provided.

ZTXGate itself can continue operating without a CoreZT-hosted cloud control plane, and integrated ZTXBAS can remain available for phishing-resistant biometric authentication inside the isolated environment when licensed.

Explore all integrations · Identity & Device Trust · Start Free Trial