2022 CW 07 Microsoft 365 Message Center changes

When users in a particular Teams team and channel are covered by Teams DLP policy, all the messages (initiated by the user covered under the policy) wil be protected. With this capability, you can apply the same Teams DLP policy rules and actions on the associated SharePoint site that stores documents shared by users within that Team/Channel. This will enable you to manage protection with the same Teams DLP policy rather than requiring the application of distinct policies to SharePoint and OneDrive for Business individually to cover the documents.
Additionally, when users protected as a part of the Teams DLP policy initiate a One-on-One chat, the chat conversation is protected by the Teams DLP policy. With this new capability, you will be able to apply the same Teams DLP policy rules and actions on the associated OneDrive for Business folder that stores any documents shared by a chat participant
Note: If the recipient of a message is covered by the Teams DLP policy, and the sender is not covered under any Teams DLP policy, then there will be no protection applied.

When users in a particular Teams team and channel are covered by Teams DLP policy, all the messages (initiated by the user covered under the policy) wil be protected. With this capability, you can apply the same Teams DLP policy rules and actions on the associated SharePoint site that stores documents shared by users within that Team/Channel. This will enable you to manage protection with the same Teams DLP policy rather than requiring the application of distinct policies to SharePoint and OneDrive for Business individually to cover the documents.
Additionally, when users protected as a part of the Teams DLP policy initiate a One-on-One chat, the chat conversation is protected by the Teams DLP policy. With this new capability, you will be able to apply the same Teams DLP policy rules and actions on the associated OneDrive for Business folder that stores any documents shared by a chat participant
Note: If the recipient of a message is covered by the Teams DLP policy, and the sender is not covered under any Teams DLP policy, then there will be no protection applied.

You will be able to roll out Windows 11 using many of your existing management and deployment tools and processes including, but not limited to, Windows Update for Business, Microsoft Endpoint Manager, and Windows Autopilot. For Enterprise and Education customers the Windows Update for Business deployment service provides you with more control over Windows Update than ever before to approve, schedule or expedite updates via Microsoft Endpoint Manager.

Between now and July 31st, organizations using Skype for Business Online will experience no change in service, and you will be able to continue to add new users as needed. After that date, the service will no longer be accessible.
Services that integrate with Skype for Business Online will not be supported beyond the July 31, 2021, retirement. This includes support for third-party audio conferencing providers (ACP), Skype for Business Online Cloud Connector Edition (CCE), hybrid voice configurations, and Skype Meeting Broadcast.
The retirement of Skype for Business Online does not affect the Skype consumer service, Skype for Business Server products and Skype for Business Online operated by 21Vianet (China Sovereign Clouds Instance).

We know that every organization will need time to transition to Windows 11. You choose the pace at which you want to upgrade. Our goal is to support you, so the effort is seamless and strategic. Windows 11 is built on the Windows 10 code base so it’s natively compatible with the software and solutions you use today and the investments you’ve made in Windows 10 will carry forward. In addition, Windows 11 and Windows 10 are designed to coexist, backed by a common set of security and management capabilities delivered by the Microsoft cloud.

What changes and doesn't change with Windows 11
Upgrade paths and deployment tools
Unpacking Microsoft 365 and Windows licensing
Servicing and lifecycle: Windows 11 and Windows 10
Windows Update for Business
Delivery Optimization
Application compatibility (Test Base, App Assure)
Preparing for Windows 11 with Microsoft Intune & Configuration Manager
Planning for Windows 11 with analytics
Windows Autopilot
Microsoft Edge
Universal Print
What's new and what's changed with MSIX

When will this happen:

July 21, 2021, from 08:00 AM - 06:00 PM (PDT)

We are announcing exciting plans that bring together the manageability of Microsoft Endpoint Manager, the openness of the new Microsoft Store, and the flexibility of Windows Package Manager. These plans will enhance the new Microsoft Store experience that is coming soon to both Windows 11 and Windows 10.

Starting in the first half of 2022 you will be able to find applications from the entire breadth of the Microsoft Store catalog and deploy to your managed devices all from within Microsoft Intune, or your unified endpoint management (UEM) solution. This will include support for all the new (and existing) app types coming to the new Microsoft Store including Win32, .NET, Universal Windows Platform (UWP), and Progressive Web Apps (PWAs).

Additionally, we are announcing that the Microsoft Store for Business and Microsoft Store for Education will be retired in the first quarter of 2023. You may continue to use the current capabilities for free apps until that time. There will be no support for Microsoft Store for Business and Education on Windows 11.

Please expect a Message Center update with more information once the preview mentioned above is available for your evaluation.

Key points:
Timing: Key milestones that we are working toward to improve the overall commercial app management experience:
Windows Package Manager v1.0: Generally available
Intune integration with Windows Package Manager app repository & the new Microsoft Store (Preview): Expected in the first half of 2022
Intune integration with Windows Package Manager app repository & the new Microsoft Store (general availability): Expected in the second half of 2022
Retirement of Microsoft Store for Business and Education for Windows 10: Expected Q1 2023
Action: review and assess impact on your organization

