Martin Gibney - Microsoft Teams

As part of my dive into automating as much as possible of a Microsoft Teams implementation or migration from Skype for Business On-Premise, I am focusing on scripting as much as possible. This post focuses on the licensing element. You are unable to enable users in Teams unless they have the correct licenses already assigned. The following commands will allow us to check what licensing is available to the tenant. To check this you must first connect to the Microsoft Online Service. Run: Connect-MsolService You will be prompted for your O365 credentials and any MFA (you have MFA enabled right...) Now run:  Get-MsolAccountSku You will see the output on the screen of the different licenses on the tenant: In the output the first element before the license type we have the tenant name XXXXX: followed by the License type and how many units of each, warnings and ConsumedUnits (Assigned Licenses) This ties in with what we see in the GUI in Office 365 Admin Center: Thes

Why can't things just be easy.... Now that Microsoft Teams allows "Guest Access" it is important to note that you need to enable this in a few locations in Office 365 unfortunately and not just in the Teams Admin Portal as (I) and most people seemed to think.  Teams Portal: Log in to the  Microsoft Office 365 Admin Center Under  Admin Centers , select  Teams  Go to  Org-Wide Settings Under  External Access , you can enable this if you want to let your Teams and Skype for Business users communicate with users that are outside of your organization. You can also whitelist specific domains here. Under  Guest Access , you’ll want to turn on the  Allow Guest Access in Teams button Office 365: Log in to the  Microsoft Office 365 Admin Center Under  Settings , go to  Security & Privacy Click  Edit  beside Sharing Turn on  the setting for  Let Users Add New Guests To The Organization From here, you can also click on the  Site Settings  link to verify

So the most common issue I come across is edge server replication issues in Skype for Business during a build stage. I had one today and I followed all the details in my previous post on replication yet still had UpToDate: FALSE. This was getting very annoying and certs were checked and Front End and Edge both used same CA, so that  looked good....except when i dug a little deeper, it seemed that the SQL server where the CMS was hosted was using a different CA and of course the CA was not in the Trusted Root Certificate Authority store on the edge server. I found this by running the CLS Logger on the Front end and ran an Invoke-CsManagementStoreReplication , waited about 30 seconds then stopped logging. The result showed: Issue with Remote Source  - which means where it is coming from, NOT the Edge server. I confirmed the SQL Cluster has a certificate from a different CA, installed the cert to the Trusted Root Certificate Authority store on Local Machine  and off it went!!!.