Microsoft Roadmap, messagecenter en blogs updates van 16-10-2024

Updated October 14, 2024: As an update, we would like to inform you that we are resuming the automatic uninstallation of classic Teams in your organization starting October 21, 2024. The attempt to uninstall classic Teams will commence in a staggered rollout.

This message applies to:

• Teams for Windows on non-VDI and VDI with the new Teams Only policy. Please see MC807466 for Mac details on the automatic uninstallation.
• VDI customers in persistent environments where Classic Teams is version 1.7.00.7956 or higher. Persistent VDI environments are environments where Classic Teams was installed with the .exe installer in Appdata\Local.

Note: For customers in non-persistent VDI environments where Teams was installed using the MSI in C:\Program Files (x86), this MC Post does not apply, and IT admins should remove Classic Teams from the golden image.

[What you need to do to prepare]

No additional changes are needed. This is for informational purposes only.

[Can I uninstall classic Teams manually?] 

Please refer to How to uninstall the classic Teams client for details.

–Original message for reference–

Out of caution, we have paused automatic uninstallation of classic Microsoft Teams due to a rare issue impacting the Teams Meeting Add-in in Microsoft Outlook application. This message applies to Teams for Windows only. We will update this message when we are ready to resume the uninstallation. 

[How this will affect your organization]

• This pause will only impact customers who have not already uninstalled classic Teams.
• This issue could result in the Microsoft Teams Meeting Add-in in Outlook disappearing from the Outlook application for Windows or could cause failure when users try to schedule or join Teams meetings.

[What you need to do to prepare]

If your users are experiencing this issue, a temporary workaround is to use the Microsoft Teams Calendar to schedule or join meetings. To repair users who continue to experience the Teams Meeting Add-in issues in Outlook, please refer to Teams meeting add-in missing from Outlook and new Teams – Microsoft Teams | Microsoft Learn

Can I uninstall classic Teams manually?

• Customers who experience this issue after the automatic uninstallation of classic Teams or after they manually uninstall classic Teams can review the troubleshooting steps in Teams meeting add-in missing from Outlook and new Teams – Microsoft Teams | Microsoft Learn
• Additional details can be found in the What happens if we can’t update users to new Teams section of End of availability for classic Teams client

Updated October 15, 2024: We have updated the content. Thank you for your patience.

Currently, Viva Amplify users have no easy way to reuse content that has previously been published in a campaign and often must copy and paste content from one publication to the next manually. Coming soon, a Viva Amplify user will be able to reuse content by copying an existing publication using a centralized ‘Save copy’ button available on any given campaign publication. This new feature streamlines the content creation process and maximizes efficiency for all communicators.

Important: Due to the recent our recent editor updates for Outlook and Teams distribution channels, any publications that were created using the old editor version will have their content reset to the main draft without customizations when copying a publication. This only applies to publications created on the old editor versions. For any new publications created, copying a publication will create a copy of the publications including any customized content and audiences as intended. 

This message is associated with Microsoft 365 Roadmap ID 409234

[When this will happen:]

General Availability (Worldwide):We will begin rolling out late October 2024 (previously late September) and expect to complete by late November 2024 (previously early October).

[How this affects your organization:]

Soon, Amplify users will be able to copy existing publications in a campaign regardless of the publication’s status. This feature is available for users in the web/desktop experience. Please note that Amplify on Mobile iOS & Android applications are out of scope currently.

The “save a copy” button is present under the ‘More options’ button in the campaign overview and publications tab where all the publications are present. Users can also access it when authoring right under the ‘Save and close’ button on the command bar. Please note that when a publication is copied, it will copy all content of the publication, including all channel customization across SharePoint, Teams and Outlook, as well as the audiences of the original publication if desired. 

Additionally, for preview customers, the copy a publication feature does not support the ability to copy Viva Engage customized content. This will come as part of a separate release in the future.  

[What you can do to prepare:]

There is no action for admins beyond reviewing any internal help or guidance you have may have created for end users.  

