Connect Microsoft 365 Admin Center to GitHub Copilot
Give GitHub Copilot governed access to Microsoft 365 Admin Center’s 1 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Microsoft 365 Admin Center to GitHub Copilot in four steps
Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.
- 1
Approve Microsoft 365 Admin Center in Runlayer
Add Microsoft 365 Admin Center from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot to Runlayer
GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Microsoft 365 Admin Center’s 1 tool through the plugin’s search and execute tools.
GitHub Copilot setup guide - 3
Sign in to Microsoft 365 Admin Center
Each user signs in to Microsoft 365 Admin Center with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Microsoft 365 Admin Center from GitHub Copilot
Microsoft 365 Admin Center’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.
Tools
1 Microsoft 365 Admin Center tools in GitHub Copilot
Runlayer policy decides which of these GitHub Copilot users can call.
Bulk add user
Add/create unlicensed users in bulk to the tenant.
Control
What Runlayer can see and stop in GitHub Copilot
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.
Gateway policy (available)
Every Microsoft 365 Admin Center call from GitHub Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.
Frequently asked questions
Connect more