Launch Teams app when clicking “Join Microsoft Teams Meeting” link in Meeting invite

I’ll start of by saying that I really love Teams, I do, BUT there is definitely room for improvement!

One of the things that really annoyed me lately is when joining an online meeting, the default web browser opens up and you need to click the “Open” button in the popup…. Why Microsoft….. Just Why??

Luckily (For you๐Ÿ˜) it annoyed me enough to do some research and figure out how to get around it. Unfortunately I cant suppress the opening of the web browser, but I can get it to open the Teams app automatically ๐Ÿ‘

So here we go. Oh, and by the way, this guide will work with Google Chrome and Edge Chromium.

So you get an invite to a Teams meeting, and when you want to join, you click the “Join Microsoft Teams Meeting”


It opens your web browser, and that box, where you have to press “Open” (If you have the desktop app installed),


it launches you’re Teams app, and you’re ready to go. But why? Why not just open you’re Teams app right away?

Here is how in Edge Chromium

Open your registry and navigate to


Now, most likely you don’t have much in there, so you need to add the following key’s


Now add a new STRING value, name it 1, open it up and add the value



and that’s it๐Ÿ˜ณ, from now on when you click the “Join Microsoft Teams Meeting”, it opens your default browser and then the Teams meeting๐Ÿ‘

If you want to do it with a Commandline, this should do it (Remember to run CMD as Administrator ๐Ÿ˜‰)

REG ADD HKCU\Software\Policies\Microsoft\Edge\URLAllowlist /v “1” /d “msteams://*” /t REG_SZ

Here is how in Google Chrome


Now add a new STRING value, name it 1, open it up and add the value



Again, if you want to do it with a Commandline, this should do it (Remember to run CMD as Administratorย ๐Ÿ˜‰)

REG ADD HKCU\Software\Policies\Google\Chrome\URLWhitelist /v “1” /d “msteams://*” /t REG_SZ

You can double check that the policy works correctly, if you open Google Chrome or Edge Chromium and go to:


Or for Edge



Happy Teaming ๐Ÿ˜Š


Teams – now in Lock-down – Limit creations

So, in these times, Teams are becoming extremely popular and valuable for company’s with everybody working from home, and Microsoft giving away 6-months of free Teams licenses for new Tenants, it’s growing crazy fast. Its easy to get started, and users can create teams out-of-the-box๐Ÿ™ˆ.

But for a few Administrators it can (In my own humble opinion, anyways) turn into a Wild West with out any form of control, with users creating new teams, as they like. (Why this isn’t a build in feature, and enabled by default, I don’t understand?๐Ÿ™„)

It might be an “old school” kind of thinking, but I would like some control over who does what in “my environment”.

I figured that others would be in the same situation, so I started my little adventure, in to figuring out how to “Lock-down” Teams, so that normal users wont be able to create what ever they want. You can do this in various ways, but the one I liked the most, is where you can control access to Teams creation through Group access. Fortunately for us, Microsoft has released an article on how to. You can read the original MS article HERE.

Lets get into it wlEmoticon-fingerscrossed.png

First of, you need to log in to your Office 365 Tenant, with your Global Admin and create the security groupgroup creationIn my Example I created the group “Office 365 group limitation” Copy the below PowerShell script to your favorite editor, like Notepad, PowerShell ISE or Visual Studio Code. Name the script how you like, I kept it like MS suggested, GroupCreators.ps1

$GroupName = "Office 365 group limitation"
$AllowGroupCreation = "False"


$settingsObjectID = (Get-AzureADDirectorySetting | Where-object -Property Displayname -Value "Group.Unified" -EQ).id
	  $template = Get-AzureADDirectorySettingTemplate | Where-object {$_.displayname -eq "group.unified"}
    $settingsCopy = $template.CreateDirectorySetting()
    New-AzureADDirectorySetting -DirectorySetting $settingsCopy
    $settingsObjectID = (Get-AzureADDirectorySetting | Where-object -Property Displayname -Value "Group.Unified" -EQ).id

$settingsCopy = Get-AzureADDirectorySetting -Id $settingsObjectID
$settingsCopy["EnableGroupCreation"] = $AllowGroupCreation

	$settingsCopy["GroupCreationAllowedGroupId"] = (Get-AzureADGroup -SearchString $GroupName).objectid
 else {
$settingsCopy["GroupCreationAllowedGroupId"] = $GroupName
Set-AzureADDirectorySetting -Id $settingsObjectID -DirectorySetting $settingsCopy

(Get-AzureADDirectorySetting -Id $settingsObjectID).Values

Change the Group name in the script, to the group name you created in the beginning. You will need your O365 Global admin, to run the script. Also if you haven’t already, you need to install the Azure AD module for PowerShell.

Install-Module AzureADPreview

If you have the used the module before or maybe have the general availability version (2.0), make sure you either remove and reinstall or update it before continuing.

And you’re ready ๐Ÿ‘ If you have a handful of users that you trust, you add them to the group, or maybe your Helpdesk workers, so that they can create Teams for the users.

This is what it looks like now for the users!

Without group membership…


With group membership…


From now on, when users go to Teams and click the “Join or Create a team”, the only options is to join a team with a code or they can search for the Team, if they know the name. Here’s a few options:

  1. You as an admin, add them.
  2. You tell the newly appointed owner to add users themselves ๐Ÿ‘
  3. The users search for the Team and join ๐Ÿ‘
  4. Or you send them a Code, that they can use to join the Team with (Team owner can do this) ๐Ÿ‘

That’s it, you’re done and have just a little more control with what’s going on again ๐Ÿ˜Š