ITJoeSchmo

If this is an assembly conflict, this workaround solution may work but would need to be adjusted for the particular conflicting assembly and versions. There is instruction on seeing that...

> Please run `[System.AppDomain]::CurrentDomain.GetAssemblies() | where {$_.FullName -ilike "*newtonsoft.json*" } | select -Property FullName,location | sort -Property FullName | fl` and share the result. If you see Newtonsoft.Json being loaded...

Same issue as here: https://github.com/Azure/azure-powershell/issues/21960 -- a conflict on the assembly NewtonSoft.Json due to modules loading 2 different versions and Windows PowerShell (aka 5.1 and older) do not know what...

We have been using this work-around for the issue for a few days. The problem is that the strings in the JSON are not being wrapped in quotes. It may...

I thought it was worth hopping on here, I _believe_ this is basically just another instance of Microsoft bundling conflicting versions of the NewtonSoft.Json assembly between modules which end up...

We're also experiencing this issue, luckily not affecting our automations since they all leverage MSI/client+secret/certificates. -ContextScope Process seems to be a valid work-around for now.

Same issue as here: https://github.com/Azure/azure-powershell/issues/21960 -- a conflict on the assembly NewtonSoft.Json due to modules loading 2 different versions and Windows PowerShell (aka 5.1 and older) do not know what...