Fix MSAL COM interop exception by forcing system browser authentication #50
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MSAL 4.56.0's embedded WebBrowser authentication throws
ArgumentException: ObjectForScripting's class must be visible to COMwhen connecting to Power Automate API via OAuth.Changes
AcquireTokenInteractiveto use system browser instead of embedded WebViewThis avoids MSAL's internal COM interop requirements while providing standard browser-based OAuth flow.
Original prompt
This section details on the original issue you should resolve
<issue_title>'Unhandled exception' error after clicking Connect to Power Automate API</issue_title>
<issue_description>FEH ver: 1.2025.10.2
XRMToolBox ver: 1.2025.10.73
Updated to the latest versions of XRMTB and FEH yesterday and am now getting the following error after clicking Connect to Power Automate API:
I am connected to the environment using OAuth.
Full error text: