Teams External Access vs. B2B Direct Connect vs. B2B Collab
I've received conflicting info regarding whether B2B Direct Connect and Teams External Access are the same thing. Last time I looked into this, they both seemed to rely on the 'Default External Identities' controls from Entra - they were two faces of the same coin. Now it's not so clear. Can someone clarify?
Microsoft Teams transcription language settings
Hi! With a Microsoft 365 Business Premium license and a Copilot license, I can use transcription during a Teams meeting by setting the spoken language to Auto Detect. However, the transcription is sometimes inaccurate. Is there a way to limit the language detection scope? For example, is it possible that I select only English and Chinese, and Auto Detect is restricted to those two languages instead of also attempting to detect languages such as Spanish or French ?
Architectural Limitation: Move LBR from Gateway to Voice Routes for Shared Trunks
The Problem: Currently, Location-Based Routing (LBR) in Microsoft Teams is hard-locked to the root OnlinePSTNGateway object (e.g., via -GatewaySiteLbrEnabled). This creates two major administrative roadblocks: Derived Trunk Limitations: For organizations utilizing multi-tenant partner architectures and derived trunking models (such as AudioCodes Live Pro/Express), the underlying global gateway configuration is owned and managed by the provider. Because administrators lack root modification rights over these shared gateway objects, they cannot enable or configure LBR. https://imgur.com/a/RzTE4nu Managing gateways via the Teams Admin Center (Voice > Direct Routing > SBCs) results in restricted or failing LBR configurations. Rigid Global Enforcement: Forcing LBR as a strict hardware-level switch creates deployment roadblocks, such as entirely blocking unmapped or remote workers. This is overly restrictive in regions like North America, where strict anti-toll-bypass compliance is not a legal mandate (unlike regions like India). The Proposed Solution: Decouple LBR from the Gateway Object: Shift LBR evaluation away from the root hardware gateway switch toggle and allow it to occur at the Voice Route, PSTN Usage, or Calling Policy layer. Support Derived & Shared Trunks: This decoupling will instantly make LBR compatible with multi-tenant SBC models, allowing enterprises to manage geographic routing via distinct voice routes (which are already peered with gateways), bypassing the need for root gateway property access. Regional Flexibility & Compliant Enforcement: Enable regional flexibility so enterprises can bypass unnecessary toll-bypass blocks in regions where they aren't mandated (like North America) without breaking calls for "Unknown" network sites. Crucially, for heavily regulated regions like India, system-enforced policies should automatically lock LBR on to strictly maintain local country regulations without relying on manual overrides. Business Impact: This enhancement will unlock advanced routing flexibility for thousands of enterprises utilizing modern cloud-hosted and derived trunking architectures. It bridges the gap between legacy PBX design constraints and modern multi-tenant cloud voice management, significantly reducing deployment friction for global organizations.
Meeting setup in teams Channel is not allowing me to update the Agenda and send updates
I am interested to understand why when I have setup a meeting from A channel I am not able to change the invitation to all the team members. When I go into teams Calendar ,. I update the agenda description, the send updates at the top right view shows up when I do the changes , however , When I click it , the changes don't take effect.
Management of unsupported WFH Teams-certified desk phones
Hello, I'm looking for best practice or suggestions on management of unsupported WFH Teams-certified desk phones for company with Microsoft enterprise E3 and E5 licensed users. We're a Microsoft shop with Teams for messaging, but not for desk phones. So far, we've had only one employee buy their own Yealink Teams-certified desk phone for WFH use. It showed up as an incident in our MTR Pro Management portal for Account management Sign in (Teams) and we found out it was for a personal Yealink Teams-certified desk phone they setup and logged into at home. I asked multiple IT groups at the company I work for, and this is the answer they gave me "This device was allowed to enroll into Intune/Entra/MTR Pro portal because the user is a user in our Microsoft Tenant. The Android AOSP enrollment does not have any method of limiting what devices are allowed to enroll or of identifying that it is either personal or corporate. I was unable to find any Microsoft documentation that would have prevented this from occurring. If another user finds a used Teams Room device at a garage sale and thinks it would be cool to have one at home, the same thing will happen again." What are our options to manage unsupported Teams-certified desk phones in our environment? TIA
Seperate retention times for meeting recording and transcript?
Dear all, as a user (not an admin) I was told from IT, that the global data retention time for recordings and transcripts is set to 60 days and that they cannot change it separately. I'm using the transcipt with Copilot now for every meeting but as recordings and transcripts are deleted after 60 days, Copilot completely loses his purpose, because it cannot access transcripts older than 60 days. Is there a way that you can set different retention times for recordings and transcripts? Best, ChristianTeams calls reporting as potentially scams incorrectly
Hey Teams Community, In the past 5 days I am seeing callers from external tenants that are trusted and in mto showing as suspected scam callers when they call me. They see.me as a suspected scam also when I call. These tenants are all trusted and most of them are.members of the same MTO. This only started happening in the last 7 days. What is causing this? Does anybody else see this happening recently with a similar setup?Teams PowerShell no longer works on MacOS - Windows only dependency after 7.9.0
Since MicrosoftTeams 7.9.0, Connect-MicrosoftTeams with the default interactive sign-in fails on macOS before any sign-in prompt appears. It throws System.DllNotFoundException: Unable to load shared library 'kernel32.dll'. Version 7.8.0 connects without error on the same machine. The current release, 8.0.0, has the same problem. Environment macOS 27.0.1 on Apple silicon (Arm64) PowerShell 7.6.2 on .NET 10.0.8 MicrosoftTeams 7.9.0 and 8.0.0 fail; 7.8.0 works Steps to reproduce Install-Module MicrosoftTeams -RequiredVersion 8.0.0 -Scope CurrentUser Import-Module MicrosoftTeams -RequiredVersion 8.0.0 Connect-MicrosoftTeams Expected result A browser sign-in opens and the session connects, as it does with 7.8.0. Actual result No sign-in prompt appears. The command fails straight away: System.DllNotFoundException: Unable to load shared library 'kernel32.dll' or one of its dependencies. at Microsoft.TeamsCmdlets.Powershell.Connect.TeamsPowerShellSession.GetConsoleWindow() at Microsoft.TeamsCmdlets.Powershell.Connect.TeamsPowerShellSession.GetConsoleWindow() at Microsoft.TeamsCmdlets.Powershell.Connect.TeamsPowerShellSession.GetConsoleOrTerminalWindow() at Microsoft.Identity.Client.PublicClientApplicationBuilder.<>c__DisplayClass12_0.<WithParentActivityOrWindow>b__0() at Microsoft.Identity.Client.AcquireTokenInteractiveParameterBuilder.WithParentActivityOrWindowFunc(Func`1 parentActivityOrWindowFunc) at Microsoft.Identity.Client.PublicClientApplication.AcquireTokenInteractive(IEnumerable`1 scopes) at Microsoft.TeamsCmdlets.Powershell.Connect.TokenProvider.MsalTokenProvider.GetAccessTokenInteractive(ModuleConfiguration config, AzureAccount azAccount, IEnumerable`1 scopes) at Microsoft.TeamsCmdlets.Powershell.Connect.AuthenticationFactory.Authenticate(AzureAccount account, AzureEnvironment environment, String tenantId, SecureString password, AuthenticationFlow authFlow, String resource, IEnumerable`1 scopes, String clientAppId) at Microsoft.TeamsCmdlets.Powershell.Connect.RMProfileClient.AcquireAccessToken(AzureAccount account, AzureEnvironment environment, String tenantId, SecureString password, AuthenticationFlow authFlow) at Microsoft.TeamsCmdlets.Powershell.Connect.RMProfileClient.Login(AzureAccount account, AzureEnvironment environment, String tenantId, SecureString password, AuthenticationFlow authFlow) at Microsoft.TeamsCmdlets.Powershell.Connect.ConnectMicrosoftTeams.ProcessRecord() The full exception message also lists every path .NET tried for kernel32.dll.dylib, libkernel32.dll and so on, all "no such file". Cause TeamsPowerShellSession.GetConsoleOrTerminalWindow() calls the Windows GetConsoleWindow function through [DllImport("kernel32.dll")]. The module passes it to MSAL as the parent-window callback (PublicClientApplicationBuilder.WithParentActivityOrWindow), and MSAL calls that callback inside AcquireTokenInteractive. macOS has no kernel32.dll, so the call throws before sign-in starts. Comparing Microsoft.TeamsCmdlets.PowerShell.Connect.dll across versions: 7.8.0: only the Integrated Windows Authentication path, which runs only on Windows, sets this callback. 7.9.0 and 8.0.0: AzureSessionProvider also sets it when it builds the client application, and that client is used for interactive sign-in on every platform. A fix would be to set the callback only on Windows, or have GetConsoleOrTerminalWindow() return IntPtr.Zero on other platforms. Linux has no kernel32.dll either, so I'd expect interactive sign-in to fail there too, but I haven't tested it. Workarounds Stay on 7.8.0: Install-Module MicrosoftTeams -RequiredVersion 7.8.0 -Scope CurrentUser Import-Module MicrosoftTeams -RequiredVersion 7.8.0 Use device code sign-in. Connect-MicrosoftTeams -UseDeviceAuthentication doesn't call GetConsoleWindow, and on 8.0.0 it gets to the device code prompt without this error. I found this while testing Maester (maester.dev), which calls Connect-MicrosoftTeams from Connect-Maester -Service Teams and -Service All.Unable to access Teams from a PC (only mobile access)
We have a user who can't access Teams on PC, but it works as usual on mobile (however, no connections to Outlook for Teams or the ability to create Teams meetings). Have tested several different PC’s as well as app and browser, none of them work. The problem is that the user cannot find the primary organization when logging in to Teams and it only shows guest organizations (which cannot be connected to either). Below is the answer I got when I made a diagnosis of the login problems. I have found that this "guest account" is Microsoft.com, but that does not remove the fact that the primary organization does not show up at all. Do not know if anyone has seen this before or knows what to do. So all kinds of info are helpful because I am completely out of ideas. What identifies the right external organization User: Name (email address removed for privacy reasons) App: Microsoft Teams Type of access: B2B collaboration Error code: 500571 Error: Guest account is disabled External target tenant: f8cdef31-a31e-4b4a-93e4-5f571e91255a Correlation-ID: d7c0c004-ed20-4cd5-a056-7ce0d7f0ae24 This means that it is the organization that owns the tenant ID f8cdef31-a31e-4b4a-93e4-5f571e91255a that should be contacted. If you have several guest organizations associated with you, there is no need to guess in this case — the failed event points out exactly which external tenant received the request. Practical way to find which organization it is Search your documentation or previous invitations by tenant ID f8cdef31-a31e-4b4a-93e4-5f571e91255a. Ask User to check which organization he was trying to switch to in Teams just when the error occurred. If you have multiple external partners with similar names, match the tenant ID to the partner you have B2B collaboration with. Please send the correlation ID and time 2026-09-09 10:43 UTC to the external administrator so that they can find the same event at their place. Conclusion You need to contact the external organization that corresponds to the tenant ID f8cdef31-a31e-4b4a-93e4-5f571e91255a and ask them to check Users guest account. This is where the account appears to be disabled.
