01-January-2025 Below you will find a collection of news published yesterday. This news consists of Microsoft’s Roadmap when it is updated it will be below with items. Then there will be a section with the message center, if there is anything new there, this will be automatically included. And it contains a piece from blogs that I follow myself and would like to share with you. If I miss something in the blogs that do have an RSS feed, please let me know.
This entire post was automated via Microsoft Flow
have fun reading!
The blogs of this day are:
Office 365 Roadmap Updated: 2025-01-01
Additions : 0
Updates : 1
More Details At: www.roadmapwatch.com
Updated Features | Current Status | Update Type | ||
---|---|---|---|---|
Bookings: ”Cc" functionality to email notifications | In Development | Title |
Items from the MessageCenter in Microsoft 365
(Updated) Microsoft Purview | Information Protection: Auto-labeling policies will support “Fingerprint based SIT”Category:Microsoft 365 suite Microsoft PurviewNummer:MC920308Status:planForChange | Updated December 31, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Purview | Information Protection: Admins will be able to use auto-labeling policies to automatically label files and emails with Fingerprint based SIT (sensitive info type). This message is associated with Microsoft 365 Roadmap ID 396173. [When this will happen:] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late November 2024 and expect to complete by mid-January 2025 (previously mid-December). [How this will affect your organization:] Before this rollout, admins are not able to use auto-labeling policies to automatically label files and emails with Fingerprint based SIT. After this rollout, you can configure Fingerprint based SIT using the condition Content contains sensitive information types. Files that match Fingerprint based SIT will show in simulation.
Note: Contextual summary is not available for Fingerprint based SITs. This change will be on by default and available for admins to configure. [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 use cases and set up for configuring document fingerprinting. Learn more |
Upcoming changes to Defender for Identity activities and alerts in Defender for Cloud Apps experiencesCategory:Microsoft Defender XDRNummer:MC940078Status:planForChange | Updated December 31, 2024: We have updated the content. Thank you for your patience. As part of the convergence of both Microsoft Defender for Identity and Microsoft Defender for Cloud Apps into Microsoft Defender XDR services, we are continuing to move away from legacy experiences and enhancing the unified experiences. Therefore, we will gradually retire Defender for Identity’s Active Directory and alerts data from Defender for Cloud Apps dedicated experiences. All data, as well as all functionality of the affected experiences, remain available through Microsoft Defender XDR unified experiences, where we will continue to invest our development resources. [When this will happen:] General Availability (Worldwide, GCC, GCC High, DoD): This retirement will begin rolling out in late January 2025 and is expected to complete in early March 2025. [How this will affect your organization:] You are receiving this message because the following changes may affect your organization: Active directory activities coming from Defender for Identity will no longer be available in Defender for Cloud Apps activity logs. Consequently, Defender for Cloud Apps activity policies will cease from triggering based on Active Directory data. All Active Directory activities data remains available through Advanced Hunting, in the following tables:
To learn more about Advanced Hunting and the Data Schema, visit Proactively hunt for threats with advanced hunting in Microsoft Defender and Understand the advanced hunting schema. New Active Directory activities, as well as Defender for Identity’s alerts data, will no longer be available through Defender for Cloud Apps Activities API, Alerts API, or dedicated SIEM agents. All activities and alerts data remains available through Defender XDR Streaming API and Event Hubs. Learn more about Streaming API. For more information about how to integrate your SIEM tools with Microsoft Defender XDR, visit Ingesting streaming event data via Event Hubs. The Identities page under ‘Assets’ in the XDR portal will be updated to better support the new experiences. The page will be divided into two distinct tabs: First-party identities and Third-party accounts. In the User page, “View related activity” action will no longer be available. To learn more about Defender for Identity’s experiences in the XDR portal, visit Microsoft Defender for Identity in the Microsoft Defender portal. [What you need to do to prepare:] To ensure a seamless experience, create new custom detections for any activity policies based on active directory data in Advanced Hunting. To learn more about how to create custom detections, visit Create and manage custom detections rules. Suggested queries related to Active Directory activities are available through the portal under Advanced Hunting > Community Queries. For more information, see Use shared queries in Advanced Hunting. If you are still using Defender for Cloud Apps dedicated API and SIEM agents to consume Defender for Identity activities or alerts, make sure to update your resources according to the above information.
|
(Updated) Microsoft Secure Score: Changing Microsoft Defender for Endpoint recommendationCategory:Microsoft Defender XDRNummer:MC941863Status:planForChange | Updated December 31, 2024: We have updated the rollout timeline below. Thank you for your patience. We’re updating the Microsoft Secure Score improvement action of Microsoft Defender for Endpoint (MDE) to ensure a more accurate representation of security posture. As part of this change, we will gradually retire the MDE recommendation on SCID-2020, Turn on all system-level Exploit protection settings. We are working to refine the recommendation, ensuring it aligns more accurately with recommended policies and enhances the overall security value. [When this will happen:] General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early January 2025 (previously early December) and expect to complete by early February 2025 (previously early January). [How this will affect your organization:] The Turn on all system-level Exploit protection settings recommendation will be completely removed from the UI, and the score will be changed in accordance. 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 as appropriate.
|
Power Automate – Use Copilot to analyze desktop flow runsCategory:Microsoft Power AutomateNummer:MC969381Status:stayInformed | We are announcing the Use Copilot to analyze desktop flow runs feature for Power Automate. This feature allows users to ask questions about cloud flow and desktop flow activity, work queues, and Power Automate features. This feature will reach general availability on January 31, 2025. How does this affect me? This feature allows Copilot within automation center to answer questions about desktop flow run history and view Copilot’s insightful analysis of desktop flow run history. What do I need to do to prepare? This message is for awareness and no action is required. If you would like more information on this feature, please visit Automation center (preview). |
Power Automate – Use Copilot to analyze work queue dataCategory:Microsoft Power AutomateNummer:MC969385Status:stayInformed | We are announcing the Use Copilot to analyze work queue data feature for Power Automate. This feature enables Copilot to answer questions about work queue statuses and handling times. This feature will reach general availability on January 31, 2025. How does this affect me? This feature allows Copilot within automation center to ask questions about cloud flow and desktop flow activity, work queues, and Power Automate features. What do I need to do to prepare? This message is for awareness and no action is required. If you would like more information on this feature, please visit Automation center (preview). |
Power Automate – Use Copilot to ask Power Automate product questionsCategory:Microsoft Power AutomateNummer:MC969397Status:stayInformed | We are announcing the Use Copilot to ask Power Automate product questions feature for Power Automate. This feature allows users to ask questions about cloud flow and desktop flow activity, work queues, and Power Automate features. This feature will reach general availability on January 31, 2025. How does this affect me? This feature allows Copilot within automation center to analyze automation activity, view work queue performance, and provide answers to common questions about Power Automate capabilities. What do I need to do to prepare? This message is for awareness and no action is required. If you would like more information on this feature, please visit Automation center (preview). |
Microsoft Copilot in the Microsoft 365 admin centersCategory:Microsoft Copilot (Microsoft 365)Nummer:MC969450Status:stayInformed | Microsoft Copilot in the Microsoft 365 admin center will soon be generally available. Tenants that have at least one Microsoft 365 Copilot license will be able to access Copilot in the Microsoft 365 admin center via the Copilot button on the top right corner of the screen. Copilot experiences in the Teams and SharePoint admin centers will be introduced in the coming months as part of this feature set. Admin accounts do not require a Microsoft 365 Copilot license to be assigned to them, and no additional action is required. Copilot in the Microsoft 365 admin center is a set of experiences that harnesses the value of generative AI to boost Microsoft 365 admins’ productivity by streamlining daily work, so admins are empowered to focus on their strategic priorities, make faster decisions, and maximize the value of their investments. [When this will happen:] General Availability (Worldwide): We will begin rolling out late January 2025 and expect to complete by late March 2025. [How this will affect your organization:] Copilot in the Microsoft 365 admin centers will be available to all admins and will respect role-based access controls (RBAC) within the admin center, only surfacing information and controls that the particular admin has access to. Copilot will not make any configuration changes on behalf of an admin, keeping security integrity intact. When available, Copilot in the Microsoft 365 admin centers can help:
Optimizing for the flow of your work Copilot agents are specialized AI assistants designed to enhance the capabilities of Microsoft 365 Copilot by connecting to your organization’s knowledge and data sources. Alongside Copilot in the Microsoft 365 admin center, we’re also rolling out a pre-built admin agent. Rollout of the agent will begin later than Copilot in the Microsoft 365 admin centers but is expected to be completed by the end of March. This Copilot agent allows admins to access IT administration capabilities directly within various Microsoft 365 workflows from Business Chat without needing to be in an admin center. The Microsoft 365 admin agent respects Role Based Access Controls (RBACs) within the admin center and only surfaces information that the account has access to. When rolled out, if a user has an admin role assigned to them and they have a Microsoft 365 Copilot license assigned, the admin agent will be pre-installed. [What you need to do to prepare:] To learn more about Copilot in the Microsoft 365 admin centers, including how to disable it, please see Copilot in Microsoft 365 admin centers (Preview), and watch our Empowering IT with the latest Microsoft 365 innovation session at Ignite. This rollout will happen automatically with no admin action required.
|
Microsoft Purview | Communication Compliance: Detect workplace safety concerns in user-reported Microsoft Teams messagesCategory:Microsoft PurviewNummer:MC969453Status:planForChange | Microsoft Purview Communication Compliance introduces the ability to identify and flag potential workplace safety concerns in user-reported messages in Microsoft Teams. Investigators now have an additional indication to decide what risk exists in user-reported messages and can configure an Inappropriate Content policy to proactively identify similar inappropriate content moving forward. This message is associated with Microsoft 365 Roadmap ID 422329. [When this will happen:] General Availability (Worldwide): We began rolling out mid-November 2024 and expect to complete by late December 2024. [How this will affect your organization:] Communication Compliance customers automatically have a user-reported message policy provisioned when they begin their Communication Compliance journey. After this rollout, user-reported content that triggers a Content Safety classifier will display the classifier name that flagged the message and a severity value in the Severity column: This feature will be on by default and cannot be turned off. The feature does not change the user-reported message experience. It will only show the following additional information:
For more information, see Create and manage communication compliance policies. [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. Microsoft Purview Communication Compliance provides the tools to help organizations detect regulatory compliance violations (e.g. 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. |
Power Automate – Streamline workflow creation with the next best actionCategory:Microsoft Power AutomateNummer:MC969477Status:stayInformed | We are announcing the streamline workflow creation with the next best action feature for Power Automate for desktop. This feature will provide you with the next best action for your workflow creation by continually analyzing your workflow and suggesting the most appropriate action. By leveraging this feature, you can automate repetitive tasks more quickly and efficiently. This feature will reach general availability on January 31, 2025. How does this affect me? The next best action suggestion feature has been designed to streamline the automation process, making it easier for you to create and automate workflows without requiring extensive flow creation knowledge. With this new addition, you will be able to create more complex workflows with ease. The feature will suggest the next action that makes sense based on the context of the current workflow and the actions that have already been added. What do I need to do to prepare? This message is for awareness and no action is required. If you would like more information on this feature, please visit Adding actions from the suggested actions panel. |
Power Automate – Use Copilot to analyze automation activityCategory:Microsoft Power AutomateNummer:MC969523Status:stayInformed | We are announcing the use Copilot to analyze automation activity feature for Power Automate. This feature will allows users to use natural language to ask copilots about past flow runs, machines and other related data. It will provide advanced operational visibility, without the need to build and deploy custom reports with a predefined set of queries and reports. This feature will reach general availability on January 31, 2025. How does this affect me? Administrators, CoE teams, business users, and makers with access to flow run histories can query past runs in natural language across their environment. For example, users may ask how many flows ran yesterday, on which machines or groups, what the success rate looked like, and how they compare to last month. Users may inquire about recent runs, their durations, volumes, failures, failure frequency, machines, machine groups, parent flows and much more. What do I need to do to prepare? This message is for awareness and no action is required. If you would like more information on this feature, please visit Use Copilot to analyze automation activity. |