winget update shows different results if run locally vs remotely

Relevant area(s)

WinGet CLI

Relevant command(s)

locally

winget update --source winget

remotely

Invoke-Command -ComputerName "SOME_SERVER_NAME" -ScriptBlock { winget update --source winget }

Brief description of your issue

Via Powershell the command "winget update" shows different results when run locally on a server as to run via "invok-command"

Steps to reproduce

Running "winget update" directly on a server shows the following options:

While running the same command via invoke command, gives these results:

The update for "MS Teams" is missing

Expected behavior

Both ways should produce the same results

Actual behavior

Different ways different results

Environment

PS C:\Windows\System32> winget -v
v1.28.190

PS C:\Windows\System32> winget --info
WindowsPackageManager
MainCopyrightNotice

Windows: Windows.Server v10.0.17763.8511
SystemArchitecture

KeyDirectoriesHeader
----------------------------------------------------------------------------------------
Logs                 %TEMP%\WinGet\defaultState
UserSettings         %LOCALAPPDATA%\Microsoft\WinGet\Settings\defaultState\settings.json
PortableLinksUser    %LOCALAPPDATA%\Microsoft\WinGet\Links
PortableLinksMachine C:\Program Files\WinGet\Links
PortableRootUser     %LOCALAPPDATA%\Microsoft\WinGet\Packages
PortableRoot         C:\Program Files\WinGet\Packages
PortableRoot86       C:\Program Files (x86)\WinGet\Packages
InstallerDownloads   %USERPROFILE%\Downloads
ConfigurationModules %LOCALAPPDATA%\Microsoft\WinGet\Configuration\Modules

Links
--------------------------------------------------------------------------------
PrivacyStatement         https://aka.ms/winget-privacy
LicenseAgreement         https://aka.ms/winget-license
ThirdPartSoftwareNotices https://aka.ms/winget-3rdPartyNotice
MainHomepage             https://aka.ms/winget
WindowsStoreTerms        https://www.microsoft.com/en-us/storedocs/terms-of-sale

AdminSettingHeader                        StateHeader
-------------------------------------------------------
LocalManifestFiles                        StateDisabled
BypassCertificatePinningForMicrosoftStore StateDisabled
InstallerHashOverride                     StateDisabled
LocalArchiveMalwareScanOverride           StateDisabled
ProxyCommandLineOptions                   StateDisabled
DefaultProxy                              StateDisabled

Start by reproducing both commands from the issue on Windows Server v10.0.17763.8511 with WinGet v1.28.190, comparing the local and Invoke-Command session environments. Investigate why the MS Teams result differs between the two executions. Done means the discrepancy is explained and the two commands produce consistent results or the behavior is clearly documented.