Microsoft Roadmap, messagecenter en blogs updates van 28-09-2024

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

Scheduling, setting up, and managing an event is not a simple task. Which is why we allow co-organizer to be added to the event so they can work alongside or on behalf of the organizer. So far co-organizers were able to set up event theming, manage registration, meeting options, view reports and more but were not able to edit event details like title, date/time, description, event group; nor publish or cancel event. Now they can! Co-organizer can edit event details, publish, and cancel the event like the organizer can. So once the co-organizer is added they will have full parity of experience as organizer and control/manage/edit event. 

This message is associated with Microsoft 365 Roadmap ID 168524

[When this will happen:]

Targeted release: We will begin rolling out early December 2024 (previously early October) and expect to complete by mid-December 2024 (previously mid-October).

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

[How this will affect your organization:]

When co-organizer opens the event scheduling page, they should have the ability to edit the details page, publish, and cancel the event. 

[What you need to do to prepare:]

Nothing required to prepare.

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

We are announcing the retirement of the ApplicationImpersonation Role Based Access Control (RBAC) role in Exchange Online. 

[When this will happen:]

We will begin the retirement in September 2024 (previously May) and in February 2025 will remove this role and its feature set from Exchange Online.

[How this will affect your organization:]

You are receiving this message because this RBAC role is commonly used with Exchange Web Services (EWS) to enable one-to-many mailbox access. We are removing this feature and will begin blocking the assignment of the ApplicationImpersonation (RBAC) role to accounts.

This will require all apps to have an App Registration, use Application permissions (not Delegated), and use a secure credential for access. Despite this change, if your app is granted the full_access_as_app Application permission, it will provide the same level of mailbox access as the ApplicationImpersonation RBAC role.

[What you need to do to prepare:]

Review your current configuration and make changes as appropriate to minimize disruption to your service.

For more information, please see:

• Retirement of RBAC Application Impersonation in Exchange Online.
• Impersonation and EWS in Exchange

Updated September 26, 2024: We have updated the list of countries below to include all EU countries. Thank you for your patience.

Microsoft SharePoint eSignature allows users to easily request eSignatures on a PDF document via SharePoint online. Signers can easily add their electronic signature. Signed documents are saved securely back to SharePoint.

As communicated in MC690925 (Updated) SharePoint eSignature electronic signature service (November 2023), SharePoint eSignature is currently available in the United States. With this rollout, eSignature is coming soon to the United Kingdom, Canada, and these European countries:

• Austria
• Belgium
• Bulgaria
• Croatia
• Cyprus
• Czech Republic
• Denmark
• Estonia
• Finland
•  France
•  Germany
•  Greece
•  Hungary
•  Ireland
•  Italy
•  Latvia
•  Lithuania
•  Luxembourg
•  Malta
• Netherlands
• Poland
• Portugal
• Romania
• Slovakia
• Slovenia
• Spain
• Sweden

[When this will happen:]

We will begin rolling out to the UK, Canada in August 2024, and the European countries in this message in early October 2024 (previously late September). 

[How this will affect your organization:]

Before this rollout: Users only had third-party (non-Microsoft) plugin options for eSignatures in SharePoint.

After the rollout: If your region is now supported, you will be able to configure and use SharePoint eSignature in SharePoint.

If you have SharePoint Premium configured before this rollout, you will need to turn on this feature.

If you sign up for SharePoint Premium after the rollout, the feature will be on by default, but you can turn it off.

[What you need to do to prepare:]

References

• Set up SharePoint eSignature | Microsoft Learn
• SharePoint eSignature – Microsoft Adoption (adoption-dev.azurewebsites.net)
• Overview of SharePoint eSignature | Microsoft Learn

Updated September 26, 2024: After further review we have decided not to proceed with this change at this time. We apologize for any inconvenience.

Coming soon to Microsoft Outlook mobile apps: Users will be able to sign in with a QR code (instead of entering a username and password).

This message is associated with Microsoft 365 Roadmap ID 406169.

[When this will happen:]

