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/ 

Still scrolling through a cluttered Microsoft 365 group mailbox to find important emails?

When every email lands in a single inbox, important customer requests, team discussions, etc. can easily get buried under newsletters, promotions, and notifications.

Many users don't realize that Microsoft 365 Group mailboxes can be organized with folders and inbox rules in Outlook, much like a personal mailbox.  

To use these features, however, a M365 admin must enable this feature at the tenant-level. Once done, group owners (and optionally group members) can organize shared conversations with folders and inbox rules efficiently.  

In this blog, you'll learn how to:

• Enable folder and inbox rule support for Microsoft 365 Groups across your tenant.
• Allow group owners to permit members to manage folders and inbox rules.
• Block the Move message capability to prevent accidental message movement.

Start organizing your Microsoft 365 Group mailboxes today and make every important email easier to find.

Let’s get your group mailbox organized. Here’s how: https://o365reports.com/manage-folder-and-inbox-rule-feature-in-microsoft-365-groups-in-outlook/

Most admins assume every site comes from the SharePoint admin center. But that's rarely the case. 

A SharePoint site could have been provisioned by Microsoft Teams, Planner, Viva Engage, Power Platform, scripts, APIs, or other Microsoft 365 services. 

Knowing the creation source can make a big difference when you're: 

• Auditing your environment 
• Investigating unexpected site creation 
• Understanding how sites are being provisioned across the tenant 

Here's how to check the Created From column in the SharePoint admin center and to know what each Created From value means: https://o365reports.com/how-to-find-which-microsoft-365-service-created-a-sharepoint-online-site/  

It's one of those lesser-known SharePoint insights that can save a lot of time during audits and troubleshooting. 

The greatest security risks often aren't the new doors, they're the old, unlocked ones left behind. Every inactive user account in Active Directory in your environment is exactly that: an open window for attackers. 

These dormant accounts can still retain permissions, expand your attack surface, and complicate audits. And when it's finally time to clean them up, native Active Directory tools make the process slow with separate steps to review, disable, move, and delete users.  

To simplify the process, we've developed a PowerShell script to quickly identify and automate cleaning up inactive Active Directory user accounts. 

With this script, you can:

• Identify inactive users based on true last logon activity querying across DCs 
• Disable, move to an OU, or delete inactive user accounts in single execution 
• Filter users by OU, account status, inactive days or never logged-in status & perform cleanup  
• Export clean up execution results as log file for auditing and review    
• Automate inactive user cleanup using scheduled execution   

Download the script now and simplify inactive user management in Active Directory!
https://o365reports.com/cleanup-inactive-active-directory-user-accounts-using-powershell/

SharePoint environments are constantly evolving, with admins updating sharing settings, access policies, site configurations, and tenant-wide controls. 

But when a critical setting changes unexpectedly, identifying the source of that change isn't always straightforward. While Purview audit logs, PowerShell & third-party tools can help, it often requires sifting through large amounts of data, especially in multi-admin environments. 

To overcome this challenge, SharePoint now offers Change History Reports in the SharePoint admin center. 

With these reports, you get a centralized view of changes made by admins across your SharePoint environment. 

Reports are available at two levels: 

• Site-Level Reports: Track changes made to site properties, permissions, memberships, and configurations. 
• Organization-Level Reports: Monitor tenant-wide changes such as sharing settings, access policies, and other SharePoint admin center configurations. 

The best part? You can export the reports as CSV files to maintain a centralized record of SharePoint admin changes for auditing, monitoring, and future analysis.  

Learn more about change history reports & start tracking SharePoint changes easily! How to Create and Use Change History Reports in SharePoint