Resolve customer issues faster with Queues app's collaborative calling for Microsoft Teams
Queues app for Microsoft Teams turns an existing call queue into a collaborative workspace where calling representatives and supervisors work the same set of customer conversations together in Teams. Eligible organizations can try it with a 90-day Teams Premium trial and discount opportunity. Terms and conditions apply.
Mouse button 'Back/Forward' not working in 'New Teams'
Though there are options to 'pop out' windows from Teams, Teams is a generally a single page app. As such, one of my most used features in 'Classic Teams' is switching back 'n forth between several 'tabs' I'm currently working with. Say I've got somebody on chat, but then have to quickly check something in Teams, then go back to chat. In Classic Teams this works just fine using the mouse's back & forward buttons. In 'New' Teams, this no longer registers any action at all. I assume the feature still exists, since left of the search bar there are still the back/forward UI buttons. But moving the mouse over for every time you need to switch back and forth is a lot slower and less intuitive than just using the mouse buttons. Current behavior: Mouse 'back'/'forward' buttons do not work in 'New Teams' Expected behavior: Mouse 'back/forward' buttons register the 'back' and 'forward' navigation commands as they did in 'Classic' Teams
Cannot deploy Custom backgrounds for Teams in VDI environment
We have detected (or so we think) a malfunction in Teams on VDI when attempting to deploy Teams backgrounds that should be available to users for their video calls. The only article that documents how to do this is the following: https://learn.microsoft.com/en-us/microsoftteams/custom-meeting-backgrounds It clearly states that the path where custom Teams backgrounds are stored is in the user profile, specifically in the folder: %LOCALAPPDATA%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Backgrounds\Uploads Expected Process The process is not direct, but it is straightforward. Using a script, a UUID is generated, which is used to create two image files (JPG, BMP, or PNG format, depending on the original image). For example, if the original is a JPG: UUID.JPG UUID_thumb.JPG These two files are copied to the path above, and on the next Teams session startup they should be available to the user. ✅ This works correctly in physical (non-VDI) environments. Tested many times without issues. What We Have Observed in VDI Even when the file pair is copied to the correct path within the user's FSLogix profile, the image does not become available in the Teams client — even after restarting Teams multiple times or even the VDI session itself. After each restart, the files are confirmed to be persistent and located at the correct profile path.[ %LOCALAPPDATA%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Backgrounds\Uploads folder contents] When a background image is added manually through the Teams UI, a folder is created in OneDrive called "Microsoft Teams User Custom Video Backgrounds". If additional images are manually added to that OneDrive folder, they do not appear as available in Teams. This leads us to believe that the upload process performs additional operations in the registry or other configuration locations beyond simply copying the file. A ProcMon capture was performed, but after an initial superficial inspection, it was not possible to determine exactly what is happening under the hood.
New Poly Phones : No Microsoft Teams Sign In Option
Hi everyone, Today I just set up the brand new Poly phones. I connected them to the office network and powered them up. However, Microsoft Teams Sign In Option is not available over the phone screen(see phone screen shot below). It also appears that the firmware is generic, and it look it doesn’t come with Microsoft Teams firmware or profile (see phone screen shot below). The phones are just out-of-box. Please kindly advise how these Poly phones can come up with Teams Sign In option. Thanks for your help in advance. Poly phone models I tested: Edge E100, E220 (BTW, I also test C60, the Teams Sign In option(window) pops up as expected once switching to Teams profile from generic one.) These will be set up as common area phone. I followed this official guide: Set up common area phones for Microsoft Teams: https://learn.microsoft.com/en-us/microsoftteams/set-up-common-area-phones Best regards, E.Z.Focus on the Teams Phone calls that matter most with intelligent call delegation
We're excited to announce that intelligent call delegation can now help answer your incoming Teams calls and schedule follow-up appointments on your behalf. This experience helps users focus on engaging with the calls that matter most and is available through the Frontier program.
App Validation failing for no clear reason
We're trying to get our (very simple) Teams App listed on the app store, but during the App Validation we keep getting the same error: "Unable to upload the manifest.zip file in MS Teams." as seen below: Downloading the report doesn't give any more information, it only lists the only successful validation step ("BotID should be registered") and the error doesn't appear there. I've validated the manifest.json file against the schema, tried reuploading the same manifest to a different org (creating a new app and bot) - validation fails there too. Does anyone have any pointers? Here is my (anonymized) manifest file: { "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.19/MicrosoftTeams.schema.json", "manifestVersion": "1.19", "version": "1.1.1", "id": "[redacted]", "developer": { "name": "[redacted]", "websiteUrl": "https://www.[redacted].com", "privacyUrl": "[redacted]", "termsOfUseUrl": "[redacted]" }, "icons": { "color": "color.png", "outline": "outline.png" }, "name": { "short": "[redacted]", "full": "[redacted]" }, "description": { "short": "[redacted]", "full": "[redacted]" }, "accentColor": "#4A3AFF", "bots": [ { "botId": "[redacted]", "scopes": ["personal"], "supportsFiles": false, "isNotificationOnly": false, "commandLists": [ { "scopes": ["personal"], "commands": [ { "title": "help", "description": "Show what this bot does and how to connect your account" }, { "title": "connect", "description": "Get a fresh link to (re-)connect your account" } ] } ] } ], "staticTabs": [ { "entityId": "conversations", "scopes": ["personal"] }, { "entityId": "about", "scopes": ["personal"] } ], "permissions": ["identity", "messageTeamMembers"], "validDomains": ["app.[redacted].com", "auth.[redacted].com"] }Best way to automatically bring unfinished 1:1 action items into the next meeting?
One thing our managers keep running into is losing track of action items between recurring 1:1s. They might agree on 2–3 follow-ups during one meeting, but by the time the next one comes around those notes are sitting in Loop, OneNote, a Teams chat, or someone’s personal task list. Ideally, I’d like unfinished action items from the previous 1:1 to automatically show up in the next meeting agenda so both sides can quickly review what was actually completed.
Is Microsoft Teams a good Intranet?
Our company is fully on Microsoft 365, but employees still struggle to find basic information like policies, company updates, forms, department resources, and important links. Most of it is scattered across SharePoint sites, Teams channels, emails, and random folders. I want to turn Microsoft Teams into that hub where all of this lives, kind of like an intranet. Any suggestions?Customizing pasted image preview size for better visibility
Hi all, Currently, the ctrl+c and ctrl+v function works well in Microsoft Teams, and the app will scale down the image to a preview version which is clickable to expand and view the full sized image. If the pasted image is of a certain dimension, it may be resized to a un-readable version (Bottom Image vs the top image) without clicking to expand it. Would like to know if it is possible to enlarge the image previews done by Teams for ctrl+c and ctrl+v images? Thanks!
