Microsoft announced they would change Teams meeting recordings to auto-expire after 60 days.  A guide for this change along with a FAQ was published by Microsoft:  MS Docs . Per the linked article, this setting can be found using the 'Set-CsTeamsMeetingPolicy' cmdlet in the Teams PowerShell module. Changing the Teams Meeting Policy to Never Expire: First, connect to Teams PowerShell: To get a list of all Teams Meeting Policies, run the 'Get-CsTeamsMeetingPolicy' and get the Name, Identity, and NewMeetingExpirationDays properties: (NOTE: I already change the ExpirationDays parameter on several policies 😉.) Run the 'Set-CsTeamsMeetingPolicy' command with the 'NewMeetingRecordingExpirationDays' parameter set to -1. The command will not return anything if successful. Validate the policy has been updated with the 'Get-CsTeamsMeetingPolicy' command once again: An error occurs when you try to set the expiration days for a policy that does not have Cl
                                                 I'm the member of a project team deploying retention policies in Teams. A colleague asked what happens to saved messages when a retention policy is applied. I didn't know offhand, so I added this to our list of test cases. The saved message feature in Teams is something I use quite a bit. It's super helpful when someone sends you a link or a message that you'll need to refer back to in the future. Teams organizes saved messages into a list that can be easily referred back to later. I have a test user account with a one-day retention policy set. I sent a few 1:1 messages from that account to a colleague on my team and saved a few of their replies: After saving the messages, I waited 24 hours to verify what happened after the retention policy applied. Here's a screenshot of the Teams client for test user account: The saved messages still appeared underneath the 'Saved' window pane on the left, but the message c
Replying to an individual Teams message is now in Public Preview. While this isn't a big change, it's certainly helpful. For those in Public Preview, hover over the message and click the '...' button and select the 'Reply' option:                                    That will copy & paste the message you're replying to in the chat text box: Prior to this feature being released, the only way to achieve this functionality was with the 'quote' feature by clicking the 'format' button in the chat text box: At this time, this is only available in the desktop client, but the web client is planned. This feature is also not available within channel or external chats yet. NOTE: A 'how-to' on switching your client to Public Preview is available at this link . If you do not have the ability to switch, you may need to ask your Teams Administrator to enable it.
My department had an initiative this year to clean up our on premise Exchange environment. Any mailbox that did not have a reason to stay on premise was migrated to Exchange Online. One mailbox in particular was utilized by our E-Fax service. When an incoming fax was sent to the mailbox, a PowerShell script copied the email attachment to a NAS share. The process is outlined below: I had a meeting with the mailbox owner prior to the migration. I could tell she was very uneasy with any sort of major change the current process. In addition, the NAS share had permissions for a large number of users. Therefore, I wanted to make as few changes to the process as possible.  That's exactly why Power Automate with a Data Gateway connection works well for this use case. I can create a Flow that leaves the existing NAS share and all permissions in place. The new process is outlined in the diagram below: Pre-Requisite M365 Licensing is required to use the Data Gateway feature. This article exp