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

Updated October 3, 2024: We have updated the rollout timeline below. Thank you for your patience.

In new Outlook for Windows and web, when single-clicking on an empty time slot on the calendar surface, the quick compose pop-up will no longer appear. Instead, you will be able to create an appointment by typing directly in the time slot on the calendar grid, just as you can in classic Outlook for Windows. There will be no change to double-click behavior; the full compose form will still open as it does today.

This message is associated with Microsoft 365 Roadmap ID 406948.

[When this will happen:]

Targeted Release: We will begin rolling out early November 2024 (previously early September) and expect to complete by early December 2024 (previously early October).

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

[How this will affect your organization:]

This may affect how users create appointments quickly on the calendar surface. We expect this to be a better experience, especially for those familiar with classic Outlook inline appointment creation.

This update is available by default.

[What you need to do to prepare:]

This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation.

Updated October 3, 2024: We have updated the content.

Go to Connections button is now rolling out to customers. It will show up on your company’s intranet site header in a few days.

If your company is not ready to roll out Viva Connections to your employees, you can turn it off using the navigation setting which is now 100% GA and available to all customers. Thank you for your patience.

Microsoft Viva Connections is already available in any browser, giving your employees easy access to Viva Connections outside of Teams.

We are working on an additional entry point to access Viva Connections on web. This entry point will allow your employees to access Connections on web from your organization’s Microsoft SharePoint home site.

Navigation setting to turn the link to Connections on your SharePoint home site is starting to release now and will be available to you in next few days as we continue rolling out.

[When this will happen:]

Targeted Release: We will begin rolling out late August 2024 (previously early August) and expect to complete by early September 2024 (previously mid-August).

General Availability (Worldwide, GCC, GCCH, DoD): We will begin rolling out early September (previously mid-August) 2024 and expect to complete by late October 2024 (previously late September).

[How this will affect your organization:]

After this release, the Go to Connections link will display in the upper right of your company’s SharePoint home site menu. This feature will be on by default and accessible to all users in your tenant unless you turn it off.

[What you need to do to prepare:]

Go to Connections button is now rolling out to all customers. It will show up on your company’s intranet site header.

If your company is not ready to roll out Viva Connections to your employees, you can turn it off using the navigation setting.

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’re making some changes to on-demand indexes used to support SharePoint and OneDrive Search using Application Permissions. On/Starting November 1, 2024, if an on-demand index has not been queried in 100 days, the index will be decommissioned.

App-only permissioned requests (Search content with application permissions – Microsoft Graph | Microsoft Learn) may be created by custom applications using public Search APIs such as Microsoft Search Graph API or SharePoint Search REST API. This change will NOT affect normal user or delegated permissioned Search traffic from Enterprise Search endpoints (e.g., SharePoint, Teams, Outlook, Office.com, Bing@work, etc.), search-based web parts, or custom apps using the signed-in user’s permissions.

[When this will happen:]

Beginning November 1, 2024

[How this will affect your organization:]

Searching using Application Permissions is a latency expensive option. To make the process more efficient, when you run the initial search request and request private content, an on-demand index is provisioned to serve “private” results. The time required to build the index depends on the number of items in your users’ OneDrive and SharePoint. For a medium-to-large tenant, this may take days to a week to complete. Very large tenants will take longer. While the index is provisioning, search requests will only return shared and public content. Once the new index is complete, private and shared content will be returned. If no additional search requests for private content are sent within 100 days, the private index will be decommissioned. If needed again, a subsequent search request for private content will rebuild the index.

[What you need to do to prepare:]

If you have applications which run infrequently (e.g. every four months) and use Search with Application Permissions, plan for time to allow the on-demand index to rebuild.

Please click Additional Information to learn more.

Search content with application permissions – Microsoft Graph | Microsoft Learn

Coming soon for Microsoft Purview compliance portal | Communication Compliance: A notification banner designed to enhance transparency will alert users when keywords embedded in hidden content (such as hyperlinks or encoded strings) trigger a compliance policy match. With this rollout, investigators will be able to quickly recognize that some or all keyword matches are not immediately visible in the main content body, saving time and ensuring a more efficient triage experience.

