Skip to content

Application Proxy Connector Health

The question it answers: Which Application Proxy connector groups serving apps have no active connector, or hang on a single one, and which connectors are inactive?

Apps published through Microsoft Entra Application Proxy stop working the moment their connector group has no active connector. Groups serving apps with no active connector, inactive connectors and groups that hang on a single connector are listed first.

Where in the appEntra ID › App & Workload Identities › App Proxy Connectors
WorkloadEntra ID
KindTable
DataBuilt from the tenant data IntensiveReports keeps in memory and refreshes in the background, so it opens at once.
LicenceMicrosoft Entra ID P1 (Application Proxy).
Report id (API and MCP)entra.security.app-proxy-connectors
ColumnKeyType
Connector groupGroupNameText
MachineMachineNameText
StatusStatusStatus
FindingFindingText
Apps in groupGroupApplicationsText
Active in groupGroupActiveConnectorsText
External IPExternalIpText
RegionRegionText
Default groupIsDefaultGroupYesNo
FilterKey (API)On when the page opens
Only connectors and groups that need attentionattentionYes

Licence: Microsoft Entra ID P1 (Application Proxy).

Application permissions on the IntensiveReports app registration (all permissions):

PermissionAPIWhat it allowsNote
OnPremisesPublishingProfiles.ReadWrite.AllMicrosoft GraphManage on-premises published resourcesthe only permission this API accepts - read-write
Data sources it reads
  • GET /beta/onPremisesPublishingProfiles/applicationProxy/connectorGroups
  • GET .../connectorGroups/{id}/members
  • GET .../connectorGroups/{id}/applications
GET /ir-api/v1/reports/entra.security.app-proxy-connectors?size=100
GET /ir-api/v1/reports/entra.security.app-proxy-connectors?filter=attention

An AI assistant reads it with the MCP tool get_report and the id entra.security.app-proxy-connectors. The client needs the Read grant for Entra ID. See Using the API.