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

This rollout will enable users to use prompts in to create charts, graphs and data analysis in Microsoft 365 Copilot Business Chat (BizChat). Users can also view the Python code for these charts, graphs, and data analysis. This feature requires a license for Microsoft 365 Copilot.

This message is associated with Microsoft 365 Roadmap ID 420363.

[When this will happen:]

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

[How this will affect your organization:]

Before this rollout, Copilot users are not able to use prompts to create charts, graphs, and data analysis in Copilot Business Chat.

After this rollout, Copilot users can enter prompts in Copilot Business Chat to create charts, graphs, and data analysis. To view the Python code that is generated for a chart/graph, users can select the Code button.

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. You may want to notify your users about this change and update any relevant documentation.

Learn more: Get started with Microsoft 365 Copilot Business Chat – Microsoft Support

In September 2024, we added new built-in reporting buttons in new Microsoft Outlook for Mac desktops that allow users to report emails as phishing / junk / not junk. Admins can control the appearance and behavior of these buttons from the User reported settings page in the Microsoft 365 Defender portal (security.microsoft.com). Admins can also customize where messages get reported to (reporting mailbox, Microsoft, or both) and what the user sees both before and after reporting messages from these buttons. Your current User reported settings page has not been changed by this rollout. This message applies to new Outlook for the Mac using version 16.89.24090815(16.89.908.0).

This message is associated with Microsoft 365 Roadmap ID 371393.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD): Available now.

[How this will affect your organization:]

Before this rollout: Outlook for Mac users did not see reporting buttons.

After the rollout

• OWA (Outlook on the web), new Outlook for Windows, and classic Outlook for Windows have had this functionality since August 2024 and there is no change to it
• Other versions of Outlook such as Mobile (iPhone and android) will remain unaffected by this change. We are working on the adding the reporting buttons to other versions of Outlook.
• If you have the reporting feature turned off in the Microsoft 365 Defender User reported settings page or are using a third-party add-in, the reporting buttons in Outlook for Mac will not be visible to users.
• The Microsoft reporting add-in (the Microsoft report message add-in and the Microsoft phishing add-in) will be supported until further notice. Customers who currently use the add-in and the new reporting buttons will see two sets of reporting buttons in the ribbon. However, when we add the new reporting buttons to Outlook Mobile clients in the near future, the reporting add-in will no longer be needed and can be removed.
• The selections you make on the User reported settings page will determine whether your users choose the add-in or built-in reporting option in Outlook. Either option will report to the same place (Microsoft, custom mailbox, or both) based on the User reported settings selected.
• Unlike OWA and new Outlook for windows, the built-in reporting buttons in Outlook for Mac do not support reporting from shared and delegate mailboxes.

New reporting buttons in Outlook for Mac

From all folders except junk folder:

From the junk folder:

[What you need to do to prepare:]

Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.

Learn more

• Report phishing and suspicious emails in Outlook for admins – Microsoft Defender for Office 365 | Microsoft Learn
• User reported settings – Microsoft Defender for Office 365 | Microsoft Learn

Coming soon to Microsoft Exchange Online: A significant rollout that introduces two new subfields under AppAccessContext for improved field consistency and enhanced telemetry in other Exchange APIs:

• ClientAppId
• APIId

[When this will happen:]

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

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

General Availability (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: The ClientAppId and AppAccessContext fields exist across previous schemas outside of the Microsoft Exchange Web Service (EWS) schema.

After this rollout: The AppAccessContext field, which serves a similar purpose to the ClientAppId field, will be in EWS schema with two new subfields: ClientAppId and APIId. This update is on by default. The ClientAppId field and the ClientAppId subfield under the AppAccessContext field will both be populated more consistently and robustly with a new fallback.

Field definitions

• AppAccessContext: Used to provide additional information about the application context in which an event or action occurs. This field helps in tracking and auditing purposes by identifying the specific application or service involved in each operation.
  • ClientAppId: The original field used to identify the application that initiated a particular action or event. After this rollout, this subfield will have a new fallback to enhance capabilities.
  • APIId: Used to uniquely identify an API endpoint or service. This subfield is particularly useful in scenarios where admins need to filter or track activities specific to certain APIs, such as the Microsoft Exchange Web Service (EWS).

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout.

After the rollout, we recommend admins review and update your workflows to accommodate both the ClientAppIdand AppAccessContext fields. This will ensure that your operations continue seamlessly and leverage the new features effectively.

Accessing and using the new fields

1. Navigate to the admin center: Start by logging into the Microsoft 365 admin center.
2. Access the audit logs: Go to the section where audit logs are managed. This is typically found under the Security & Compliance section or the Microsoft Purview section.
3. Search for relevant logs: Use the search to filter logs that include the AppAccessContext and ClientAppId fields. You may need to specify the event types or actions that involve these fields.
4. View and analyze logs: After the logs are filtered, you can view the details, which will include the AppAccessContext and ClientAppId fields. These fields provide additional information about the application context and the client application involved in each operation.

Learn more

• The Engage Mailbox schema section in Office 365 Management Activity API schema | Microsoft Learn
• Mailbox audit logging in Exchange Server | Microsoft Learn

With this new capability, Microsoft 365 Mobile app users can open PDF files that are protected with Microsoft Purview Information Protection sensitivity labels and read them using Microsoft 365 Mobile app in read-only mode. Only authorized users will be able to access these PDF files.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD): Available now.

[How this will affect your organization:]

MIP (Microsoft Information Protection) is an umbrella term for the Information Protection Services provided by Microsoft. Primarily MIP provides Classification, Labelling, and Protection (CLP) capabilities. With this feature, Microsoft 365 Mobile App will allow for previewing MIP encrypted PDF files.

This feature will be available by default.

[What you need to do to prepare:]

You may want to notify your users about this new capability and update your training and documentation as appropriate.

As announced earlier in MC616550 (June ’23), InfoPath Forms Service is being deprecated and will be removed from existing tenants after July 14, 2026. To support this transition, we will prevent the publication of new InfoPath forms in SharePoint Online for tenants with no detected usage of the InfoPath forms service. This proactive action aims to reduce the migration effort for new InfoPath forms in anticipation of the service’s retirement.

[Key Points:]

• Major: Retirement update
• Timeline: After December 20, 2024, Microsoft will prevent the publication of new InfoPath forms for tenants who are not actively using InfoPath services.
• Action: Review and assess impact

[How this will affect your organization:]

After December 20, 2024, InfoPath designers and publishers will no longer be able to publish new forms to SharePoint Online as no active usage of the InfoPath forms service has been detected in your tenant over the past year. Existing published forms will remain unaffected, and end users can continue to fill in these forms in SharePoint Online if needed.

[What you need to do to prepare:]

As we have detected no usage of the InfoPath forms service in your tenant over the past year, we recommend running the Microsoft 365 Assessment tool and using the Power BI InfoPath Report to confirm this. If active usage is detected, please raise the issue with your support engineer for our further assistance.

If you need a solution for the form scenario in your organization, we recommend using the modern solutions of Microsoft Power Apps, Microsoft Power Automate or Microsoft Forms, and additional details can be found in this blog.