MSAL - AcquireTokenInteractive - different user experience

I am performing an oauth flow for signing into EWS using MSAL (4.22) and AcquireTokenInteractive.
This is working but it is offering a different and much less convenient sign-in experience from that in a 3rd party off-the-shelf tool that is also signing in using the same Azure App and the same user.
I do not know if this app is using MSAL (or ADAL etc).

My code gets the experience below:

When the user selects the account A the user is always asked to supply the password and always given an MFA challenge, even if already signed in and challenged previously.
MFA is set via CAP with a 30 day sign in.

The third party app has the following user experience:

In this case when choosing accoount A the user is immediately signed in with no request for password and no MFA challenge even on the first use.
This is much more convenient.

My problem is that I do not know what I need to do to provide this same experience.

The prompt above has some immediate differences from the prompt from my code.
It lists more accounts.
Two of the accounts, included Account A, have a larger desciption.
Instead of a single line with the email address they have a three line description, with the display name on the first line, the email on the second and "Connected to Windows" on the third.
Potentially the stream-lined sign-in for Account A in this case is related to it being "recognized" as connected to Windows.

Again I do not know how to get this experience, i.e. all 4 account listed, "Connected to Windows" displayed, sign-in without beiung promptoed for password and MGA every time.

I have referred to the following resources:

https://video2.skills-academy.com/en-us/azure/active-directory/develop/scenario-desktop-acquire-token?tabs=dotnet
https://video2.skills-academy.com/en-us/azure/active-directory/develop/msal-authentication-flows

Also googled, but still puzzled.

Apologies in advance if this has an obvious answer, but any advice is appreciated.