Azure / Azure/azure-rest-api-specs
Identifying GitHub Enterprise License Users via Azure DevOps API
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
### API Spec link
(https://vsaex.dev.azure.com/%7Borganization%7D/_apis/userentitlements?top=10000&api-version=4.1-preview.1
### API Spec version
7.1
### Describe the bug
Identifying GitHub Enterprise License Users via Azure DevOps API
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!
Environment
### Expected behavior
"licenseDisplayName": "Github Enterprise",
### Actual behavior
"licensingSource": "account",
"accountLicenseType": "express",
"msdnLicenseType": "none",
"gitHubLicenseType": "none",
"licenseDisplayName": "Basic",
"status": "active",
"statusMessage": "",
"assignmentSource": "none"
### Reproduction Steps
we are using API can't do much at our end.
### Environment
_No response_
Contributor guide
Research direction
Start with the Azure DevOps User Entitlements API URL and API version cited in the issue, then compare the reported license fields with the expected GitHub Enterprise value. Done means establishing whether the API exposes a reliable GitHub Enterprise distinction and recording the supported behavior or required API change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- api
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100