Microsoft Graph connectors enable you to index enterprise content in third-party systems for knowledge extension in Microsoft 365 Copilot. Microsoft offers a wide range of free connectors for products like ServiceNow, Jira, Confluence, Salesforce, File shares etc.

We are announcing early preview (space limited) of new connectors for the following systems –

• GitHub (repositories)
• Google Drive (files)
• Jira Data Center (issues)
• PostgreSQL (records)
• Salesforce (knowledge base articles)
• Stack Overflow (QnA)
• WordPress (webpages)
• Zendesk (help center articles)
• Zoom (meeting transcripts)

[When will this happen:]

Early Preview (limited slots only): We will begin rolling out from early October 2024 and complete by mid-November 2024.

Targeted Release: We will begin rollout in mid-November 2024 and expect to complete by end of December 2024.

[What you need to do to prepare:]

If you would like to try out the preview of new connectors, sign-up for preview. The form to sign up is available in our documentation page (hyperlinks available in list above). Alternatively, you may drop us an email with the connectors you wish to preview at [email protected].

Our team will reach out to you to discuss your requirements and will share relevant documentation and next steps. Please note that slots are limited, and we may not be able to accommodate all customers during preview.

[How this will affect your organization:]

Upon configuration of Graph connectors, your end users will be able to prompt Copilot to ask queries about the indexed content. Your end users will also be able to search for the content in any of the Microsoft Search clients like SharePoint, Bing, Microsoft 365 (Office) app etc.

To learn more about Microsoft Graph connectors, please visit our official documentation at Microsoft Graph connectors overview for Microsoft Search

Coming soon to Microsoft Teams: A new feature to enhance the security in external collaboration. If your company allows external domains to contact your users in Teams, we will identify if an external user is impersonating a brand commonly targeted by phishing attacks during their initial contact with your user through Teams Chat. If we detect potential impersonation, we will show a high-risk alert to the user, notifying them to check for suspicious name/email and proceed with caution.

This message is associated with Microsoft 365 Roadmap ID 421190.

[When this will happen:]

Targeted Release: We will begin rolling out late October 2024 and expect to complete by late October 2024.

General Availability (Worldwide): We will begin rolling out mid-November 2024 and expect to complete by mid-November 2024.

[How this will affect your organization:]

Before this rollout: For organizations that have enabled Teams external access, user can receive messages from any user from external domain. Teams does not scan the sender for impersonation risks. When a user receives a chat invitation, the user can accept, or block, or preview the message. Note: Previewing the message does not put the organization at risk. 

After this rollout: If your organization enables Teams external access, we will check for potential impersonation activity when your user receives a message from an external sender for the first time. Your users will see a high-risk warning in the Accept/Block flow if we think there is potential impersonation risk, and users must preview the message before they can choose to Accept or block. If users choose to accept, we will prompt them again with potential risk before proceeding with Accept.

This security check will be done automatically. No admin configuration is required. Admins can check the audit log for impersonation attempts detected.

Teams detects an impersonation attempt in chat. In this case, the sender claims to be associated with Microsoft, but is not coming from a legitimate Microsoft domain:

When a user selects Preview their messages in the first screen, and then selects Accept, the user is alerted again to the potential for risk in this screen:

This feature will be on by default.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to update any relevant documentation. We recommend that you educate your users on what the new high-risk Accept/Block screen means and remind users to proceed with caution.

Before rollout, we will update this post with revised documentation.

Support for Office 2016 and Office 2019 will end one year from today, on October 14, 2025. After that date, no further updates, security fixes, or technical support will be available for these versions of Office. While the applications may continue to function, using unsupported software could lead to potential security risks and other issues. Because migrations can take time, we recommend starting to upgrade any remaining devices your organization has running Office 2016 or Office 2019 to a supported version as soon as possible.

[What you need to do to prepare:]

