Open hidemaruki opened 2 years ago
Sorry I've missed this one, does the issue still persist with the enhancements that were made in the latest 1.3.6 release related to encoding?
I'm referring to this from the release notes:
Private function Invoke-IntuneGraphRequest has been updated with UTF-8 encoding content type support. From this version and on, when the script file is properly encoded with UTF-8 with BOM, special characters should now work as expected.
Thank you for developing amazing tool!
If possible, I'm glad that you make this code support for double-byte character languages .