Connecting an Azure subscription

Wenn Sie am oder nach dem 1. August 2024 eine Testversion von GitHub Enterprise Cloud erstellt haben, verwenden Sie die nutzungsbasierte Abrechnung, um Ihre Lizenzen zu bezahlen. Bei nutzungsbasierter Abrechnung bezahlen Sie für die Anzahl der Lizenzen, die Sie jeden Monat verwenden. Sie müssen keine vordefinierte Anzahl von Lizenzen im Voraus kaufen.

About connection of an Azure subscription

You can pay for usage of GitHub features through Azure by connecting an Azure Subscription ID to your organization or enterprise account on GitHub.com.

In this article, the instructions that you must follow to connect an Azure subscription depend on whether your company uses a single organization or an enterprise account on GitHub.com. For more information about the differences between these two types of accounts, see Arten von GitHub-Konten.

If you use GitHub Enterprise Cloud through a Microsoft Enterprise Agreement, connecting an Azure subscription is the only way to use GitHub Advanced Security, GitHub Codespaces, or GitHub Copilot, or to use GitHub Actions, Git Large File Storage (LFS), or GitHub Packages beyond your plan's included amounts.

About usage-based billing on GitHub

GitHub provides usage-based billing for the following products.

• GitHub Actions, see GitHub Actions billing
• GitHub Codespaces, see GitHub Codespaces billing
• GitHub Packages, see GitHub Packages billing
• Git Large File Storage, see Git Large File Storage billing

In addition, usage-based billing is available for the following licenses

• GitHub Enterprise, see Billing for GitHub Enterprise
• GitHub Copilot, see GitHub Copilot billing
• GitHub Advanced Security, see GitHub Advanced Security billing

For information about controlling spending, see Setting up budgets to control spending on metered products.

About billing through Azure

If you link your GitHub account to Azure, any usage-based costs starting from that point will be billed through Azure and charged on the 1st of each month. However, remaining GitHub charges, for example charges for your GitHub plan, will still be billed on your usual billing date.

For example, you link your Azure subscription to your organization or enterprise account on June 16th and you also have a GitHub Copilot Business subscription. From that date onwards, any usage costs for Copilot Business will be included in your Azure bill and charged on July 1st. However, any charges incurred before June 16th for Copilot Business will be billed separately through GitHub on your account's usual billing date.

Prerequisites

• You must have either an organization or an enterprise account on GitHub.com. For more information about the differences between these two types of accounts, see Arten von GitHub-Konten.

  If the organization you want to connect an Azure subscription to belongs to an enterprise account, you must connect your Azure subscription to the enterprise account, not the organization.

• You must be an owner of the organization or enterprise account. See the following articles.

  • Rollen in einer Organisation
  • Rollen in einem Unternehmen

• You must be logged into Azure as a user who is able to provide tenant-wide admin consent, which is required to install GitHub's Subscription Permission Validation app on the Azure AD tenant. The app requires read access to display a list of available subscriptions, and is only used during this one-time process of connecting the Azure subscription. See Grant tenant-wide admin consent to an application in Microsoft Docs.

  • Alternatively, before following the instructions in this article, users who are not able to provide tenant-wide admin consent can work with an Azure AD global administrator to configure an admin consent workflow. See User and admin consent in Azure Active Directory in Microsoft Docs.

    Hinweis

    If your tenant provides user consent settings, users included in those settings might not require admin consent to install GitHub's Subscription Permission Validation app. See User consent in Microsoft Docs.

• To select an Azure subscription from the list of available subscriptions, the user must be an owner of the Azure subscription. See Assign a user as an administrator of an Azure subscription in Microsoft docs.

• You must know your Azure subscription ID. See Get subscription and tenant IDs in the Azure portal in the Microsoft Docs or contact Azure support.

Video demonstration of connecting a subscription

To connect an Azure subscription, you'll need appropriate access permissions on both GitHub and the Azure billing portal. This may require coordination between two different people.

To see a demo of the process from beginning to end, see Billing GitHub consumption through an Azure subscription on GitHub's YouTube channel. This video demonstrates the process for an enterprise account. If you're connecting a subscription to an organization account, see Connecting your Azure subscription to your organization account.

Connecting your Azure subscription to your enterprise account

To connect your Azure subscription, you must have owner permissions to the Azure subscription and be an enterprise owner on GitHub.

1. Klicke auf GitHub in der oberen rechten Ecke auf dein Profilfoto.

2. Klicke je nach deiner Umgebung auf Dein Unternehmenoder auf Deine Unternehmen, und klicke dann auf das Unternehmen, das du anzeigen möchtest.