How will this affect your organization:
If you are using Microsoft Store for Business or Education to manage and deploy applications to your organization, you will need to move to the new system before Q1 2023.

Even though Microsoft has discontinued the publication of drivers to Windows Update for Windows 7 SP1, Windows Server 2008, and Windows Server 2008 R2, signed drivers will continue to be made available to ensure driver reliability for Volume Licensing customers who have elected to participate in an Extended Security Update (ESU) program. Windows 7, Windows Server 2008, and Windows Server 2008 R2 driver submissions for the Windows Hardware Compatibility Program (WHCP) will continue to be available through January 2023.

For driver publication changes, organizations that use the ESU program will continue to have the ability to deploy drivers to managed devices using Windows Server Update (WSUS) and other supported methods. Microsoft discontinued publishing of SHA-2 signed drivers to Windows Update which target Windows 7 SP1, Windows Server 2008, Windows Server 2008 R2 devices on June 17, 2021. While these Windows versions reached the end of support on January 14, 2020, we are making this change to diminish disruptions for users who remain on these versions of Windows. This includes:

Any driver package submitted for multi-targeting for currently supported versions of Windows and Windows Server
Any driver package targeting versions of Windows or Windows Server that have reached the end of support.

Windows 7, Windows Server 2008, and Windows Server 2008 R2 driver submissions for the Windows Hardware Compatibility Program (WHCP) will continue to be available through January 2023. These submissions will continue to be made available to ensure optimal driver reliability for Volume Licensing customers who have elected to participate in the Extended Security Update (ESU) program.

Action: review, assess and decide what you want the default expiration period to be for your organization

I want to be part of the early adopter program for this feature, how can I do that?
Please reach out to your CSAM or review Changes to meeting expiration for details to enroll. If accepted to the early adopter program, we will turn the feature on for your tenant within a week.
As part of the evolution of the new Stream (built on SharePoint), we are introducing the meeting recording auto-expiration feature, which will automatically delete Teams recording files stored in OneDrive or SharePoint after a preset period of time. Admins can disable this feature if desired.

[Key points]

Microsoft 365 Roadmap ID: 84580.
Timing: late March (previously early January) through late April (previously late February)
Roll-out: tenant level
Control type: user control and admin control
Documentation:
Meeting policies and meeting expiration in Microsoft Teams
Record a meeting in Teams

Action: review, assess and decide what you want the default expiration period to be for your organization

[When this will happen:]

We expect this update to begin rolling out at in late January (previously early January) and expect the rollout to be completed by late February (previously late January).

[When this will happen:]

We expect this update to begin rolling out at in early February (previously late January) and expect the rollout to be completed by early March (previously late February).

This message is associated with Microsoft 365 Roadmap ID 85639
[When this will happen:]

Rollout will begin in early January (previously early December) and complete by the end of January (previously end of November).

This message is associated with Microsoft 365 Roadmap ID 85639
[When this will happen:]

Rollout will begin in early January (previously early December) and complete by the mid-February (previously end of January).

Microsoft 365 Lists content is personalized to the individual user

Note: The new Microsoft 365 Lists entry point cannot be disabled or customized.
[Key points:]
Microsoft 365 Roadmap ID: 85641.
Timing:
Targeted release: will begin rolling out in early January (previously late November) and is expected to be complete in mid-January (previously early December).
Standard: will begin rolling out in late January (previously early January) and is expected to be complete in early February (previously mid-January).
Roll-out: tenant level
Action: Action: review and assess

Microsoft 365 Lists content is personalized to the individual user

Note: The new Microsoft 365 Lists entry point cannot be disabled or customized.
[Key points:]
Microsoft 365 Roadmap ID: 85641.
Timing:
Targeted release: will begin rolling out in early January (previously late November) and is expected to be complete in mid-January (previously early December).
Standard: will begin rolling out in mid-March (previously late January) and is expected to be complete in late March (previously early February).
Roll-out: tenant level
Action: Action: review and assess

To avoid suppressing music and to allow users to enable the new high-fidelity music mode, we have built an ML-based music detector which will inform the user whenever music is present through a notification. This will give the end user the choice whether music is indeed an unwanted background noise, such as when calling into a meeting from a coffee shop, or if music is a desired signal, such as when participating in a music lesson.
[Key points]
Microsoft 365 Roadmap ID: 89016
Timing:
Standard: We will begin rolling this out in late January and expect to complete rollout mid-February.
GCC: We will begin rolling this out in mid-February and expect to complete rollout late February.
GCC-H: We will begin rolling this out in early March and expect to complete rollout early April.
DoD: We will begin rolling this out in late March and expect to complete rollout late April.
Roll-out: Tenant level