This message is associated with Microsoft 365 Roadmap ID 417483.

[When this will happen:]

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

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

[How this will affect your organization:]

Before this rollout, users and investigators are not notified if policy matches occur for hidden text.

After this rollout, users will be notified if any policy matches in a message are concealed and not readily discernible in the main content.

This feature is available 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 notify your admins about this change and update any relevant documentation.

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

In February 2024, the retirement of Viva Topics was announced. As part of the change, Viva Engage will return to a simplified topics model, called Engage topics, and the integration with Viva Topics will be retired. This message is for customers who have tenants with topics data that currently resides in Viva Topics or Topics lightweight management and who are not licensed to use Viva Topics.

In November 2024, your organization’s topics data will be migrated to reside in Viva Engage. Migrations for all tenants notified will be completed by the end of November. During the migrations employees should not experience any degradation in their core topics experiences, including the ability to create topics, add topics to posts, follow topics, edit topics they created and increase the relevance of their feeds by following topics.

After the migration, topic creators will gain the ability to delete topics they created. Applicable admins will continue to edit topics and will gain the ability to delete topics within Viva Engage.

[Why is this change happening?]

As a result of the retirement of Viva Topics, Viva Engage will deprecate the integration with Viva Topics, but continue to support a simplified topics model to help organize, amplify, route and recall knowledge posted with topics. To ensure customer data is retained we will migrate customer topics data from Viva Topics or Lightweight Topics into Viva Engage to preserve topics applied to posts and associated Engage topic metadata such as followers, topic description and creator.

Learn more about the migration to Viva Topics, the Topics experience, and the Topics retirement.

[When this will happen:]

Rollout will begin in early November 2024 and will complete for all tenants notified by late November 2024.

[How this will affect your organization:]

During the migration, the experience of people using topics should not be disrupted. 

All topics used in Viva Engage that were Lightweight Topics or Viva Topics will be migrated to Engage topics the only exceptions are AI-suggested or access-controlled topics and topics listed in your topic exclusion list. As topic featuring will be deprecated any data associated with this feature will be deleted and will not be included in the topic migration. 

After your migration, post migration reports can be viewed by exporting two reports from Viva Engage called EngageTopicsMigration.csv and EngageTopicApplicationsMigration.csv (Learn more: Manage data in the Viva Engage admin center | Microsoft Learn). In the post migration reports, migrated topics will show the date of migration and what action was taken for the topic. Topics not migrated will include a short explanation about why the topic did not migrate. 

To restore topics that were not migrated an admin can: 

1. Review the post migration EngageTopicApplicationMigration.csv report 
2. Filter out imported and deleted topics 
3. Refer to the ThreadID for topics that were not imported
4. Rebuilt the thread url with the applicable thread ID and your network domain: https://www.yammer.com/<NetworkDomain>/#/Threads/show?<threadId>
5. Run the VivaTopicApplications.csv report to identify the topic name for the topic 
6. Create the topic in Viva Engage and attach the topic to the thread

Please note that metadata (i.e. topic creator, topic description) for topics that were not imported cannot be restored. 

[What you need to do to prepare:]

Before the migration a tenant admin can get a snapshot of which topics will be migrated by exporting topics in Viva Engage with PowerShell. No other actions are recommended. 

Currently all conversations (questions & discussions) posted in a community live event feed are automatically posted in the community feed.

With this feature update, conversations will remain restricted to the event feed only.

[When will this happen:]

General Availability (Worldwide): We will begin rolling out this feature in early October 2024 and expect to complete by early November 2024

[How this will affect your organization:]

With this update, we are making a change that will restrict conversations (questions & discussion posts) in a community live event to the event feed only. This means that posts for new events after this release will be visible only when you access the event feed within the community NOT within the community feed itself. When you delete the event, the community feed will remain unimpacted. It can be made available to the community feed if a user explicitly shares a conversation from the event feed to the community feed. 

