[Ryan Yates (kilasuit)]

This Fixes #3822 (I think)
This also fixes PowerShell/PowerShell#27711 where it was originally reported.

Changes proposed in this pull request

• Bump the MSAL Libraries from 4.90.0 to 4.92.0 to fix an issue with the Graph Module working in PowerShell 7.7.0-rc.1 which is built on .NET 11
• Bump the version from 2.41.2 to 2.41.3

Note: I have not attempted any local builds of this repo at all to confirm that this does indeed fix the issue.
This is because I am not familiar with this repo, nor do I have much need for using the Graph SDK at this time.

However, in all I've read, I am confident that this should be the main things that are needed to be able to build a PowerShell 7.7.0-rc.1 compatible build of the Graph SDK.

Let me know if you need anything else from me at all?

[Ramses Sanchez-Hernandez (ramsessanchez)]

Ryan Yates (@kilasuit) , have you built/run the auth module locally with these version bumps? Can you confirm this works with 7.6 as well as the 7.7 version you mentioned. Once confirmed I can approve this

[Ryan Yates (kilasuit)]

Ryan Yates (Ryan Yates (@kilasuit)) , have you built/run the auth module locally with these version bumps?

Ramses Sanchez-Hernandez (@ramsessanchez) - I did mention that I'd not tried to build the repo so could not test that these proposed changes will indeed fix them, & i don't have a personal need for this fix as I don't have a need to use the SDK in any of my current projects.

If you read the issue this should close #3822 then you'll see more of the investigation that lead to finding that to fix this will require the bump of MSAL to 4.92.0 so that Connect-MgGraph will work without needing -UseDeviceCode which Andres Bohren (@BohrenAn) confirmed as a workaround in this comment in the issue that originally been raised back in the PowerShell repo back on July 22 by Ryan Markwald (@RMarkwald) where I asked them to raise an issue in here one Oct 9th.

Can you confirm this works with 7.6 as well as the 7.7 version you mentioned. Once confirmed I can approve this

I couldn't see from the changes why it would end up breaking in 7.6 at all, though this was very much quite a quick jump in for 15min or so & step through provided logs and walk back through the code path & do some issue searches across the dependant repos whilst I was between other things that I really need to jump back into instead of digging into trying out a local build and test myself at this time.