Microsoft Teams PowerShell Module 7.6.0 is broken
Dear Community I have a few Script with Microsoft Teams PowerShell, witch authenticate via Access Token. Everything works fine until latest Microsoft Teams PowerShell Module Update 7.6.0. I got following Error with the Script. Connect-MicrosoftTeams : Could not load file or assembly 'Microsoft.IdentityModel.JsonWebTokens, Version=8.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. If I downgrade my environment from Version 7.6.0 to Version 7.5.0 and rerun my script, the authentication is working as expected. What is wrong here with latest PowerShell Module 7.6.0 and how can I resolve the issue Many thanks for sharing any hint or tip ANDYHow to explicitly state an external org is trusted
We have a B2B relationship with our parent company. They manage their own M365 we manage ours, but we added each others' domains as instructed in Cross-Tenant Access Settings and allowed access to each other's directory and calendar. However, on our Teams, their users pop up with a grey "external" badge stating "This person's org hasn't yet been added to your org's trusted list" even though Team's External Access Settings is set to Allow all External Domains, which means there is no trust list to begin with. Do the trusted domains have to be specified explicitly if so, is there a way to set this external domain as trusted without having to change "Allow all External domains" to "Allow only specific external domains"?Allow only specific external domains
When External Access is set to “Allow only specific external domains” Scenario 1 If Microsoft Teams External Access is set to “Allow only specific external domains”, and a user from a domain not on the allowed list joins a meeting while signed into their work Teams account, Will they still appear with their actual name and organization, rather than as Anonymous? Is this correct? Scenario 2 If a user from a non-allowed domain joins the meeting link through a browser and selects “Join as guest”, Will they appear under the name they manually enter, instead of showing as Anonymous? Is this correct? Scenario 3 If a user joins without authenticating and meeting policy allows anonymous access, Will they appear as Anonymous only in that situation, and not because of the External Access restriction? Is this correct?'Registering user becomes local admin on Joined Devices' - WHAT
Stumbled on a tenant with 'JOIN' available for all users. Haven't worked with this much - most tenants I see only have registration. But then I noticed the horrifying 'Registering user is added as local administrator on the device during Microsoft Entra join' option was ALSO set to ALL. This is a tenant we just took on, but I've never seen that control before. This is terrifying, considering AFAIK, there is no real way for a registering user to know if they're registering or joining. Beneath it is an option to 'Manage Additional local administrators on all Microsoft Entra joined devices', which leads to the Role page for Device Administrators, which is empty. Under Description, this describes what APPEARS to be to be the same thing mentioned in the previous control - 'Users with this role become local machine administrators on all Windows 10 devices that are joined to Microsoft Entra'. But no one is assigned this. Conveniently, on my own tenant, I happened to let someone JOIN yesterday. We have this limited to 2 (now 3) people - most just register... But this user Joined, and the 'Joining user becomes local admin' option was on ALL. But I can't validate that the user ever become local admin. They don't have the role, their device shows as joined, but there's no additional roles. The audit logs don't look weird. They're not in that 'Device Administrators' group, which describes itself as 'Users with this role become local machine administrators on all Windows 10 devices that are joined to Microsoft Entra'. Thoughts? Freaking out, honestly. We have a mix of DC and Cloud users. I've inherited them all, and had the understanding that Join was essentially registration but with Org ownership. I've tried to get some input from Copilot, but he has basically waffled between 'No, this setting is just badly named' and 'no, actually it's this other setting' and 'no, you know what, it all makes sense somehow'. 1. Does that option actually set the joining user as global admin? Is that really the default setting? 2. can you validate this ANYWHERE in Entra? Or does it just disappear? 3. what is that Device Admin group? A separate group, independent of these two settings, that gives local admin? 4. Is there a graph endpoint that can be used to set this? Thanks
Restrict Users from Creating New Teams in Microsoft Teams
Hello together, I've do this here: https://learn.microsoft.com/en-us/previous-versions/microsoft-365/solutions/manage-creation-of-groups?view=o365-worldwide#step-2-run-powershell-commands I create a group for users, that allowed to create new Teams Channels and run the script, but i didnt see in the updated settings the group ID: What im doing wrong? At the moment no one can create new Teams Channels, also the members of the GroupCreationAllowed Group. Can somebody help, whats the problem of the script is? Thx Peter
New MTR devices unable to connect workplace
Hello collective im facing an issue with new Poly devices Poly X52 + Poly TC10 + Poly Trio 60 Poly X52 + Poly TC10 Both devices can not connect to M365. Error message: "Couldn't connect to Workplace Join. try again, or contact your admin." Firewall settings seems to be ok and devices are on the same VLAN. What is the workaround for this kind of issue or what should we check first? Best regardsDirect Routing PSTN calls to Teams Auto Attendant does not forward to Shared Voicemail
Hi all, I’m running into a strange issue with a Teams Auto Attendant and I’m hoping someone here has seen it before. We have a Direct Routing number where business hours calls go to a Call Queue, which works, and after hours calls should go to Shared Voicemail for a Microsoft 365 Group. If I call the Auto Attendant from inside our Teams tenant, the after-hours Shared Voicemail works correctly. I can leave a message and the voicemail is delivered to the group inbox as expected. If I call the same number from the PSTN over Direct Routing, I hear the after-hours greeting, so the schedule and call flow are clearly being hit, but once the greeting finishes I get: “Sorry, we cannot connect your call at the moment, please try again later.” I have already verified that the resource account has the correct Teams Phone Resource Account license, Enterprise Voice is enabled, the LineURI is assigned, the Online Voice Routing Policy is assigned, the Direct Routing route and SBC look healthy, the Auto Attendant is associated with the correct resource account, the after-hours call flow points to the correct Microsoft 365 Group, and the group mailbox exists and is healthy. What makes this more confusing is that redirects to internal or tenant-side destinations work, but redirect to Shared Voicemail from a PSTN-originated call does not work. I also tested redirect to an external PSTN number, and that fails with the same error as well. Because the after-hours greeting plays correctly, and because internal Teams calls can successfully leave voicemail in the shared mailbox, I do not think the issue is with the Auto Attendant configuration itself or with the Microsoft 365 Group mailbox. At this point it looks more like the handoff or redirect path for PSTN-originated calls over Direct Routing is where things break. Has anyone run into this with a Teams Auto Attendant, Shared Voicemail, and inbound PSTN over Direct Routing? I’m trying to figure out whether this is a known limitation, a bug, or if there is some specific setting related to PSTN-originated redirects that I am missing. Thanks!
Issue with Teams 'Add a User to Group Chat' API call?
I am getting a very strange error when trying to add a new user to an existing group chat using a GraphQL call. I have looked through the documentation, asked AI, and even contacted Microsoft support and no one can seem to explain why this API call is failing. Below is the API call that I am making. I can find no reason that I should be receiving the error message '#microsoft.graph.aadUserConversationMember' To get the basic questions out of the way.... Yes, the account making the API call DOES have permission to add users to the channel (and can do so using the frontend as normal.) Yes, the thread in question is a group chat, so adding members to that chat should be a valid command. Yes, ALL members in the group chat currently have the type '#microsoft.graph.aadUserConversationMember', so it is definitely a valid type for users in this channel. Yes, I have tried both the beta and stable channel; each gives the same error message. Yes, the invited user is internal to our organization, and is a valid target for the invite (invites work through frontend as well.) No, I cannot use the 'add member to channel' endpoint, because the chat is a group chat, not a channel. I can only assume, at this point, that the error message is a red herring and there's something else wrong with my API call?Why am I receiving this error message when trying to add a member to a pre-existing group chat? Thanks in advance for any assistance. POST to URL: https://graph.microsoft.com/beta/chats/[[THREAD_ID]]@thread.v2/members BODY: { "@odXXX.type": "#microsoft.graph.aadUserConversationMember", "roles": [], "email address removed for privacy reasons": "https://graph.microsoft.com/v1.0/users/[[USER_ID]]" } ERROR MESSAGE: {"error":{"code":"BadRequest","message":"The provided '#microsoft.graph.aadUserConversationMember' for 'odXXX.type' is not valid for this operation.","innerError":{"date":"2026-01-29T18:10:32","request-id":"<PII:moderator removed>","client-request-id":"<PII:moderator removed>"}}}
Teams Transcription (Licensing / Button greyed out for some users)
Hello, i have questions regarding transcription in Teams. Our org has Microsoft 365 Business Standard licenses, two users have icrosoft 365 Copilot Business on top of that. First question: is transcription possible for users without Copilot Business License? If the meeting policy is specified as something other than "off", some people can start the transcription, even if all participants of the meeting have no Copilot Business License. Is this on purpose or am i using a loophole and am i violating my license agreement in any way? Second question: some users can start the transcriptions, while others with the same teams version, license and meeting policy can not I read that having the personal setting disabled to identify yourself automatically in meetings will prevent you from starting the transcription, but that setting is enabled for every participant. On the teams app for android, one participant can enable the transcription, in the same meeting in the desktop app it is not available (disabled by Administrator per Policy) Teams version is 26072.519.4556.7438. Any pointers how i can locate the user specific difference, that is responsible for the transcription? I checked the assigned meeting policy and it is the same. Thanks for your time and help! Best regards, AndiYOption to change default recording & transcription settings?
I've been asked to look at changing the default settings for recordings & transcriptions, specifically the “Who has access to the recording or transcript.” setting, changing it from "Everyone" to "Specific people". I've looked through Meeting Policies in Teams Admin Center but can't see an option that governs this behaviour. Although we've advised users to change this setting if needed, we have had instances where the user has forgotten to change the default and has inadvertently allowed guest/temporary participants (who may have only been in attendance for a specific item) to see the whole meeting transcript. Many thanks, Olly
