The challenge
A development team that needed a secure platform
The client is a Canadian organization with its own in-house development team.
The team wanted GitHub Enterprise Cloud for source control and GitHub Copilot for AI-assisted development, connected securely to the organization's existing corporate identity so developers could sign in the way they already do. It also needed a clear, well-governed baseline its IT team could manage on its own.
Our approach
The engagement covered discovery and design, configuration, and documentation with knowledge transfer.
Design first
BITSUMMIT reviewed the identity setup, the existing repository structure and the developer workstations, then produced a design for the GitHub Enterprise organization, team hierarchy, repository standards, the single sign-on connector and the Copilot enablement approach. The client signed off on the design before any configuration began.
GitHub Enterprise base setup
BITSUMMIT set up the base GitHub Enterprise Cloud organization and hardened its security settings, including visibility, permissions and member privileges.
Sign-in, teams and Copilot
The engagement covered single sign-on through an Entra ID enterprise application registration, teams aligned to development roles with least-privilege repository access, branch protection on primary branches, and GitHub Copilot enablement with organization policies, including code reference settings. Scope also included a Copilot check inside Visual Studio and end-to-end tests of sign-in, clone, commit and push, and Copilot suggestions.
Handover
Scope included as-built documentation, an administrator operations guide and a knowledge-transfer session for the client's IT team.
The outcome
The engagement was designed to deliver:
- One secure place for code. GitHub Enterprise Cloud for the development team, with sign-in through the corporate identity it already uses.
- AI assistance where developers work. GitHub Copilot inside Visual Studio, under organization policies the client controls.
- Guardrails from the start. Role-based teams, least-privilege repository access and branch protection as part of the baseline.
- A foundation to build on. A base the client can extend with later governance and security scanning work.
