Lookout v3.0.4: Fix APIKey bracket escaping in mainTemplate.json

[fgravato]

Summary

• Fixed a bracket escaping bug in the ResourcesDataConnector inner template that caused connector configuration to fail with an ARM evaluation error.
• Rebuilt 3.0.4.zip with the corrected mainTemplate.json.
• Updated SolutionMetadata.json and ReleaseNotes.md to version 3.0.4.

Root Cause

The APIKey field in the connector's auth block was set to:

"APIKey": "[[parameters('applicationKey')]]"

In ARM templates, a string starting with [[ is treated as an escaped literal — the first [ is stripped, producing the stored value:

[parameters('applicationKey')]]

When the Sentinel connector framework later evaluated this stored string as an ARM expression, it stripped the outer […] and attempted to parse:

parameters('applicationKey')]

The trailing ] caused the error:

Unable to parse language expression 'parameters('applicationKey')]': expected token 'EndOfData' and actual 'RightSquareBracket'

Fix

Changed ]] → ] at the end of the APIKey value:

"APIKey": "[[parameters('applicationKey')]"

This matches the identical pattern already used by the adjacent dcrConfig fields:

"dataCollectionEndpoint": "[[parameters('dcrConfig').dataCollectionEndpoint]",
"dataCollectionRuleImmutableId": "[[parameters('dcrConfig').dataCollectionRuleImmutableId]",

After the outer ARM deployment strips the escaping [, the stored value is [parameters('applicationKey')] — a valid ARM expression that Sentinel correctly evaluates to the customer's API key when instantiating the connector.

Files Changed

File	Change
Solutions/Lookout/Package/mainTemplate.json	Fixed APIKey bracket; bumped all version refs 3.0.3 → 3.0.4
Solutions/Lookout/Package/3.0.4.zip	Rebuilt zip with corrected template
Solutions/Lookout/SolutionMetadata.json	Version 3.0.4, lastPublishDate 2026-04-24
Solutions/Lookout/ReleaseNotes.md	Added 3.0.4 release entry