I often get asked how we manage networks without an RMM tool and I always reply that we take full advantage and make use of what Microsoft has to offer. This type of rule is an example of that philosophy.
Microsoft 365
29 posts
To resolve this error, you need to remove three security groups from Azure AD. These groups were created by default in your tenant but have since been deprecated by Defender.
This is a collection of posts about Microsoft Defender. How to set, configure, troubleshoot and implement.
There are a number of basic settings in Defender that should be configured before you start using Defender.
Finally, there is an easy way to deploy a base set of conditional access policies to users, devices and apps in a tenant. Microsoft calls it Conditional Access Templates and you will find them in Azure AD – Security – Conditional Access – Conditional Access Templates.
There’s mandatory migration underway from SSPR and MFA settings to policy and you have until later this month to get them into place voluntarily or Microsoft will do it for you
I’m going to show you how adding a single word to a user’s profile in Azure Active Directory (Azure AD) can kick off an entire onboarding process and move user add/remove from an IT task into an administrative assistant task.
The Risky User report is useful sure, but wouldn’t it be better if you didn’t have to remember to see if any users have been flagged as Risky?
It’s an Attack Surface Reduction rule and it is exploited in the wild, so it’s import to close up this vulnerability to fileless attacks.
Understanding what we can recover from deletion in Azure AD and what cannot be recovered is important. Especially, the not recoverable par