What Changed
Fixed critical ARM template parameter syntax error in MailRisk CCF connector that was preventing successful deployments.
Deployment Template Fix
ARM template parameter extraction corrected:
- Before: Double bracket syntax causing parsing failures
- After: Single bracket syntax enabling proper parameter extraction
The incorrect syntax was causing ARM template parsing failures during connector deployment.
Security Impact (Data Ingestion)
This was a complete connector deployment blocker:
- Pre-fix: MailRisk connector deployments failed entirely due to ARM template parsing errors
- Post-fix: Connector deploys successfully and can ingest threat intelligence data from MailRisk API
Any organization attempting to deploy MailRisk CCF connector since v3.0.0 migration (Oct 2025) experienced deployment failures, resulting in zero data ingestion from MailRisk threat feeds until this fix.
CCF Authentication Configuration
Fixed authentication block in MailRisk polling configuration:
- UserName: Maps to API key parameter
- Password: Maps to API secret parameter
- Endpoint: https://api.mailrisk.com/v1/events (unchanged)
Per PR discussion: connector functionality verified with successful connection screenshot provided by contributor.
Affected Files
Solutions/MailRisk/Data Connectors/MailRisk_CCP/MailRisk_PollingConfig.json
(packaging artefacts: 3.0.0.zip, ReleaseNotes.md, Solution_SecurePracticeMailRisk.json, mainTemplate.json)