Green Blocky Glitch on Shared Screen in New Teams Meeting
I have a user on New Teams that repeatedly has trouble with screens being shared in meetings by other people showing up as a Green Blocky mess on her end. So far we have cleared cache, uninstalled and reinstalled New Teams, updated graphics drivers, tested her internet connection (measured at 300Mbps down by 35Mbps Up and she is the only user on it) performed normal system maintenance (SFC, D.I.S.M, CHKDSK), and restarts galore. No luck. Any suggestions would be greatly appreciated.
New to teams: Are multiple outgoing sales lines possible?
Hey everyone! I am the sys admin of my small law firm, and we officially switch to Teams and Microsoft as a phone provider on September 15th. Currently we use 3cx as our PBX and Callcentric as our provider. Most everything is already set up, and waiting for the port. I already have a reception and incoming sales queue set up with a main auto attendant, basically cloning what we have now. We are noticing that our main phone line is being marked as spam when we call out, likely due to it being our main line and our sales dept is going gangbusters. It was suggested we buy multiple sales lines and switch the number our salesperson is dialing from every so often. What I am wondering is: If we purchase a handful of these numbers, is there an easy way to switch what the outgoing number of our salesperson/sales team/sales queue is showing on outgoing calls and is there a way to have incoming calls from each of those numbers funnel into our incoming sales queue, which is often populated with at least two people? For reference, we will no longer be using 3cx after the 15th so everything is under MS's roof. I also asked copilot hoping it would have some insight, but Im not entirely sure if it understood my situation. Any help is appreciated.
Securing Microsoft Teams Best Practice & Cleanup
Working on a Teams environment that is fully wide open. They have seen a huge number of Teams created and are looking to get it under control from here on out and clean up. Wanted some advice on what you recommend doing and if you have the instructions to complete those tasks. My thoughts would be Block Team creation where IT would need to be involved. I believe this could be accomplished by blocking M365 Group creation. Way to expire or archive old Teams with no activity in X amount of time? Also, how are you handling guest invitations or access? Doing anything that allows but might secure things better for the organization. Thanks all.
App availability - exclude a group
Hi all, I have a use case to have an app be available on Teams for everyone, except a group of people. I know you can update app availability in Teams admin center, but it doesn't give me the option to exclude the group and make it available for all other users. Is there a way to achieve this? Thanks in advance!
Teams Channels Policy – ThreadedChannelCreation Not Honored
We have noticed a change in behavior with the ThreadedChannelCreation parameter in Teams Channel Policies. Previously, setting ThreadedChannelCreation = Disabled in the Global policy prevented users from creating threaded channels. Since the end of August (coinciding with the rollout of the new threaded channel experience), this control no longer works. Users assigned to the Global policy (with the parameter set to Disabled) can still create and edit threaded channels. Microsoft documentation also flags this parameter as “reserved for internal Microsoft use.” Question: Has Microsoft removed customer ability to control threaded channel creation at the tenant level? If so, is there an alternative or roadmap for reintroducing this control?
Teams - Camera and screen share issue
Hi, Since yesterday we have been having firm wide issues with camera usage and screen share in Teams calls. When user 1 calls user 2, user 1 can see user 2s camera and screen share. User 2 cannot see user 1s camera or screen share. It seems to be that the recipient cannot see camera feed or screen share, but the original caller can see incoming camera feeds and screen shares. We have tried fully reinstalling and nuking local cache, but no luck. Before we start looking a bit deeper, has any others had this at all. Many thanks guys
Microsoft Teams App in Task Bar shows up as white square after opening app
Using Windows 11 Pro 24H2 (installed on 8/4/2025) with Microsoft Teams: You have Microsoft Teams version 25198.1112.3855.2900. You've got the latest version. It was last checked on 8/15/2025. When I launch the Microsoft Teams App it shows up as a white square icon in the task bar? What can be done to get this icon back to what it was originally. I've used the Microsoft Store to remove this app and install it back again, but does not work. I've also removed the iconchache files stored in: C:\Users\%userprofile%\AppData\Local\IconCache.db.old C:\Users\%userprofile%\AppData\Local\Microsoft\Windows\Explorer\Team call handling - option to redirect calls if there is no answer
Dear Community To prevent calls from being dropped when the Teams client is offline, we have set the global calling policy 'Voicemail for inbound calls' to 'On' (AllowVoicemail: AlwaysEnabled in PowerShell CsTeamsCallingPolicy). With this setting enabled, incoming calls to users who are not logged in to a client are forwarded to their voicemail. Until recently (1-2 month?) users had the option to set the rule "When you can't answer a call" and "Ring for this many seconds before redirecting" in the Teams client. Now, only the 'Ring for this many seconds before redirecting' option is shown, and sometimes even that setting is unavailable. We cannot rule out an issue with the Teams client; however, resetting the app does not help at the moment. Reversing the entry on the calling policy 'Voicemail for inbound calls' to 'Let users decide' does solve the issue in the Teams client. However, depending on the user's configuration, calls may be dropped if the user is offline. According to Microsoft's documentation, this is an expected behaviour; however, the user should not be able to change the redirection time (fixed to thirty seconds). https://learn.microsoft.com/en-us/powershell/module/microsoftteams/set-csteamscallingpolicy -AllowVoicemail Enables inbound calls to be routed to voicemail. Valid options are: AlwaysEnabled: Calls are always forwarded to voicemail on unanswered after ringing for thirty seconds, regardless of the unanswered call forward setting for the user. AlwaysDisabled: Calls are never routed to voicemail, regardless of the call forward or unanswered settings for the user. Voicemail isn't available as a call forwarding or unanswered setting in Teams. UserOverride: Calls are forwarded to voicemail based on the call forwarding and/or unanswered settings for the user. What is the recommended policy setting for 'Voicemail for inbound calls' and how can we ensure that incoming calls are transferred to voicemail when the user is offline, while still enabling them to set 'When you can't answer a call'? Many thanks.
