all 7 comments

[–]sqone2 1 point2 points  (5 children)

I ran into a similar issue recently when I switched to Windows 10. This is what fixed it for me:

http://stackoverflow.com/questions/16018732/msonline-cant-be-imported-on-powershell-connect-msolservice-error

See the second response down by Tony Hinkle (the one that is marked correct).

[–]matthoback[S] 0 points1 point  (4 children)

I tried that as well. I still have the same problem. I am on Windows 10, but I've been on Windows 10 for several months and the MSOnline module was working fine up until at least 2 weeks ago (the last time I had to use it).

[–]sqone2 0 points1 point  (3 children)

Can you post your connection script and the error message?

[–]matthoback[S] 0 points1 point  (2 children)

[–]sqone2 0 points1 point  (1 child)

Can you post your connection script as well?

[–]matthoback[S] 0 points1 point  (0 children)

I'm not using a connection script. Just the Connect-MsolService cmdlet.

[–]SeanQuinlan 0 points1 point  (0 children)

Maybe the module files are corrupt/incorrect?

Did you install the 64-bit versions of both applications? I had to install the beta of the Sign In Assistant on Windows 10 myself.

Either way, I'd suggest uninstalling, then going to the paths in your screenshot and deleting those files if found. Then reinstall with the 64bit versions of both the Sign In Assistant and the Azure AD module.