To avoid suppressing music and to allow users to enable the new high-fidelity music mode, we have built an ML-based music detector which will inform the user whenever music is present through a notification. This will give the end user the choice whether music is indeed an unwanted background noise, such as when calling into a meeting from a coffee shop, or if music is a desired signal, such as when participating in a music lesson.
[Key points]
Microsoft 365 Roadmap ID: 89016
Timing:
Standard: We will begin rolling this out in late April (previously late January) and expect to complete rollout mid-May (previously mid-February).
GCC: We will begin rolling this out in mid-May (previously mid-February) and expect to complete rollout late May (previously late February).
GCC-H: We will begin rolling this out in early June (previously early March) and expect to complete rollout early July (previously early April).
DoD: We will begin rolling this out in late June (previously late March) and expect to complete rollout late July (previously late April).
Roll-out: Tenant level

Microsoft Team Templates allow administrators to easily deploy consistent teams across their organization using predefined or customized team templates across their organization.
SharePoint templates offer a straightforward way for admins to build sites with pre-populated pages, page templates, news post templates, and web parts that can be customized to fit the needs of their organization.
Through this integration, Teams administrators can create templates that include SharePoint components, bringing together the capabilities of the Teams and SharePoint templates.
This message is associated with Microsoft 365 Roadmap ID: 84724
[When this will happen:]
We will begin rolling this out in mid-January and expect to complete rollout early February.

Microsoft Team Templates allow administrators to easily deploy consistent teams across their organization using predefined or customized team templates across their organization.
SharePoint templates offer a straightforward way for admins to build sites with pre-populated pages, page templates, news post templates, and web parts that can be customized to fit the needs of their organization.
Through this integration, Teams administrators can create templates that include SharePoint components, bringing together the capabilities of the Teams and SharePoint templates.
This message is associated with Microsoft 365 Roadmap ID: 84724
[When this will happen:]
We will begin rolling this out in mid-January and expect to complete rollout mid-March (previously early February).

We expect this rollout to begin in late January and expect the rollout to be completed by early February.

[When this will happen:]

We expect this rollout to begin in early February (previously late January) and expect the rollout to be completed by mid-February (previously early February).

This message is associated with Microsoft 365 Roadmap ID 84906, 84001.
[When this will happen:]
Live captions for web: We expect the rollout to begin in early February and expect the rollout to be completed by mid-February.
CART captions for web: We expect the rollout to begin in early April and expect the rollout to be completed by mid-April.

Roll-out: tenant level
Control type: Team owner and team member control
Action: review and assess by February 28, 2022

Roll-out: tenant level
Control type: Team owner and team member control
Action: review and assess by February 28, 2022

We will begin rolling out this change beginning in early March and completing by late March 2022.

We will begin rolling out this change beginning in early March and completing by late March 2022.

This change only affects Office on devices running Windows and only affects the following applications: Access, Excel, PowerPoint, Visio, and Word.

[Key points:]
Timing: The change will begin rolling out in Version 2203, starting with Current Channel (Preview) in early April 2022. Later, the change will be available in the other update channels, such as Current Channel, Monthly Enterprise Channel, and Semi-Annual Enterprise Channel.
At a future date to be determined, we also plan to make this change to Office LTSC, Office 2021, Office 2019, Office 2016, and Office 2013.
Action: Review and assess impact

This change only affects Office on devices running Windows and only affects the following applications: Access, Excel, PowerPoint, Visio, and Word.

[Key points:]
Microsoft 365 Roadmap ID 88883
Timing: The change will begin rolling out in Version 2203, starting with Current Channel (Preview) in early April 2022. Later, the change will be available in the other update channels, such as Current Channel, Monthly Enterprise Channel, and Semi-Annual Enterprise Channel.
At a future date to be determined, we also plan to make this change to Office LTSC, Office 2021, Office 2019, Office 2016, and Office 2013.
Action: Review and assess impact

Windows 11 will have an annual feature update cadence, a change from the semi-annual cadence of Windows 10. Windows 11 feature updates will release in the second half of the calendar year and will come with 24 months of support for Home, Pro, Pro for Workstations, and Pro Education editions. Windows 11 will come with 36 months of support for Enterprise and Education editions, continuing to provide additional time and flexibility for the validation and at-scale deployments common on those editions.

When this will happen

Windows 11 will be available via all the existing Windows 10 servicing channels our commercial organizations are familiar with later this calendar year.

While Windows 11 marks an exciting milestone for the future of Windows, we want to remind you that we will continue to support Windows 10 through October 14, 2025. We will be introducing Window 10, version 21H2 in the second half of this year along with a Windows 10 Long-Term Servicing Channel (LTSC) edition.

How this will affect your organization

When Windows 11 reaches general availability, you will find Windows 11 added to Windows release health under Health in the Microsoft 365 admin center. There you will find information on any known issues, including safeguard holds implemented to ensure an optimal update experience for all devices.

