Configuration des abonnements Visual Studio avec GitHub Enterprise

Visual Studio subscriptions with GitHub Enterprise is a combined offering from Microsoft that allows a subscriber to use both Visual Studio and GitHub Enterprise. See About Visual Studio subscriptions with GitHub Enterprise.

Prerequisites

• Your team's Visual Studio subscription must include GitHub Enterprise. For more information, see:

  • Visual Studio Subscriptions and Benefits on the Visual Studio website
  • Overview of admin responsibilities in Microsoft Docs.

• Your team must have an enterprise on GitHub, see About enterprise accounts.

  • If you're not sure whether your team has an enterprise, contact your GitHub administrator.
  • If you're not sure who on your team is responsible for GitHub services, contact GitHub's Sales team.

Setting up Visual Studio subscriptions with GitHub Enterprise

To set up Visual Studio subscriptions with GitHub Enterprise, members of your team must complete the following tasks.

One person may be able to complete the tasks because the person has all of the roles, but you may need to coordinate the tasks with multiple people. For more information, see Roles for Visual Studio subscriptions with GitHub Enterprise reference.

1. A GitHub enterprise owner must create at least one organization in your enterprise. For more information, see Adding organizations to your enterprise.

2. The Visual Studio subscription admin must assign a license for Visual Studio to a subscriber in the administrator portal for Visual Studio subscriptions. For more information, see Overview of the Visual Studio Subscriptions Administrator Portal and Assign Visual Studio Licenses in the Visual Studio Subscriptions Administration Portal in Microsoft Docs.

3. Optionally, if the Visual Studio subscription admin assigned licenses to subscribers in Visual Studio before adding GitHub Enterprise to the subscription, the subscription admin can move the subscribers to the combined offering in the Visual Studio administration portal. For more information, see Manage Visual Studio subscriptions with GitHub Enterprise in Microsoft Docs.

4. If the Visual Studio subscription admin has not disabled email notifications, the subscriber will receive two confirmation emails. For more information, see Visual Studio subscriptions with GitHub Enterprise in Microsoft Docs.

5. A GitHub organization owner must invite the subscriber to the organization created in step 1. The subscriber can accept the invitation with an existing personal account or create a new account. After the subscriber joins the organization, the subscriber becomes an enterprise member. For more information, see Inviting users to join your organization.

   Conseil

   • While not required, we recommend that the organization owner sends an invitation to the same email address used for the subscriber's User Primary Name (UPN). When the email address on GitHub matches the subscriber's UPN, you can ensure that another enterprise does not claim the subscriber's license.
   • If the subscriber accepts the invitation to the organization with an existing personal account on GitHub, we recommend that the subscriber add the email address they use for Visual Studio to their personal account on GitHub. For more information, see Adding an email address to your GitHub account.
   • If the organization owner must invite a large number of subscribers, a script may make the process faster. For more information, see the sample PowerShell script in the github/platform-samples repository.

6. If any enterprise members aren't automatically matched to their Visual Studio account, an enterprise owner can match the accounts manually on GitHub. See Reconciling users across Visual Studio and GitHub.

After Visual Studio subscriptions with GitHub Enterprise is set up for subscribers on your team, enterprise owners can review licensing information on GitHub. For more information, see Viewing usage for your GitHub Enterprise plan.

Reconciling users across Visual Studio and GitHub

To stay compliant with the terms of use, a GitHub enterprise owner should ensure all user accounts are correctly matched across GitHub and Visual Studio.

Most users are automatically matched across GitHub and Visual Studio. If a user has different email addresses in GitHub and Visual Studio, you may need to match the accounts manually.

Under the terms of use, the GitHub account and Visual Studio account for a single license must belong to the same person.

1. Audit user mappings

To audit your user mappings, download a summary of assigned users from the Visual Studio portal, and compare it against the verified emails of users in your GitHub enterprise. See Viewing people in your enterprise.

2. Match users to Visual Studio

When you've identified GitHub users who aren't correctly matched to their Visual Studio account, you can update the mappings on GitHub. You can't update mappings for users who have been automatically matched.

1. Go to your enterprise on GitHub and click Billing and licensing.
2. In the left sidebar, click Licensing.
3. On the Licensing page, next to "Enterprise Cloud", click Manage.
4. In the list of users, look for users with an "Enterprise" license type. These are enterprise members that aren't matched to a user in your Visual Studio subscription.
5. To match a user to their Visual Studio account, click , then click Change to Visual Studio license.
6. Select the user's Visual Studio login email, then click Confirm change.

Viewing available licenses

You can view the number of GitHub Enterprise licenses available to your enterprise on GitHub.com. The list of pending invitations includes subscribers who are not yet members of at least one organization in your enterprise. For more information, see Viewing usage for your GitHub Enterprise plan and Viewing people in your enterprise.

You can also see pending GitHub Enterprise invitations to subscribers in the administrator portal for Visual Studio subscriptions.

Further reading

• Getting started with GitHub Enterprise Cloud