Loading...

Microsoft Teams PowerShell: Web Account Manager (WAM) becomes the default authentication broker

Microsoft Teams PowerShell: Web Account Manager (WAM) becomes the default authentication broker

Microsoft Teams PowerShell module will use Web Account Manager (WAM) as the default authentication broker on Windows starting late June 2026 (version 7.8.1). A temporary -DisableWAM parameter allows bypassing WAM. Non-interactive and older Windows versions are unaffected. Admins should review and update scripts accordingly. What and Why We are updating the Microsoft Teams PowerShell module to use Web Account Manager (WAM) as the default authentication broker for sign-in. This change improves security and provides a more consistent authentication experience on Windows. A new temporary parameter, -DisableWAM, is available in the Connect-MicrosoftTeams cmdlet, allowing admins to bypass WAM for a single connection if it is not supported in their environment. This change is available starting with preview version 7.8.1 of the Teams PowerShell module. Rollout Schedule General Availability (Worldwide, GCC, GCCH, DoD): Rollout will begin in late June 2026 and is expected to complete in late June 2026. Impact on Your Organization Who is affected Admins using the Microsoft Teams PowerShell module on Windows Platforms/Services Microsoft Teams PowerShell module Windows What will happen Sign-in for the following scenarios will use WAM as the authentication broker: Interactive sign-in using Connect-MicrosoftTeams Connect-MicrosoftTeams with credential (-Credential) Connect-MicrosoftTeams with AccountId (-AccountId, Integrated Windows Authentication) The following sign-in methods are not affected: Service principal with certificate Managed identity Pre-acquired access tokens A temporary -DisableWAM parameter is available to bypass WAM for a single connection. The -DisableWAM parameter will be removed in a future release. Known limitations: On macOS, Linux, and Windows versions earlier than Windows 10 or Windows Server 2019, existing authentication behavior remains unchanged. WAM requires an interactive Windows session with UI access. WAM will not work in non-interactive scenarios such as Windows services, scheduled tasks without a logged-in user, or scenarios that run under impersonation. Action Required / Recommendations Review any scripts that use the Teams PowerShell module, especially those running in non-interactive environments. Update scripts if needed to support WAM authentication. Use the -DisableWAM parameter as a temporary workaround if required. Learn more: Connect-MicrosoftTeams | Microsoft Teams | Microsoft Learn Compliance considerations No compliance considerations identified. Review as appropriate for your organization. Message […]

The post Microsoft Teams PowerShell: Web Account Manager (WAM) becomes the default authentication broker appeared first on M365 Admin.

Published on:

Learn more
Need help with this product?

We can help you with Microsoft Teams PowerShell: Web Account Manager (WAM) becomes the default authentication broker

If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.

M365 Admin
M365 Admin

by João Ferreira

Share post:

Related posts

Microsoft Defender: Similar cases comes to the unified security operations platform

A new Similar cases tab in the Microsoft Defender portal lists up to 20 related incidents by alert titles or entities, aiding analysts in iden...

13 hours ago

Microsoft SharePoint: Enhanced data access governance reports and site access reviews

Microsoft SharePoint will enhance data access governance reports and site access reviews starting late November 2026, giving admins better con...

13 hours ago

Microsoft PowerPoint: Introducing plugins for Microsoft 365 Copilot

Microsoft 365 Copilot in PowerPoint will gain plugins to enhance capabilities with specialized skills and connectors, improving presentation w...

13 hours ago

Microsoft Teams Mobile: Introducing shared call history in the Queues app

Microsoft Teams mobile Queues app now offers shared call history for authorized representatives, showing missed, answered, outgoing, and voice...

14 hours ago

Plugins in PowerPoint for Microsoft 365 Copilot [Mac]

Plugins will be added to PowerPoint for Microsoft 365 Copilot on Mac, enhancing presentation capabilities. The rollout starts mid-November 202...

14 hours ago

Microsoft Teams: Audio announcement for Recording and Transcription

Microsoft Teams now supports an optional audio announcement when recording or transcription starts, configurable via Meeting and Calling Polic...

14 hours ago

Microsoft 365 Copilot: Learning Agent introduces personalized learning experiences

Microsoft 365 Copilot Learning Agent will provide personalized learning experiences based on users’ work context, roles, and activities....

14 hours ago

Microsoft 365 Copilot: Learning Agent introduces personalized upskilling notifications in Teams

Microsoft 365 Copilot Learning Agent will deliver personalized upskilling notifications in Teams based on users’ roles and usage. Rollin...

14 hours ago

Changes to site logo URL metadata in SharePoint search results

SharePoint will change how site logo URLs are updated in search metadata, stopping automatic updates of the SiteLogoUrl property on individual...

14 hours ago

Microsoft Teams: End of support for iOS 17 and iPadOS 17

Microsoft Teams will end support for iOS 17 and iPadOS 17 starting mid-December 2026, requiring iOS/iPadOS 18 or later for new releases. Exist...

14 hours ago

Newsletter

Get the latest Dynamics 365 and Power Platform content in your inbox

A curated digest of community blogs, product news, videos, and podcasts — delivered without the noise.

Weekly updates Unsubscribe anytime Fresh community picks
We use your email only for the newsletter and you can unsubscribe at any time.
By subscribing, you agree to the privacy policy.