Team Spaces

Confluence-style spaces for Azure DevOps projects: a page tree, a rich editor, live blocks, diagrams, page templates, history and comments, with every published page kept as Markdown in Git.

What you get

• Spaces and a page tree. Each space has its own home page, nested pages and folders, icons, labels, starred pages, and search: titles as you type, and the text of every page with Enter.
• A rich editor. Type / for headings, tables, task lists, coloured panels, columns, code with highlighting, images, a table of contents, status and date pickers, @mentions, and diagrams drawn in the page (flowcharts, Azure and AWS shapes).
• Diagrams as code. Mermaid, in its current version with every diagram type (ER, C4, sequence, Gantt, git graph, mind maps…), drawn as you type, with zoom. PlantUML too, through a server you choose.
• Live blocks. Child pages, pages by label, task and decision reports and roadmaps keep themselves up to date, and so do blocks showing work items from a query (as a table or a chart), work item cards, a sprint's work, pipeline runs and pull requests. Include another page, or a README from any repository, and it stays current.
• Work items in pages. Type # to link a work item. It shows as a card with its type, state and title, and opens the work item. The page shows in the work item's Links tab, like any wiki page.
• Embeds. Videos, Figma, Miro, Power BI, Loom and other sites a space allows. PDFs preview in the page.
• Drafts of your own. Edits are drafts only you see until you publish them, and nobody is locked out of a page. If someone publishes while you edit, you're told, and can compare and choose what to keep.
• History, comments and following. Every publish is a version you can compare or restore. Comment on a page or on a passage of it. Follow a page, or a page and everything under it, to get an e-mail when it changes.
• Content health. Give pages an owner and a review date, see which pages are overdue, out of date or read most, and hand a review to someone as a task linked to the page.
• Export. Any page, or a page and the pages under it, as PDF or Word.
• Dashboards. Put a page on a project dashboard with the Team Spaces page widget.
• Templates. Start pages from built-in templates (meeting notes, decisions, how-to, retrospectives, and more), or save any page as a template for the space.
• Import. Bring in a Confluence export, including one holding several spaces, or any folder of Markdown files.
• Your space, your look. A colour and a header and footer line for each space.

Your pages stay in your organisation

Each space keeps its published pages and images in its own Git repository in your project, shown as a code wiki. That means they appear in the wiki and its search, pull requests and branch policies work on them if you want, and Microsoft 365 Copilot's Azure DevOps wiki connector can index them. Drafts are kept on a separate branch of the same repository. The page tree, comments and page view counts are kept in the extension's storage in your organisation. Nothing is sent to us. The only things that reach other sites are the ones a space chooses: embeds load from their own sites, and PlantUML diagrams, when a space admin turns them on, are drawn by the PlantUML server they name. See the privacy policy.

Permissions

The extension asks for these when it's installed, and uses them as the signed-in user:

Good to know

• People need the Basic access level (or Read permission on a space's repository) to read pages: Stakeholder access doesn't include Azure Repos.
• This is a preview. Questions and problems: support.