You will be able to roll out Windows 11 using many of your existing management and deployment tools and processes including, but not limited to, Windows Update for Business, Microsoft Endpoint Manager, and Windows Autopilot. For Enterprise and Education customers the Windows Update for Business deployment service provides you with more control over Windows Update than ever before to approve, schedule or expedite updates via Microsoft Endpoint Manager.

What you need to do to prepare

Stay tuned for more information on Windows 11 availability and remember that being on the latest version of Windows provides you with both the latest features and security protections to help keep your devices safer.

More information

To learn more, see Windows lifecycle and servicing update.

Windows 11 will have an annual feature update cadence, a change from the semi-annual cadence of Windows 10. Windows 11 feature updates will release in the second half of the calendar year and will come with 24 months of support for Home, Pro, Pro for Workstations, and Pro Education editions. Windows 11 will come with 36 months of support for Enterprise and Education editions, continuing to provide additional time and flexibility for the validation and at-scale deployments common on those editions.

When this will happen

Windows 11 will be available via all the existing Windows 10 servicing channels our commercial organizations are familiar with later this calendar year.

While Windows 11 marks an exciting milestone for the future of Windows, we want to remind you that we will continue to support Windows 10 through October 14, 2025. We will be introducing Window 10, version 21H2 in the second half of this year along with a Windows 10 Long-Term Servicing Channel (LTSC) edition.

When will this happen:

Skype for Business Online will be retired on July 31, 2021.

How this will affect your organization:

Between now and July 31st, organizations using Skype for Business Online will experience no change in service, and you will be able to continue to add new users as needed. After that date, the service will no longer be accessible.
Services that integrate with Skype for Business Online will not be supported beyond the July 31, 2021, retirement. This includes support for third-party audio conferencing providers (ACP), Skype for Business Online Cloud Connector Edition (CCE), hybrid voice configurations, and Skype Meeting Broadcast.
The retirement of Skype for Business Online does not affect the Skype consumer service, Skype for Business Server products and Skype for Business Online operated by 21Vianet (China Sovereign Clouds Instance).

What you need to do to prepare:

We recommend that organizations currently using Skype for Business Online upgrade to Teams. As noted on April 29, 2021, Microsoft has been scheduling Microsoft-assisted upgrades to Teams for Skype for Business Online customers with cloud-only or hybrid deployments. Assisted upgrades help with last-mile technical steps of the transition to Teams. Organizations will be notified through the Teams admin center and the Microsoft 365 message center, 90 days prior to the scheduled date of their assisted upgrade.
Coexistence modes can enable your organization to operate Skype for Business Server/Teams side-by-side experiences until you are ready to move users to Teams Only. Users can be moved directly from Skype for Business Server to Teams Only mode after configuring Skype for Business hybrid with Microsoft 365 or Office 365. (Please note; however, that you will not be able to move online users out of Teams Only mode after retirement.)
While the duration of each upgrade to Teams will vary, users within a tenant will generally be upgraded within 24 hours from the start of the upgrade. During this window, users will still be able to access Skype for Business Online. Once the upgrade has completed and users log out of Skype for Business Online, they will only be able to use Teams to initiate and receive messages and calls as well as to schedule and host meetings. These users will be able to join a Skype for Business meeting scheduled by a user on Skype for Business Server or in a federated organization.

Learn more:

Whether you’re at the start of your upgrade journey or are wrapping up, these resources can help guide your organization through its transition to Teams:
Microsoft Teams admin documentation provides guidance for rolling out, managing, and preparing users for Teams.
Online upgrade guidance helps you prepare your technical environment and end-users for the upgrade to Teams.
Teams upgrade planning workshops take you through a proven framework for planning and implementing your upgrade from Skype for Business to Teams.
Microsoft Chalk Talks workshops teach best practices and practical guidance around some of the most popular and compelling scenarios in Teams.
FastTrack deployment assistance is available for eligible subscriptions.
Microsoft Partners can help you plan and execute your upgrade.

When will this happen:

Skype for Business Online will be retired on July 31, 2021.

How this will affect your organization:

We know that every organization will need time to transition to Windows 11. You choose the pace at which you want to upgrade. Our goal is to support you, so the effort is seamless and strategic. Windows 11 is built on the Windows 10 code base so it’s natively compatible with the software and solutions you use today and the investments you’ve made in Windows 10 will carry forward. In addition, Windows 11 and Windows 10 are designed to coexist, backed by a common set of security and management capabilities delivered by the Microsoft cloud.

What you need to do to:

Here are four key things you can do today to pave the way for a smooth integration of Windows 11 into your device estate:
Get started today. Join the Windows Insider Program for Business and start reviewing your devices, applications, and deployment processes.
Assess readiness. Validate your hardware and software. Engage App Assure to help solve and application compatibility issues.
Create a Windows 11 deployment plan. Prepare for Windows 11 and engage with Microsoft and our partners for guidance and support as needed.
Take advantage of cloud-based endpoint management capabilities offered in Microsoft Endpoint Manager such as Windows Autopilot which enables you to deploy new Windows 11 devices in a “business ready” state.

