Forum Discussion
ExchangeOnlineManagement v3.5.1 Breaks Application Authentication
We use and provide services that leverage the application authentication method of the ExchangeOnlineManagement PowerShell module. The latest stable version of the module, 3.5.1, breaks this functionality.
Additionally, any errors are unavailble as they are now behind a GDPR compliant error message:
OperationStopped: IDX12729: Unable to decode the header '[PII of type 'System.String' is hidden. For more details, see https://aka.ms/IdentityModel/PII.]' as Base64Url encoded string.
There does not appear to be a way to disable the PII bit through the PowerShell Module to troubleshoot this either.
We have reverted to v 3.5.0 to continue to be able to use our current scripts and processes.
v3.5.1 introduces GDPR-compliant error obfuscation, making troubleshooting harder. Reverting to v3.5.0 is a good workaround. Microsoft does not currently allow disabling PII obfuscation. Monitor updates for a fix or consult Microsoft support.
Hi, Carl.
If your script also happens to be using the Microsoft.Graph modules, then you might want to have a read of the following thread.
It could easily be the case that the introduction of the Json.Utf8JsonReader .NET library to the ExchangeOnline module is causing conflicts with other modules, too, but I'm only aware of the conflict with the Graph modules.
As I summarised over in the other thread, this specific coexistence scenario isn't a bug and will always be around given it's not practically possible to have all module developers perform inter-module compatibility testing against every version of every other module. It'll remain incumbent on end-users to pick versions of modules that can happily coexist.
Cheers,
Lain
