A cloud-based identity and access management service for securing user authentication and resource access
Hi Keith,
Thank you for posting your query on Microsoft Q&A.
The issue you are encountering with Secure Score incorrectly flagging the onPremisesSyncEnabled property as “disabled” in cloud-only tenants is a known limitation related to how Secure Score interprets this property. In Microsoft Graph API, the onPremisesSyncEnabled property is null for tenants that have never used on-premises synchronization, which is typical for cloud-only tenants. However, Secure Score currently treats this null value as “disabled” rather than marking it as “Not applicable.” This causes inaccurate security recommendations and score impact.
In Microsoft Entra Identity Secure Score, recommendations are tailored to your tenant’s configuration and are scored based on how well your environment aligns with Microsoft’s security best practices. Some recommendations may appear even when they are not applicable to your setup. Although you can dismiss such recommendations, they may still influence your overall score, which can cause confusion.
Please consider the following steps to effectively understand and manage this situation:
Review Your Secure Score Dashboard: Secure Score aggregates security findings into a score to help you assess your security posture across subscriptions. You can view detailed recommendations, including those related to synchronization, in the Microsoft Entra admin center under Identity Secure Score or in Microsoft Defender for Cloud.
Interpret Null onPremisesSyncEnabled Correctly: Recognize that a null value for onPremisesSyncEnabled means no on-premises synchronization is configured and that this state should ideally be considered “Not applicable” and not “disabled.”
Manage Recommendations: Dismiss recommendations that do not apply to your environment. Note that dismissed recommendations may still appear in your score calculations, but the Microsoft Entra portal provides options to set certain improvement actions as “ignored” or “risk accepted,” which excludes them from scoring.
Focus on Relevant Security Controls: Prioritize recommendations based on their impact and relevance to your environment. Microsoft’s secure score focuses on key security controls such as enabling MFA, managing access and permissions, and protecting against vulnerabilities, which have a greater effect on improving your security posture.
Understand Scoring Mechanisms: The score updates periodically based on your security configuration. Partial compliance with a recommendation is reflected in partial points. The score is not an absolute risk measure but an indicator of your alignment with best practices.
For detailed information, please refer to the official Microsoft documentation on secure score in Defender for Cloud and Identity Secure Score in Microsoft Entra:
By understanding these nuances, you can better interpret and manage your Secure Score and focus on security improvements that are meaningful to your environment.
Please click "Accept as Answer" if this resolves your issue. This will help others experiencing similar challenges find the solution.