Multi-Instance Support Cloud Apps

Muti-instance support lets you connect and manage multiple instances of Cloud Apps within a single tenant.

Currently mutli-instance is supported for multiple GitHub organizations only.

Managing Multiple GitHub Organizations in CASB

Modern enterprises often operate across multiple GitHub organizations - whether due to mergers and acquisitions, regional segmentation, or separating production and sandbox environments. To support these complex environments, CASB enables customers to connect and manage multiple GitHub instances within a single tenant.

This capability provides unified visibility and control across all GitHub orgs, helping security teams streamline operations and strengthen governance.

Key Benefits

  • Centralized Security & Compliance: Gain unified visibility into access, audit logs, and policy enforcement across all GitHub orgs - from a single pane of glass.

  • Operational Efficiency: Manage multiple GitHub orgs without switching between tenants or duplicating configurations. Reduce overhead and simplify administration.

  • Scalability: Support growing organizational structures with flexible instance management — ideal for enterprises with regional teams or multiple business units.

How It Works

Connecting Multiple GitHub Instances

Admins can now onboard multiple GitHub organizations directly from the Cloud Applications page in CASB:

  1. Navigate to CASB > Cloud Applications

  2. Select GitHub.

  3. Click + Instance to add a new GitHub org.

  4. Provide credentials and configure sync settings.

  5. Repeat for additional GitHub orgs.

Each instance is displayed in a grouped view, showing connection status, instance name, and first connected time.

Policy & Monitoring

To make is easier to investigate incidents and track behavior across different GitHub orgs the following are now available:

  • Alerts now include the instance name for easier triage.

  • Security teams can filter activities by: Instance Name (user-defined), Instance ID (system-generated).

Migration Considerations for Existing GitHub Integrations

If your tenant already has an existing GitHub instance connected:

Action Required: You must delete the existing GitHub instance and re-onboard all GitHub organizations using the new multi-instance flow. This ensures compatibility with the updated backend schema and enables full visibility and control across multiple GitHub orgs.

Data Preservation: Existing activity and files from the previous instance will remain accessible via Workbench and post consolidation, the rules will apply to all of the GitHub integration instances.

If your tenant does not currently have any GitHub instances connected:

No Action Required: You can begin onboarding multiple GitHub organizations directly using the new flow from the Cloud Applications page.

For assistance with migration planning or questions about the new multi-instance architecture, contact your Proofpoint representative.

User Experience Enhancements

The Cloud Applications page has been redesigned to support the following capabilities:

  • New filters for Instance Name and Instance Connectivity Status

  • Improved layout showing all connected GitHub orgs in a grouped format

  • Easy access to onboarding guides and instance-level actions

Related Topic:

Cloud Applications