Register the new Teams as the chat app for Microsoft 365(requires restarting Microsoft 365 applications) is not working

Anonymous
2023-10-13T06:21:17+00:00

Register the new Teams as the chat app for Microsoft 365(requires restarting Microsoft 365 applications) is not working, Can't chat with contacts in Outlook

Microsoft Teams | Microsoft Teams for business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

44 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-04-05T16:11:44+00:00

    We looked at this one all day today. Here's what worked for us as of 4/5/2024.

    $RegistryPath = 'HKCU:\SOFTWARE\IM Providers\'

$FriendlyName = 'MsTeams'

If (-NOT (Test-Path $RegistryPath)) {

New-Item -Path $RegistryPath -Force | Out-Null

}

New-ItemProperty -Path $RegistryPath -Name "DefaultIMApp" -Value $FriendlyName -PropertyType String -Force

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-04-05T07:41:19+00:00

    how to enable this file

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  4. Anonymous
    2024-03-22T08:35:31+00:00

    Thanks Thomas. Our GPO team initially told that there is no GPO deployed for same. After investigating myself we found that there is a GPO policy pushing classic Teams "Teams" as DefaultIMApp.
    Disabled the GPO and this resolved the issue.

    Others you can run below command to get the client machine's applied GPO list and find the culprit policy.

    cmd:\> gpresult /h c:\temp\gpresult.html

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-03-21T13:42:51+00:00

    We found the issue internally to be a old policy that was writing "Teams" to the DefaultIMApp registry at a periodic check-in, that's why it was happening. New Teams is supposed to contain the value "MSTeams". Running Procmon on that registry path helped determined that.

    Was this answer helpful?

    0 comments