FAQ - Frequently Answered Questions

Administration

(GHES+GHEC) How do I order a GitHub Organization?

Question: How do I order a GitHub Organization?

Answer: An organization is granted for each organizational unit of the University of Bern. The prerequisite is a technical group in Active Directory. The naming convention and organization administration are based on this. The OU admins are authorized to order an organization and will be registered as its administrators accordingly.

Please submit the organization order via Service Request. Select “GitHub Enterprise” as the technical service.

(GHES) Users cannot be found

Question: Why can some accounts of my organizational unit be found while others cannot?

Answer: Authentication on GHES is done via EntraID. Accounts are created upon their first login and can only be found and invited to an organization or team from that point on. Those who can be found have already logged in to https://github.unibe.ch at least once.
The missing accounts need to be contacted and asked to perform their initial login.

(GHES) Switching from a Student to an Employee CAMPUS Account

Question: I have already logged in at github.unibe.ch with my student email address. Now I have a new CAMPUS account with a new email address. How can I log in at github.unibe.ch?

Answer: On GHES, an account can only be identified by one email address. If this email changes (due to a switch from a student to an employee account), a ticket must be created via the Service Portal.

Billing/Price (GHEC)

Question: What costs are charged for GitHub products (GHEC)?

Answer: The IT Services of the University of Bern receive a monthly consolidated invoice from Microsoft covering the costs incurred by all organizations that belong to the university-of-bern enterprise.
Independently of this, the IT Services calculate an invoice for each organizational unit based on the usage data provided by Microsoft and the price list shown below.

Billing is carried out on a monthly basis. Accordingly, the invoice is routed via eForms to the cost center specified by the organization and must be approved there.

Product	Item	Unit	Price per Unit (CHF)
Actions	actions_linux	minutes	0.006
Actions	actions_linux_2_core_advanced	minutes	0.006
Actions	actions_macos	minutes	0.062
Actions	actions_self_hosted_linux	minutes	0
Actions	actions_storage	gigabyte-hours	0.00033602
Actions	actions_windows	minutes	0.01
Codespaces	codespaces_compute_d2	hours	0.18
Codespaces	codespaces_prebuild_storage	gigabyte-hours	0.07
Codespaces	codespaces_storage	gigabyte-hours	0.07
Copilot	coding_agent_ai_credit	ai-credits	0.01
Copilot	copilot_ai_credit	ai-credits	0.01
Copilot	copilot_enterprise	user-months	39
Copilot	copilot_for_business	user-months	19
Git LFS	git_lfs_bandwidth	gigabytes	0.0875
Git LFS	git_lfs_storage	gigabyte-hours	0.000094086
Packages	packages_bandwidth	gigabytes	0.5
Packages	packages_storage	gigabyte-hours	0.00033602

GitHub Copilot

(GHEC) Seats and license types

Question: What license types does GitHub Copilot offer and what do they include?

Answer: For enterprises, you can choose between the plans “Copilot Business” and “Copilot Enterprise”. A seat is allocated per user and billed monthly. The choice of plan applies to all seats in an organization; mixing plans is not possible. The plan should be chosen based on the required features and price. The following documents are helpful:

• Plan comparison
• Choosing your enterprise’s plan for GitHub Copilot

(GHEC) License management

Question: How are GitHub Copilot seats assigned to users?

Answer: Assigning GitHub Copilot seats is the responsibility of the organization owner and is described in detail in the GitHub documentation on the page Setting up GitHub Copilot for your organization.
As described there, activation of GitHub Copilot must first be requested from the IT services via ticket. The following information is required:

• Name of the GitHub organization
• OU abbreviation
• Cost center (REF-XYZ-AB) for billing

(GHEC) Costs and budgets

Question: What costs arise for the organization?

Answer: First, each seat has a fixed monthly price, see Plan comparison. Once the plan’s included credits are exhausted, further usage is billed continuously based on consumption.

Question: What safeguards prevent excessive costs?

Answer: Budgets can be set up to ensure costs do not get out of hand, see

• Setting up budgets to control spending for products with usage-based billing

(GHEC) Billing modalities

Question: How does billing of GitHub Copilot seats and costs work?

Answer: As described above, these costs are included in the monthly GitHub cost invoice.