May 26 enhancements
 |
[SETTINGS] Service account management modes in Admin Read Only: in “Organization Settings > Admin read only”, service account management is now split into “Manual” and “Automatic” modes through a dedicated toggle. “Manual” mode lets Tenant Admins update service account usernames and passwords. “Automatic” mode lets Tenant Admins create or recreate service accounts. The selected mode can be changed at any time after onboarding. |
 |
[COREY REPORTING] Tenant configuration alignment reporting: Corey can now return tenant configuration alignment data against the CIS baseline. It reports configuration status, baseline values, current values, deviations, and related compliance context. |
 |
[COREY ACTIONS] Remove mailbox forwarding: Tenant Admins can now remove both internal and external mailbox forwarding from one or more email addresses by chatting with Corey. |
 |
[COREY UI] CSV and Excel file upload for prompt targets: a new file upload option is available in the Corey prompt box. Users can upload CSV and Excel files by clicking the “+” button or by dragging and dropping a file. Corey validates the file format, reads the uploaded identifiers, and uses them as target inputs for the management action or reporting request specified in the prompt. |
ANNOUNCEMENTS
[COREVIEW APP] Per-user MFA property deprecation: the “Per-user MFA” property has been deprecated. The following capabilities are no longer available:
- The “Per-user MFA status” field in reports and User Cards
- The “Manage MFA” management action and workflow action
- The “Users without MFA” and “Admins without MFA” Playbook policies
Automation based on this property no longer works. This includes workflows, custom actions, and custom Playbooks.
[COREVIEW APP] Conditional Access IP update required: thanks to recent infrastructure optimizations, including the removal of some Windows Machines now that PowerShell 7 is mature enough to handle M365 Modules, we have reduced the number of IPs required by our platform.
Please review the updated IP list and remove any outdated IPs from your Conditional Access policies:
May 12 enhancements
 |
[COREY ACTIONS] Convert user mailbox to shared mailbox: Corey can now convert an eligible user mailbox to a shared mailbox through chat. It validates the mailbox and asks for confirmation before running the action. |
 |
[COREY ACTIONS] Revoke user sessions: Corey can now revoke active user sessions through chat in both CoreView and Microsoft 365. After confirmation, Corey executes the action directly. |
 |
[COREY REPORTING] In-chat result limit increased to 25: Corey reporting previews shown in chat now return up to 25 results. This change supports quicker investigations without leaving the conversation. This enhancement was inspired by a CoreView customer. |
 |
[COREY REPORTING] Sorting added to report queries: sorting is now a standard step in Corey’s reporting flow. When supported, Corey builds report queries by selecting columns, applying filters, applying sorting, and then returning results. Requests for top, bottom, largest, smallest, newest, and oldest results are now handled more reliably across supported workloads. This enhancement was inspired by a CoreView customer. |
 |
[COREY UI] Chat management and modal UI updates: chat management in the Corey modal was updated. Users can now favorite chats, access them from a “Favorites” section, and delete chats. |
  |
[REPORTS] Additional columns in App Registrations and Service Principals reports: the “Internal notes” property is now available as a column in the “App registrations” report. The “Note” and “Assignment required” properties are now available as columns in the “Service principals” report. These columns support report visibility and, where applicable, filtering. This enhancement was inspired by a CoreVoice. |
ANNOUNCEMENT
[COREVIEW APP] Per-user MFA property deprecation: the “Per-user MFA” property will be deprecated on 26 May 2026. Starting on this date, the following capabilities will no longer be available:
- The “Per-user MFA status” field in reports
- The “Per-user MFA status” field in User Cards
- The “Manage MFA” management and workflow action
- The Playbook policies “Users without MFA” and “Admins without MFA”
Automation that depends on this property will also stop working. This includes workflows, custom actions, and custom Playbooks.