When installing in our application, I’m seeing install/runtime breakage on Windows ARM64 due to MSAL’s transitive dependency allowing a 'cryptography' package version that no longer publish Win ARM64 wheels.
In current MSAL (1.36.0), install_requires includes cryptography>=2.5,<49, which allows cryptography 46.0.4+. Starting with 46.0.4, cryptography dropped win_arm64 wheels, so installers fall back to
source builds that commonly fail in environments without full Rust/MSVC/OpenSSL toolchains.
I validated that pinning to a wheel-backed version restores functionality on ARM64 (e.g., cryptography==46.0.3 + msal==1.36.0 installs and
imports successfully).
When installing in our application, I’m seeing install/runtime breakage on Windows ARM64 due to MSAL’s transitive dependency allowing a 'cryptography' package version that no longer publish Win ARM64 wheels.
In current MSAL (1.36.0), install_requires includes cryptography>=2.5,<49, which allows cryptography 46.0.4+. Starting with 46.0.4, cryptography dropped win_arm64 wheels, so installers fall back to
source builds that commonly fail in environments without full Rust/MSVC/OpenSSL toolchains.
I validated that pinning to a wheel-backed version restores functionality on ARM64 (e.g., cryptography==46.0.3 + msal==1.36.0 installs and
imports successfully).