To mitigate these risks and ensure your organization remains secure and compliant, we recommend upgrading devices running Office 2016 or Office 2019 to Microsoft 365 E3, which includes Microsoft 365 Apps for enterprise plus core device management, security, and compliance capabilities. Microsoft 365 Apps for enterprise provides the latest versions of desktop apps like Word, Excel, and PowerPoint with regular updates and continuous support under the Modern Lifecycle Policy and is eligible for the Microsoft 365 Copilot add-on.

For scenarios that require a fully disconnected solution, we recommend upgrading to Office LTSC 2024. Office LTSC 2024 includes a subset of the value in Microsoft 365 Apps and will be supported for five years under the Fixed Lifecycle Policy.

Resources to help you prepare for this transition:

• Read the upgrade guidance for an overview of how to move from Office 2016 or Office 2019 to Microsoft 365 Apps.
• Consider engaging Microsoft FastTrack, a Microsoft support service for moving to Microsoft 365 E3.
• Visit our Office End of Support Tech Community for more information and resources about the end of support for Office.

Planning ahead will help you avoid potential disruptions and keep your organization’s software environment secure and up to date.

Before this rollout, the use of third-party providers as part of the Microsoft SharePoint eSignature pay-as-you-go platform is limited to regions supported by the native Microsoft SharePoint eSignature.

With this rollout, customers across the globe will be able to use third-party providers, wherever they are supported. Users will no longer be required to enable native SharePoint eSignature as a prerequisite for enabling either Docusign or Adobe Acrobat Sign. Pay-as-you-go must be set up to enable SharePoint eSignature, but Microsoft will not charge customers for using third-party providers.

This message is associated with Microsoft 365 Roadmap ID 421194.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out early November 2024 and expect to complete by mid-November 2024.

[How this will affect your organization:]

After this rollout, admins can enable a third-party provider without enabling native SharePoint eSignature, and vice versa.

Microsoft 365 users who have licenses with Adobe Acrobat Sign or Docusign will be able to initiate eSignature requests with these providers from SharePoint.

[What you need to do to prepare:]

Admins need to enable the feature in the Microsoft admin center at Setup > Automate content with Syntex> Go to Syntex > eSignature

Coming soon for Microsoft Teams: When users or admins configure Microsoft Edge as the browser to open web links in Teams, then links in Teams chat will be open in Edge, and Edge launches in the profile that matches the authenticated profile. Users will benefit from a seamless browsing experience that integrates their identity and user data across Microsoft apps.&

This message is associated with Microsoft 365 Roadmap ID 414521.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out late October 2024 and expect to complete by late November 2024.

[How this will affect your organization:]

Before this rollout, users are asked to reauthenticate links in the browser, which slows down users.

By default, there are no changes.

By default, the feature will be on with setting System default browser and Teams links will open in the system’s default browser. System default browser refers to the default browser specified on the user’s Mac device.

Admins can control the settings and availability of this feature (and override user settings) by policy in the Microsoft 365 Apps admin center:

• If this policy is enabled, admins can go to Choose which browser opens web links and select Microsoft Edge.
• If this policy is disabled or not configured, web links will open in the system default browser.

How admins update the policy in the Microsoft 365 Apps admin center:

After admins configure the policy to open links with Edge in Teams, this banner displays to users:

How users update the browser settings in Teams:

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your admins and users about this change and update any relevant documentation.

Before rollout, we will update this post with revised documentation.

In early November 2024, we’re releasing the Allow web search in Copilot policy to offer more ways for you to manage web search in Microsoft 365 Copilot and Microsoft Copilot. This includes the ability to manage web search separately from other optional connected experiences (OCE) for Microsoft 365.

Allowing Copilot to reference web content via web search improves the quality of Copilot responses by grounding them in the latest information from the web via the Bing search service. Learn more about web search queries.

[When this will happen:]

General Availability: We will begin rolling out the Allow web search in Copilot policy in early November 2024 and expect to complete by mid-November 2024.

[How this will affect your organization:]

