Provisioned wikis vs. published code as a wiki

Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019 | TFS 2018

In Azure DevOps, you have the following options for maintaining wiki content.

While both options maintain the wiki content in Git repositories, the way you add, update, and manage the wiki content differs.


The publish code as wiki feature is currently available on Azure DevOps Server 2018 and later versions. For older versions, you can only provision a wiki for your team project.

Wiki page menu options

With a provisioned wiki, you add and edit pages directly within the Wiki. All content updates to a provisioned wiki occur within the Wiki.

With a publish code as wiki, you add, edit, and update content from Repos or Code.

The unavailable menu options for the wiki pages are shown in the following illustration. As you can see, several options aren't supported for the publish as code wiki pages.

Provisioned wiki

Provisioned wiki page menu options.

Publish code as wiki

Publish code page menu options.

For example, the Edit in Repos option for the publish code as wiki takes you to the Repo page to edit that specific page. Updates you make to a page in the branch you selected for the wiki get automatically published to the wiki.

Supported features and operational differences

Provisioned wikis and publish as code wikis support the following features:

The following table summarizes those operations or features that may differ, depending on the wiki type.

Add pages

For a provisioned wiki or publish code as wiki, select New page or Add subpage. To learn more, see Add and edit wiki pages.

Page sequence and page list in navigation pane

The provisioned wiki manages the page sequence and page list automatically as you add or move pages within the navigation pane.

To structure the list of pages in the navigation pane for a publish code as wiki, define the .order file at the root, and for each subfolder or parent page that contains subpages.

Both types of wikis follow the same file structure, it's just that the publish code as wiki requires you to maintain the page sequence manually.

To learn more about working with .order files, see Wiki Git repository files and file structure.

Page revisions and reverting to a previous version

From the Wiki, you can view the revisions of any wiki page by choosing Revisions or selecting the View revisions menu option.

However, the revert process differs depending on the wiki page type.

  • For a provisioned wiki page, select Revert, as described in Revert a commit to a provisioned wiki page
  • For a publish as code wiki page, work from a local branch and submit a pull request to update the branch you're working from.

Versioning and unpublishing a wiki

With versioning, you can publish different content versions to distinct wikis, based on a versioned branch of a Git repo. Versioning and unpublishing content you've previously published to a wiki, is supported only for wikis that you've created by publishing code to a wiki.

To learn more, see Version, select, or unpublish a published wiki.

Delete project wiki

  1. Get the wiki corresponding to the wiki ID or wiki name provided. For more information, see Wikis - Get REST API.


You can also get all wikis in a project or collection. For more information, see Wikis - List REST API

  1. Delete the wiki corresponding to the wiki ID or wiki name provided. For more information, see Wikis - Delete REST API.

Update a wiki by working offline

You can work offline or in a local branch to update content for a provisioned wiki and publish as code wiki. To learn more, see Clone and update wiki pages offline.