I have an issue that I get these warnings on existing resources which I cannot do anything about in Bicep. And I can’t seem to turn the warning of for specific lines in Bicep? I’ve tried putting //NOSONAR everywhere around the code both with and without the specific warning id. Do you have any solution? 
Hello @Wesztman and welcome to community!
Thanks for raising awareness on this topic.
We are already aware of this issue, here is the corresponding Jira ticket.
We hope to fix it soon.
I unfortunately do not see any workaround for this issue.
Sorry for the inconvenience caused.
Best,
Rudy
Looks like you are in your IDE, so you are getting the issue thanks/because of SonarLint. It looks to be a False-Positive issue.
If you connect your SonarLint to a SonarQube or SonarCloud instance, then you can manage the statuses of your issues on the server side, share this with your colleagues and silence the issue on your IDE.
See this documentation, the keyword is “Connected Mode”.
Alex
Hello @Wesztman,
We just wanted to highlight that the issue has been fixed and will be part of the next version.
Best,
Rudy
2 Likes
Awsome! Thanks for letting me know! 
Is there a way to still use NOSONAR for bicep files?
For example I want to leave a todo comment, but it is not adhering to the NOSONAR comment.
// TODO: check best practices with diagnostic settings NOSONAR
This for example still raises S1135