Observed behaviour:
I'm deploying ACI container groups with ARM template. The attributes Microsoft.ContainerInstance/containerGroups/diagnostics.logAnalytics.workspaceId and Microsoft.ContainerInstance/containerGroups/diagnostics.logAnalytics.workspaceKey to not appear to be validated upon deployment. I can enter any workspaceId, e.g. "thisisnotavalidID", and I can enter the wrong workspaceKey for a valid workspaceId, but the container group is still deployed, and log collection by Log Analytics Workspace fails silently.
Expected behaviour:
If I try to deploy a container group with invalid Log Analytics Workspace credentials, the deployment should fail. Any combination of workspaceId and workspaceKey which do not correspond to an existing workspace where workspaceKey is a valid key, should fail.
Observed behaviour: I'm deploying ACI container groups with ARM template. The attributes
Microsoft.ContainerInstance/containerGroups/diagnostics.logAnalytics.workspaceId
andMicrosoft.ContainerInstance/containerGroups/diagnostics.logAnalytics.workspaceKey
to not appear to be validated upon deployment. I can enter anyworkspaceId
, e.g. "thisisnotavalidID", and I can enter the wrongworkspaceKey
for a validworkspaceId
, but the container group is still deployed, and log collection by Log Analytics Workspace fails silently.Expected behaviour: If I try to deploy a container group with invalid Log Analytics Workspace credentials, the deployment should fail. Any combination of
workspaceId
andworkspaceKey
which do not correspond to an existing workspace whereworkspaceKey
is a valid key, should fail.