Allow Instrumentation Key Regeneration
In order to be able to recover from an exposure through the JS SDK, it would be necessary to be able to regenerate the instrumentation key
Thanks for your feedback, can you please help provide more information on the scenario you are trying to achieve , which would help us and also the user community to upvote & comment on.
Security key rotation and revocation should be part of every system that relies on secrets.
Yu, Roger (Cambridge) commented
In my situation it would be useful to be able to regenerate a compromised key like we can with Storage account keys. In our case our AI is young so recreating is not significant. I can see it is a worse situation for others though.
Others with same issue:
Jochen Zeischka commented
Unbelievable to see only 10 votes on this...
Daisuke Sasaki commented
If a key is misused, the holder of Application Insights must pay for data illegally sent by an unauthorized user.
This is a problem.
Well, the Szenario is quite easy :D... somehow your key got exposed (e.g. pushed to a public repo) and you now want to change the instrumentation key to prevent abuse of it. E.g. some evil guy on the internet creating fake telemetry to drive your costs up