Microsoft Roadmap, messagecenter en blogs updates van 06-12-2024

Updated December 4, 2024: We recently discovered a significant issue that has resulted in the temporary disabling of this feature until it is resolved. We apologize for any inconvenience this may cause.

There is a new experience for selecting which users should have which permissions when a sensitivity label configured for user-defined permissions is applied to a file in Microsoft 365 apps or when a user applies protection using standalone Information Rights Management.

This message is associated with Microsoft 365 Roadmap ID 189826

[When this will happen:]

Preview (Worldwide, GCC): We will begin rolling out mid-July 2024 and expect to complete by late July 2024.

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

[How this will affect your organization:]

Users will see a modernized dialog when configuring user-defined permissions, whether these are applied using a sensitivity label configured for user-defined permissions or with standalone Information Rights Management. There are new names for some usage rights groupings for pre-set permissions levels compared to those in Microsoft Azure Information Protection (AIP):

• Reviewer is now called Restricted Editor.
• Co-Author is now called Editor.
• Co-Owner is now called Owner.

The rights contained in each grouping are unchanged.

See Configure usage rights for Azure Information Protection for further information on usage rights.

This new feature is available by default.

[What you need to do to prepare:]

If your organization has training materials or internal documentation regarding the use of pre-set permissions levels, you may need to make updates based on the new names for these permissions levels.

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

Coming soon to Microsoft Outlook: The Reset People Suggestion feature will allow users to reset, export, and/or opt out of people suggestions in search through Outlook on the web and the new Outlook for Windows settings. If a user resets their People Suggestions in Outlook on the web or Outlook for Windows, all versions of Outlook will reflect that change (even Outlook Mobile). This message applies to Outlook on the web and the new Outlook for Windows.

This message is associated with Microsoft 365 Roadmap ID 98137.

[When this will happen:]

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

[How this will affect your organization:]

Before the rollout: Users were not able to reset or export their suggested contacts from Outlook on the Web and the new Outlook for Windows.

After the rollout

• The default on/off value for the Reset People Suggestion feature in Outlook will inherit each user’s existing configuration from their Microsoft 365 My Account privacy settings at https://myaccount.microsoft.com/settingsandprivacy/privacy. No further action from users is needed to prepare.
• Users will be able to reset, export, and/or opt out of People Suggestions from Outlook on the Web and the new Outlook for Windows Privacy and data settings. This setting will stay in sync with the Privacy configuration in My Account.

Initial People Suggestion settings will be inherited from each user’s Microsoft 365 My Account privacy settings at Settings & Privacy > Manage Contact Search:

To modify the behavior of People Suggestions: Users can go to Microsoft Outlook > Settings > General > Privacy and data > Suggested people:

