Thorsten Pickhan
@thorpick.de
MVP for #Microsoft365 Apps & Services | #MicrosoftTeams enthusiast and Microsoft Teams Phone guy | #Community speaker | blogger | Organizer of the @TeamsUG_DE in #Bochum
The new dropdown filter will be added to the "All schedules" view. It will help to concentrate on the schedules of active Teams.
The rollout will start early February and Microsoft expects to complete the rollout by mid-February 2025.
The rollout will start early February and Microsoft expects to complete the rollout by mid-February 2025.
January 9, 2025 at 1:59 PM
The new dropdown filter will be added to the "All schedules" view. It will help to concentrate on the schedules of active Teams.
The rollout will start early February and Microsoft expects to complete the rollout by mid-February 2025.
The rollout will start early February and Microsoft expects to complete the rollout by mid-February 2025.
The rollout will begin for Targeted Release user late January, for GA users February. Microsoft expects to complete the rollout by late February 2025.
January 8, 2025 at 2:52 PM
The rollout will begin for Targeted Release user late January, for GA users February. Microsoft expects to complete the rollout by late February 2025.
Unfortunately, the label of the Loop workspace will not change, if the label of the M365 will change 🙈 In late February Microsoft will fix it and updated labels will apply to the Loop Workspace, too.
January 8, 2025 at 2:52 PM
Unfortunately, the label of the Loop workspace will not change, if the label of the M365 will change 🙈 In late February Microsoft will fix it and updated labels will apply to the Loop Workspace, too.
the user will lose access to the Loop workspace.
Users can use different Loop components in the workspace.
If the Team will be deleted, also the Loop workspace will be deleted.
Also, the Loop workspace will automatically receive the sensitivity label of the M365 group at creation time.
Users can use different Loop components in the workspace.
If the Team will be deleted, also the Loop workspace will be deleted.
Also, the Loop workspace will automatically receive the sensitivity label of the M365 group at creation time.
January 8, 2025 at 2:52 PM
the user will lose access to the Loop workspace.
Users can use different Loop components in the workspace.
If the Team will be deleted, also the Loop workspace will be deleted.
Also, the Loop workspace will automatically receive the sensitivity label of the M365 group at creation time.
Users can use different Loop components in the workspace.
If the Team will be deleted, also the Loop workspace will be deleted.
Also, the Loop workspace will automatically receive the sensitivity label of the M365 group at creation time.
The Loop workspace membership is the #Microsoft365 group membership of the team. Also, the membership of the Loop workspace will follow the M365 group membership. Adding a new member to the Team will grant access to the Loop workspace and when removing a user from the Team,
January 8, 2025 at 2:52 PM
The Loop workspace membership is the #Microsoft365 group membership of the team. Also, the membership of the Loop workspace will follow the M365 group membership. Adding a new member to the Team will grant access to the Loop workspace and when removing a user from the Team,
And again: this update applies to new tenants starting early February, but also for existing tenants without customized policies.
January 8, 2025 at 9:50 AM
And again: this update applies to new tenants starting early February, but also for existing tenants without customized policies.
Transcription in Teams will be enabled by default for new tenants created in February 2025 and after that date AND tenants without customized policies.
Today, the setting for transcription in the Default Policy is disabled or off. After the update, the setting is on by default.
Today, the setting for transcription in the Default Policy is disabled or off. After the update, the setting is on by default.
January 8, 2025 at 9:50 AM
Transcription in Teams will be enabled by default for new tenants created in February 2025 and after that date AND tenants without customized policies.
Today, the setting for transcription in the Default Policy is disabled or off. After the update, the setting is on by default.
Today, the setting for transcription in the Default Policy is disabled or off. After the update, the setting is on by default.
The rollout will start for Targeted Release user early February, and for GA users mid-February. Microsoft expects to complete the rollout by late February 2025.
January 8, 2025 at 9:12 AM
The rollout will start for Targeted Release user early February, and for GA users mid-February. Microsoft expects to complete the rollout by late February 2025.
It will help you to see when one of your tags that you are subscribed to has been mentioned in a message or chat.
The existing @Mentions filter allows you to catch messages in which you have been personally mentioned.
The existing @Mentions filter allows you to catch messages in which you have been personally mentioned.
January 8, 2025 at 9:12 AM
It will help you to see when one of your tags that you are subscribed to has been mentioned in a message or chat.
The existing @Mentions filter allows you to catch messages in which you have been personally mentioned.
The existing @Mentions filter allows you to catch messages in which you have been personally mentioned.
Set-CsTeamsEventsPolicy -Identity Global -RecordingForTownhall Enabled
Set-CsTeamsEventsPolicy -Identity Global -RecordingForWebinar Enabled
More details can be found here 👇
learn.microsoft.com/powershell/m...
New-CsTeamsEventsPolicy (MicrosoftTeamsPowerShell)
TeamsEventsPolicy is used to configure options for customizing Teams Events experiences.
learn.microsoft.com
January 6, 2025 at 12:00 PM
Set-CsTeamsEventsPolicy -Identity Global -RecordingForTownhall Enabled
Set-CsTeamsEventsPolicy -Identity Global -RecordingForWebinar Enabled
More details can be found here 👇
learn.microsoft.com/powershell/m...
The new policy will roll out in mid-February and expect to complete by late February 2025.
Microsoft recommends to act today and set the new parameter by PowerShell:
Example to set the recording behavior for Town Halls or Webinars:
Microsoft recommends to act today and set the new parameter by PowerShell:
Example to set the recording behavior for Town Halls or Webinars:
January 6, 2025 at 12:00 PM
The new policy will roll out in mid-February and expect to complete by late February 2025.
Microsoft recommends to act today and set the new parameter by PowerShell:
Example to set the recording behavior for Town Halls or Webinars:
Microsoft recommends to act today and set the new parameter by PowerShell:
Example to set the recording behavior for Town Halls or Webinars: