As we are all aware, the next wave of Office 365 is currently in preview and will be available soon. One of the expected (and long awaited) new features is the ability to administer Lync Online via PowerShell, this is something that is lacking in the current release. I was recently working with a customer who are preparing for to transition several thousand users to Lync Online and this got me curious about remote PowerShell and Lync Online 2013. Since there is no documentation available yet for the upcoming release, I thought I would share my initial findings.
Before I go any further I should mention that at the time of writing this I am testing with a Office 365 Preview tenant and as with all things still in development, it is possible (likely even) the the final release will behave differently. I also want the mention that remote PowerShell does not work with Lync Online on an Office 365 Preview tenant (see details below) so I am sharing this information purely for those who might be interested in how it may or could work in future – I will of course update this post once the next wave of Office 365 has been released.
My discovery came after I installed the Lync 2013 administrative tools on my laptop, I was browsing around the modules folder when I noticed it had installed a module called “LyncOnlineConnector” which is not imported by default.
So as any curious geek would, I thought I would play around a little.. I imported the module and took a look at the cmdlets available.
Once imported, the “LyncOnlineConnector” module contains a “New-CsOnlineSession” cmdlet which according to the help file is used to set up a remote session to Lync Online.
If you attempt to run the cmdlet, you receive the following error: “Remote Windows PowerShell session creation is restricted by tenant Windows PowerShell policy”. This leads me to believe that remote PowerShell is currently restricted on Office 365 Preview tenants.