3. Klicke oben auf der Seite auf Billing and licensing (sichtbar bei Verwendung der neuen Abrechnungsplattform). Klicke alternativ auf Settings und dann auf Billing.

4. Klicke unter „Billing & Licensing“ (neue Plattform) oder „Billing“ auf Payment information.

5. Under "Payment Information", click Add Azure Subscription.

6. To sign in to your Microsoft account, follow the prompts.

7. Review the "Permissions requested" prompt. If you agree with the terms, click Accept.

   Wenn keine Eingabeaufforderung „Berechtigungen angefordert“ angezeigt wird und stattdessen eine Meldung angezeigt wird, die angibt, dass du eine Administratorgenehmigung benötigst, lies Meldung: "Administratorgenehmigung erforderlich".

8. Under "Select a subscription", select the Azure subscription ID that you want to connect to your enterprise. Um ein Azure-Abonnement auswählen zu können, musst du über Besitzerberechtigungen für das Abonnement verfügen. Wenn der Standardmandant nicht über die richtigen Berechtigungen verfügt, musst du möglicherweise eine andere Mandanten-ID angeben. Weitere Informationen findest du unter Voraussetzungen und Microsoft Identity Platform und der OAuth 2.0-Autorisierungscodeflow in der Microsoft-Dokumentation.

9. Wählen Sie Indem Sie auf „Verbinden“ klicken, bestätigen Sie, dass Sie über das ausgewählte Azure-Abonnement für gebührenpflichtige Dienste abgerechnet werden möchten.

10. Klicke auf Verbinden.

Disconnecting your Azure subscription from your enterprise account

After you disconnect your Azure subscription from your enterprise account, your usage can no longer exceed the amounts included with your plan.

1. Klicke auf GitHub in der oberen rechten Ecke auf dein Profilfoto.

2. Klicke je nach deiner Umgebung auf Dein Unternehmenoder auf Deine Unternehmen, und klicke dann auf das Unternehmen, das du anzeigen möchtest.

3. Klicke oben auf der Seite auf Billing and licensing (sichtbar bei Verwendung der neuen Abrechnungsplattform). Klicke alternativ auf Settings und dann auf Billing.

4. Klicke unter „Billing & Licensing“ (neue Plattform) oder „Billing“ auf Payment information.

5. Under "Azure subscription", to the right of the subscription ID you want to disconnect, click .

6. Review the prompt, then click Remove.

Troubleshooting connection of an Azure subscription

You can troubleshoot some common issues with connection of an Azure subscription to your account on GitHub.

Message: "Need admin approval"

If the user account you used to sign into Azure does not have adequate permissions to install the app that GitHub uses to connect a subscription, you'll see a message with the following text.

Need admin approval

GitHub Inc needs permission to access resources in your organization that only an admin can grant. Please ask an admin to grant permission to this app before you can use it.

To avoid this message when you try again, you must either ensure that the Azure user can provide tenant-wide admin consent, or you must work with an Azure administrator to configure the admin consent workflow. For more information, review Prerequisites.

Frequently asked questions about Azure subscriptions

The following are answers to some common questions about connecting an Azure subscription to your account on GitHub.

Can I connect more than one enterprise or cost center to the same Azure subscription?

Yes. There’s no limit to the number of enterprises or cost centers you can connect to a single Azure subscription. For details on how charges are applied to cost centers, see Using cost centers to allocate costs to business units.

Can I connect multiple Azure subscriptions to one enterprise?

Yes. You can connect multiple Azure subscriptions to a single enterprise account by creating cost centers. Cost centers let you allocate metered usage across different Azure subscriptions.

How are charges split in Azure for multiple enterprises?

Azure usage is separated by SKU and either enterprise ID or cost center ID. The format used is enterprise:sku or costcenter:sku.

What happens if I don’t assign an Azure subscription to a cost center?

Charges will fall back to the enterprise-level Azure subscription. This also happens if a cost center becomes invalid or is deleted—any future usage from those resources is billed to the enterprise-level subscription.

Can billing managers connect to Azure subscriptions?

Yes. Billing managers for organizations or enterprises can connect Azure subscriptions.

Can I use metered products during an Enterprise Managed User trial without connecting an Azure subscription?

Yes. During an Enterprise Managed User trial, you can use metered products up to the included limits. To exceed the included limits, you’ll need to link an Azure subscription.

What should I do if I see a banner saying my Azure ID is missing?

If you see this banner, it means your Azure payment method information is missing. To avoid service interruptions for your enterprise or organization, make sure to add this information before the date provided in the alert.

If you have questions or if you believe you are seeing this banner by mistake, contact GitHub-Support.