Configure Bookings with Microsoft Teams

Just a quick little article on how to set up bookings with Microsoft Teams


  1. E3/E5 licenses
  2. Business Apps (Free)

Next confirm bookings is turned on in your tenant M365 admin center –> Settings –> org settings –>Bookings:

Once this is done verify that your user(s) are licensed for Bookings:

From the user(s) Teams client that will be using the Booking App simply add this to the Teams client:

This will then add the bookings tile to the Teams client and allow you to add a booking calendar:

Create a new book and fill out all the necessary information:

Once this is done you can then schedule a booking:

Fill in the necessary information and send you Bookings meeting:

Once sent you should get a meeting invite like this:

Hopefully this helps with the initial setup with Bookings and Teams.

How to stop Microsoft Teams from auto launching

If you would like for Teams to be installed but to not launch without user intervention there are a few things you can do to accomplish this.

First you will need to go here and download the adm and adml files for the GPO. Once you have downloaded them and the .exe has completed you will need to copy the admx file to C:\Windows\PolicyDefinitions then while there copy the .adml file over to C:\Windows\PolicyDefinitions\en-US.

Once you have completed that you can now go to your Group Policy Management Editor. In my lab I just added this to the Default Domain Policy under user configuration –> Policies –> Admin Templates –Microsoft Teams and enabled “Prevent Microsoft Teams from starting Automatically after installation”

That takes care of the GPO settings. Now if you or your users have already launched Teams then you also have to run this script There are a few things to note on the script. First if you do not want Teams to launch at all you need to edit the line $desktopConfigFile.appPreferenceSettings.openAtLogin = $True to $false. Then run the script, possibly run gpupdate /force on the desktop or wait until the policy pushes out and reboot. At this point you should not see Teams launch at all.

Should you still want Teams to launch but not sign in you can take that same line and flip it to $true. This line is simply changing the settings in the .json file found in %appdata%\roaming\Microsoft\Teams file is desktop-config.json The line is

Now once this is all set and working your end user if they prefer can go to settings and check “auto-start application” if they would rather have the app auto start.


How to release a Conferencing service number in Microsoft Teams

From time to time you may need to give up a Dial in conferencing number and assign a new one for whatever reason. This is a quick how to on the subject.

Fist you should get the conference bridge identity.

Get-CsOnlineDialInConferencingBridge and note down bridge identity

Then you can run something similar to this:

Set-CsOnlineDialInConferencingUserDefaultNumber -FromNumber 14255550100 -ToNumber 14255550101 -NumberType Toll -RescheduleMeetings -BridgeId 9884626f-dcfb-49f4-8025-912f5bc68fdc

The above cmdlet simply replaces the default number from 0100 to 0101

Once that is done it will start the process of rescheduling meetings.

Now we can move forward with unassigning the number from a conference bridge and release it.

The cmdlet we want to use is:

Unregister-CsOnlineDialInConferencingServiceNumber -BridgeName “Conference Bridge” -RemoveDefaultServiceNumber 14255550100

Once I ran the above cmdlet it turned my service number to “unassigned” which then I was able to release the number.

The simplest way to do this is to go into your Teams admin portal. Then select voice –> phone numbers –> select the phone number and then click release.