[Problem/Bug]: Msal authentication Msal via a broker to webview2

What happened?

I have a desktop app that I am successfully authenticating utilizing a broker for authorization through a public client. I have the authentic result; which gives me user identifier, access token, and user principal name. I asked copilot and it recommended adding cookies and then says adding a header to webview2 request handler. All were successful with the addition, but Microsoft when going to office apps like word and outlook it still wants a login. I’ve done this is a react app with local storage or
Persistent caching as well. But winui3 desktops that host a webview2 for its primary functionality doesn’t cross authenticate.
Please help me ?

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

No response

SDK Version

16.2

Framework

WinUI2/UWP

Operating System

Windows 10

OS Version

H22

Repro steps

Tried cookies and request via webview2 apis and handlers

Repros in Edge Browser

Yes, issue can be reproduced in the corresponding Edge version

Regression

Don't know

Last working version (if regression)

No response

Start by reviewing the WebView2 APIs and request handlers mentioned in the report, then reproduce the behavior in the stated WinUI2/UWP environment with SDK 16.2 on Windows 10. Done means a broker-authenticated session in the desktop app also works when opening Word and Outlook without another login.