Azure DevOps
Boards, repos, pipelines, and planning in one engineering workspace.
Integration features
Members will click “Open Project” on your portalry to launch Azure DevOps. Use this checklist to give them a smooth landing every time.
Portalry recognises dev.azure.com URLs and uses the project segment in the link as the portal name fallback.
What Portalry handles for you
- Detects links in the format /{organization}/{project}/...
- Uses the second URL segment (project name) when metadata is unavailable.
- Keeps one stable entry point for boards, repos, and sprint planning.
Setup checklist
- Copy your project URL (for example, https://dev.azure.com/BibleSocietyDevelopment/Digital%20Ezra%20(Product)).
- You can also use deeper links (for example, boards URLs) and Portalry still maps the project name from the same URL.
- Confirm invitees have Azure DevOps access before sharing the portal publicly.
What still lives in the platform
- Portalry cannot manage Azure DevOps memberships, permissions, or work items.
- Pipelines, repos, and boards stay fully managed inside Azure DevOps.
Extras & best practices
- Include a quick description in Portalry for which team board/backlog members should open first.