An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
Hi @Stephen Baker
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.
Issue:
My Bicep deployment is demanding a "format" parameter when it's not even supported
Solution:
I was able to solve the issue by adding properties.ValidationRules to the resource. While they aren't stated to be required in the official documentation, it would seem that they are.
The final (working) resource definition looks like this. Hopefully this helps someone:
param resourceName string
param userDefinedName string
param description string
param frequency int
param timeout int = 30
param kind string
param locations array
param requestUrl string
param appInsightsResourceId string
resource webTest 'Microsoft.Insights/webtests@2022-06-15' = {
name: resourceName
kind: kind
location: resourceGroup().location
properties: {
Name: userDefinedName
Description: description
Enabled: true
Frequency: frequency
Kind: kind
Locations: locations
Request: {
HttpVerb: 'GET'
RequestUrl: requestUrl
}
ValidationRules: {
ExpectedHttpStatusCode: 200
IgnoreHttpStatusCode: false
ContentValidation: null
SSLCheck: false
}
RetryEnabled: false
SyntheticMonitorId: userDefinedName
Timeout: timeout
}
tags: {
'hidden-link:${appInsightsResourceId}': 'Resource'
}
}
output webTestId string = webTest.id
If you have any other questions or are still running into more issues, please let me know. Thank you again for your time and patience throughout this issue.
Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.