Apps notification settings missing in Teams settings
Hello Teams Community, I'm facing a strange issue with App notifications in Microsoft Teams. I've already researched this and found nothing. I've opened a Microsoft case and I'm waiting for an answer but it's taking longer than expected. So, I'm turning to you for expedited help! Scenario: You're an administrator in Teams. You've applied a setup policy for a pinned app like Viva Engage. After the policy is applied and the tool is launched, users complain that notifications are either too frequent or not frequent enough. You direct them to the Teams Notification and activity settings to control app notifications. The users go to Teams notification settings but report back to you that the App section of Teams settings doesn't exist. Problem Statement: Microsoft explicitly states in their documentation that in order for the App notifications section to appear, you must first add an app yourself within Teams and get at least one notification. But relying on users to add an app, somehow create a notification, and then remove it, just to access App notifications is impractical and would never work. Desired Outcome: I'm looking for a way to bypass this prerequisite and force the Apps section to appear in the Notifications and activity section without any user action whenever an app is pinned in the Teams admin center with a setup policy. I'm hoping this can work with any app, not just Viva Engage. Any help is appreciated. Thanks, Teams experts! -Rob
Sample Apps not listed in available apps, but are allowed via Teams admin center
Tenant is GCC. The Power Apps sample apps are allowed in the Teams admin center, but are not visible to users in org under app catalog. Also, Teams admin center cannot see these apps listed in the available apps for pinning to sidebar. Sample Apps were available up until just about a week ago. I feel this is a Teams issue and not a Power Apps/Power Platform issue. What could have changed to cause this?
Non-optimized VDI Policy Teams
We are having a bit of a problem with VDI policy application in Teams. We are running Server 2016 terminal services (no Citrix) in the full desktop experience and don't currently run Teams in this setup. We run Teams separately on individual local PCs. Teams is an important LoB application for us as we use it as our complete telephone system. We want to run Teams in our RDS environment as well as on local PCs to get the benefit of integrated chat, Outlook, colloaboration features, etc. Essentially we want the entire Teams experience in RDS, except for audio and video features. This seems entirely possible, but doesn't seem to be working. We have used the IsWVDEnvironment registry key to allow us to install Teams as a machine-wide per machine instance using the current msi with the ALLUSER=1 switch. Teams installs and runs completely in RDS in this way. We have also created a Teams VDI policy in powershell and assigned it to our users. The policy disables audio and video in calls and meetings using the CsTeamsVdiPolicy cmdlets. The policy applies to the required users and we can see that when we query the user via powershell. However, the two things do not join up. When a user signs in to the terminal server via RDS Teams loads in the normal experience. Video is disabled because there is no redirected camera, but since audio is redirected through the rds session the calling option is there. It is as if the Teams VDI policy has not applied to this instance of Teams. Just to confirm, our VDI policy disables all calling features in the non-optimized environment: Identity : Tag:DisableCallsAndMeetingsTrue DisableCallsAndMeetings : True DisableAudioVideoInCallsAndMeetings : True MS does clearly state that the policy will only apply to non-optimized VDI environments. RDS is barely supported for Teams and we have no optimization features in place for it. I'm not sure how to tell if it is technically a VDI optimized environemnt or how we can specifically set it to be non-optimized so that our policy applies to the Teams instance? I hope that all makes sense. Does anyone have any experience of the Teams VDI policies and how we can make sure they apply in the right instances? ThanksPrevent folder creation in Onedrive when new channel is created in Teams
We are seriously annoyed. Being familiar with the "folder chaos" companies can sink into over time, we have a very strict folder structure in order to minimize redundancy. However, having migrated to Microsoft just a few days ago, we are seriously annoyed that every time we create a Teams channel, a corresponding folder is created in Onedrive. Just because we want a channel about where to go for lunch, we don't necessarily want a lunch folder on our Onedrive. It just really messes things up!!! How can I prevent this from happening?
How to set default Profile Picture Instead of FirstName & LastName Initials?
When I am trying to REMOVE user image from MS Teams, it is replacing the user image with the FirstName & LastName Initials image and I am getting the same image from MS Graph endpoint. Question: 1. Is there any way to set default user placeholder image instead of Initials? 2. Is there any MS Teams administrator setting that can not set the initials as a default user profile image.
