[Question][AzureDevOps] handling deprecation og all organisation access tokens

[wouldd]

Question

I note that microsoft have announced that they are deprecatine PATs with 'all available organisations' access - which the devlake documentation currently says is required.
Is this already handled or on a radar somewhere?
I'm not entirely sure why devlake required all available orgs in the first place, but after March we will no longer be able to provide a token with that level of access.

Additional context

Microsoft announcement here: https://devblogs.microsoft.com/devops/retirement-of-global-personal-access-tokens-in-azure-devops/

[dosubot]

DevLake's codebase already supports organization-scoped Azure DevOps PATs—the requirement for "all available organisations" is just in the documentation and UI, not a technical limitation. You can use an organization-scoped PAT by specifying the organization in the connection settings. The backend will use the PAT for that specific org, and there are no hidden dependencies on global PATs in the code (source, source).

However, there are currently no issues or PRs tracking the upcoming deprecation or updating the docs/UI to reflect this, so the guidance hasn't caught up yet (source, source). For now, you can safely use organization-scoped PATs with DevLake by entering your org name in the connection config. It would be a good idea for the project to update the documentation and UI to clarify this before the deprecation deadline.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[github-actions]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

[github-actions]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.

[cfarrend]

@dosu When using an organization-scoped token, I get taken to this page on set up when testing the connection

"Sign in to DevLake
Single Sign-On is not configured. Use an API key (Authorization: Bearer ...) to access /rest endpoints, or ask your administrator to enable OIDC."

If I do it with "All Accessible Organizations", it works.

Version: v1.0.3-beta14