I was helping a coworker install and set up the 365/Azure cmdlets on her laptop today. Following the instructions on this page:
http://technet.microsoft.com/en-us/library/jj151815.aspx
She downloaded and installed the sign-in assistant and the AzureAD Module for both 32 and 64 bit. Then she tried to connect using
$msolcred = get-credential
connect-msolservice -credential $msolcred
She was getting: Connect-MsolService : The term 'Connect-MsolService' is not recognized as the name of a cmdlet, blah blah blah.
I told her to check to see if the module was available, and it was not in her list of available modules. The MSOnline/MSOnlineExtended folders were not in her C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules or C:\Windows\System32\WindowsPowerShell\v1.0\Modules directories. I *did* just see Ed Wilson's post about the default path for the modules changing (http://blogs.technet.com/b/heyscriptingguy/archive/2014/03/24/getting-started-with-office-365-and-powershell.aspx) and I will check that out tomorrow when she gets back in.
I got a new laptop (Surface 3!) last month and noticed the same thing - the msonline module folders were missing after I installed the Azure cmdlets. I cursed and copied the folders from my old laptop and was fine from there. But I have to get a bunch of people set up with powershell for 365, and if the cmdlets have been replaced with the Azure cmdlets or something I'd like to figure that out now.
Has anyone else experienced this recently when installing the Azure cmdlets?