Communities tab in Teams
Hi there I've recently had the Communities tab pop up in my Teams alongside the Teams and Channels tab. No one else in my organisation can see this yet and we aren't sure why. I know it's being rolled out on a timeline but I was also wondering if it might be because I'm the only one in the org who has an Microsoft Viva Employee Communications and Communities licence? Does anyone have any insights into this? We'd like to make a bit of a roll out plan once this appears in our colleagues Team's set ups.Upcoming change: disabling Teams meeting recording expiration notification emails
UPDATE: Please see the updated post on this topic here: Update: You can now control Teams Meeting Recording expiration notification emails | Microsoft Commu… Hello, We wanted to share an important update regarding email notifications for expired Microsoft Teams meeting recordings. Based on valuable feedback from our community, we’ve decided to make a change to how notifications are handled. What’s changing: Starting June 1st, we will stop sending email notifications for expired Microsoft Teams meeting recordings. We are making this change due to complaints we received from many customers about the high volume of notifications which they deemed low value. This change allows us to respect your preferences while ensuring critical communications remain accessible. Recording expiration and deletion policies remain unchanged and items that expire will be deleted even when notifications are not being sent. How to keep receiving notifications: For those customers that would like to continue receiving email notifications, we will create a new setting and make it available before June 1st. This will be a per-tenant setting. We will send another message center post once this setting is available and update our documentation in this discussion and on our support page. After June 1st: If you didn’t change notification settings before the deadline, you can still re-enable them at any time by running the PowerShell command. Note: Our original message center post incorrectly asked recipients to fill out a survey and failed to include a link to the survey. We are committed to providing options that work for your organization, and we would like to hear from you. If you have questions or additional feedback about this change, please complete this survey and join the discussion: Teams Meeting Recording Notification Changes – Fill out form Thank you for being part of our community.Update: You can now control Teams Meeting Recording expiration notification emails
Hey Teams community, We've heard the feedback. For admins and users managing a high volume of meetings, TMR expiration emails can pile up fast. We've been working on giving you control, and that control is now here. What's new Tenant admins can now use a PowerShell cmdlet to suppress Teams Meeting Recording expiration and deletion notification emails across their organization. Notifications stay on by default (no change if you do nothing), but if you'd like to turn them off, here's how. Prerequisites Latest version of SharePoint Online Management Shell (download here). Note, it's Windows-only, so you'll need a Windows machine or Azure Virtual Desktop SharePoint Admin or Global Admin permissions Steps 1. Connect to your tenant powershell Connect-SPOService -Url https://<your-tenant>-admin.sharepoint.com 2. Check the current value powershell Get-SPOTenant | Format-List *Recording* False = notifications currently on (default). True = notifications suppressed. 3. Suppress notifications powershell Set-SPOTenant -DisableTeamsMeetingRecordingDeletedNotification $true You'll see a confirmation prompt — enter Y to proceed. 4. Verify powershell (Get-SPOTenant).DisableTeamsMeetingRecordingDeletedNotification True means you're all set. No more expiration emails for your tenant. Want to turn them back on later? Just run the same command with $false. What doesn't change Recordings still expire and delete on the same schedule No per-user settings, no UI changes. This is purely a tenant-level admin toggle We'll keep monitoring feedback, and as always, drop your questions below.
'New Teams' - DOES NOT Remember Window Positions
Can anyone tell me if there is a FIX for this??? Ever since I upgraded to the NEW and IMPROVED [and I choke on those words] Teams, DOES NOT remember my previous window positions for either the main window or individual chats. The Classic Teams did this. When can we expect this be FIXED? This is HIGHLY annoying. It is bad enough that Microsoft feels the need to have this fill nearly your entire screen [as if it was the only application you used]. The very least you could do is check these sorts of issues before the app went to production and in my opinion this app is nowhere near production worthy. Please FIX this immediately or provide a workaround that can be utilized as soon as possible. I wish I could use the old 'classic' Teams, but it will no longer let me. At least it would remember my previous Window Positions.
"None" option missing from Teams background options
Hi, Our teams "none" background option is missing. Forcing users to use a background or the blur backgrounds. I have tried to revert back to classic teams to see if that is a fix, but I am unable to toggle it off and it takes me to download the classic teams which is just the new teams download. I do see this message "Your org sets background to blur unless something else is selected" when trying to update the background in a call. We are not disabling this option as an organization. And I can switch to other backgrounds.
How much should Teams presence influence call routing
One thing I've noticed recently is that many Teams Phone environments still treat presence as a destination state rather than a routing input. A typical flow might look like: Caller selects an option Call is transferred User is unavailable Caller ends up in voicemail or another queue Technically the routing worked. From the caller's perspective, it often didn't. I'm curious how others are approaching this. Are you using Teams presence as part of your call-routing logic? For example: Available → transfer immediately Busy → offer an alternative path In a meeting → capture context Offline → route elsewhere Or are traditional queues and escalation paths still sufficient for most scenarios? Interested to hear what people are doing in real deployments.
Is anyone building individual development plans inside Teams?
So hear me out. I discovered that if something is in a live document, sharepoint, etc, I've found that employees dont really check up on it or follow through with it unless they are regularly reminded. Same goes for any software we try to implement that requires a seperate login and lives in another app completely. Our employees spend most of their time communicating in Teams so I want to take our IDP process into Teams. Are there any decent talent or employee development apps for Teams that anyone can recommend for IDPs?Anyone found a good way to run performance reviews inside Teams?
Our company just switched to doing everything in Teams and the one thing that still lives outside is performance reviews. We use a separate web app that nobody logs into until the last minute and managers hate it. Is there anything that actually handles the full review cycle with self assessments, manager ratings, maybe even 360 feedback? Our IT team said they'd prefer something that uses our existing M365 directory so we dont have to manage another user list.
