how to schedule meeting from Teams channel and email all members.

With the latest release of Microsoft Teams you now have the option to schedule a meeting from inside the channel itself.

The problem is no-one is seeing the invite and therefore missing the meeting. The meeting is setup and shows in the channel but it never makes it to the Outlook calendar for reminders.

There is a real easy solution to this. You can either do a few steps from powershell and Outlook using the following methods:

First we will connect to Exchange online powershell:

$cred = get-credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $cred -Authentication Basic -AllowRedirection
Import-PSSession $Session

Once we are connected to Exchange online then we run the cmdlet:

Set-UnifiedGroup -Identity <groupname> -HiddenFromExchangeClientsEnabled:$False

At this point you will now need to go to your groups folder in OWA or Outlook:

Navigate to the group we are editing, in Outlook Highlight the group and go to Group settings and edit the group.

Once the group edit comes up enable “subscribe new members so they receive group emails in their inbox. Hit Ok and wait a few for it to populate out to the members in the group.

If you want to hide the group after making the changes simply run the cmdlet: Set-UnifiedGroup -Identity <groupname> -HiddenFromExchangeClientsEnabled:$True

Now all users in the group will receive the email.

Now if you have access to the admin portal for your tenant you can do this a little quicker.

Simply login to the 356 admin center –> groups –> test group –> settings –> check the box Send copies of group conversations and events to group members.

Its up to you if you want to hide it from the GAL. One that is done you can then go back and schedule a meeting and all the members will get the meeting invite as they would if you were to send this from Outlook.

This will work for both Private and Public Groups.

Skype For Business contact migration to Teams

Every now and then when migrating Skype users to Microsoft Teams the contacts will not migrate over. Here is a quick blog on what is required and limitations of what can be migrated over.

Requirements for SFB to Teams:

  • Users cannot be UCS enabled, The users contacts must be stored on SFB and NOT Unified contact store or UCS.
  • Obviously the users account must be online
  • Users need to be in Teams only for the contacts to be migrated

Limitations:

  • Only Federated and Tenant contacts will be migrated
  • Maximum number of contacts is 1000
  • Max number of groups is 64
  • Skype consumer contacts do not get migrated
  • Any distribution groups also will not get migrated

How the migration process works:

  1. The contacts will be triggered to migrate once the user clicks on the contacts tab in Teams. While this will trigger the migration the users will not see the contacts until the migration is complete and they have logged out and back in.
  2. If the migration fails it will re-trigger after 8 hours.
  3. If users are not enabled for federation the federated contacts will not migrate
  4. If users are UCS enabled then the contacts will not migrate. Once UCS is set to false and the contacts have moved over to SFB the process will re-trigger

UCS cmdlets can be found here:
https://docs.microsoft.com/en-us/skypeforbusiness/deploy/integrate-with-exchange-server/use-the-unified-contact-store

Set-CsUserServicesPolicy -Identity global -UcsAllowed $False

Rollback the UCS policy by using Invoke-CsUcsRollback -Identity “user” if you do not roll back the user from UCS the contacts will not be removed for the contact store. If you do not change the policy and you run the rollback after 7 days the contacts will revert back to UCS.

Configure Bookings with Microsoft Teams

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

Prerequisites:

  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
appPreferenceSettings”:{“disableGpu”:false,”openAsHidden”:false,”openAtLogin”:false,”registerAsIMProvider”:false,”runningOnClose”:true}

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.

Enjoy!

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.

Custom Background in Teams meeting

With all the hype with video chat and the customization of Teams now I figured a quick blog post of the “How-To” would be cool.

There are two ways you can do this, the first way is if the option has not made it out to your tenant yet. Get your custom picture and upload to %APPDATA%\Microsoft\Teams\Backgrounds then you can create a meet now to test.

Meet now can simply be created by going to the calendar tab –> Meet now in the top right

Once that is done you can click on the 3 … (More Action) Select “show Background effects” In the list you should see you custom background. Select it and you are all set.

Now, If your tenant has the latest update you can do the same as above but simply upload your custom background by selecting the “Upload Image” button.

Select your background that you would like

you can preview or apply and turn on video.

At this point you are all set.

Thanks for visiting #COYS!!

Configuring information barriers in Teams

Pre reqs:

  1. First make sure scoped directory search is turned on:

Teams admin center, select Org-Wide settings –> Teams settings

Under search, next to Scope Directory search in Teams using an Exchange address book policy (ABP), turn the toggle on.

Please note this can take up to 24 hours to replicate. https://docs.microsoft.com/en-us/MicrosoftTeams/teams-scoped-directory-search

2. Licensing and permissions:

  • Microsoft 365 E5
  • Office 365 E5
  • Office 365 Advanced Compliance
  • Microsoft 365 E5 Information Protection and Compliance

    3. To define or edit information barrier policies, you must be assigned one of the following roles:
  •  Microsoft 365 global administrator
  •  Office 365 global administrator
  •  Compliance administrator
  • IB Compliance Management (this is a new role!)

    4. Turn on audit logging
  • 0365 admin –> compliance –> Search –> Audit log search
  • Click “turn on auditing”