With the Allow web search in Copilot policy, you will be able to manage web search in Microsoft 365 Copilot and Microsoft Copilot separately from how you manage other optional connected experiences (OCE). Both the Allow web search in Copilot policy and the OCE policy can be managed at the user/group-level.

You will be able to manage the Allow web search in Copilot policy from Microsoft 365 Apps admin center at config.office.com when the policy becomes available in early November.

If the Allow web search in Copilot policy is not configured, web search in Microsoft 365 Copilot and Microsoft Copilot will be determined by your existing OCE policy setting. Refer to the Allow the use of additional optional connected experiences in Office policy to confirm your OCE policy settings. If neither the Allow web search in Copilot policy nor the OCE policy is configured, web search will be available in Microsoft 365 Copilot and Microsoft Copilot. 

If the Allow web search in Copilot policy is configured [Enabled], you have three settings to configure web search in Copilot separately from your desired OCE policy setting:

• Enabled web search in Microsoft 365 Copilot and Microsoft Copilot
• Disabled web search in Microsoft 365 Copilot and Microsoft Copilot.
• Disabled in Microsoft 365 Copilot Work mode, Enabled in Microsoft 365 Copilot Web mode/Microsoft Copilot

Note: If web search is enabled for Work mode in Microsoft 365 Copilot, users will have the option to disable it from the plug-ins menu. The option is not available for Web mode in Microsoft 365 Copilot.

Both the OCE policy and the Allow web search in Copilot policy can be managed for groups of users. If you want to separately manage groups of users, such as managing your Microsoft 365 Copilot users separately from your Microsoft Copilot users, you can create groups for each and apply the policies.

[What you need to do to prepare:]

Allowing Copilot to reference web content via web search improves the quality of Copilot responses by grounding them in the latest information from the web via the Bing search service. The Allow web search in Copilot policy is not configured by default when it becomes available in early November 2024. No action is needed if you wish to continue with your current settings–this will be the case for most customers who are already using web search in Copilot.

Once available, the Allow web search in Copilot policy will let you manage web search in Microsoft 365 Copilot and Microsoft Copilot separately from how you manage the OCE policy. If you had previously managed the OCE policy to enable or disable web search, consider how you want to manage the OCE policy and the Allow web search in Copilot policy separately to achieve your desired scenario once the new policy is available in early November.

Once you choose your desired setting using the Allow web search in Copilot policy, the setting will take effect in your environment within 24 – 48 hours.

In Exchange Online PowerShell (EXO) V3.0, we introduced the Connect-ExchangeOnline cmdlet to connect to the Microsoft Exchange Online environment through Microsoft PowerShell, which loads the help file by default. This help file is required for running the Get-Help cmdlet. However, not many customers used the Get-Help cmdlet. In EXO V3.3, we added the -SkipLoadingCmldteHelp parameter. When -SkipLoadingCmldteHelp is used with Connect-ExchangeOnline, help files do not load the on the customer system, which saves resources.

However, starting with EXO V3.7, we are changing this default behavior. The Help file will not be loaded by default, and a new parameter -LoadCmdletHelp will be required to load the cmdlet help and use the Get-Help cmdlet. To avoid breaking existing scripts, the -SkipLoadingCmldteHelp parameter will continue exist, but will not function.

[When this will happen:]

General Availability (Worldwide): The changes will be available in EXO V3.7 (the next release of our EXO V3 module) in early November 2024.

[How this will affect your organization:]

Starting with EXO V3.7, if you want to use the Get-Help cmdlet, you will have to use the parameter -LoadCmdletHelp along with Connect-ExchangeOnline.

[What you need to do to prepare:]

This message only applies to customers who upgrade their EXO module version to 3.7.0. Earlier versions will not be affected by these changes.

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.

Learn more

• Connect-ExchangeOnline (ExchangePowerShell) | Microsoft Learn (will be updated before rollout)
• Get-Help (Microsoft.PowerShell.Core) – PowerShell | Microsoft Learn
• Download an EXO module from PowerShell Gallery | ExchangeOnlineManagement 3.6.0.

