Setting up Visual Studio subscriptions with GitHub Enterprise

Your team's subscription to Visual Studio can also provide access to GitHub Enterprise.

この記事の内容

About setup of GitHub Enterprise を持つ Visual Studio サブスクリプション

GitHub Enterprise を持つ Visual Studio サブスクリプション は、サブスクライバーが Visual Studio と GitHub Enterprise の両方を使用できるように組み合わせて販売されている Microsoft の製品です。 See About Visual Studio subscriptions with GitHub Enterprise.

This guide shows you how your team can get Visual Studio subscribers licensed and started with GitHub Enterprise.

Roles for GitHub Enterprise を持つ Visual Studio サブスクリプション

Before setting up GitHub Enterprise を持つ Visual Studio サブスクリプション, it's important to understand the roles for this combined offering.

RoleServiceDescriptionMore information
Subscriptions adminVisual Studio subscriptionPerson who assigns licenses for Visual Studio subscriptionOverview of admin responsibilities in Microsoft Docs
SubscriberVisual Studio subscriptionPerson who uses a license for Visual Studio subscriptionVisual Studio Subscriptions documentation in Microsoft Docs
Enterprise ownerGitHubPerson who has a personal account that's an administrator of an enterprise on GitHub.comエンタープライズにおける役割
Organization ownerGitHubPerson who has a personal account that's an owner of an organization in your team's enterprise on GitHub.comOrganizationのロール
Enterprise memberGitHubPerson who has a personal account that's a member of an enterprise on GitHub.comエンタープライズにおける役割

Prerequisites

Setting up GitHub Enterprise を持つ Visual Studio サブスクリプション

To set up GitHub Enterprise を持つ Visual Studio サブスクリプション, 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 GitHub Enterprise を持つ Visual Studio サブスクリプション.

  1. An enterprise owner must create at least one organization in your enterprise on GitHub.com. For more information, see エンタープライズへの組織の追加.

  2. The subscription admin must assign a license for Visual Studio to a subscriber in Visual Studio サブスクリプションの管理者ポータル. 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 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 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. An organization owner must invite the subscriber to the organization on GitHub.com from 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 組織参加へのユーザーの招待.

    ヒント

    • 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.com 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.com, we recommend that the subscriber add the email address they use for Visual Studio to their personal account on GitHub.com. For more information, see GitHub アカウントへのメールアドレスの追加.
    • 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 GitHub Enterprise を持つ Visual Studio サブスクリプション is set up for subscribers on your team, enterprise owners can review licensing information on GitHub.com. 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 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.

Further reading