The banner is then updated:

You can also do this via the Exchange online Powershell:

Turn on audit log search:

Set-AdminAuditLogConfig -UnifiedAuditLogIngestionEnabled $true

Turn off audit logs search:

Set-AdminAuditLogConfig -UnifiedAuditLogIngestionEnabled $false

To verify that audit log is off via Powershell

Get-AdminAuditLogConfig | FL UnifiedAuditLogIngestionEnabled

Or via the Admin Center 

5. Make sure no exchange address book policies are in place

https://docs.microsoft.com/en-us/exchange/address-books/address-book-policies/remove-an-address-book-policy

6. Provide admin consent for Microsoft Teams:

On this step first you need to make sure you have the permissions for the 0365 security and Compliance:

https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/permissions-in-the-security-and-compliance-center?view=o365-worldwide#permissions-needed-to-use-features-in-the-security–compliance-center

Login-AzureRmAccount $appId=”bcf62038-e005-436d-b970-2a472f8c1982″ $sp=Get-AzureRmADServicePrincipal -ServicePrincipalName $appId if ($sp -eq $null) { New-AzureRmADServicePrincipal -ApplicationId $appId } Start-Process “https://login.microsoftonline.com/common/adminconsent?client_id=$appId

Step 2 Segment users:

  1. Before we proceed to this section make sure your directory data has values that you can use to define segments. List of attributes you can use with information barriers can be found here:

https://docs.microsoft.com/en-us/microsoft-365/compliance/information-barriers-attributes?view=o365-worldwide#reference

2. Create the “segment”

New-OrganizationSegment -Name “Sales” -UserGroupFilter “Department -eq ‘Sales'”

New-OrganizationSegment -Name “Research” -UserGroupFilter “Department -eq ‘Research'”

Now we set it so Sales and Research are not able to communicate

New-InformationBarrierPolicy -Name “Sales-Research” -AssignedSegment “Sales” -SegmentsBlocked “Research” -State Inactive

Since the above cmdlet is no symmetrical we need to also block research from talking with sales:

 New-InformationBarrierPolicy -Name “Research-Sales” -AssignedSegment “research” -SegmentsBlocked “sales” -State Inactive

Apply the information barrier policy:

  1. First run Get-informationbarrierpolicy to see a list of our policies we defined:

In this example the Guid from running the above cmdlet is 15912fe7-0dd5-4b90-b3e0-4b94168cb63e so we will run:

Set-InformationBarrierPolicy -Identity 15912fe7-0dd5-4b90-b3e0-4b94168cb63e -State Active

Then you must also run this same cmdlet for the other segment we created using its guid.

Now that we have defined our two segments  you must run the following cmdlet to “start” the policy:

Start-InformationBarrierPoliciesApplication

At this point you should be all setup. However, After approximately a half hour, policies are applied, user by user, for your organization. If your organization is large, it can take 24 hours (or more) for this process to complete. (As a general guideline, it takes about an hour to process 5,000 user accounts.)

How to give a Teams channel a new owner

At times we have users that create channels leave the org and we end up with a rouge channel. When this happens we need to assign ownership to a new user. This blog will quickly touch on that and hopefully give some guidance on how to do so.

We will go through creating a private room then disable the creator in AD.

First we login and build a team from scratch

Once the channel has been created we add a few users to the room.

After this we disable the owner in AD

Wait for AD replication and then try to sign in as the current owner

As you can see this user is no longer valid in AD but they are still considered the owner of the channel

To fix this simply go into your Teams admin center select Teams –> Manage Teams –> select the Team you want to edit –> then select the user that will be the new owner. This should then take care of a rouge user being an owner of the channel in question.

Comments and feedback is welcome.

How to stop Microsoft Teams from starting at startup

Method 1: Disable from Task Manager

You can disable Microsoft Teams from Task Manager and it will not start up automatically:

  1. Press Ctrl + Shift + Esc key to open Task Manager.
  2. Go to Startup tab.
  3. Click on Microsoft Teams, and click on Disable.

Method 2: Change settings

You can the settings in Microsoft Teams and see if that helps:

  1. Launch Microsoft Teams.
  2. Click on the Profile icon on the top right corner and click on Settings.
  3. Scroll down and clear the checkbox for Auto Start Application.

Method 3: Modifying Registry

You can delete the entry for Microsoft Teams from Registry and check:

Note:  Important this section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.

Follow the steps to take backup of registry.  

  1. Press Windows key + R, to open Run dialog box.
  2. Type regedit and click on OK.
  3. Go to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
  4. On the right pane, right click on the registry entry for Microsoft Teams and select Delete.

If you want to uninstall Microsoft Teams from the computer, refer the steps mentioned in the article Uninstall Microsoft Teams.