You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My log analytics primary key was hashed correctly in the scripting, but the hashed string included &. This caused the script to fail as the & symbol is protected.
... 55-4020-bf82-8fa3c12c28f4 -SharedKey rz3tpbr7Pz3AWKi5z8xkV3A&oLC2x&nN ... ~
The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double
quotation marks ("&") to pass it as part of a string.
At C:\ADOAgent_work_temp\c3b03806-9538-471e-b928-bcbd70e48fc7.ps1:4 char:291
... 0-bf82-8fa3c12c28f4 -SharedKey rz3tpbr7Pz3AWKi5z8xkV3A&oLC2x&nNtF%PFa ... ~
The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double
quotation marks ("&") to pass it as part of a string.
(Yes, this is the hashed and old version of the key.)
I was able to solve this by using my Loganalytics secondary key. I was however unable to detect where exactly to input the needed wraps for the & symbol to avoid this problem in the future.
The text was updated successfully, but these errors were encountered:
My log analytics primary key was hashed correctly in the scripting, but the hashed string included &. This caused the script to fail as the & symbol is protected.
(Yes, this is the hashed and old version of the key.)
I was able to solve this by using my Loganalytics secondary key. I was however unable to detect where exactly to input the needed wraps for the & symbol to avoid this problem in the future.
The text was updated successfully, but these errors were encountered: