Azure SDK

PowerShell modules like AZ and MS Graph each include their own versions of MSAL, causing assembly load context conflicts when users load multiple modules in the same session. This results in silent failures or misleading error messages as the runtime continues using whichever MSAL version was loaded first, rather than the expected version.