You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
EBOOZ 7fc3cc5d99
Added note on status
1 month ago
Get-TeamsStatus.ps1 Update Get-TeamsStatus.ps1 3 years ago
Install.txt Updated instructions to unblock Settings.ps1 3 years ago Added note on status 1 month ago
Settings.ps1 Improvements and adddition of friendly names to Settings file 3 years ago
nssm.exe Initial version 3 years ago

[!NOTE] This solution only works for the legacy version of Microsoft Teams. The new version does not contain a logs.txt file which can be read by the script. Therefor this repository is not maintained anymore.


We're working a lot at our home office these days. Several people already found inventive solutions to make working in the home office more comfortable. One of these ways is to automate activities in your home automatation system based on your status on Microsoft Teams.

Microsoft provides the status of your account that is used in Teams via the Graph API. To access the Graph API, your organization needs to grant consent for the organization so everybody can read their Teams status. Since my organization didn't want to grant consent, I needed to find a workaround, which I found in monitoring the Teams client logfile for certain changes.

This script makes use of two sensors that are created in Home Assistant up front:

  • sensor.teams_status
  • sensor.teams_activity

sensor.teams_status displays that availability status of your Teams client based on the icon overlay in the taskbar on Windows. sensor.teams_activity shows if you are in a call or not based on the App updates deamon, which is paused as soon as you join a call.


This solution is created to work with Home Assistant. It will work with any home automation platform that provides an API, but you probably need to change the PowerShell code.


  • Create the three Teams sensors in the Home Assistant configuration.yaml file
    name: Microsoft Teams status
    icon: mdi:microsoft-teams
    name: Microsoft Teams activity
    icon: mdi:phone-off

  - platform: template
        friendly_name: "Microsoft Teams status"
        value_template: "{{states('input_text.teams_status')}}"
        icon_template: "{{state_attr('input_text.teams_status','icon')}}"
        unique_id: sensor.teams_status
        friendly_name: "Microsoft Teams activity"
        value_template: "{{states('input_text.teams_activity')}}"
        unique_id: sensor.teams_activity

  • Generate a Long-lived access token (see HA documentation)
  • Copy and temporarily save the token somewhere you can find it later
  • Restart Home Assistant to have the new sensors added
  • Download the files from this repository and save them to C:\Scripts
  • Edit the Settings.ps1 file and:
    • Replace <Insert token> with the token you generated
    • Replace <UserName> with the username that is logged in to Teams and you want to monitor
    • Replace <HA URL> with the URL to your Home Assistant server
    • Adjust the language settings to your preferences
  • Start a elevated PowerShell prompt, browse to C:\Scripts and run the following command:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
Unblock-File .\Settings.ps1
Unblock-File .\Get-TeamsStatus.ps1
Start-Process -FilePath .\nssm.exe -ArgumentList 'install "Microsoft Teams Status Monitor" "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" "-command "& { . C:\Scripts\Get-TeamsStatus.ps1 }"" ' -NoNewWindow -Wait
Start-Service -Name "Microsoft Teams Status Monitor"

After completing the steps below, start your Teams client and verify if the status and activity is updated as expected.