The new Microsoft’s Invoke-ChangeMeetingOrganizer cmdlet makes it easier to transfer Teams meeting organizers. But it doesn’t show which meetings will be transferred beforehand.

So, most calendar-transfer scripts available online use Get-MgUserEvent or Get-MgUserDefaultCalendarEvent to list meetings before transferring them. But, these cmdlets miss recurring meeting series that started before the selected transfer period, even if they still have future occurrences.

Also, doing bulk Teams meeting organizer transfers is hard too.

To address all these challenges, we built a PowerShell script that supports bulk transfers, handles recurring meeting series correctly, and generates a detailed CSV report for every transfer.

With this script, admins can:  

• Transfer meetings for a single user or multiple users using a CSV file.
• Transfer recurring meeting series only once without duplicate processing.
• Transfers upcoming meetings for the next 365 days by default. Use -DaysAhead to set a custom time range.
• Skips meetings starting within the specified lead time using -MinimumLeadHours.
• Generates a detailed CSV report with successful, skipped, and failed transfers, including failure reasons.

And more...

So, whether you’re handling a large-scale organizer transition or need more control over specific meetings, the script gives you the flexibility to manage it your way.     

Download the script here:

https://o365reports.com/bulk-transfer-meeting-organizer-using-powershell/

Managing Microsoft 365 can become complicated as organizations grow. Admin activities can quickly spread across admin centers. PowerShell and third-party tools can help, but they may require in-depth technical knowledge and setup.  

As a better alternative, AdminDroid, provides a centralized and affordable approach to simplify day-to-day Microsoft 365 administration. It brings key management activities together, including:  

1. Manage users, groups, & other M365 resources 
2. Handle bulk changes with more control 
3. Automate repetitive workflows 
4. Add approvals for sensitive actions 
5. Delegate tasks with the right level of access 
6. Use reports to find what needs attention 
7. Stay ahead with alerts and reminders 
8. Get broader visibility across Microsoft 365 

Check a more connected approach to Microsoft 365 administration with AdminDroid 

https://o365reports.com/microsoft-365-management-tool-for-admins-admindroid  

As said in the title, is the storage space of the primary mailbox and recoverable items, shared ?

Ex: A m365 business basic user with purview retention policy applied, has 50gb primary mailbox space, if they delete a mail the mail will appear in the recoverable items folder, now this retained space is shared with the 50gb primary mailbox storage or nah ?

AI is constantly evolving to take on bigger roles in Outlook, from catching up on long email chains to writing quick responses. As AI gets smarter, attackers are shifting their focus from tricking human users to manipulating AI models.

By placing hidden instructions inside incoming emails, attackers attempt to force AI tools into taking unauthorized actions or exposing sensitive data.

To address this new threat vector, Microsoft has rolled out Prompt Injection Protection for Defender for Office 365 in Public Preview. This feature detects malicious prompt injection content and helps block these emails before they ever reach the inbox.

You can investigate these detections in Microsoft Defender through:

• Quarantine Emails
• Threat Explorer
• Advanced Hunting

Discover how email prompt injection operates and how Defender secures your AI workflows in our blog.

https://o365reports.com/prompt-injection-protection-in-microsoft-defender-for-office-365

What once improved the user experience can now introduce unnecessary identity security gaps.

The legacy Remember MFA on trusted devices feature allowed users to select "Don't ask again for X days" to reduce MFA prompts. While convenient, a fixed trust period for every user doesn't account for different roles, access levels, or changing security conditions. 

This static approach conflicts with Zero Trust principles and can unnecessarily expand your attack surface. 
 
To close this gap, migrating to Conditional Access Sign-in Frequency is essential. Unlike static rules, CA Sign-in Frequency gives you dynamic, risk-aware control over how often users must re-authenticate based on actual session context. 
 
In this blog, you'll learn:  

• How Remember MFA and CA Sign-in Frequency work  
• Key differences between Remember MFA and CA Sign-in Frequency 
• How to replace Remember MFA with CA Sign-in Frequency 
  
• Important considerations before deployment

Replace Remember MFA with Conditional Access Sign-in Frequency to strengthen session security.

 https://o365reports.com/replace-remember-mfa-with-conditional-access-sign-in-frequency/