What Changed
Fixed critical deployment issues in the Upwind cloud security connector that prevented the Azure Function App from deploying correctly. The fix restructured the Function App package and ARM template configuration.
Security Impact (Visibility & Fidelity)
Deployments using version 3.0.1 experienced Function App deployment failures, resulting in zero data ingestion from the Upwind cloud security platform. The connector was unable to fetch compute platform assets into the UpwindLogsAssets_CL table, creating a complete visibility gap for Upwind security events.
Per PR discussion and test plan: users deploying via the “Deploy to Azure” button were unable to get the function code to deploy correctly, blocking all data collection from the Upwind platform.
Technical Details
- ARM Template Fix: Removed separate Microsoft.Web/serverfarms resource and configured the Function App to use implicit hosting plan with alwaysOn and reserved properties
- Package Structure Fix: Restructured UpwindLogsLoader.zip to flat layout (removed deployment/ prefix) and removed pre-compiled macOS packages
- Reference Links: Restored official aka.ms short links for deployment and package references
- Version Bump: Updated to v3.0.2 and repackaged via createSolutionV3.ps1
Affected Files
Solutions/Upwind/Data Connectors/azuredeploy_UpwindLogsLoader_API_FunctionApp.json
(packaging artefacts: 3.0.2.zip, ReleaseNotes.md, Solution_UpwindLogsLoader.json, UpwindLogsLoader.zip, mainTemplate.json)