Start with one application, not a subnet
Fictional Boreal Workshop wants buyers to reach commandes.atelier.example on TCP 443 from outside. Personal devices may view selected Microsoft 365 content, but the ordering app requires a managed device. Test these paths separately.
Global Secure Access (GSA) brings together Entra Private Access, Microsoft's ZTNA service for private resources, and Entra Internet Access, the gateway for covered internet and SaaS traffic. The Microsoft traffic profile has separate entitlements and scope. Defender for Endpoint assesses device risk, Intune evaluates compliance and Entra enforces access. Defender does not publish the private app.
A VPN can already be segmented. Private Access ties specific destinations and an application to a user group and policy, reducing the need to expose an entire network segment. The trade-offs are operating connectors, profiles and clients, testing DNS and actual protocols, and depending on the cloud service. Traffic logs cover supported forwarded traffic; retain application permissions and firewall controls.
1. Prepare entitlements, connectors and pilot scope
Check entitlements per user: Entra ID P1 or P2 and Entra Private Access (standalone or included in Entra Suite); full Internet Access is separate. Verify Intune and the applicable Defender for Endpoint subscription for risk-based compliance. Microsoft documents Defender P1 and P2 for the Windows configuration; verify the platforms and features separately. A subscription or an installed Defender mobile app does not establish compliance.
Choose a pilot group and a connector group that can resolve and reach the app. Microsoft lists Windows Server 2016 or later and .NET Framework 4.7.2 as minimums. Use a supported, patched Windows release and current connector. Plan multiple connectors for production continuity and allow the documented outbound Microsoft destinations on ports 80/443 and access to the backend. The connector needs no inbound port from the internet. Assign the required GSA, application, Intune and Conditional Access roles separately.
2. Verify platform and enrollment support
For unenrolled Android use Authenticator or Company Portal as documented; for unenrolled iOS use Authenticator. The documented mobile path uses the Defender app to host the GSA client and creates a device-wide VPN profile. Enable GSA for private traffic and test coexistence with other VPNs. Check the OS and client release notes per platform. Entra registration, MDM enrollment and compliance are distinct.
| Device state | GSA profiles for this device state |
|---|---|
| Windows Entra joined or hybrid joined | Microsoft Entra, M365, internet and private, subject to entitlements and configuration |
| Windows Entra registered | Private only |
| macOS Entra registered and MDM enrolled | All four subject to entitlements and configuration; unenrolled BYOD is unsupported |
| Android and iOS Entra registered | Microsoft's matrix lists all four with and without MDM enrollment; for unmanaged devices follow the mobile procedure for enabling private traffic |
3. Configure the private path and device-risk signal
Pilot changes: create a Private Access application for commandes.atelier.example:443, bind its connector group, assign pilot users, enable the private forwarding profile and install the supported client. Inventory dependent destinations before widening the port list. Quick Access groups destinations under one enterprise app and one policy target. Use a separate app for more granular scoping of the sensitive service. Check whether an existing VPN or direct path circumvents the intended controls.
Connect Defender for Endpoint to Intune and confirm that enrolled pilot devices report a signal. In compliance policies on supported platforms, set a maximum risk level, for example Low for ordering, and check grace periods and how devices with no assigned policy are evaluated. Risk above the threshold should make the device noncompliant according to those settings. Conditional Access consumes compliance. Device risk, sign-in risk and user risk are different signals. Measure the delay between risk reporting, compliance and a fresh connection; do not assume an existing connection ends immediately.
4. Turn BYOD rules into Conditional Access policies
Target the private app and pilot group in Entra. Under Grant, require the device to be marked compliant and require an appropriate authentication strength, such as phishing-resistant MFA. Select the option requiring all selected controls. If the policy calls for generic MFA, select the MFA control instead of an authentication strength. MFA alone must not satisfy a compliant-device requirement.
For company-only access, add a block policy for the same target and users with an include filter of device.deviceOwnership -ne "Company". The negative comparison is intended to catch unregistered devices whose attributes are null. Test registered devices with missing ownership and sign-ins without a device claim as well as Company and Personal. Govern how Intune ownership is assigned. A compliant personal device is still personal.
| Device state | Sensitive private app |
|---|---|
| Compliant company device within risk threshold | Allow if assigned and authentication requirement is met |
| Managed and compliant personal device | Allow only if policy permits it; otherwise block by ownership |
| Unmanaged personal device or no compliance proof | Deny sensitive private access |
| High-risk device | Deny once noncompliance is evaluated; investigate the device in Defender |
5. Keep lower-risk Microsoft 365 access separate
For a lower-risk SharePoint site, consider limited browser access on unmanaged devices through SharePoint-enforced restrictions. Test downloading, sync clients, Teams and sharing within the policy scope. Intune app protection can restrict data movement in supported clients without enrolling the whole device. Check the app, platform and supported grant control before enforcing it. These controls do not establish device compliance for the private app.
6. Observe, enforce and roll back
Start in report-only mode. In Entra sign-in logs check the target app, device identity and policy outcome. Compare with Intune and Defender, then GSA client diagnostics and available traffic logs. Record time, pilot identity, destination, outcome and correlation identifier when present. Verify emergency accounts have a tested independent administration route without granting them access to the business app.
When outcomes match expectations, enforce only the pilot policy. Retest from outside using fresh sessions: healthy company device allowed, unmanaged device denied, managed personal device subject to your decision, noncompliant device denied. Use a noncompliant test device or approved test signal without creating a production incident. Verify unassigned users cannot reach the app and traffic cannot use a parallel route.
If an intended user is denied or an unintended device is allowed, stop expansion. Return the pilot policy to report-only only if approved controls still protect the service; otherwise remove pilot assignment or published access before relaxing the policy. Keep baseline controls in place, record the cause and repeat positive and negative tests.
Microsoft Learn documentation
- GSA licensing and profiles ↗
- Platform and BYOD matrix ↗
- Private network connectors ↗
- Private apps and Conditional Access ↗
- Per-app setup ↗
- Quick Access ↗
- Intune and Defender integration ↗
- Defender risk and Conditional Access ↗
- Conditional Access device filters ↗
- SharePoint unmanaged access ↗
- Windows app protection ↗
- Known limitations ↗