Azure / Azure/azure-rest-api-specs

Identifying GitHubEnterprise license is not happening

Open
#33,726 0 comments 0 reactions 0 assignees View on GitHub
customer-reported DevOps feature-request question Service Attention
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
3d 2h
Merged PRs (30d)
424

Description

### API Spec link

[https://vsaex.dev.azure.com/{organization}/_apis/userentitlements?top=10000&api-version=4.1-preview.1](https://vsaex.dev.azure.com/%7Borganization%7D/_apis/userentitlements?top=10000&api-version=4.1-preview.1)

### API Spec version

7.1

### Please describe the feature.

API Spec link
[https://vsaex.dev.azure.com/{organization}/_apis/userentitlements?top=10000&api-version=4.1-preview.1](https://vsaex.dev.azure.com/%7Borganization%7D/_apis/userentitlements?top=10000&api-version=4.1-preview.1)

API Spec version
7.1

Question/Query
We are using the User Entitlements API in Azure DevOps to retrieve user license details. However, we noticed that GitHub Enterprise users are being shown with "Basic + Direct" under accountLicenseType.

[https://vsaex.dev.azure.com/{organization}/_apis/userentitlements?top=10000&api-version=4.1-preview.1](https://vsaex.dev.azure.com/%7Borganization%7D/_apis/userentitlements?top=10000&api-version=4.1-preview.1)

Currently, there is no clear way to distinguish GitHub Enterprise license users from regular Azure DevOps users via this API.

Questions:
Is there an existing API or feature that can accurately identify GitHub Enterprise license users within Azure DevOps?

Are there any upcoming updates planned to include this capability in the API?

Any insights or guidance on this would be greatly appreciated!

Thanks!

Contributor guide

Open the contributing guide

Research direction

Start with the User Entitlements API specification linked in the issue and inspect how accountLicenseType is defined and populated. Determine whether the documented API supports distinguishing GitHub Enterprise users; done means an accepted API change or clear documentation of the supported identification path.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, openapi
Domain
api, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.