Public Preview: We will begin rolling out mid-August 2024 and expect to complete by mid-September 2024 – We will not be proceeding with this change at this time.

General Availability (Worldwide): We will begin rolling out mid-September 2024 and expect to complete by mid November2024 – We will not be proceeding with this change at this time.

[How this will affect your organization:]

In Outlook on the web, your users will be able to go to the Help tab at the top of the screen and select the new Outlook mobile option to get the QR code. Users can scan the QR code with their Outlook Mobile app to sign in without entering their username and password. Outlook will use their identity from Microsoft Entra to securely log them into the mobile app, and users will remain signed in to their mobile app unless manually they sign out.

[What you need to do to prepare:]

This feature will be enabled by default. Admins can disable QR sign in in Microsoft admin center by setting the mailbox policy AccountTransferEnabled to false. This action will prevent the QR code sign in, but users who have already used the QR code will not be signed out from their Outlook mobile app.

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

Learn more: Use a QR code to sign-in to the Outlook mobile apps – Microsoft 365 admin | Microsoft Learn

Updated September 26, 2024: We have updated the content. Thank you for your patience.

Starting October 16, 2024, we’re gradually enabling IPv6 for all customer Accepted Domains that use Exchange Online for inbound mail. Microsoft is modernizing Exchange Online so our customers can easily meet their local regulations as well as benefit from the enhanced security and performance offered by IPv6.

More information on IPv6 support for Microsoft 365 services can be found at: IPv6 support in Microsoft 365 services

[When this will happen:]

October 16, 2024 (previously October 1, 2024)

[How this will affect your organization:]

After we enable IPv6 for your Accepted Domains, when someone tries to send an email to one of your users and queries the MX record for the domain, they will receive both IPv4 and IPv6 addresses (AAAA records) in response to their MX record query.

[What you need to do to prepare:]

To take advantage of IPv6 connectivity, please make sure that you and your partner’s update network allow-lists to allow Exchange Online IPv6 endpoints in the same way it allow-lists IPv4.

The Exchange Online IPv6 endpoints can be found here: Microsoft 365 URLs and IP address ranges.

To opt a domain out of inbound IPv6 so traffic flowing to the domain remains IPv4-only, please use Disable-IPv6ForAcceptedDomain -Domain for each domain you want to opt out of IPv6 (Disable-IPv6ForAcceptedDomain (ExchangePowerShell) | Microsoft Learn).

IPv6 enablement may impact the source IP type used by Senders when connecting to Exchange Online, as the source and destination IP versions must match. For any IP Address-based Inbound connectors in Exchange Online that are referencing IPv4 addresses, you need to either:

• Keep the sending server as IPv4.
  • Coordinate with the Sender so the Sender keeps connecting to your domain(s) via IPv4 or Opt your domain(s) out of IPv6
• Change the IP based connector to certificate domain based connector.
  • This applies to both OnPremises type (From: Your organization’s email server, To: Office 365) and Partner Type connectors (From: Partner organization, To: Office 365).

Update: If you are using any Exchange Transport Rules or Data Loss Prevention policies which rely on the SenderIPRanges predicate, you need to opt out all your domains from IPv6.

You can manage IPv6 for your Exchange Online Accepted Domains using the commands Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain.

Currently, you can check the status of your Accepted Domains with the Get-IPv6StatusForAcceptedDomain command. While some customers have already enabled IPv6, most will see it as disabled until October 16th.

After October 16, once IPv6 is enabled for your tenant, if you haven’t explicitly set the IPv6 status for your Accepted Domains, the Get-IPv6StatusForAcceptedDomain command will reflect the new default behavior (enabled).

IMPORTANT: To ensure your preferred settings are applied, please use the Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain commands before October 16th, after which IPv6 will be enabled by default if you haven’t explicitly set it.