For full details about what each best practice entails, visit this page: Planning for Windows 11: best practices for organizations

For additional guidance, see the following resources:

Windows 11 overview - What's new in Windows
Windows Insider
FastTrack Center Benefit for Microsoft 365​ - FastTrack
Windows 11 requirements - What's new in Windows
Prepare for Windows 11 - What's new in Windows
Windows lifecycle and servicing update
Introducing Windows 11
Windows 11: The operating system for hybrid work and learning

When this will happen:

Both changes are effective beginning June 17, 2021.

How this will affect your organization:

Even though Microsoft has discontinued the publication of drivers to Windows Update for Windows 7 SP1, Windows Server 2008, and Windows Server 2008 R2, signed drivers will continue to be made available to ensure driver reliability for Volume Licensing customers who have elected to participate in an Extended Security Update (ESU) program. Windows 7, Windows Server 2008, and Windows Server 2008 R2 driver submissions for the Windows Hardware Compatibility Program (WHCP) will continue to be available through January 2023.

For driver publication changes, organizations that use the ESU program will continue to have the ability to deploy drivers to managed devices using Windows Server Update (WSUS) and other supported methods. Microsoft discontinued publishing of SHA-2 signed drivers to Windows Update which target Windows 7 SP1, Windows Server 2008, Windows Server 2008 R2 devices on June 17, 2021. While these Windows versions reached the end of support on January 14, 2020, we are making this change to diminish disruptions for users who remain on these versions of Windows. This includes:

Any driver package submitted for multi-targeting for currently supported versions of Windows and Windows Server
Any driver package targeting versions of Windows or Windows Server that have reached the end of support.

Windows 7, Windows Server 2008, and Windows Server 2008 R2 driver submissions for the Windows Hardware Compatibility Program (WHCP) will continue to be available through January 2023. These submissions will continue to be made available to ensure optimal driver reliability for Volume Licensing customers who have elected to participate in the Extended Security Update (ESU) program.

What you need to do to:

For driver signing changes, Microsoft partners should utilize the process below to sign drivers for Windows 7, Windows Server 2008, and Windows Server 2008 R2 through the Partner Center for Windows Hardware:
Remove existing signatures from driver binaries.
Generate new catalog files using INF2CAT.
Sign the security catalog files using the IHV/OEM certificate registered with the Partner Center for Windows Hardware.
Add the driver to your HCK file.
Sign the HCK file using the IHV/OEM certificate registered with the Partner Center for Windows Hardware.
Submit the driver package to the Partner Center for Windows Hardware for signing.
Download the signed driver bundle from the Partner Center for Windows Hardware.

For more details, read the official announcements:

Changes to driver signing for Windows 7, Windows Server 2008 R2, and Windows Server 2008
Changes to driver publication for Windows 7 SP1, Windows Server 2008 R2, and Windows Server 2008

For additional guidance, see the following resources:

Microsoft to use SHA-2 exclusively starting May 9, 2021
Windows Hardware Certification Kit (Windows HCK)
Windows 7 end of support FAQ
Window Server 2008 and 2008 R2 end of support FAQ

When this will happen:

Both changes are effective beginning June 17, 2021.

When will this happen:
The ability to apply layered Group Policy is available for all versions of Windows 10 as part of the July 2021 optional “C” client release and was made more broadly available beginning with the August 2021 Update Tuesday release. This feature will also be supported in Windows 11.

How this will affect your organization:
Adding the new apply layered Group Policy to the existing device installation policies improves intuitive usage and flexibility as follows:
Intuitive usage: With this new policy, you don’t need to know different device classes to prevent USB classes only from being installed. The new policy allows you to focus scripts on USB classes and be confident that no other class is going to be blocked unless specified by the IT admin.
Flexibility: In the past, every prevent policy took precedence over any allow policy, which created a set of definitions and a rigid set of allow/prevent devices, causing update strains every time a new set of devices entered the market. With the new policy, we introduce hierarchical layering in the following order:
Instance ID: the highest ranking
Hardware IDs and compatible IDs (Device IDs)
Class
Removable device property: the lowest ranking

For more details, read the official announcement: Introducing the ability to apply layered Group Policy.

For detailed guidance, see the following resource: Manage Device Installation with Group Policy (Windows 10).

When will this happen:
The ability to apply layered Group Policy is available for all versions of Windows 10 as part of the July 2021 optional “C” client release and was made more broadly available beginning with the August 2021 Update Tuesday release. This feature will also be supported in Windows 11.

