Bi-directional sync missing in Defender for Cloud (Tenant-Based) connector in Sentinel?

You’ve raised some really valid points here. From what I’ve seen in the rollout notes, the bi-directional sync feature for the Defender for Cloud (Tenant-Based) connector in Sentinel is still being deployed gradually across tenants and regions, so it’s not unusual that the toggle doesn’t appear everywhere yet.

A couple of things worth checking:

Permissions – Ensure you’re using an account with both Security Admin / Security Reader and Sentinel Contributor rights. Limited permissions can sometimes hide connector settings.

Region / Workspace type – Some features roll out to specific regions or workspace SKUs first before reaching all tenants globally.

Connector refresh – Removing and re-adding the connector may help, but in most cases it’s just a matter of waiting for the backend deployment to complete.

If it’s already listed as GA, then yes, it should eventually appear across all subscriptions without extra steps. At this point, I’d suggest monitoring the Azure Updates page or the Sentinel release notes to track the rollout status. If you still don’t see the option after a while, opening a support ticket with Microsoft might clarify whether your tenant is included in the current wave.

In short: it’s most likely a phased deployment, not a misconfiguration on your side.