Microsoft Roadmap, messagecenter en blogs updates van 31-08-2024

Coming soon: Microsoft Copilot for Microsoft 365 usage in your tenant will be added to the Microsoft Graph API to facilitate the creation of customized reporting and analytics. Metrics included in the Graph API will match those available in the Copilot for Microsoft 365 usage report in the Microsoft 365 admin center, including tenant-level count of enabled users and active users, as well as last activity date per user (totals for each Microsoft 365 app and a grand total). A Microsoft Copilot for Microsoft 365 license is required to use this feature.

This message is associated with Microsoft 365 Roadmap ID 396562 and with MC724835 Microsoft 365 admin center Usage report: Microsoft Copilot with Graph-grounded chat (Preview) (published March 2024).

[When this will happen:]

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

[How this will affect your organization:]

Before this rollout, the Graph API did not include Copilot for Microsoft 365 usage.

After this rollout, admins can use the Graph API to create customized reporting and analytics for Copilot for Microsoft 365 usage.

Sample request for one of the three APIs: getMicrosoft365CopilotUserCountSummary.

Sample response:

HTTP/1.1 200 OK

Content-Type: application/json

Content-Length: 537

{

"@odata.context": "https://graph.microsoft.com/beta/reports/getMicrosoft365CopilotUserCountSummary(period='D7')?$format=application/json",

"value": [

{

"reportRefreshDate": "2024-06-26",

"adoptionByProduct": [

{

"reportPeriod": 7,

"anyAppEnabledUsers": 354590,

"anyAppActiveUsers": 144022,

"microsoftTeamsEnabledUsers": 354449,

"microsoftTeamsActiveUsers": 88737,

"wordEnabledUsers": 354449,

"wordActiveUsers": 17493,

"powerPointEnabledUsers": 354449,

"powerPointActiveUsers": 7245,

"outlookEnabledUsers": 354449,

"outlookActiveUsers": 38140,

"excelEnabledUsers": 354449,

"excelActiveUsers": 2554,

"oneNoteEnabledUsers": 354449,

"oneNoteActiveUsers": 1382,

"loopEnabledUsers": 354449,

"loopActiveUsers": 955,

"copilotChatEnabledUsers": 354449,

"copilotChatActiveUsers": 64401

}

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

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

To learn more about Microsoft’s own review of this product with its works councils, please consider reading: https://aka.ms/Copilot/MSWorksCouncilsArticle 

Many users have voiced frustrations over copying messages in Teams, particularly the inclusion of metadata like names and timestamps. Customer feedback has been clear, signaling that this feature was adding more noise than value to user workflow.

We are rolling out the change that copied messages are only showing the message content moving forward.

• Streamlined Experience: Most users simply want to copy and paste messages without the extra clutter. Removing names and timestamps from copied content helps maintain focus and reduces unnecessary noise.
• Better Alternatives for Specific Needs: For those who need to forward messages or extract conversations, we recommend using the Forward feature for message transfer between chats, and the Teams Export API for conversation extraction. These tools are more robust and prevent manipulation of message content.

[When this will happen:]

General Availability (Worldwide): Available now and we apologize for not communicating prior to the rollout occurring.

[How this will affect your organization:]

Some users might have used this timestamp and message author name for different purposes and might report that this information is not part of the pasted content anymore.

[What you can do to prepare:]

You may consider updating your training and documentation as appropriate.

The cloud.microsoft domain was provisioned in early 2023 to provide a unified, trusted, and dedicated DNS domain space to host Microsoft’s first-party authenticated SaaS products and experiences. This post is to inform admins that the following Microsoft products and scenarios are now available at the cloud.microsoft domain, in parallel with the previous domains.

• Microsoft Excel (https://excel.cloud.microsoft)
• Microsoft PowerPoint (https://powerpoint.cloud.microsoft)
• Microsoft Word (https://word.cloud.microsoft)

A full list of product experiences already being delivered on this domain can be found here: Unified cloud.microsoft domain for Microsoft 365 apps – Microsoft 365 Enterprise | Microsoft Learn.

[When this will happen:]

The services above are already available on cloud.microsoft, in parallel to their previous domains. You can expect the previous domains to be redirected to cloud.microsoft in the coming months. 

[How this will affect your organization:]

• The cloud.microsoft domain has been a part of standard Microsoft network guidance on domains and service endpoints since April 2023. If you are currently following this guidance, this change should not impact users in your organization using the above applications under the new domain.
• Users will be redirected to applications under cloud.microsoft domains gradually and automatically. No specific user action is required. Links to the previous domains are backwards compatible and continue to be supported. Users may notice that the new application domains are lacking the “.com” extension. This is by design, as “.microsoft” is Microsoft’s own top-level domain – and this exclusivity allows for additional security and protection against spoofing.

[What you need to do to prepare:]

• Educate users to recognize and expect cloud.microsoft as a key domain for Microsoft cloud experiences. You can refer them to What is cloud.microsoft? – Microsoft Support for more information.
• If your organizational websites, tools, or other materials reference the old URL, those links will be automatically redirected. However, it would be good practice to update those assets to avoid user confusion.
• Partner with developers of in-house Teams apps – including those that run on Outlook and Microsoft 365 – to take the actions described in Action required: ensure your Microsoft Teams apps are ready for upcoming domain changes so the apps continue to function on the new domain.
• Admins should ensure that connections to *.cloud.microsoft are not blocked from their clients and enterprise networks. This should require no action if standard Microsoft network guidance on domains and service endpoints is being followed.

A new column will be added to the Readiness section of the Copilot for Microsoft 365 Usage report called Suggested candidate for Copilot. This new column is intended to help admins make licensing decisions by quickly identifying users who are in a strong position to get the most value from Copilot for Microsoft 365 based on their relevant Microsoft 365 app usage. 

This message is associated with Microsoft 365 Roadmap ID 410202.

[When this will happen:]

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

[How this will affect your organization:]

This addition of the new Suggested candidate for Copilot column in the Readiness section of the Copilot for Microsoft 365 Usage report is intended to help admins make licensing decisions by quickly identifying users with relevant Microsoft 365 app usage. Examples of relevant Microsoft 365 app usage indicators can also be found in the same report, including flags indicating whether or not the user was active in Microsoft Teams meetings, Teams chats, Microsoft Outlook emails, and Microsoft Office documents over the prior 30 days. 

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

A new Microsoft Purview compliance portal introduces a pivotal communications enhancement that integrates Insider Risk Management (IRM) alerts within Communication Compliance (CC) triage flows, providing a holistic approach to compliance risk assessment. This integration empowers investigators with enriched insights by correlating communication alerts with a user’s risk profile and activity history from IRM directly in a CC triage flow. This synergy between IRM and CC facilitates a more nuanced and informed decision-making process during investigations. 

This message is associated with Microsoft 365 Roadmap ID 408534.

[When this will happen:]

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

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

[How this will affect your organization:]

The integration of IRM context into CC is a significant stride towards enhancing the efficacy of compliance investigations. This will allow investigators to view a user’s risk profile and history alongside communication alerts, enabling a more informed and efficient triage process.

The insider risk severity (Low, Medium, or High) determined by activity detected in IRM policies helps to prioritize and respond to user activity accordingly. A new user activity timeline will show messages and activities from IRM in one screen, simplifying the review process.

[What you need to do to prepare:]

To use this feature, please connect with IRM administrators to enable Data sharing from IRM settings. If you don’t turn this setting on, you will see Insider risk activity not available.