Today I’ve released a new version of my Conditional Access Framework. The previous version (2024.4.1) was mostly focused on Windows Modern Workplace environments. Version 2024.6.1
Category: AzureAD
Few months ago i decided to redesign my Conditional Access Framework. While reading some docs and blogs for recent changes i found Claus Jespersen his
Microsoft has released (globally available) a new form of Conditional Access (CA) policies. This CA policy requires users to use MFA when accessing admin portals.
In the past it was possible to create non-expiring client secrets. When creating a client secret the drop down menu showed the option Never expires.
Protecting users and authentications with MFA is one of the most important things to do. Users need to identify their authentications with at least one
While using Conditional Acces, we can require specific requirements for users, devices, apps, countries (locations), device states, etc. This gives us the opportunity to allow
The SMTP Authentication protocol (in Exchange Online) is the most attacked (legacy) protocol now a days. This happened since Microsoft is currently disabling all other
While most people rely on Azure AD Sign-in logs, there are some additional features which are worth implementing in your tenant. One of these features
The idea Since a while I’m testing/playing around with Windows 365 Cloud PC’s. For performance purposes I would like to reboot and/or reprovision Windows 365
Require dynamic lock as part of your compliance policy using custom compliance policies.