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.
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.
We have a sustained 100% secure score in Identity Security and you can too. There's an actual method and implementation process
This is a limited time opportunity to join a group in owner-led growth. Ready to take the growth of your business seriously? Willing to share and learn?
Azure AD creates its own password policy. It’s a secure by default item
Office fails to install. The SARA tool fails to resolve the problem.
What does no RMM mean? It means not subscribing to a third-party tool to manage Microsoft products