Or modify the setting in PowerShell by setting the attribute NewMeetingRecordingExpirationDays. If you use PowerShell, set the attribute to “-1” to never auto-expire TMRs, or set it to a specific number of days (min: 1 day, max: 99,999 days). PowerShell documentation here: Set-CsTeamsMeetingPolicy (SkypeForBusiness) | Microsoft Docs
Example PowerShell Cmd:
Set-CsTeamsMeetingPolicy -Identity Global -NewMeetingRecordingExpirationDays 30
If you are going to specify a tenant level expiration standard, inform your user base about the change before we deploy it so that they are aware they will need to take action to retain their new recording files past the specified time period once the feature is enabled. They will also be notified in various ways as described in the FAQs link below.
Learn more about the feature: Meeting policies and meeting expiration in Microsoft Teams.
https://admin.microsoft.com/Adminportal/Home?ref=MessageCenter/:/messages/MC222640
https://docs.microsoft.com/powershell/module/skype/set-csteamsmeetingpolicy?view=skype-ps
https://support.microsoft.com/office/record-a-meeting-in-teams-34dfbe7f-b07d-4a27-b4c6-de62f1348c24
https://www.docs.microsoft.com/MicrosoftTeams/meeting-expiration
https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=84580%2C

Or modify the setting in PowerShell by setting the attribute NewMeetingRecordingExpirationDays. If you use PowerShell, set the attribute to “-1” to never auto-expire TMRs, or set it to a specific number of days (min: 1 day, max: 99,999 days). PowerShell documentation here: Set-CsTeamsMeetingPolicy (SkypeForBusiness) | Microsoft Docs
Example PowerShell Cmd:
Set-CsTeamsMeetingPolicy -Identity Global -NewMeetingRecordingExpirationDays 30
If you are going to specify a tenant level expiration standard, inform your user base about the change before we deploy it so that they are aware they will need to take action to retain their new recording files past the specified time period once the feature is enabled. They will also be notified in various ways as described in the FAQs link below.
Learn more about the feature: Meeting policies and meeting expiration in Microsoft Teams.
https://admin.microsoft.com/Adminportal/Home?ref=MessageCenter/:/messages/MC222640
https://docs.microsoft.com/MicrosoftTeams/meeting-expiration#changes-to-meeting-expiration
https://docs.microsoft.com/powershell/module/skype/set-csteamsmeetingpolicy?view=skype-ps
https://support.microsoft.com/office/record-a-meeting-in-teams-34dfbe7f-b07d-4a27-b4c6-de62f1348c24
https://www.docs.microsoft.com/MicrosoftTeams/meeting-expiration
https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=84580%2C

Allow users to submit feedback to Microsoft
Allow users to include log files and content samples when feedback is submitted to Microsoft
Allow Microsoft to follow up on feedback submitted by users
Learn more about image tags: Work with Image Tags in a SharePoint library
https://config.office.com/
https://docs.microsoft.com/microsoft-365/admin/manage/manage-feedback-ms-org?view=o365-worldwide
https://www.microsoft.com/en-ww/microsoft-365/roadmap?filters=&searchterms=68902

Allow users to submit feedback to Microsoft
Allow users to include log files and content samples when feedback is submitted to Microsoft
Allow Microsoft to follow up on feedback submitted by users
Learn more about image tags: Work with Image Tags in a SharePoint library
https://config.office.com/
https://docs.microsoft.com/microsoft-365/admin/manage/manage-feedback-ms-org?view=o365-worldwide
https://www.microsoft.com/en-ww/microsoft-365/roadmap?filters=&searchterms=88708

Learn more:
Data loss prevention and Microsoft Teams
https://compliance.microsoft.com/
https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=85667

Learn more:
Data loss prevention and Microsoft Teams
https://compliance.microsoft.com/
https://docs.microsoft.com/microsoft-365/compliance/dlp-microsoft-teams?view=o365-worldwide
https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=85667

More information

To learn more, see Windows lifecycle and servicing update.
https://techcommunity.microsoft.com/t5/windows-it-pro-blog/announcing-the-windows-update-for-business-deployment-service/ba-p/2178419
https://techcommunity.microsoft.com/t5/windows-it-pro-blog/windows-lifecycle-and-servicing-update/ba-p/2493043
https://www.microsoft.com/microsoft-365/blog/2021/06/24/windows-11-the-operating-system-for-hybrid-work-and-learning/

