IDECSI now offers a central Campaign Hub within MyDataSecurity to streamline how end-users interact with their M365 security posture. This new interface supports two distinct governance strategies pilotable via MyDataAdmin:
We have extended our governance capabilities for shared mailboxes. You can now use Security Groups to identify and manage shared mailbox owners. Furthermore, these group memberships and their individual members are now visible within MyDataSecurity, providing a comprehensive view of who can access shared resources.
To improve user identification, MyDataSecurity now displays custom labels (e.g., "Contractor") with localized tooltips. This feature includes search support for "Contractor" profiles, helping owners quickly identify external access.
(This feature is currently in Beta. Please contact your Customer Success manager for activation.)
Members of Microsoft 365 Groups, Teams, and SharePoint sites can now be promoted to Owner directly within the MyDataSecurity interface. This eliminates the need to switch to Microsoft native tools, streamlining governance. To ensure security, external users are restricted from being promoted via this interface.
Enhanced Notification Tracking: The Alerts dataset now includes Notification Counters (Initial sends vs. Reminders for both users and admins), allowing CS and AMT teams to track delivery efficiency accurately.
Some bugs have been corrected and technical improvements have been made on our platform.
Align MyDataSecurity with Microsoft 365 sensitivity labels so users cannot attempt privacy changes (Public/Private) when a label forbids it. This reduces confusion and failed remediations while matching Microsoft governance rules.
How to use it?
From MyDataAdmin, navigate to MyDataSecurity, use the new “Groups Privacy” toggle (ON by default) to reflect label behavior. 
In MyDataSecurity, if a label forbids privacy changes, the modal shows a clear banner and disables the primary action. Points of Attention (PoA) for “Public Group” are suppressed when visibility changes are blocked by policy.
Automatically adjust SharePoint on‑prem log collection frequency based on recent activity to avoid infrastructure saturation while keeping alerting responsive on active sites.
How to use it ?
The system gradually reduces polling during inactivity (e.g., 10m → 15m → 1h → 3h → 1d → 3d → 1w) and restores the highest frequency as soon as activity resumes.
Improve access governance by displaying the security groups (with mail extension) and their members that have permissions on personal or shared mailboxes, using a UX similar to SharePoint.
We now also collect and analyze mail‑enabled security groups that have permissions on mailboxes, in order to:
How to use it?
In MyDataSecurity, open the mailbox permissions panel in the mailbox views to see group‑based access and members. Items with Full Access are surfaced for easier review.
Make critical risks stand out and improve discovery with AI sensitivity labels. We now allow classify data using metadata, user context, and workspace characteristics to better prioritize risks :
Accelerate remediation with a targeted “Specific checkup” limited to admin‑selected Points of Attention (e.g., anonymous links).
How to use it ?
(This feature is currently in Beta. Please contact your Customer Success Manager for activation.)
Gain operational visibility with new counters in the Alerts dataset/report that indicate initial notifications and reminders sent to end‑users and admins (excluding Support/AMT), improving overall tracking and follow‑up.
How to use it ?
The reports will be updated with new data, relying on the new columns available for each alerts:
Some bugs have been corrected and technical improvements have been made on our platform.
The MyDataSecurity homepage has been slightly redesigned to provide a clearer and more dynamic experience. Users now benefit from a better information hierarchy, including dynamic banners for active campaigns and dedicated cards for different security checkups.
A new module is now available to strengthen your security posture regarding external access. The "Externals CheckUp" allows end-users to review external users with accesses on their personal and collaborative resources.
A new campaign type "External checkup" enable administrators to invite specific user populations to review their resources' guest and external permissions.
How to use it?
Our reporting capabilities continue to grow:
SharePoint & Teams Structure : New fields have been added to the SharePoint dataset, including channel types (Private vs. Shared) and parent team IDs, providing deeper visibility into your collaborative structure. A new report page will be available in late January.
Alert Metrics : The Cross Dataset now includes comprehensive alert data from the last 12 months, tracking generated, transmitted, and user-reported alerts for better security trend analysis (Available late January).
SharePoint OnPrem log collection can now be done dynamically.
The system now automatically adjusts the collection frequency based on site activity, ensuring high reactivity for active sites while reducing load for inactive ones.
Access Log Sorting: You can now sort access logs numerically in Permissions Explorer, making it easier to identify highly accessed resources at a glance.
Expired Link Exclusion: Expired organizational and specific sharing links are now automatically excluded from MyDataSecurity calculations to eliminate false positives.
Some bugs have been corrected and technical improvements have been made on our platform.
As part of our transition to a unified administration experience within MyDataAdmin, the legacy campaign management screens have been decommissioned from the Expert interface.
We have improved transparency within MyDataSecurity to help users better understand the context of their shared items. The interface now explicitly displays who shared a document and when, directly within the MDS modals.
This enhancement allows users to verify sharing provenance and exposure at a glance, facilitating faster and more informed access management decisions without leaving their current workflow.
How to use it?
To combat alert fatigue, we have introduced a whitelisting capability for FileMalware alerts. Administrators can now suppress future alerts for known legitimate files based on their SHA-256 hash.
This feature is designed to drastically reduce noise and false positives for SOC analysts, allowing them to focus on genuine threats.
How to use it?
Administrators can now track the evolution of their tenant's security and storage posture over time. We have implemented a monthly snapshot process that records key KPIs (including storage usage, permissions, and group analytics) into the dataset. This historical data enables trend analysis, helping you measure the long-term impact of your governance actions.
How to use it?
We have enriched the alerts dataset available for reporting. The dataset now includes standardized date fields and new dimensions for Escalation, Autoclose events, and Feedback qualification. These additions provide a more comprehensive view of alert lifecycles and analyst actions in your custom reports.
How to use it?
A new filter has been added to the Mailboxes Risks tab on the dashboard, enabling differentiation and review of risks for personal and shared mailboxes separately from classic mailboxes.
To help keep your campaign workspace organized, we have added an archiving feature. Administrators can now hide completed campaigns that are no longer relevant (such as tests or old occurrences) from the main view, reducing clutter while ensuring the data remains accessible if needed.
How to use it?
Some bugs have been corrected and technical improvements have been made on our platform.
You can now prioritize your most critical security risks at a glance. Attention points (POAs) can now be displayed and ordered by a new criticity score (1–5) calculated by our AI engine. This allows users to focus on what matters most, using a score based on sensitivity, file names, user context, and more.
Once activated, the AI scoring feature automatically assigns each POA a score from 1 (Very Low) to 5 (Very High). A new AI_scoring property is created or updated whenever a POA is added or modified. This feature can be enabled through a configuration option in MyDataAdmin. Analysis is currently available in dashboards
We’ve created a new, robust data model to feed alert data into MyDataReport (Power BI). This is the first step toward replacing old manual alert reports with a centralized, self-service dashboard, giving administrators a single place to analyze alert KPIs (e.g., open, closed, transmitted). The new data model will power updated Power BI reports starting in November.
Some bugs have been corrected and technical improvements have been made on our platform.
We’ve enhanced the collaborative resources pages in MyDataSecurity to help users more easily identify and manage their team-related content.
Improved visibility of flagged resources: Teams and SharePoint resources marked with Points of Attention will now appear at the top of their respective tabs.
New filter cards: Four quick-filter cards are now available at the top of the Teams, SharePoint, Engage, and Outlook pages:
All
With Attention Point
Managed by me
Read Only
Clicking a card will highlight it and instantly apply the selected filter. The default sort order remains alphabetical.
These enhancements are available in both MyDataSecurity and MyDataManagement. Filter cards will be hidden when there are one or fewer resources to display.
Several improvements have been made to the Management Transfer Card in the Security CheckUp interface:
Clearer display of email addresses: The label (Vous / You) has been replaced with the actual email address for better clarity.
Ownership rules: If a user is the sole owner of a resource under review, their email address will now be disabled. In this case, the appointed manager will be responsible for both current and future reviews of those resources.
Automatic step progression: If no other eligible manager is available for a given resource, the process will automatically proceed to the next step.
Improved guidance and reliability: These changes help prevent blocking situations and errors by ensuring that users only see valid transfer options and clearly understand the implications of transferring management responsibilities.
The governance option in MyDataAdmin now controls only changes from “Private” to “Public”.
The option label is updated to: “Allow end-users to update confidentiality of Microsoft 365 Group from Private to Public”.
If unchecked, the “Update privacy” action is hidden and the status button disabled in the MyDataSecurity portal.
End-users can still change resources from “Public” to “Private”.
This prevents accidental data exposure while keeping resources secure.
A new NotMemberOf("GroupName") operator is being added to Filtering Policies (FP) to exclude users in specific Active Directory groups.
This enables queries such as:
IsEnabled == True && IsDomain == True && OnPremisesExtensionAttributes.ExtensionAttribute15 ~= "ME5" && NotMemberOf("VIP_Users")
allowing administrators to exclude VIP users or other designated groups from selections.
Some bugs have been corrected and technical improvements have been made on our platform.
Several improvements and new features have been added to the Notifications tab in MyDataAdmin.
Selected template in a campaign is now displayed in the campaign overview.
Deployment will be gradual with LEM updates
Enhanced Filers Collection
Implementation of differential collection.
Deployment will be gradual, depending on the clients.
A full collection is performed at regular intervals to check the complete status of the collected files.
A differential collection speeds up the detection of file additions and deletions.
It also allows changes to be displayed more quickly in Permission Explorer.
This improvement increases both the speed and efficiency of detecting changes in collected files.
The list of languages in the drop-down menu is now translated into the selected language (e.g., English is always displayed as “English” regardless of the language).
We have modified the introductory sentence about permissions on sensitive files:
Some bugs have been corrected and technical improvements have been made on our platform.
You can now configure email and reminder notifications sent by your campaigns:
Use custom HTML layouts
Apply predefined templates
We’ve introduced a new graphic charter for the Expert, Permission Explorer, and Monitoring platforms to align their visual identity with MyDataSecurity and MyDataAdmin.
Following the launch of the "Policies" section in MyDataAdmin, we’re continuing to improve interface customization features:
Some bugs have been corrected and technical improvements have been made on our platform.
Added graphics for :
Reminder: Contact your CS agent for questions or if you want an access to MyDataAdmin BETA
You can now manage and configure your MyDataSecurity and MyDataManagement platform on MyDataAdmin through the policies tab.
You can now :
Documentation will be add on the 3rd of June
New color consistency for Expert, Permission Explorer and Monitoring.
Some bugs have been corrected and technical improvements have been made on our platform.
You can now add to the Teams Bot messages :
HVE is now available (OAUTH or SMTP) to send a large number of emails.
Added a "last modified " filter.
Added the name of the campaign creator.
Available on the 20th of may
Some bugs have been corrected and technical improvements have been made on our platform.
Related links will lead to a 404 error page.
A new administration platform is now available upon request for managing campaigns, including :
The previous campaign management system will be decommissioned by the end of 2025
Upon request to your Customer Support team, you can now:
Simplified filter for MyDataManagement
Added before-campaign and after-campaign data on the powerBI Dashboard.
Available on the 15th of April, only for campaigns started after the 8th of April
Some bugs have been corrected and technical improvements have been made on our platform.
Some bugs have been corrected and technical improvements have been made on our platform.
Some bugs have been corrected and technical improvements have been made on our platform.
Example 1:
We display a banner at the Teams and channel level.
We display the “Delete” function at Teams level only if all channels below are also inactive.
Example 2:
We don't display the “Delete” function at the Teams level if at least one of the channels is active.We display a banner at the Teams and channel level.
⚠ On the 14/01/2025, the dashboards won't be refreshed for 1 day.
Some bugs have been corrected and technical improvements have been made on our platform.
Dashboards publication have been improved to be more reliable and reduce the risk of empty dashboards.
Some minor display bugs have been rectified : empty KPIs, validation dates for MDM usage etc.
We have added a new alert rule, able to generate alerts only if the inbox rule created or modified is a conditional delete with a condition set on the subject of the email.
Some bugs have been corrected and technical improvements have been made on our platform.
Some bugs have been corrected and technical improvements have been made on our platform.
Some bugs have been corrected and technical improvements have been made on our platform.
Some bugs have been corrected and technical improvements have been made on our platform.
Some bugs have been corrected and technical improvements have been made on our platform.