"Microsoft Teams"
64 TopicsTeams Panels - check-in issues
Hey, anyone experience issues with Teams Panels check-in feature? We have seen that the "Check-In" button on the panel is there but suddenly is dissapears. When that happens the rooms is not released and the email "Booking declined: No one checked in, so the room was automatically removed from your meeting to make it available for others." is never sent to the organizer.1.3KViews1like12CommentsBreakout room issues to assign user to a room
Anyone else seen issues to assign a user to a break out room? Screenshot in Swedish but the "i" say "This user can't access breakout room" At the time for testing that user was signed in to Teams with an external identity and used Edge browser. Ended meeting and rejoined and this time it worked but that is not the case all the time. Issue seems to be random. This happens quite often last couple of months, anyone seen this?1KViews3likes6CommentsApprovals to shared mailbox
Hi, We use the "approvals" app in Teams to coordinate leave with colleagues and managers. The app works, but we still have to manually place the approved leave request in a shared mailbox. Is there a solution within the app "approvals" or via PowerAutomate to make this happen automatically? RC172Views0likes1CommentDeep links for published apps ignoring entityId in the new Microsoft Teams client
For apps already published in the Microsoft Teams store, deep links to personal static tabs are not working correctly in the new Teams client. To reproduce: - Paste a link to a personal tab of an app in the channel chat. - Click on link in new Teams web client. - Note that the link takes you to the app, but it always loads the first static tab in the app, ignoring the entityId provided in the link. - Try clicking on the link in the old Teams web client. - Note that you are now correctly redirected to the personal static tab associated with the entityId in the link. Sample link: https://teams.microsoft.com/l/entity/6eacb5f0-68b0-46f0-9507-9e906c6861fc/about However, if I try this same use case on a custom uploaded app (not published), I am correctly redirected to the appropriate static tab. I am using the following documentation for building the link - https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/deep-link-application?tabs=teamsjs-v2#configure-deep-link-to-browse-within-your-app-manually857Views0likes6CommentsEntra Groups and managing Access to Teams or Town Hall
Wouldn't it be great if there was a way to grant access to a Teams or Town Hall meeting using an Entra ID Group without inviting all the users in the Group? This way you could send the meeting link to users in the Group as needed. For large organizations with many external partners managed in Entra, this would be very beneficial. This can be done already with the meeting recordings in Stream via the Share button.114Views0likes0CommentsCreate Your Own Copilot Using Copilot Studio
Hello everyone, I am Suniti, Beta MLSA pursuing my graduation in the field of Data Science. Today, we're diving into creating our very own copilot to guide students towards ‘becoming MLSAs’. But first thing first, let's explore Copilot Studio!14KViews3likes2CommentsNew Microsoft Teams issue, This bot is disabled. Contact your IT admin for more information
This issue is happening only on new Microsoft Teams desktop application for some selected users. It works fine with old Teams classic and new browser application for all users. Senario: When an effected users click on adaptive card button, user is getting error "This bot is disabled. Contact your IT admin for more information". Also issue gets resolved automatic after few hours. Then some other set of users start facing the same issue.3.5KViews0likes12CommentsIntune Android: Shared Device mode Teams calls
I am currently testing the shared device mode, we would also like to use Teams calls on the devices (Samsung). It rings but the interface does not appear. I can't even accept a call in the app. Do you have the same problem? And how did you solve it? I have already added the following ‘apps’. com.samsung.android.incallui com.android.server.telecom com.samsung.android.app.telephonyui221Views0likes0CommentsNew Teams on terminal servers
We have Teams installed on our terminal servers (Windows Server 2022) as well as locally. The video and voice functions aren't usable on the terminal servers, but everything else works (most notably the Outlook addin). I've been letting users decided whether to try the new Teams. I've been using it locally for months and not recently had any issues. It initially seemed OK on the terminal servers too. I decided to set it as the default in the Teams admin centre recently, and in setting up a couple of new user profiles on a terminal server the problems have started to come to light. Specifically: 1) Teams doesn't want to update - it displays a restart and update icon on the menu, but this doesn't actually cause it to update. Even logging in as an admin and using right-click run as administrator doesn't make any difference. The standalone installer uses an msix package, which doesn't work on WIndows Server (I am aware that there are ways to get it to run these packages, but it shouldn't be necessary and I'd rather avoid it for now if I can) 2) The Outlook addin doesn't work (as in doesn't appear in Outlook). I've looked for Microsoft documentation, and all I can find is this: https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy Which doesn't seen to specifically refer to local terminal servers at all! Assuming that much of what applies to AVD will also apply, I've checked the registry settings it lists and they all appear correct. Today I have created a new test VM, Server 2022, terminal server role, and installed Office using the normal XML config file method (using the latest available .exe for this). Office installed, and as expected only included the new Teams, not the old one. Still doesn't work properly - even after a clean install Teams wasn't up to date and the update now button didn't work. Manually closing and opening Teams caused it to update in this case (that doesn't work with the live terminal servers), but it's unclear whether this is going to continue to work reliably, or why it won't update on the live servers. The Oulook addin doesn't appear at all, although the settings and registry entries as listed in the link above all appear correct. Anyone got any ideas? The lack of mention in the documentation suggrsts that - as usual - Microsoft isn't making any effort to accommodate those using on-prem session hosts. Thanks66KViews0likes24Comments