Overe Protect policies safeguard your tenant's security posture by enforcing best practices to maintain a secure and healthy environment.
Because policy controls impact various Microsoft systems, certain requirements may arise during their evaluation. If a control cannot be evaluated, the interface will indicate the reason, which will fall into one of two categories:
Missing Microsoft Licenses
Some of Overe's Policy Controls require integration with Microsoft Conditional Access Policies, which are available with specific Microsoft Entra ID plans. Others may depend on features included in higher-tier licenses.
The interface will identify controls that cannot be evaluated due to a missing license and will specify the required Microsoft product.
If you don’t intend to acquire the missing license, you can prevent Overe from flagging this issue or generating errors in policy evaluation by disabling the specific control that requires it.
Pending Configuration Actions
Beyond having the appropriate licenses to evaluate all policy controls, some controls may also require specific tenant configurations. These are general settings that Overe does not enforce automatically, as doing so would require maintaining elevated access permissions solely for these tasks. Additionally, these configurations may be subjective, leaving it up to the tenant administrator to decide whether they should be applied.
The potential system configuration prerequisites include:
Assigning the Exchange Administrator role to the Overe app
This role is necessary to enable email security-related controls. Learn how to grant this role in the following video:
Disabling Security Defaults
Microsoft Security Defaults provide baseline protections against identity-related threats. However, they are incompatible with Conditional Access Policies, which Overe relies on for enforcing advanced policy controls. While Overe can still function with Security Defaults enabled, some Policy Controls may fail as a result.
Overe recommends following the suggested configuration to ensure full access to all available Policy Controls. However, similar to licensing requirements, if you choose not to adopt a required configuration, you can disable the conflicting controls to prevent inaccurate evaluations and error messages.