You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/library/overview/release-notes/2026-q2.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,9 +2,9 @@
2
2
3
3
## 2026 Q2
4
4
5
-
-**New Content: [Governing agents in GitHub Enterprise](/library/governance/recommendations/governing-agents/)** - Published governance and policy guidance for managing GitHub Copilot agents across the enterprise, covering policy configuration, security boundaries, MCP server governance, and audit pipelines
6
-
-**New Content: [Essentials of governance and administration with GitHub Enterprise](/library/governance/recommendations/governance-administration-essentials/)** - Published a comprehensive guide for enterprise governance and administration fundamentals, covering GitHub structural components, user access models, org architecture strategies, policy baselines, and operational topics such as integrations, roles, and audit logging
7
-
-**New Content: [Managing AI credits](/library/governance/recommendations/managing-ai-credits/)** - Published a FinOps-oriented guide for governing AI credit consumption across GitHub Enterprise, covering layered budgets design, cost attribution, usage guidance, and an operating cadence
5
+
-**New Content: [Governing agents in GitHub Enterprise](../governance/recommendations/governing-agents)** - Published governance and policy guidance for managing GitHub Copilot agents across the enterprise, covering policy configuration, security boundaries, MCP server governance, and audit pipelines
6
+
-**New Content: [Essentials of governance and administration with GitHub Enterprise](../governance/recommendations/governance-administration-essentials)** - Published a comprehensive guide for enterprise governance and administration fundamentals, covering GitHub structural components, user access models, org architecture strategies, policy baselines, and operational topics such as integrations, roles, and audit logging
7
+
-**New Content: [Managing AI credits](../governance/recommendations/managing-ai-credits)** - Published a FinOps-oriented guide for governing AI credit consumption across GitHub Enterprise, covering layered budgets design, cost attribution, usage guidance, and an operating cadence
8
8
-**Deprecated: Managing GitHub Copilot Premium Request Units (PRUs)** - Retired the PRU enterprise admin playbook, replaced by the managing AI credits guidance
9
-
-**New Content: [Governing agentic workflows with gh-aw and APM](/library/governance/recommendations/governing-agentic-workflows/)** - Published guidance for enterprises adopting sandboxed AI agents, GitHub Agentic Workflows (gh-aw), and Agent Package Manager (APM) to enforce execution isolation, dependency governance, and auditable agent runs in regulated environments
10
-
-**Update: [Defending against dependency supply chain attacks](/library/application-security/recommendations/managing-dependency-threats/)** - Expanded trusted publishing registry coverage to include NuGet and Crates alongside npm, PyPI, and RubyGems
9
+
-**New Content: [Governing agentic workflows with gh-aw and APM](../governance/recommendations/governing-agentic-workflows)** - Published guidance for enterprises adopting sandboxed AI agents, GitHub Agentic Workflows (gh-aw), and Agent Package Manager (APM) to enforce execution isolation, dependency governance, and auditable agent runs in regulated environments
10
+
-**Update: [Defending against dependency supply chain attacks](../application-security/recommendations/managing-dependency-threats)** - Expanded trusted publishing registry coverage to include NuGet and Crates alongside npm, PyPI, and RubyGems
Copy file name to clipboardExpand all lines: content/library/productivity/recommendations/adopting-copilot-at-scale.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,19 +22,19 @@ areas:
22
22
# Classifications of industries who may be at different stages of the customer journey.
23
23
verticals:
24
24
- automotive
25
-
- manufacturing
25
+
- education
26
+
- energy
26
27
- finance
27
28
- gaming
28
-
- media
29
29
- government
30
-
- information-technology
31
30
- healthcare
31
+
- hospitality
32
+
- information-technology
33
+
- manufacturing
34
+
- media
35
+
- professional-service
32
36
- retail
33
-
- education
34
-
- energy
35
37
- telecommunications
36
-
- hospitality
37
-
- professional-services
38
38
39
39
# Individuals in key roles on the customer journey, typically consisting of one or more administrators and the end-user community.
40
40
personas:
@@ -111,7 +111,7 @@ An example GitHub Copilot launch plan should include the following minimum eleme
111
111
#### Launch week (week 0)
112
112
113
113
- Communicate the opportunity, benefits, and availability of GitHub Copilot to your organization
114
-
- Provide on-demand [training](https://learn.microsoft.com/en-us/training/modules/introduction-to-github-copilot/) and [resources](https://docs.github.com/en/enterprise-cloud@latest/copilot/quickstart) for users to get started with GitHub Copilot
114
+
- Provide on-demand [training](https://learn.microsoft.com/en-us/training/modules/introduction-to-github-copilot/) and [resources](https://docs.github.com/en/enterprise-cloud@latest/copilot/get-started/quickstart) for users to get started with GitHub Copilot
115
115
116
116
#### Post-launch (weeks 1-4)
117
117
@@ -122,7 +122,7 @@ An example GitHub Copilot launch plan should include the following minimum eleme
122
122
#### Post-launch (weeks 5-8)
123
123
124
124
- Monitor GitHub Copilot adoption and activity metrics
125
-
- Develop a GitHub Copilot reporting mechanism to track KPIs and derive meaningful insights about GitHub Copilot by using the [Copilot Usage API](https://docs.github.com/en/enterprise-cloud@latest/rest/copilot/copilot-usage?apiVersion=2022-11-28) and [Copilot User Management API](https://docs.github.com/en/enterprise-cloud@latest/rest/copilot/copilot-user-management?apiVersion=2022-11-28)
125
+
- Develop a GitHub Copilot reporting mechanism to track KPIs and derive meaningful insights about GitHub Copilot by using the [Copilot usage metrics API](https://docs.github.com/en/enterprise-cloud@latest/rest/copilot/copilot-usage-metrics?apiVersion=2022-11-28) and [Copilot User Management API](https://docs.github.com/en/enterprise-cloud@latest/rest/copilot/copilot-user-management?apiVersion=2022-11-28)
126
126
- Build on your GitHub Copilot Expert Hub with advanced training and resources specific to your organization
127
127
- Gather feedback from users and iterate on your GitHub Copilot program
128
128
@@ -146,7 +146,7 @@ GitHub offers many free resources to help users get started with GitHub Copilot:
To best prepare your existing team and future hires, consider offering a mix of instructor-led and on-demand Copilot enablement resources.
152
152
@@ -184,10 +184,10 @@ GitHub Copilot licenses can be assigned in a few different ways, each with their
184
184
3) Specific teams in an organization
185
185
4) Specific teams in an enterprise
186
186
187
-
While assigning licenses out of a single organization can simplify license management, it restricts the granularity of Copilot telemetry data from the [Copilot Usage API endpoint for organizations](https://docs.github.com/en/enterprise-cloud@latest/rest/copilot/copilot-usage?apiVersion=2022-11-28#get-a-summary-of-copilot-usage-for-organization-members).
187
+
While assigning licenses out of a single organization can simplify license management, it restricts the granularity of Copilot telemetry data from the [Copilot usage metrics API](https://docs.github.com/en/enterprise-cloud@latest/rest/copilot/copilot-usage-metrics?apiVersion=2022-11-28#get-copilot-organization-usage-metrics).
188
188
If you would like to track GitHub Copilot usage across your GitHub Organizations, consider assigning licenses to specific teams or individuals in those organizations.
189
189
190
-
<!-- PLACEHOLDER FOR COPILOT USAGE API ENDPOINT FOR TEAMS TRADE-OFFS -->
190
+
<!-- PLACEHOLDER FOR COPILOT USAGE METRICS API ENDPOINT FOR TEAMS TRADE-OFFS -->
191
191
192
192
{{< callout type="info" >}}
193
193
When a user receives a seat from multiple organizations in the same enterprise, GitHub takes care of deduplicating these seats before billing for the user.
0 commit comments