Skip to content

Tag: PowerShell Core

Microsoft Teams Client customisation settings via PowerShell

I deploy Microsoft Teams to all my clients by default. Some of the default settings are not what I want, but many of my test clients are not managed in a domain (or just Azure Active Directory joined), and that makes it hard to deploy any configuration. And as a bonus, I use Mac Clients!

I started to create a PowerShell Script to manipulate the desktop-config.json. During some digging, I found an article Eli Shlomo: Microsoft Teams Client Personalization with PowerShell. I really liked his code, so I decided to drop my approach and adopted his solution to fit my own requirements.

Connect to Office 365 with PowerShell Core from non-Windows

As a Apple Fan boy, I'm happy that PowerShell Core is now available for macOS! Together with Visual Studio Code I'm able to run a lot of things on my Mac without having a virtual Windows machine running.

I was asked: "Do you use the native macOS PowerShell to connect to Office 365".
The short answer is: "Not really"!

And at the moment (December 2017) there are two main reasons for that:

  1. The connection is not fast and connection is not reliable! (See below)
  2. Many Office 365 services, like Skype for Business or Sharepoint, need a PowerShell local module and they are not available for non-Windows platforms yet!

I tested all the v6 beta releases and the basic Exchange Online connection worked in some, sometimes better, sometimes not. Even with the latest PowerShell Core v6 RC2 the connection isn't always working or it is very slow during the connection or the import. Connecting to the Compliance Center seems to work like the Exchange Online connection: In general it seems to work… With exactly the same issues.

This content is older than 2 years. It might be outdated.