Execution policy matters. I tend to use the Unrestricted policy because it allows me do what I need to do and it always warns when it is running a script or configuration file unlike bypass.

It’s always helpful to unload PSSnapins and Modules and variables from memory when you’re using PowerShell scripts – but that’s outside the scope of this blog.

There are a few things to note about this script and anything else you do in PowerShell:

Windows PowerShell Module for Lync Online (Skype for Business Online).

Windows Azure Active Directory Module for Windows PowerShell (64-bit version).

Microsoft Online Service Sign-in Assistant for IT Professionals RTW.

The links below have the software you’ll need – if you don’t connect to the Skype for Business you don’t have to download the last one. What You Need to Beginīefore you can connect at all you need to download and install some modules to help you make the connection. Regardless, you still must be logged in as the user that created the encryption key to decrypt it. The bad news about the encrypted password: you can decrypt it back to clear text.

The good news about the encrypted password: you can decrypt it back to clear text. It can only be decrypted by the user who created it. Since you would never save a password in a text file (even if your hard drive is encrypted), I recommend you use a feature in PowerShell to encrypt the password.

Here’s how you do it…īut, before you get to that, have you read my article on getting started with Office 365 and PowerShell? A Note on Encrypting Passwords in PowerShell I find logging into Office 365 in PowerShell can be cumbersome, so I always try to do it by using a script to make it easier.

Log in o365