Finding in the Wild | Teams Meeting Button Missing in Outlook – Even Though the Add-In Is Active?

An interesting issue appeared in a current Windows Server 2022 multi-user environment: ✅ Microsoft Teams Meeting Add-in was installed ✅ Outlook showed the add-in as active ✅ TeamsAddin.FastConnect reported Connect = True ❌ Yet the Teams button was

An interesting issue appeared in a current Windows Server 2022 multi-user environment:

✅ Microsoft Teams Meeting Add-in was installed
✅ Outlook showed the add-in as active
✅ TeamsAddin.FastConnect reported Connect = True
❌ Yet the Teams button was missing from the Outlook calendar

The cause was no longer COM registration, but a missing configuration file:

Without this file, the Outlook add-in cannot reliably recognize New Teams as the active Teams client. The add-in loads, but does not fully initialize the calendar area.

The solution was to create the file with the following content:

Then:

– Close Teams and Outlook
– Start Teams first and sign in
– Then open Outlook

The Teams meeting button was available in the calendar again afterwards.

Particularly important for Citrix, RDS and FSLogix environments:

The following path should persist in the user profile and must not be lost through exclusions or profile cleanup:

AppData\Local\Publishers\8wekyb3d8bbwe\TeamsSharedConfig

A small missing JSON file with a big impact: a classic Microsoft 365 moment. 😉

Finding in the Wild | CWA CleanInstall & Teams SlimCore

During a recent Citrix Workspace App update , I encountered interesting behavior involving Microsoft Teams SlimCore . The Microsoft Teams VDI Plugin was already installed on the client. Workspace App was then updated using /CleanInstall . Initially, everything

During a recent Citrix Workspace App update, I encountered interesting behavior involving Microsoft Teams SlimCore.

The Microsoft Teams VDI Plugin was already installed on the client. Workspace App was then updated using /CleanInstall.

Initially, everything looked fine:
Citrix Workspace App ✔️
Teams VDI Plugin ✔️
Software deployment ✔️

Nevertheless, SlimCore optimization no longer worked.

The investigation revealed that the required DLLs were no longer present in the ICA Client directory, although the Teams VDI Plugin still appeared as installed under Apps & Features.

That is precisely what makes this issue interesting.

If an automated CWA update checks only installation status, you get a successful deployment even though the actual Teams optimization no longer works.

For my update tests, this means:
CWA version → Teams VDI Plugin → DLLs → SlimCore → actual optimization mode
must be checked together.

Especially with the increasing move to SlimCore, I believe this functional test should be part of a CWA/Teams update.

👉 Finding in the Wild: installed does not automatically mean operational.

These issues are exactly why I do not just install Citrix updates, but also check the relevant functions afterwards.

Finding in the Wild: I will keep investigating.

Finding in the Wild | Teams Warns That VDI Optimization Is Ending – but Not Every Endpoint Needs SlimCore Yet

Users of classic Citrix HDX/WebRTC optimization are currently seeing a prominent message in Microsoft Teams: “Teams optimization for your virtual desktop will soon be unsupported.” The problem: There apparently is no documented way to suppress this warning administratively

Users of classic Citrix HDX/WebRTC optimization are currently seeing a prominent message in Microsoft Teams:

“Teams optimization for your virtual desktop will soon be unsupported.”

The problem:
There apparently is no documented way to suppress this warning administratively at present.

The result is predictable:
👉 Users see the message.
👉 Users contact the help desk.
👉 Yet immediate action is not required everywhere.

Microsoft distinguishes between endpoint platforms for the end of support:

🪟 Windows endpoints
The previous WebRTC-based optimization reaches end of support on October 1, 2026. Here, the direction is towards SlimCore.

🐧 Linux thin clients such as IGEL
are explicitly exempt from this date. The existing optimization remains supported until the corresponding new VDI optimization is available for Linux.

This creates an interesting situation in mixed environments:

Windows → SlimCore
IGEL/Linux → existing optimization continues

