What Changed

Fixed folder structure in zip packages for all 20 IPinfo Data Connectors by moving host.json to the root level, eliminating an extra wrapping folder that prevented Azure Functions runtime from starting.

Security Impact (Visibility & Fidelity)

Per PR discussion: deployments of IPinfo Solution v3.0.3 from Content Hub experienced complete Function App failure — Azure Functions did not appear in the Function App UI and were unable to ingest any data. This represents a total loss of IP intelligence visibility for affected deployments.

The transformKql error caused the connector to fail at creation — zero data was ingested by affected deployments since the v3.0.3 marketplace release.

Connector Fix Scope

All 20 IPinfo Data Connectors affected:

  • Core, Plus, Residential Proxy (added in v3.0.3)
  • ASN, Abuse, Carrier, Company, Country ASN, Domain
  • IP Location, IP Location Extended, Privacy, Privacy Extended
  • RIRWHOIS, RWHOIS, WHOIS ASN, WHOIS MNT, WHOIS NET, WHOIS ORG, WHOIS POC

Each connector uses Function App ingestion mechanism and was completely non-functional due to the packaging error.

Affected Files

(packaging artefacts: 3.0.4.zip, IPInfoWHOISASNConn.zip, IPinfoASNConn.zip, IPinfoAbuseConn.zip, IPinfoCarrierConn.zip, IPinfoCompanyConn.zip, IPinfoCoreConn.zip, IPinfoCountryConn.zip, IPinfoDomainConn.zip, IPinfoIplocationConn.zip, IPinfoIplocationExtendedConn.zip, IPinfoPlusConn.zip, IPinfoPrivacyConn.zip, IPinfoPrivacyExtendedConn.zip, IPinfoRIRWHOISConn.zip, IPinfoRWHOISConn.zip, IPinfoResProxyConn.zip, IPinfoWHOISMNTConn.zip, IPinfoWHOISNETConn.zip, IPinfoWHOISORGConn.zip, IPinfoWHOISPOCConn.zip, ReleaseNotes.md, Solution_IPinfo.json, mainTemplate.json)