Skip to main content
Question

Updating MS Teams (MSIX)

  • November 27, 2025
  • 5 replies
  • 58 views
J
Forum|alt.badge.img

We have a Windows 11 Golden Image running for VDI.

We noticed that MS Teams wasn’t being upgraded to latest version.

I found a worklet.

  • Windows - Software Lifecycle - Upgrade to the New Microsoft Teams (MSIX)

I created a policy from it and assigned to that specific VM.

The initial evaluation code runs and comes back with:

  • The New Microsoft Teams client is already installed. Device is compliant.

This is not true because when I check the version installed its:

  • 2025 July 25

    [removed by moderator] .8024

and of course, latest version is

2025 November 19 [removed by moderator] .7193

Version update history for Teams app deployments - Office release notes | Microsoft Learn

When i look at the powershell code it’s running, the Evaluation Code checks the package name:

# Defining the New Teams package
$package = 'MSTeams_8wekyb3d8bbwe'

I also check the version on the golden image and it matches this team:

PackageFamilyName : MSTeams_8wekyb3d8bbwe

but obviously something is off because the VDI doesn’t have the most recent version so not sure what is happening and would love to be pointed to correct direction here.

Just FYI. I changed the PackageFamilyName to the

PackageFullName : MSTeams_ [removed by moderator] .8024_x64__8wekyb3d8bbwe

in the evaluation code and then of course i get:

  • The New Microsoft Teams client was not found.
  • Flagging for remediation.

In this event I’m assuming it will go and download/install new teams if it runs the Remediation Code

Thank you for your help in advance.

5 replies

M
Forum|alt.badge.img
  • Maulik_Busa
  • Pro
  • November 27, 2025

Hi ​@jguzmantransre, if im not wrong the worklet you are running is for replacing teams Classic, machine-wide, and AppX client with latest Teams (MSIX) client.

You should be able to update teams manually from Device Details > Software page if there's any update available for teams. 

Thanks 

BrandonG-Automox
J
Forum|alt.badge.img

​@Maulik_Busa  thank you for your reply. I believe you are right now that I’m reading the title worklet again. I read it differently. Thank you for your suggestion, I don’t want to update it manually, I’ll like for it to update automatically by a policy instead. 

M
Forum|alt.badge.img

​@jguzmantransre Although Teams should auto update but if you wanna create policy just for it then go with patch only policy in Automox. it will give you option to what you particularly want to patch. 

Thanks

BrandonG-Automox
BrandonG-Automox
Forum|alt.badge.img

Hi ​@jguzmantransre ,

I second what ​@Maulik_Busa has suggested and would also like to add a little more context.

Microsoft Teams has a patching behavior where it will not patch when running and isn’t typically shut down at patch time through automatic processes (which is to avoid data loss or ending a mid-meeting session).
We have an article in our Help Center that showcases patching behavior for all of our supported software titles in our catalog, along with a suggestion for how to overcome applications that don’t close at patch time.

In your case, you can use a Patch Only policy scoped for Microsoft Teams (hint: use the “everything” checkbox when searching for that software, it acts as a wildcard), and then use the override Worklet from our Catalog (linked in the help article) to ensure Teams shuts down at patch time to avoid patch failures or strange update behaviors.

 

You can join us live on Tuesdays at 11am Eastern for our Live Q&A to walk through that together, or join our guided workshops on Wednesdays that focus on specific policy types for more depth.

See you there!
Brandon

J
Forum|alt.badge.img

Hi ​@jguzmantransre ,

I second what ​@Maulik_Busa has suggested and would also like to add a little more context.

Microsoft Teams has a patching behavior where it will not patch when running and isn’t typically shut down at patch time through automatic processes (which is to avoid data loss or ending a mid-meeting session).
We have an article in our Help Center that showcases patching behavior for all of our supported software titles in our catalog, along with a suggestion for how to overcome applications that don’t close at patch time.

In your case, you can use a Patch Only policy scoped for Microsoft Teams (hint: use the “everything” checkbox when searching for that software, it acts as a wildcard), and then use the override Worklet from our Catalog (linked in the help article) to ensure Teams shuts down at patch time to avoid patch failures or strange update behaviors.

 

You can join us live on Tuesdays at 11am Eastern for our Live Q&A to walk through that together, or join our guided workshops on Wednesdays that focus on specific policy types for more depth.

See you there!
Brandon

Thank you Brandon. My colleague has taken over this request from me so will share these findings. I’ve joined a few of these webinars in the past, will make sure i join this coming Tuesday again.

 

Thank you again.

BrandonG-Automox
Terms & ConditionsCookie settingsAccessibility statement