We recommend that organizations currently using Skype for Business Online upgrade to Teams. As noted on April 29, 2021, Microsoft has been scheduling Microsoft-assisted upgrades to Teams for Skype for Business Online customers with cloud-only or hybrid deployments. Assisted upgrades help with last-mile technical steps of the transition to Teams. Organizations will be notified through the Teams admin center and the Microsoft 365 message center, 90 days prior to the scheduled date of their assisted upgrade.
Coexistence modes can enable your organization to operate Skype for Business Server/Teams side-by-side experiences until you are ready to move users to Teams Only. Users can be moved directly from Skype for Business Server to Teams Only mode after configuring Skype for Business hybrid with Microsoft 365 or Office 365. (Please note; however, that you will not be able to move online users out of Teams Only mode after retirement.)
While the duration of each upgrade to Teams will vary, users within a tenant will generally be upgraded within 24 hours from the start of the upgrade. During this window, users will still be able to access Skype for Business Online. Once the upgrade has completed and users log out of Skype for Business Online, they will only be able to use Teams to initiate and receive messages and calls as well as to schedule and host meetings. These users will be able to join a Skype for Business meeting scheduled by a user on Skype for Business Server or in a federated organization.

Learn more:

Whether you’re at the start of your upgrade journey or are wrapping up, these resources can help guide your organization through its transition to Teams:
Microsoft Teams admin documentation provides guidance for rolling out, managing, and preparing users for Teams.
Online upgrade guidance helps you prepare your technical environment and end-users for the upgrade to Teams.
Teams upgrade planning workshops take you through a proven framework for planning and implementing your upgrade from Skype for Business to Teams.
Microsoft Chalk Talks workshops teach best practices and practical guidance around some of the most popular and compelling scenarios in Teams.
FastTrack deployment assistance is available for eligible subscriptions.
Microsoft Partners can help you plan and execute your upgrade.
https://aka.ms/successwithteams
https://aka.ms/TeamsChalkTalks
https://aka.ms/upgradeworkshops
https://docs.microsoft.com/microsoftteams/faq-journey%23is-skype-meeting-broadcast-going-to-retire-at-the-same-time-as-skype-for-business-online
https://docs.microsoft.com/microsoftteams/migration-interop-guidance-for-teams-with-skype
https://docs.microsoft.com/MicrosoftTeams/upgrade-automated
https://docs.microsoft.com/microsoftteams/upgrade-start-here
https://docs.microsoft.com/skypeforbusiness/hybrid/move-users-from-on-premises-to-teams
https://docs.microsoft.com/SkypeForBusiness/hybrid/plan-hybrid-connectivity
https://docs.microsoft.com/skypeforbusiness/legal-and-regulatory/end-of-integration-with-3rd-party-providers
https://techcommunity.microsoft.com/t5/microsoft-teams-blog/changes-ahead-for-cloud-connector-edition-and-hybrid-voice/ba-p/1650055
https://techcommunity.microsoft.com/t5/microsoft-teams-blog/skype-for-business-online-retires-july-31-2021-here-s-what-to/ba-p/2303300
https://techcommunity.microsoft.com/t5/microsoft-teams-blog/skype-for-business-online-to-be-retired-in-2021/ba-p/777833
https://www.microsoft.com/fasttrack/microsoft-365/collaboration
https://www.microsoft.com/solution-providers/home

Here are four key things you can do today to pave the way for a smooth integration of Windows 11 into your device estate:
Get started today. Join the Windows Insider Program for Business and start reviewing your devices, applications, and deployment processes.
Assess readiness. Validate your hardware and software. Engage App Assure to help solve and application compatibility issues.
Create a Windows 11 deployment plan. Prepare for Windows 11 and engage with Microsoft and our partners for guidance and support as needed.
Take advantage of cloud-based endpoint management capabilities offered in Microsoft Endpoint Manager such as Windows Autopilot which enables you to deploy new Windows 11 devices in a “business ready” state.

For full details about what each best practice entails, visit this page: Planning for Windows 11: best practices for organizations

For additional guidance, see the following resources:

Windows 11 overview - What's new in Windows
Windows Insider
FastTrack Center Benefit for Microsoft 365​ - FastTrack
Windows 11 requirements - What's new in Windows
Prepare for Windows 11 - What's new in Windows
Windows lifecycle and servicing update
Introducing Windows 11
Windows 11: The operating system for hybrid work and learning
https://blogs.windows.com/windowsexperience/2021/06/24/introducing-windows-11/
https://docs.microsoft.com/fasttrack/introduction
https://docs.microsoft.com/fasttrack/products-and-capabilities#app-assure
https://docs.microsoft.com/mem/autopilot/windows-autopilot
https://docs.microsoft.com/windows/whats-new/windows-11
https://docs.microsoft.com/windows/whats-new/windows-11-prepare
https://docs.microsoft.com/windows/whats-new/windows-11-requirements
https://insider.windows.com/for-business
https://techcommunity.microsoft.com/t5/windows-it-pro-blog/planning-for-windows-11-best-practices-for-organizations/ba-p/2493081
https://techcommunity.microsoft.com/t5/windows-it-pro-blog/windows-lifecycle-and-servicing-update/ba-p/2493043
https://www.microsoft.com/microsoft-365/blog/2021/06/24/windows-11-the-operating-system-for-hybrid-work-and-learning/