Community reports now suggest that Microsoft is aware of the warning issue and is allegedly working on a way to suppress it.

However, this is not yet officially documented.

For me, this is another example of a technically correct warning not necessarily producing a good user experience. 😉

Anyone running Windows alongside IGEL/Linux should therefore not overturn their entire Teams VDI strategy based solely on this popup.

Finding in the Wild | Citrix FIDO2 – Works in the Browser, but Not in Office 365

At a customer, I encountered an interesting issue with FIDO2 redirection in a Citrix environment. The symptoms: ✅ FIDO2 authentication works in the browser. ❌ Microsoft Teams and OneDrive do not recognize the FIDO2 key. The Citrix session

At a customer, I encountered an interesting issue with FIDO2 redirection in a Citrix environment.

The symptoms:

✅ FIDO2 authentication works in the browser.

❌ Microsoft Teams and OneDrive do not recognize the FIDO2 key.

The Citrix session itself works normally, and FIDO2 redirection initially appears to be configured correctly.

After some troubleshooting, I found two interesting fixed issues in the Citrix documentation:

🔹 CVADHELP-29179: FIDO2 works only in browser sessions, not in Office 365 applications.

🔹 CVADHELP-29040: FIDO2 does not work with Edge WebView2 by default.

The solution:

Update to Citrix VDA 2402 LTSR CU4.

Afterwards, FIDO2 authentication also worked in Teams and OneDrive.

💡 My learning:

When FIDO2 works in the browser but not in Microsoft 365 applications, the cause does not have to be Entra ID, the security key or Citrix policies.

Sometimes the solution is already listed in the fixed issues for a Citrix cumulative update. 😉

Finding in the Wild | Microsoft Teams SlimCore – Where Are the Error Codes?

Microsoft Teams works inside the Citrix session, but the new SlimCore optimization is not activated? Instead, it shows: ❌ Citrix SlimCore Media Not Connected ⚠️ Citrix HDX Optimized (Legacy WebRTC) The cause is not necessarily the VDA or

Microsoft Teams works inside the Citrix session, but the new SlimCore optimization is not activated?

Instead, it shows:

❌ Citrix SlimCore Media Not Connected
⚠️ Citrix HDX Optimized (Legacy WebRTC)

The cause is not necessarily the VDA or Citrix itself!

🔎 Where can I find the error codes?

Inside Teams on the VDA:

CTRL + ALT + SHIFT + 1

Open the generated diagnostic archive in the Downloads folder:

PROD-WebLogs-*.zip → Core → vdi_debug.txt

Look for the following entries:

loadErrc and deployErrc

The key error codes:

* 2000 / 16002: Teams VDI Plugin is missing or was not loaded.
* 2003 / 16026: Citrix Virtual Channel Allow List blocks MSTEAMS, MSTEAM1 or MSTEAM2.
* 2004 / 16032: Citrix Workspace App is incompatible.
* 3002 / 24018: SlimCore could not be downloaded to the endpoint.
* 1460 / 11683: Timeout starting MsTeamsVdi.exe.
* 1722 / 13779: RPC/App Readiness issue.
* 16389: MSIX installation failed, often due to Intune policies or AppLocker/WDAC.

🛠️ My troubleshooting approach

1. Examine vdi_debug.txt and identify the error code.
2. Check whether MsTeamsVdi.exe is running on the endpoint.
3. Use Process Explorer to check whether MsTeamsPluginCitrix.dll is loaded into wfica32.exe.
4. Check the Citrix Virtual Channel Allow List.
5. For MSIX errors, investigate the AppXDeployment-Server and AppxPackagingOM Windows logs.

💡 The actual finding:

With SlimCore, Microsoft moves media processing to the local endpoint.

AppLocker, Intune, MSIX, a proxy or Windows App Readiness may therefore prevent Teams optimization even when Citrix is fully functional.

Before reinstalling the VDA, check vdi_debug.txt!

📖 My detailed Teams VDI guide:

📚 Microsoft troubleshooting: