Organisations

Start connecting Azure DevOps

Answers Microsoft's sign-in page for read-only Azure DevOps scopes, with PKCE, and sets the flow's cookie for the callback.

POST/orgs/{org}/connectors/azure-devops/connect

TL;DR

Question	Answer
What does it do?	Start connecting Azure DevOps.
What does it take?	`org` in the path.
What does it return?	Status 200 with a body of type `OrgAzureDevopsConnect`.
What can go wrong?	`401` not signed in; `403` not the owner or an admin (`orgs.forbidden`), or the plan has no trusted publishers (`plan.trusted_publishers_not_included`); `404` no such organisation, or the caller is not a member of it; `429` too many requests; `503` this server has no Microsoft Entra app for the connector (`azure_devops.not_configured`), or cannot keep a token (`connectors.unavailable`). Every failure uses the one error envelope.

Answers Microsoft's sign-in page for read-only Azure DevOps scopes, with PKCE, and sets the flow's cookie for the callback.

Field	Type	Required	Description
`org`	`string`	yes	The organisation's id or its slug.

Status	Meaning	Body
200	Where the browser goes next.	`OrgAzureDevopsConnect`
401	Not signed in.	`ErrorResponse`
403	Not the owner or an admin (`orgs.forbidden`), or the plan has no trusted publishers (`plan.trusted_publishers_not_included`).	`ErrorResponse`
404	No such organisation, or the caller is not a member of it.	`ErrorResponse`
429	Too many requests.	`ErrorResponse`
503	This server has no Microsoft Entra app for the connector (`azure_devops.not_configured`), or cannot keep a token (`connectors.unavailable`).	`ErrorResponse`

A 200 answer has the type OrgAzureDevopsConnect.

Field	Type	Required	Description
`url`	`string`	yes	Microsoft's sign-in page. The browser goes there next.

Doc	Why
API reference	Every endpoint, and the error envelope
Schemas	Every request and response type
Tool reference	The operations as callable tools