Add this event to your calendar and see the event page for more details Tech Community Live: Windows edition.
https://8gportalvhdsf9v440s15hrt.blob.core.windows.net/assets/Windows/ics/Tech%20Community%20Live%20Windows%20edition.ics
https://techcommunity.microsoft.com/t5/tech-community-live/tech-community-live-windows-edition/ev-p/2481262

Before manually deploying Update Health Tools,

If Update Health Tools have not been automatically deployed to your devices via Windows Update, please file a feedback item so we can understand why it was blocked and ensure that all eligible devices receive these important tools. To log a feedback item, launch the Windows Feedback Hub from the Start menu or by pressing Windows + F. When asked to choose a category, select Install and Update then Downloading, installing, and configuring Windows Update.
When prompted to Add more details, ensure the checkbox to Include data about Downloading, installing, and configuring Windows Update (Default) is selected.

Deployment of Update Health Tools:

Download:
The package can be downloaded from the Microsoft Download Center. The Update Health Tools package contains one Microsoft Installer each for Windows 10, versions 1809, 1909, 2004, and 20H2.

System requirements.
In order to use Update Health Tools, you will need Windows 10, version 1809, 1909, 2004, 20H2, or 21H1.

Installation instructions.
Select the files you would like to download, then select Next to start the download.
Save the files to a folder of your choice.
Use the instructions inside the Windows 10 app deployment by using Microsoft Intune document to deploy Windows 10 apps in Intune.

For more details, read the official post: Announcing Update Health Tools.

For additional guidance about using Microsoft Endpoint Manager to expedite updates, see Expedite Windows 10 quality updates in Microsoft Intune.
https://aka.ms/ExpediteUpdates
https://docs.microsoft.com/en-us/windows-insider/feedback-hub/feedback-hub-app#:~:text=Explore%20the%20Feedback%20Hub%201%20Home%20section.%20First%2C,...%207%20Your%20account.%20...%208%20Settings.%20
https://docs.microsoft.com/mem/intune/apps/apps-windows-10-app-deploy
https://docs.microsoft.com/mem/intune/protect/windows-10-expedite-updates
https://techcommunity.microsoft.com/t5/windows-it-pro-blog/announcing-update-health-tools/ba-p/2566232
https://www.microsoft.com/en-us/download/details.aspx?id=103324

The above changes will leverage Windows Package Manager, an open set of APIs that can integrate with any unified endpoint management solution. You organization can choose to integrate directly with these APIs to build your own solution to meet your specific needs, as well as for unmanaged devices. If you have internal line-of-business apps, you will be able to manage your own private app repository using Windows Package Manager as well.

Learn more:
For more information, see Evolving the Microsoft Store for Business and Education.
https://aka.ms/windows/msfb_evolution
https://blogs.windows.com/windowsexperience/2021/06/24/building-a-new-open-microsoft-store-on-windows-11/
https://docs.microsoft.com/windows/package-manager
https://docs.microsoft.com/windows/package-manager/winget/

For driver signing changes, Microsoft partners should utilize the process below to sign drivers for Windows 7, Windows Server 2008, and Windows Server 2008 R2 through the Partner Center for Windows Hardware:
Remove existing signatures from driver binaries.
Generate new catalog files using INF2CAT.
Sign the security catalog files using the IHV/OEM certificate registered with the Partner Center for Windows Hardware.
Add the driver to your HCK file.
Sign the HCK file using the IHV/OEM certificate registered with the Partner Center for Windows Hardware.
Submit the driver package to the Partner Center for Windows Hardware for signing.
Download the signed driver bundle from the Partner Center for Windows Hardware.

For more details, read the official announcements:

Changes to driver signing for Windows 7, Windows Server 2008 R2, and Windows Server 2008
Changes to driver publication for Windows 7 SP1, Windows Server 2008 R2, and Windows Server 2008

For additional guidance, see the following resources:

Microsoft to use SHA-2 exclusively starting May 9, 2021
Windows Hardware Certification Kit (Windows HCK)
Windows 7 end of support FAQ
Window Server 2008 and 2008 R2 end of support FAQ
https://docs.microsoft.com/lifecycle/faq/extended-security-updates
https://docs.microsoft.com/previous-versions/windows/hardware/hck/jj124227(v=vs.85)
https://docs.microsoft.com/windows-hardware/drivers/dashboard/
https://go.microsoft.com/fwlink/p/?linkid=2086115
https://techcommunity.microsoft.com/t5/windows-hardware-certification/changes-to-driver-publication-for-windows-7-sp1-windows-server/ba-p/2459992
https://techcommunity.microsoft.com/t5/windows-hardware-certification/changes-to-driver-signing-for-windows-7-windows-server-2008-r2/ba-p/2460039
https://techcommunity.microsoft.com/t5/windows-it-pro-blog/microsoft-to-use-sha-2-exclusively-starting-may-9-2021/ba-p/2261924
https://www.microsoft.com/windows-server/extended-security-updates