Microsoft Entra Private Access - Clarification

karthik palani 661 Reputation points
2025-04-17T13:27:29.86+00:00

Hi All,

I am trying to implement Microsoft Entra Private Access for the first time, i would like to understand the architecture and steps for integrating our core internal application with Entra private access with conditional access control.

  1. To perform above is it mandatory i need to register internal application under Entra - Enterprise application. Once done should i need to update any meta data within Internal application to use entra private access.
  2. How my internal application is aware of providing access via connector and authentication within Entra ID.
  3. I want to force the user to access internal application only when they are connected via Global secure access externally and internally it should allow automatically. Normal browser should block it. Is it possible?
  4. I have Team viewer apps in Entra - Enterprise application, my objective is to have MFA authentication before accessing Team viewer. So since it is already in Enterprise application - i can just add the users and apply conditional access policy or is there any steps i need to perform in Team viewer.

Please advice

Thanks,

Microsoft Security | Microsoft Entra | Microsoft Entra Private Access
{count} votes

1 answer

Sort by: Most helpful
  1. Alan La Pietra (CSA) 165 Reputation points Microsoft Employee
    2025-08-25T13:14:24.65+00:00
    1. Yes, registering your internal application as an Enterprise Application in Microsoft Entra is required to use Private Access. Once registered, you must:
    • Create an application segment that defines the internal resource (IP, FQDN, ports, protocols).
    • This segment is used by the Global Secure Access (GSA) client to route traffic securely to your internal app.
    • No metadata changes are needed within the internal app itself, but the app must be reachable via the connector and support authentication protocols like Kerberos or SAML. [Microsoft...rosoft Q&A]

    This setup enables per-app access, allowing granular Conditional Access enforcement.

    1. How does the internal application become aware of access via connector and Entra ID authentication?

    Your internal application doesn’t need to be explicitly aware of the connector. Instead:

    • The Microsoft Entra Private Network Connector acts as a bridge between the cloud and your internal network.
    • The connector is installed on a Windows Server inside your network and handles outbound communication only—no inbound ports need to be opened.
    • The GSA client on the user’s device routes traffic to the connector, which then forwards it to the internal app.
    • Authentication is handled by Microsoft Entra ID, using Conditional Access policies and optionally MFA.
    1. To enforce access only via GSA:

    This setup ensures:

    • External users must use GSA client and meet Conditional Access requirements.
    • Internal users can access automatically if within the corporate network.
    1. Enforcing MFA for TeamViewer via Entra Enterprise Application

    Since TeamViewer is already registered as an Enterprise Application, you can enforce MFA by:

    • Assigning users or groups to the TeamViewer app.
    • Applying a Conditional Access policy that requires MFA for access to TeamViewer.
    • No additional configuration is needed within TeamViewer itself unless it has its own MFA settings. However, ensure:
    • The app supports SAML or OAuth for integration.
      • You test the policy using the Conditional Access What If API to avoid lockouts.
    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.