It is important to note that this change will only be available for newly created events & will not apply to past events. Existing events that were created before this release in the community will still show messages in the community feed. When you delete those events, the messages will remain in the community feed.

[What do you need to do to prepare:]

This change will be available by default and doesn’t require any changes at your end.

The In development for Microsoft Intune page in our documentation has been updated.

How does this affect me?

The In development page provides a list of features in upcoming releases of Microsoft Intune to assist in your readiness and planning. The list has now been updated. You’ll start seeing these changes in the next month or in a subsequent release.

What do I need to prepare for this change?

You can inform your IT staff and helpdesk of the upcoming changes listed on this page. Plan to update your user guidance, if you feel any of these features would be important to your users.

Additional Information

Intune In development

Microsoft Viva Insights leader experiences will stop supporting the Business Leader role in January 2025.

Removing support for the Business Leader role within Viva Insights allows for clearer deployment of roles and admin management of roles. Manager, Analyst, and Delegate roles will remain in their current state.

Learn more about roles in Viva Insights.

[When this will happen:]

The Viva Insights Business Leader role removal will occur throughout January 2025.

[How this will affect your organization:]

Those with current Viva Insights Business Leader roles can still access leader experiences if someone with a Manager role assigns them as a delegate to enable access to their organizational insights. Learn more about how to delegate access to organizational insights and Copilot Dashboard.

Once the Viva Insights Business Leader role is removed, the user’s ability to see the entire company, referred to interchangeably as the “your company” or “myorg” view, will no longer be supported. Should a user need “whole company” view access, the top leader in your organization can assign that user delegate access to see the entire company.

[What you need to do to prepare:]

For those with Viva Insights Business Leader roles within the organization, ensure that someone with a Manager role assigns them as a delegate if they wish to maintain access.

Teams is making updates to its macOS keyboard shortcuts to follow macOS HIG policy.

 [When this will happen:]

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

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

General Availability (GCC, GCC High, DoD): We will begin rolling out mid-November 2024 and expect to complete by mid-December 2024.

[How this will affect your organization:]

All Mac users will have many of their Teams shortcuts updated to remove the “Options” and “Control” shortcuts from the list. This allows Mac users to use keyboard shortcuts without any collusions with existing macOS shortcuts. The new shortcut lay out will be available for users after an update to the latest version of Teams (the specific version number will be provided in an update to this post).

Details on the updated layout will be available prior to the rollout in the “Keyboard shortcuts” modal window accessible from the ellipsis (…) menu next to user’s avatar, or in Keyboard shortcuts for Microsoft Teams – Microsoft Support 

[What you need to do to prepare:]

The update of macOS keyboard shortcuts will be automatic when users receive an update to the specific build with this functionality. No admin action is required. You may want to notify your users about this change and update any relevant documentation as appropriate.

We will be retiring the Revoke-SPOUserSession PowerShell cmdlet for Microsoft SharePoint Online (SPO), as part of our ongoing efforts to enhance security and streamline scope and permissions for our users. Instead, please use the Revoke-MgUserSignInSession, where we will continue to invest resources.

[When this will happen:]

We will begin rolling this out in early November 2024 and expect to complete by mid-November 2024.

[How this will affect your organization:]

Our telemetry indicates that only a few organizations are active users of the Revoke-SPOUserSession cmdlet for their user management needs. If your organization is currently using this cmdlet, transition to utilizing ‘Revoke-MgUserSignInSession’. 

After the retirement, requests using the Revoke SPOUserSession cmdlet will be blocked with an error message similar to: 

“This cmdlet has been deprecated and replaced by Microsoft graph cmdlet ‘Revoke-MgUserSignInSession’ as described in: Revoke-MgUserSignInSession

[What you need to do to prepare:]

Please immediately begin transitioning from using the Revoke-SPOUserSession cmdlet. To avoid unexpected impact, also ensure none of your workflows are calling this cmdlet. Instead, please use the Revoke-MgUserSignInSession, <Revoke-MgUserSignInSession> where we will continue to invest resources.

Additional Information:

Revoke user access in Microsoft Entra ID