Enable Microsoft Defender for Servers

The s360 item is likely flagging that Microsoft Defender for Servers (specifically the Defender for Endpoint integration) is not fully enabled for all scenarios in the subscription, even though the main “Endpoint protection” toggle is set to On.

From the configuration shown:

• Enabling Endpoint protection in Defender for Cloud → Environment settings → Settings & monitoring deploys the Defender for Endpoint sensor to supported Windows and Linux machines in the subscription and integrates them with Defender for Cloud.
• For subscriptions that existed before spring 2022 and that have Windows Server 2012 R2 or 2016, there is an additional one‑time step to enable the unified solution for those OS versions.

To clear the s360 item, verify and complete the unified solution enablement:

1. In the Azure portal, go to Defender for Cloud → Environment settings.
2. Select the affected subscription.
3. In the Defender for Servers plan row, in the Monitoring coverage column, select Settings.
4. If Endpoint protections shows Partial, select Fix.
5. Go to Missing components → Unified solution.
6. Select Enable, then Save.
7. In Settings and monitoring, select Continue so Defender for Cloud onboards existing and new machines to Defender for Endpoint.

After this one‑time action, Defender for Endpoint integration for Windows Server 2012 R2/2016 will be fully enabled and the s360 requirement should be satisfied once onboarding completes (which can take up to several hours on the first subscription in a tenant).

References:

• Enable Defender for Endpoint integration in Microsoft Defender for Cloud
• Protect your servers with Defender for Servers