[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 as appropriate.

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

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

Introducing four new Microsoft Purview Data Loss Prevention (DLP) Microsoft Exchange (EXO) predicates:

• Message is not labeled: Detects if message body has no label.
• Attachment is not labeled: Detects if there is any attachment without a label.
• Message contains: Detects if the message body contains specified sensitive information types (SITs) or labels. Note that there is no trainable classifiers or non-advanced rule support yet.
• Attachment contains: Detects if an attachment contains specified SITs or labels. Note that there is no trainable classifiers or non-advanced rule support yet.

This message is associated with Microsoft 365 Roadmap ID 377000.

[When this will happen:]

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

[How this will affect your organization:]

You can now create new DLP policies or edit existing policies to include predicates to target specific email components like email body or attachments only.

This feature is available by default.

[What you need to do to prepare:]

For information about how to prepare, visit Create and deploy a data loss prevention policy | Microsoft Learn.

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

Coming soon for Microsoft Outlook: If users have enabled work hours and location in Settings, their colleagues will be able to more quickly see who plans to be in the office with a new calendar feature.

This message applies to new Outlook for Windows and Outlook on the web.

This message is associated with Microsoft 365 Roadmap ID 410986.

[When this will happen:]

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

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

[How this will affect your organization:]

Before this rollout: Users select the Location icon for each day in the calendar to see who plans to be in the office:

After this rollout: In addition to the Location icon, users will have a new “always on” peek in the top right of the calendar that shows who plans to be in the office for the current day:

This feature is on by default and available to all users of new Outlook for Windows and Outlook on the web.

[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.

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

When you open a document, Copilot for Microsoft 365 for Microsoft Word will generate a summary in the window at the top of the Word document. You can hide the summary or open the Copilot chat pane to ask specific questions about the document.

This message is associated with Microsoft 365 Roadmap ID 397096.

[When this will happen:]

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

[How this will affect your organization:]

Users will see a new UI between the canvas and the ribbon in Word supporting a summary of the document created by Copilot for Microsoft 365. This UI can be collapsed if the user does not want to see the summary.

Fully expanded:

Semi-expanded:

This new feature 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 as appropriate.

End User documentation:

• Create a summary of your document with Copilot – Microsoft Support

Updated December 4, 2024: We have updated the content with an End User documentation link. Thank you for your patience.

Note: A Microsoft Copilot for Microsoft 365 license is required to use this feature.

Coming soon to Microsoft Word: When you open a document, Microsoft Copilot will generate a summary in the Word window. You can hide the summary or open the Copilot chat pane to ask specific questions about the document.

This message applies to Word for Windows and Mac desktops.

This message is associated with Microsoft 365 Roadmap ID 399921.

[When this will happen:]

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

[How this will affect your organization:]

Before this release: Copilot in Word does not provide a summary when a file is opened.

After this rollout, the Copilot in Word summary will appear at the top of the document. The user can collapse the summary if desired.

Copilot in Word summary with the View more button:

Copilot in Word summary fully expanded:

This feature is on by default and available to all Word users with a Copilot for Microsoft 365 license.

[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.

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

End User Documentation:

•  Create a summary of your document with Copilot – Microsoft Support

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

The Microsoft Copilot Dashboard, powered by Viva Insights, helps organizations maximize the value of Microsoft Copilot for Microsoft 365 by providing actionable insights to help organizations get ready to deploy AI, drive adoption based on how AI is transforming workplace behavior, and measure the impact of Copilot.

Viva Pulse integrates into the Microsoft Copilot Dashboard to provide a way for organizations to capture sentiment data that helps leaders measure the effectiveness and usage of Copilot. With a research-backed template, Viva Pulse enables leaders and IT admins to send their own surveys to capture feedback quickly from their teams and requires minimal admin setup to get started. Leaders and IT admins with access to the Copilot Dashboard can launch Pulse surveys to gain insights into how Copilot impacts their workforce and combine sentiment data with usage metrics from workplace pattern data to enable IT and business leaders to plan their AI readiness, drive adoption, and measure their ROI.

For Pulse surveys results to be automatically integrated into the Copilot Dashboard, admins must assign a license from the Microsoft Viva Suite or for Viva Workplace Analytics and Employee Feedback.

This message applies to Viva Pulse on the web and in the Microsoft Teams app for Windows desktop.

This message is associated with Microsoft 365 Roadmap ID 380477.

[When this will happen:]

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

[How this will affect your organization:]

Before this rollout, users enabled to view the Copilot Dashboard do not see survey results from the Copilot impact Pulse and are not able to launch a Copilot impact Pulse from the Copilot Dashboard.

After this rollout, leaders and IT admins have two options for capturing sentiment about Copilot from their teams:

• Launch a Copilot impact Pulse survey from the Copilot Dashboard
• Launch a Copilot impact Pulse survey from Viva Pulse

Viva Pulse survey results for the Copilot impact template will be automatically shared to the Copilot Dashboard. The individual Copilot impact sentiment survey results will not be mapped to behavioral metrics in the Advanced Analytics app in Viva Insights.

Launch your Copilot impact Pulse from the Microsoft Copilot Dashboard and view your sentiment data with usage metrics from workplace pattern data to drive AI readiness, drive adoption, and measure ROI:

Build your Copilot impact Pulse in Viva Pulse to capture sentiment data that helps leaders measure the effectiveness and usage of Copilot:

[What you need to do to prepare:]

If you have not granted users access to the Copilot Dashboard, they will not be able to launch a Pulse survey from the Copilot Dashboard. Learn more about providing access to the Copilot Dashboard: Manage settings for the Microsoft Copilot Dashboard | Microsoft Learn

Ensure your tenant has assigned the required licenses from the Microsoft Viva Suite or Viva Workplace Analytics and Employee Feedback.

Review and assess the impact on your organization. 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 about the Microsoft Copilot Dashboard:

• Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn
• Assess how your organization feels about Microsoft Copilot – Microsoft Community Hub

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

On January 8, 2025, we are introducing an enhancement in Autopatch groups device management to improve the synchronization reliability between devices in Microsoft Entra groups assigned to Autopatch groups and the devices targeted via Autopatch groups. This update will ensure that any changes made by admins in Entra groups assigned to Autopatch groups are accurately reflected in Windows Autopatch-registered devices.

[When this will happen:]

General Availability (Worldwide): We will roll out on January 8, 2025. This is the 30-day notice that this change is coming to your tenant. 

[How this will affect your organization:]

With this feature update, if a device that was previously added to an Autopatch group is using an Entra group (via Assigned groups or Dynamic distribution method) is removed from the Entra group, then the device will be removed and de-registered from the Autopatch service. Consequently, the removed device will no longer have any service-created policies applied to it and will not appear in the Autopatch devices reports.

Similarly, new devices added to the Entra groups assigned to an Autopatch group will be added to the Autopatch devices report and will have policies applied to them as required. Admins can review the added devices in the Windows Autopatch devices report.

Note: Please expect 3 hours latency for the changes to be reflected in the service and reports.

This feature update will be available by default.

[What you need to do to prepare:]

If you have removed any devices from an Autopatch group, they will be fully de-registered from the service. If you wish to continue using Autopatch for these devices, please ensure they are correctly added to Autopatch groups via the Entra groups. Please note that once synchronization is enabled with this improvement, the changes cannot be reverted. This will not affect your ability to add devices to the service; you can always add more devices to an Autopatch group as needed. If you have any questions or concerns or need assistance, file a service request by visiting the Microsoft Intune admin center.  

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

Microsoft Purview Information Protection will soon support label policy settings to apply inheritance to files shared in Microsoft Teams chat or meetings. This message applies to tenants who have a license for Microsoft 365 E5 and Teams Premium. This message applies to Teams on the web, Windows desktop, Mac desktop, and iOS/Android.

This message is associated with Microsoft 365 Roadmap ID 467247.

[When this will happen:]

Public Preview: We will begin rolling out early January 2025 (previously mid-December) and expect to complete by late January 2025 (previously early January).

General Availability (Worldwide): We will begin rolling out mid-February 2025 (previously late January) 2025 and expect to complete by mid-March 2025 (previously late February).

[How this will affect your organization:]

Admins can go to Information Protection in the Purview portal and configure label inheritance settings for label policies for Teams meetings. Admins can configure label policies to automatically apply label inheritance or recommend label updates to users.

• If an admin enables automatic labels, when a file with a higher priority label than the meeting is shared in meeting chat or shared by the meeting presenter before the meeting, all participants will receive a new meeting invite that inherits the higher priority label from the file, and the new meeting will also inherit the higher priority label.
• If an admin enables label recommendation, the organizer will receive a notification that recommends the organizer upgrade the meeting’s sensitivity to match with the shared file.

Prerequisites to trigger label inheritance:

• The sensitivity label on the shared file must have Meeting scope
• The sensitivity label on the shared file must have been published by the meeting organizer
• The sensitivity label on the shared file must have a higher priority than the current meeting sensitivity label
• The meeting organizer must meet the license requirement
• There is a label inheritance (automatic or recommendation) policy enabled by the meeting organizer

Admin controls in Purview Information Protection:

Automatic inheritance:

Organizer receives label recommendation (in-meeting):

Organizer receives label recommendation (activity feed):

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

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

Your Microsoft 365 subscription is being updated with a new service in your Outlook: Org Explorer. This organization chart helps your visualize your company’s internal structure and discover connections, roles, and responsibilities among you and other people across teams. 

This message is associated with Microsoft 365 Roadmap ID 421191.

[When this will happen:]

General Availability (Worldwide) for new Outlook for Windows, Outlook for Web, and Outlook for Mac: We will begin rolling out mid-January 2025 and expect to complete by mid-April 2025 (previously late February).

General Availability (Worldwide) for classic Outlook: We will begin rolling out mid-January 2025 and expect to complete by early April 2025.

Note: The access to Org Explorer will depend on which Outlook service platform the user is using. Therefore, we recommend you switch to the new Outlook for Windows or Outlook for web to have early access to this new feature. 

[How this will affect your organization]

Once the new service is available for your organization, you can access the Org Explorer app via Outlook as below:

Is a Viva license still required to access Org Explorer?

After the rollout in January 2025, Org Explorer will not require a Viva premium license. 

We will share more information about how to disable the service.

[What you need to do to prepare]

There is no action required now. The documentation of Introducing Org Explorer is going to be updated soon for additional information regarding Org Explorer .”

The link to the webpage is the same as before: Introducing Org Explorer | Microsoft Learn

Updated December 4, 2024: We have updated the content. Thank you for your patience.

In MC855685 (August ‘24), Microsoft Forms and Excel provided a new data sync solution which can sync a form’s response data to an Excel workbook, replacing the old data sync solution which will be deprecated by Jan 13th 2025.

Note: The new data sync can currently only be triggered in Excel for the web. If users want to receive new Forms response data in the Excel desktop app, open the target file in Excel for the web to sync new responses, and then wait for the file to update in the desktop app. Direct syncing support for the Windows and Mac versions of Excel is in progress and will be released soon.

Impact

There are 0 users and 1 groups with a total of 1 forms using the old data sync solution in your tenant in the last 3 months (Aug – Oct 2024).

Action

To continue syncing new responses from their form to their Excel workbook, users will need to update the syncing solution for each affected form. To make sure users have enough time to make the update, we recommend that you reach out to those users and encourage them take the actions described below. The notification will be sent to form owners directly to guide users to take action. if there is high impact in your tenant and you have concern, please file a support ticket to Microsoft Forms for the impacted user ID list.

What do users need to do?

• Pay attention to notifications in Forms, Excel for the web and Email. For each form which is using the old syncing solution, they must migrate the form according to the instructions provided. More details can be found here: Update to the new solution for syncing forms responses to Excel – Microsoft Community Hub.
  • Notification in Microsoft Forms

  

  • Notification in Excel for the web

  

  • Notification through email to Form owners: Email subject – Important: Update sync in Forms before January 13, 2025

  

• If users are using the Forms Connector in Power Automate to get response data, they will not be impacted by this change, and no action is needed. 
• If users are using the old data sync solution in a workflow that relies on the Excel workbook being updated automatically without any user action, they will be impacted by the change as the Excel file will only get updated when it’s opened in a supported Excel client. These users will have to manually update their workflow. Our suggested solution is to use Power Automate: Setting Up an Automated Workflow Between Microsoft Forms and Excel Through Power Automate – Microsoft Support
• User who are using Excel clients which don’t support the new sync solution (e.g. a perpetual client) can also consider setting up the Power Automate workflow to get updated data in their Excel workbook. 

As mentioned in MC726113/MC674247/MC902778, Google has deprecated Android device administrator management, continues to remove management capabilities, and no longer provides fixes or improvements. Due to these changes, Intune will be ending support for Android device administrator management on devices with access to Google Mobile Services (GMS) beginning December 31, 2024. Until that time, we will support device administrator management on devices running Android 14 and earlier. For more details, read the blog: https://aka.ms/Intune-Android-DA-blog.

[How this will affect your organization:]

After Intune ends support for Android device administrator, devices with access to GMS will be impacted in the following ways:

1. Intune will not make changes or updates to Android device administrator management, such as bug fixes, security fixes, or fixes to address changes in new Android versions.
2. Intune technical support will no longer support these devices.

[What you need to do to prepare:]

Stop enrolling devices into Android device administrator and migrate impacted devices to other management methods. You can check your Intune reporting to see which devices or users may be affected. Go to Devices > All devices and filter the OS column to Android (device administrator) to see the list of devices.

Read the blog, Microsoft Intune ending support for Android device administrator on devices with GMS in December 2024, for our recommended alternative Android device management methods and information about the impact to devices without access to GMS.

Microsoft Viva Pulse capabilities will now be included with your Microsoft 365 Copilot subscription. This message applies to Pulse on Windows and Mac desktop, on the web, and on iOS/Android.

This message is associated with Microsoft 365 Roadmap ID 407706.

[When this will happen:]

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

[How this will affect your organization:]

Before this rollout: Only users assigned with a Viva Pulse premium license can create and send Pulse requests to users in their tenant. Pulse authors can use the available out of the box content and/or templates that have been made available by their tenant’s Pulse administrators.

After this rollout

Viva Pulse experience included in your Microsoft 365 subscription:

Users with a Pulse license or a Microsoft 365 Copilot license can create and send Pulse requests to users in the tenant. With Viva Pulse experience included with your Microsoft 365 Copilot subscription, leaders can send brief surveys to gather real-time feedback about Copilot implementation from teams. Pulse helps identify challenges and concerns quickly, enabling prompt and localized responses to improve the Copilot journey.

• Create and send a Pulse request: Users need a Microsoft 365 Copilot license or a Viva Pulse premium license. They also need a Microsoft Forms license.
• Respond to a Pulse request: No license needed. Anyone can respond.

Users’ view of the Pulse home page when they only have Microsoft 365 Copilot license:

This change will be available by default.

[What you need to do to prepare:]

This rollout will happen automatically, and the features described here are enabled by default 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.

• Tenant admins can review and assign licenses available to your users through Microsoft Entra Admin center.
• Tenant admins can review the new templates and questions through the Viva Pulse admin Content management feature and modify or restrict access to the templates and questions as needed.

Learn more

• Licensing requirements | Microsoft Learn
• Set up the in-app Viva Pulse experience | Microsoft Learn
• Manage available surveys and questions | Microsoft Learn
• Create a Pulse to get feedback from your team – Microsoft Support

Coming soon: Intelligent recap for Microsoft Teams town halls and webinars, just like the intelligent recap for meetings. Event organizers, co-organizers, and presenters will be able to explore the meeting recording by speakers and topics and access AI-generated meeting notes, AI-generated tasks, and name mentions. A Teams Premium license or a Microsoft 365 Copilot license is required to use this feature. This message applies to Teams for Windows and Mac desktops.

This message is associated with Microsoft 365 Roadmap ID 371588.

[When this will happen:]

Targeted Release: We will begin rolling out early January 2025 and expect to complete by mid-January 2025.

General Availability (Worldwide, GCC): We will begin rolling out mid-January 2025 and expect to complete by early February 2025.

General Availability (GCC High): We will begin rolling out mid-March 2025 and expect to complete by mid-March 2025.

[How this will affect your organization:]

After this rollout, users in your tenant can turn on the recording or transcription to get intelligent recap for town hall and webinar event instances. After an event ends, the organizer, co-organizers, and presenters can go to the meeting thumbnail in the event chat and select the View recap button to access Recap page. Alternatively, they can go to the Recap tab in the event’s Chat tab or calendar invite.

Note: Additional improvements will be available in future releases, including recap notifications.

This feature will be 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 or after the rollout. You may want to notify your users about this change and update any relevant documentation.

Learn more: Meeting recap in Microsoft Teams – Microsoft Support (will be updated before rollout)

Coming soon for Microsoft Purview | Communication Compliance: Communication compliance investigators will be able to schedule recurring or on-demand exports of message detail reports, which include item details such as metadata, review status, and remediation actions. Reports can be scheduled daily, weekly, or monthly. Users will receive email notifications when reports are ready for download. Before this rollout, investigators could only export the message detail reports on demand.

This message is associated with Microsoft 365 Roadmap ID 377680.

[When this will happen:]

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

General Availability (Worldwide): We will begin rolling out early January 2025 and expect to complete by late January 2025.

[How this will affect your organization:]

Communication compliance investigators can find the new feature in the Purview compliance portal at Communication Compliance > Policies > Select a policy > Export report:

This change will be available by default.

[What you need to do to prepare:]

Microsoft Purview Communication Compliance provides the tools to help organizations detect business conduct and regulatory compliance violations (for example, SEC or FINRA) such as sensitive or confidential information, harassing or threatening language, and sharing of adult content. Built with privacy by design, usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to help ensure user-level privacy.

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.

You can access the Communication Compliance solution in the Microsoft Purview compliance portal.

Learn more

• Learn about Communication Compliance
• Create and manage communication compliance policies | Microsoft Learn
• Use communication compliance reports and audits | Microsoft Learn

As part of Microsoft 365 Copilot for Security in Data Loss Prevention (DLP), Policy Insights helps admins understand DLP policies and its constructs. This enhancement enables DLP admins to gain insights on coverage of policies on pivots like location, classifiers, and notifications.

DLP admins can get these insights on all the policies or on a few selected policies. They will be able to use prompts to gain a deeper level view of how a policy is configured for their digital landscape. This helps them align their data posture on a regular basis and make corrections to policy posture as needed. 

This message is associated with Microsoft 365 Roadmap ID 466740.

[When this will happen:]

Public Preview: We will began rolling out mid-November 2024 and expect to complete by early December 2024.

General Availability (Worldwide): We will begin rolling out early January 2025 and expect to complete by late January 2025.

Currently, Copilot for Security is not designed for use by customers using US government clouds, including but not limited to GCC, GCC High, DoD, and Microsoft Azure Government. For more information, consult with your Microsoft representative.

[How this will affect your organization:]

Administrators can invoke the policy insights to understand the insights from all their policies or selected polices. The insights offered start with a higher-level view of how their policies:

• are effective across locations.
• detect the presence of sensitive information types throughout their digital estate.
• notify administrators of violations.
• educate users while they perform activities they should not.

These insights are offered with different pivots by location, classification, and by administrative scopes. This is offered to give the security policy administrators different views for deeper understanding of policy constructs and their impact.

Step 1:

Select the policies you wish to get insights/quick summaries about.

Step 2:

Click on the Get Insights with Copilot button. You will see the prompt is already pushed into the Copilot Experience in the side panel.

Step 3:

Copilot responds with insights on the selected policies.

[What you need to do to prepare:]

Admins can prepare by having Security Computer Units (SCUs). Copilot for Security is sold in a provisioned capacity model and is billed by the hour. 

Get more information about SCUs: Get started with Microsoft Copilot for Security | Microsoft Learn.

Coming soon: Users can seamlessly share apps and Microsoft 365 Copilot agents in Microsoft Teams chats and channels. A Microsoft 365 Copilot license is not required to share apps and agents, but a Microsoft 365 Copilot is required to use apps and agents.

This message applies to Teams for Windows desktop, Mac desktop, Teams on the web, and Teams for Android/iOS.

[When this will happen:]

Targeted Release: We will begin rolling out mid-December 2024 and expect to complete by early January 2025.

General Availability (Worldwide): We will begin rolling out early January 2025 and expect to complete by late January 2025.

[How this will affect your organization:]

After this rollout, users will experience:

• New detailed cards for shared Copilot agents and apps
• Shortened URLs for shared links
• The developer’s name and branding icon on app cards
• App details in short description in cards
• Ability to dismiss cards while pasting a link in compose mode
• Ability to right click and share apps from the left app bar
• Ability to share from an app header
• An updated sharing experience with Share and Copy link in the same window
• Shared Copilot agents created from the embedded agent builder in Teams can now be acquired from Teams and used in the Copilot app within Teams.

New detailed cards when sharing Copilot apps and agents in chats and channels:

Sharing from left app bar in Teams:

Sharing from the app header or Copilot agent header:

This change 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. 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.

Viva Goals will be retired on December 31, 2025. Microsoft will continue to maintain Viva Goals’ availability, accessibility and security through retirement. However, as of December 5, 2024, Microsoft will no longer invest in new feature development.].

While Viva Goals is being retired, Microsoft remains fully committed to the Viva suite as a whole, continuing to innovate and deliver tools to help our customers drive meaningful business impact.

[When this will happen:]

December 31, 2025

[How this affects your organization:] 

You are receiving this message because our records show your organization may be using Viva Goals.  

For more details on this decision and how it may affect you, please refer Viva Goals retirement | Microsoft Learn.  

[What you can do to prepare:]

• To prevent auto-renewal beyond the product’s retirement date, an admin should disable recurring billing in the Microsoft Admin Center. Detailed instructions can be found here.
• If your subscription extends beyond the product’s retirement date, or if you have questions or need help with your service plan, please contact your Microsoft representative or [email protected].
• If you have a technical question, please submit a support case in the Microsoft 365 admin center. 

We've released updates to the following update channel for Microsoft 365 Apps:

• Current Channel

[When this will happen:]

We'll be gradually rolling out this update of Microsoft 365 Apps to users on that update channel starting December 5th, 2024 (PST).

[How this will affect your organization:]

If your Microsoft 365 Apps clients are configured to automatically update from the Office Content Delivery Network (CDN), then no action is required.

If you manage updates directly you can now download this latest update and begin deployment.

[What you need to do to prepare:]

To get more details about this update view the following release notes:

• Current Channel