Obfuscated string literals

[Gary Bushey]

I came across this tidbit in https://docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/string#obfuscated-string-litera... about obfuscating string literals in KQL and it gives this example

print x="https://contoso.blob.core.windows.net/container/blob.txt?" h'sv=2012-02-12&se=2013-04-13T0...'

However when I run it, nothing gets obfuscated. Based on my reading I should see:

https://contoso.blob.core.windows.net/container/blob.txt?*****************************

but I don't.  Has anyone else tried this?

[#2 · Accepted solution]

@Gary Bushey 

I'm fairly sure this applies only to KQL in Azure Data Explorer and isn't supported by Log Analytics 

[#3]

@Gary Bushey I don't think obfuscation hides the data in query results, but rather in query logging. 

[#4]

@CliveWatson Well bummer.  Thanks for the answer

[#5]

@Gary Bushey : using the obfuscation format is still recommended as it would ensure the string is obfuscated when logged.

[#6]

@Ofer_Shezaf I could see using it if you are writing to the logs yourself but if I am using something like the OfficeActivity log I don't see any way that I would be able to control what is obfuscated

[#7]

@Gary Bushey : Should have been clearer, I meant when the service logs internally queries execution, and in the future also to users, they are obfuscated.