API Connection
Does ZopNight manage API Connection?
API connections carry no meter of their own. The cost sits in the Logic Apps and Power Platform workflows that use them to reach Office 365, SQL, or Service Bus. ZopNight discovers every connection via Resource Graph and links it to its consuming Logic Apps for dependency and credential-hygiene review.
Rules that fire on API Connection
No active rule family targets API Connection today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.
At a glance
| Field | Value |
|---|---|
| Scheduling notes | discovery only. |
API connections store the authenticated links Logic Apps and Power Platform use to reach services like Office 365, SQL, and Service Bus. They are free but map integration dependencies and stale credentials.
A free resource that maps paid dependencies
An API connection carries no meter: creating fifty of them adds nothing to the invoice. What each one records is an authenticated credential (an OAuth grant, a connection string, a service principal) binding a workflow to a target service such as Office 365, SQL, or Service Bus. That makes the inventory valuable for reasons other than cost: connections are the wiring diagram of an environment’s integrations, and the place where stale credentials hide.
Connection-to-workflow linkage in ZopNight
Discovered via Azure Resource Graph and linked to consuming Logic Apps for dependency and hygiene review. The linkage answers two questions the portal makes tedious: which workflows break if this credential expires, and which connections no longer have any consumer at all. As a free resource with nothing to stop or resize, its role in ZopNight is discovery only, but the dependency map it contributes informs decisions about the paid resources around it.
Stale credentials and orphaned connectors
Three hygiene patterns recur. Connections whose consuming Logic App was deleted, leaving an authenticated credential with no owner watching it. Connections authorized under an employee’s personal account rather than a service identity, which fail the day that person leaves the company. And broken connections that a workflow silently retries against, generating failures instead of results; the expired token surfaces in the connection’s status. None of these cost money directly; each of them eventually costs an outage or an audit finding.
Locating API connections in the portal
API connections get no top-level menu entry of their own. In the Azure portal, open All resources and filter Type to API Connection to see them across the subscription, or open a specific Logic App and use its API connections blade to see exactly which credentials that one workflow depends on.