Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Microsoft.Insights/webtests 2020-10-05-preview is declared but not supported by the service #14827

Open
anthony-c-martin opened this issue Jun 15, 2021 · 2 comments
Labels
Insights Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@anthony-c-martin
Copy link
Member

Originally raised under Azure/bicep#3232

2020-10-05-preview was added ~8 months ago via #11068, but is still not publicly accessible.

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jun 15, 2021
@raych1 raych1 added Insights Service Attention Workflow: This issue is responsible by Azure service team. labels Jun 17, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jun 17, 2021
@kacperwojtyniak
Copy link

Is there any timeline for a fix?

@JoeleJB
Copy link

JoeleJB commented Aug 4, 2021

Hello?

Very frustrating as documentation outlines the version (https://docs.microsoft.com/en-us/azure/templates/microsoft.insights/webtests?tabs=json) but that version is not available in any region..

I can use the previous available version being the 2018 preview and most things on that link above work, but not "ExpectedHttpStatusCode" which it just ignores as far as I can tell....

Very frustrating as you can setup in the portal but when you export it most of this section is missing from the export, if you then delete the resource and recreate with the exported template these settings are missing.. And as I said if you follow the guide in the microsoft link above (but use the latest api version as the one specified isn't available) it doesn't all work being as not everything is supported by the 2018 api version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Insights Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

4 participants