Updated September 26, 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 2024 (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 September 26, 2024: This feature is now live and is active in your tenant.

Coming soon for Microsoft Fabric: Two new settings in the Fabric Admin portal that are designed to enhance security and flexibility for applications interacting with Microsoft OneLake.

[When this will happen:]

Public Preview: We will begin rolling out late September 2024 and expect to complete by late September 2024. You can start saving your settings in late August 2024.

When the General Availability release timeline is known, we will update you.

[How this will affect your organization:]

Before this rollout: Users could not generate SAS tokens in OneLake.

After this rollout: Admins will have support for short-lived user-delegated OneLake shared access signature (SAS) tokens in public preview. This functionality allows applications to request a user delegation key backed by a Microsoft Entra ID, which can then be used to build a OneLake SAS token. This token can be handed off to provide delegated access to another tool, node, or user, ensuring secure and controlled access. OneLake SAS tokens are constructed and used similarly to Azure Storage SAS tokens, with a few key differences:

• OneLake user delegation keys and SAS tokens cannot exceed a lifetime of one hour.
• OneLake SAS tokens are always user delegated and must be backed by an Entra ID.
• OneLake SAS can only grant access to data items in Fabric.

The usage of OneLake SAS in a Fabric tenant is controlled by two tenant switches:

1. A switch managed by tenant admins that controls the generation of OneLake SAS tokens
2. A switch automatically delegated to workspace admins that controls the acceptance of OneLake SAS tokens

Both switches must be turned on to allow the use of OneLake SAS in a workspace.

Scenarios supported by SAS

Delegated access with SAS tokens allows applications without native support for Microsoft Entra to gain temporary access to specific folders or files in OneLake. SAS tokens are commonly used for data integration workloads by granting external engines temporary permissions to write data to a staging location. Many ISVs also use SAS tokens to grant their users temporary scoped-down access to their data.

New tenant settings

1. Use Short-lived user-delegated SAS tokens (Preview):

• Default Status: ON
• This setting allows the creation of short-lived user-delegated SAS tokens by turning on the user delegation key API for the entire tenant.

2. Authenticate with OneLake user-delegated SAS tokens (Preview):

• Default Status: OFF
• This setting enables authentication using OneLake user-delegated SAS tokens. This setting is automatically delegated to workspace admins, allowing them to decide whether their workspace will accept OneLake SAS as a valid authentication method.

[What you need to do to prepare:]

1. Review and decide on settings:

• Use short-lived user-delegated SAS tokens: As this setting is turned ON by default, please review its implications and decide if it should remain enabled for your organization.
• Authenticate with OneLake user-delegated SAS tokens: This setting is OFF by default, and workspace admins will be able to enable this feature. Evaluate its potential benefits and determine if you would like to enable it automatically for all workspaces.

2. Action for tenant admins:

• In late September 2024, OneLake SAS will be available in public preview. If no actions are taken on the tenant setting, workspace admins will be able to turn ON OneLake SAS authentication for their workspace. Note that Authenticate with OneLake user-delegated SAS tokens is automatically delegated to workspace admins. If you prefer not to have these features available for your organization, please turn OFF the Use short-lived user-delegated SAS tokens setting in Fabric before late September 2024. This will disable OneLake SAS generation for your tenant, ensuring OneLake SAS cannot be used, regardless of the workspace admins setting.
• Workspace admins will be able to enable authentication with SAS tokens for their workspaces if no action is taken by tenant admins.
• We encourage you to assess these new settings and make any necessary changes to align with your organization’s security and access control policies.

If you have any questions or need further assistance, please do not hesitate to contact our support team.

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

Explore Microsoft Fabric documentation. Before rollout, we will update this post with links to new documentation.

Coming soon for Microsoft Teams:

• An updated view of all teams on one Your teams page.
• An updated Manage Team > Channels page, helping team owners and team members to filter, search and manage channels in the team from one page. Team members will be able to navigate to the list of channels from the Your teams page with a single click.

This message applies to Teams on Windows desktop, Mac desktop, and on the web.

This message is associated with Microsoft 365 Roadmap ID 411779.

[When this will happen:]

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

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

General Availability (GCC, GCCH, DoD): We will begin rolling out early December 2024 and expect to complete by early December 2024.

[How this will affect your organization:]

Before this rollout, Team owners and members can hover on the team name on the left side of Teams, select the three dots, and go to Manage team to individually manage the team and its channels. Team owners and members can see all the teams they belong to from the Your teams page. Selecting a team on the Manage teams page takes Team owners and members to the team’s General channel.

The Manage team page with the Channels tab open: Access this page from the three dots next to the team name in the left panel in Teams:

The Your teams page shows all teams you belong to. Access this page from the three dots in the upper right corner of the left panel in Teams:

After this rollout:

• Team owners and members will be able to view their teams from the Your teams page, and access channels in each team. To navigate to the Your teams page, select Your teams and channels from the three dots in the top right corner of the left panel.

• Team owners and members can select a team name to review the channels in the team and choose channels of interest to show in Teams:

• Team owners and members can search and sort on the Your Teams page or hide all channels. When all channels of a team are hidden, the team will not show in the Teams and channels list on the left side of Teams.
• Team owners and members can also view the channels in the team from the Manage Team > Channels page, and show channels of interest by filtering, sorting, and searching for channels in the team from one page.

These features 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 notify your Team owners and members about this change and update any relevant documentation.

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

We are rolling out enhanced app discovery for Microsoft Teams. This rollout allows users to easily discover and use apps that they have previously used in group chats, channels, and meetings, enabling users to consent to use the app everywhere in Teams with one click. This message applies to Teams on Windows and Mac desktops and to Teams on the web.

This message is associated with Microsoft 365 Roadmap ID 397089.

[When this will happen:]

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

[How this will affect your organization:]

In Teams, when one user installs an app to a group chat, channel, or meeting, others in the group can use it without installing the app. Before this rollout, it is not easy for others in the group to rediscover these apps for use everywhere in Teams.

After this rollout, users can more easily find and use apps they previously used in Teams, because these apps will appear at the top of the list of apps in Teams menus:

After this rollout, users will be able to find apps they used in a group experience, but did not install themselves. If users click such an app, a consent screen appears. If the user agrees, the app will be installed and be available everywhere in Teams, including group chats, channels, and meetings:

[What you need to do to prepare:]

Admins should ensure that their tenant’s app permission policies are configured to allow users to add and use apps in group experiences. No additional admin configuration is needed for this feature

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

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

As a part of Team’s ongoing effort to enable our customers to create, manage, and run large scale events, end users can now embed Teams town hall in sites they manage. This capability allows town hall attendees to watch the event instance within a particular website.

Embed for town hall introduces embeddable support for town hall engagement features on release. Attendees will have the same engagement feature access within the embed player as they do in client such as Q&A, Captions, Reactions and more.

To implement embed for town hall, organizers can access their town hall events unique embed code from the town hall scheduling template upon publish. Organizers can then take that code and inject it to their SharePoint or Microsoft 365 site as desired. On event start, attendees will be able to view and engage with the embed stream on the published site.

This message is associated with Microsoft 365 Roadmap ID 401120

[When this will happen:]

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

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

[How this will affect your organization:]

Users will be able to copy embed code directly from town hall scheduling form on event publish. After the embeddable code is placed in the website, the town hall player will be accessible to attendees who have access to the URL.

Note: Attendee access to the embedded video player is driven by the town hall event access.

[What you need to do to prepare:]

Organizers with SharePoint or Microsoft 365 site who want to utilize embed support for town hall can begin implementing the embeddable code upon release.

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

We are excited to announce an important update designed to enhance the privacy and security of your organization. Before this rollout, admins had the capability to download voice and face data for their users who have opted in to enroll their voice and/or face on the Recognition tab in Microsoft Teams. With this rollout, to better protect user data, we are shifting this capability to users. This change will ensure that users have more control over their own voice and face data, aligning with our commitment to privacy and security. This change reduces the risk of unauthorized access or sharing, as users will handle their own data export requests and admins will not have access to this data. This message applies to Teams for Windows desktop and Teams for Mac desktop.

This message is associated with Microsoft 365 Roadmap ID 413709.

[When this will happen:]

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

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

[How this will affect your organization:]

With this rollout, we will remove the download button from the Teams admin center (TAC) > User > Manage user > select any user > Account:

Users can go to Teams > Settings > Recognition and select the Export button to access their data and download it to their Download folder:

The new Export feature is 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 notify your admins and users about this change and update any relevant documentation.

Learn more: Overview of voice and face enrollment – Microsoft Teams | Microsoft Learn (will be updated before rollout)

If your organization does not use Teams Android Devices you can safely disregard this message.

Planned Maintenance: Automatic updates for all certified and supported Teams Android Devices to Company Portal version 5.0.6152.0.

Upcoming Microsoft Infrastructure changes will impact Teams Android Devices running older and out of support firmware and applications. Teams Android Devices (Teams Rooms on Android, Teams Phone, Teams Display, and Teams Panel devices) running Company Portal applications older than 5.0.6061.0 may sign out or be unstable starting July 1, 2025. We recommend ensuring your devices are on 5.0.6152.0 as soon as possible as that is the latest supported version to ensure stability.

Please review your existing Teams Android devices and ensure they are on the latest supported and available firmware and application versions. In Teams Admin Center > Teams Devices you can export your current device inventory using the Excel icon for each device type, this export includes a column for Company Portal version. If you find devices not on 5.0.6152.0, please update your Teams Android devices to the latest available firmware in Teams Admin Center, you can review manual and automatic update options as explained in this link.

Since this Company Portal update is critical to ensure your devices stability, Microsoft will begin accelerated automatic firmware and company portal app only updates to ensure latest release for devices not currently running the latest release.

[When will these updates happen:]

These auto-updates will start rolling out mid-October 2024 and will continue until late December 2024.

[How this will affect your organization:]

This upgrade is required for all certified and supported Teams Android devices including Teams Rooms for Android, Teams phones, Teams panels and Teams displays.

The accelerated auto-updates include firmware, Teams app, and Company Portal app updates, as required to bring the device to Company Portal version 5.0.6152.0. This process may also include multiple updates if the devices are on older versions.

Because these updates will be rolled out at an accelerated pace, the configured update phase timelines (Validation, General, and Final) will not be adhered to. These updates will be scheduled outside of normal business hours at the local time of the device, to help minimize any impact to your organization. The configured maintenance window for the devices will not be adhered to as well.

How do I know what firmware update contains Company Portal 5.0.6152.0?

Please review these links which contain the details on the applications bundled into each firmware release:

• Teams phones: Devices for Teams – Microsoft Teams | Microsoft Learn
• Teams Rooms on Android: Teams Rooms on Android app and firmware versions – Microsoft Teams | Microsoft Learn
• Teams displays: Devices for Teams – Microsoft Teams | Microsoft Learn
• Teams panels: Devices for Teams – Microsoft Teams | Microsoft Learn

What if I don’t see a firmware with the Company Portal 5.0.6152.0 app included?

Microsoft has released the Company Portal app as a direct update in Teams Admin Center for devices which do not have a recent firmware bundle. This update can be deployed directly in Teams Admin Center and will show as an available update for your devices.

I have devices in my organization that are no longer certified and are end of support with Microsoft, will I receive an update for my devices?

Devices that are end of support and end of life will not receive new application updates due to legacy environment considerations and will be impacted by these infrastructure changes. These Teams devices are listed here: Devices for Teams – Microsoft Teams | Microsoft Learn. Please work with your Teams devices OEM to source new certified and supported devices prior to this change occurring. An additional message center post will be released with more details on the impact to these legacy devices.

[What you need to do to prepare:]

The firmware and Company Portal app versions can be updated manually for the impacted devices if you wish to control these updates, please complete your manual updates as soon as possible

For auto-updates, administrators don’t need to do anything to prepare. The changes will take affect automatically.

In case of any issues, feel free to reach out to Microsoft Support. You can also refer to Update Microsoft Teams devices remotely – Microsoft Teams | Microsoft Learn.

As we continue to invest in a unified and modern Microsoft OneNote experience, we want to remind you that the OneNote for Windows 10 app will reach end of support on October 14, 2025. After this date, the app will no longer receive support, and the app will become read only.

To ensure the best experience moving forward, we strongly recommend switching your users to the Microsoft OneNote for Windows app as soon as possible. Our team is focusing on enhancing this app, providing a sleek and modern interface and improving security, and releasing new features like Loop components, voice dictation and transcription, ink improvements, a new meeting details experience, integration with the new Microsoft Outlook, and more to align with the evolving needs of our users.

[How this will affect your organization:]

Although OneNote for Windows 10 is supported until October 14, 2025, it is no longer receiving new feature updates, and it does not benefit from improvements to data syncing.

Starting in January 2025, users will start to see notifications in OneNote for Windows 10 about the end of support. These notifications will provide additional information and direct users to resources for a smooth transition.

[What you need to do to prepare:]

1. Migration guidance:

We have developed a detailed Deployment guide for OneNote that includes best practices of migrating and a sample migration script. This sample script is designed to simplify the migration process for IT admins and to ensure that your users’ unsynchronized data is backed up during migration. We believe this migration guidance will significantly help in achieving a successful migration process.

2. OneNote migration support in October 2024:

To ensure a smooth transition, we are offering additional support from the OneNote team to help with the migration process for tenants who want to migrate early. The team is only available in the month of October 2024. After that, you will need to rely on the deployment guidance. To engage the OneNote team in October 2024, please provide feedback as usual on this post and include your email address.

3. App download restrictions for new users:

Starting November 1, 2024, new users will no longer be able to download OneNote for Windows 10 from the Microsoft Store. Given the app is approaching end of support and we are recommending using OneNote for Windows instead, we’re restricting new users from being able to install OneNote for Windows 10 moving forward. If you currently have the application installed, you will still be able to use it and receive updates until the end of support.

We are committed to supporting you through this transition and ensuring that your migration to OneNote for Windows is as seamless as possible.

Learn more

• Download OneNote for Windows from the Microsoft Store
• What is happening to OneNote for Windows 10 – Microsoft Support
• Moving to OneNote on Windows – Microsoft Support
• Deployment guide for OneNote – Microsoft 365 Apps | Microsoft Learn

Coming soon to Microsoft Viva Engage: This feature will allow users to subscribe to receive notifications after following Viva Engage topics. Users will receive an Engage notification on the bell icon on the left side of Viva Engage when a new post is tagged with a topic they are subscribed to, or the topic is added to an existing post.

This message is associated with Microsoft 365 Roadmap ID 395940.

[When this will happen:]

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

[How this will affect your organization:]

Before this rollout, users are not able to subscribe to a topic after following a topic in Engage. Instead, they can only follow a topic.

After this rollout, users will be able to subscribe to a topic after following the topic on the Viva Engage topic page. After users subscribe, they will receive notifications for those topics they are subscribed to.

This feature will be on by default.

User adds tags to a post and Viva prompts the user to subscribe to the topics:

Viva confirms that notifications are enabled:

The bell icon on the left side of the screen with an active notification:

[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 users about this change and update any relevant documentation.

Learn more: Follow or subscribe to topics – Microsoft Support

Your Microsoft Intune account has been updated to the latest service build.

How does this affect me?

You will see the service release number updated in the Tenant Status blade of the Intune console soon. We’ve introduced some changes that we’re excited for you to try out.

What do I need to do to prepare for this change?

Click additional information below to learn more about what’s new in this service release. We’ll continue to update the What’s new page with any features that are released between now and the next monthly service update. Learn more by reviewing features highlighted in the latest Intune What’s new 2409(September) Blog and how the Intune service updates each month is described in the Microsoft Intune Service Updates Blog. 

Additional Information:

• Intune What’s new
• Intune What’s new 2409(September) Blog
• Staying up to date on Intune new features, service changes, and service health