Coming soon for Microsoft Planner customers with Premium Planner licenses (P3 and P5):

• Users will be able to create Portfolios in Planner, which will have a list of plans and an associated Roadmap, giving Planner users an upgraded experience compared to the Roadmap in Microsoft Project for the web. The Project for the web Roadmap will not be changed and will continue to work as it currently does.
• Admins will be able to enable/disable the Roadmap in Project for the web and Portfolios in Planner in the Microsoft 365 admin center.

This message is associated with Microsoft 365 Roadmap ID 187140.

[When this will happen:]

Public Preview: We will begin rolling out late October 2024 and expect to complete by late October 2024.

General Availability (Worldwide): We will begin rolling out early November 2024 and expect to complete by mid-November 2024.

[How this will affect your organization:]

Before this rollout, in the Microsoft 365 admin center, admins have a toggle to turn Project for the web Roadmap on and off.

After this rollout, admins can use the toggle to enable and disable the Project for the web Roadmap and Portfolios in the Planner app.

The Roadmap in Project for the web and Portfolios in Planner are enabled by default. If you have disabled the Roadmap in Project for the web for your tenant, the same setting will be applied for Portfolios in Planner.

To do this, go to Microsoft 365 admin center > Show All > Settings > Org settings > Services > Project > A side panel opens > Check the box for Turn on Roadmap and Portfolio for your organization:

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your admins about this change and update any relevant documentation.

Before rollout, we will update this post with revised documentation.

With the ever-increasing sophistication of cyber attacks, the increasing use of cloud-based services, and the proliferation of mobile devices, it’s essential that organizations secure access for both human and non-human identities to all on-premises and cloud resources, while continuously working to improve their security posture.

We’re excited to share the Microsoft Entra feature release information for July–September 2024, along with third-quarter change announcements. This quarter’s updates include general availability releases for Entra ID and important change announcements on the retirement of Microsoft Azure AD Graph; enhancing the security of Apple devices in the enterprise with hardware-bound device identity; MFA enforcement on Microsoft Entra admin center, Azure portal, and Microsoft Intune admin center; and many more.

Please refer to the summary of the September 2024 product updates. We also communicate these updates through What’s new in Microsoft Entra ID, email, and the release notes.

Note: The product update summary is organized by Microsoft Entra products, so you can quickly scan what’s relevant for your deployment.

Learn more: What’s new in Microsoft Entra ID?

Coming soon to the Microsoft Purview AI Hub: We will update the left navigation to include sections for Overview, Recommendations, Reports, Policies, and Activity Explorer.

This message is associated with Microsoft 365 Roadmap ID 415451.

[When this will happen:]

Public Preview: We will begin rolling out mid-October 2024 and expect to complete by mid-October 2024.

General Availability (Worldwide): We will begin rolling out mid-November 2024 and expect to complete by mid-November 2024.

[How this will affect your organization:]

Before this rollout: Microsoft Purview includes Analytics, Policies, and Activity Explorer pages.

After this rollout, Microsoft Purview AI Hub will include:

• The new Overview page will include getting started steps, recommendation cards to help improve your AI data security, analytics cards, and links to documentation.
• The new Recommendations page will include the list of recommendations provided by Microsoft and their completion status.
• The new Reports page (formerly Analytics) will include analytics charts grouped by activity, user, and data.
• The updated Policies page will include a list of policies created by AI Hub with a link to edit the policies within their respective solutions.
• The updated Activity Explorer page will include events generated by the policies created through Microsoft Purview AI Hub.

This change will be on by default.

New Overview page

New Recommendations page:

New Reports page:

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your admins about this change and update any relevant documentation.

Get ready for this change by reviewing the Microsoft Purview AI Hub documentation:

• Microsoft Purview AI Hub provides insights, policies, and controls for AI apps
• Considerations for Microsoft Purview AI Hub and data security and compliance protections for Microsoft Copilot
• Permissions for Microsoft Purview AI Hub