Microsoft Defender for Cloud Apps
Cloud and workloads

Release Notes

In brief

The GitHub connector now supports Organization-level and Enterprise-level connections. An Enterprise connection covers all organizations in the enterprise and improves visibility and protection against identity-driven attacks, including device code phishing targeting GitHub Copilot CLI.

What Defender admins need to know

Admins can centralize onboarding, eliminate per-organization connector setup, and improve coverage. Creating a new Enterprise-level connector is strongly recommended, but not required by the update.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

For news about earlier releases, see Archive of past updates for Microsoft Defender for Cloud Apps.

November 2026

GitHub connector enhancements (Preview)

The GitHub connector in Microsoft Defender for Cloud Apps now supports both Organization-level and Enterprise-level connections. This update helps security teams centralize onboarding and improve visibility across GitHub Enterprise environments.

We strongly recommend creating a new connector instance and connecting at the Enterprise level. With a single enterprise connection, all organizations in that enterprise are covered, eliminating per-organization connector setup, reducing administrative overhead, and giving defenders full visibility into enterprise-wide GitHub activity.

If you connect at the Enterprise level, you also gain stronger protection against identity-driven attacks in developer workflows, including device code phishing scenarios targeting GitHub Copilot CLI.

For setup guidance, see Protect your GitHub Enterprise environment. For detection and disruption coverage, see Protect AI agents from trusted-identity attacks (Preview).

October 2026

Automatic enablement of SaaS accounts integration with Identity inventory