How to fix the error "The remote server returned an error: (405) Method Not Allowed" while trying to automate wiki documentation from azure release pipeline. This occurs when trying to update/create the wiki page from azure build pipeline using PS script.

I know this is old but thought I would help with actual powershell code. I kept trying to use Invoke-RestMethod, but found you need to get the eTag from the headers via an Invoke-WebRequest. I wanted to get the content, manipulate it and write it back if the page existed else create the page with the contents so I created a function to basically get the content and return the eTag; assuming your wiki is git based.

function Get-WikiPageContent {
param(
[Parameter(Mandatory=$true)][string]$pagePath
)
$uri = "https://dev.azure.com/${org}/${project}/_apis/wiki/wikis/${wikiName}/pages?path=/${pagePath}&includeContent=true&includeContentMetadata=true&api-version=7.1-preview.1"

$response = Invoke-WebRequest -Uri $uri -Headers $Headers -Method Get
# You need the eTag (Commit ID) to update a wiki page
$eTag= $response.Headers["ETag"].Trim('"')

# Convert only the JSON content of the response
$pageData = $response.Content | ConvertFrom-Json
$pageData | ConvertTo-Json -Depth 10 | Out-Host

return [pscustomobject]@{
PagePath = $pagePath
eTag = $eTag
Content = $pageData.content
}
}

Now when writing the content back to the page, you need to add the "If-Match = "$eTag" to the Headers before calling Invoke-RestMethod, I have a global $Headers definition and I just copy it in function and add the eTag

function Set-PageContent {
param(
[Parameter(Mandatory = $true)][string]$pagePath,
[Parameter(Mandatory = $true)]$content,
[string]$eTag # This is the eTag, only present if page exists
)

$uri = "https://dev.azure.com/${org}/${project}/_apis/wiki/wikis/${wikiName}/pages?path=${pagePath}&api-version=7.1-preview.1"

# Create local copy of headers and add If-Match if needed
$localHeaders = @{}
foreach ($key in $Headers.Keys) {
$localHeaders[$key] = $Headers[$key]
}

# If updating page, must give eTag
if ($eTag) {
$localHeaders["If-Match"] = $eTag
}

$requestBody = @{ content = $content } | ConvertTo-Json -Depth 5
# Define parameters
$params = @{
Uri = $uri
Headers = $localHeaders
Method = 'PUT'
ContentType = 'application/json; charset=utf-8'
Body = $requestBody
}
# Try Catch
$result = Invoke-RestMethod @params
}

Hello Tiwari,

Thank you for your question and for reaching out with your question today.

The error "The remote server returned an error: (405) Method Not Allowed" indicates that the HTTP request made by your PowerShell script is using a method that is not allowed by the server.

To resolve this issue, you can try the following steps:

1. Check the HTTP method: Review your PowerShell script and verify the HTTP method you are using for the request. Ensure that it is appropriate for creating or updating a wiki page. The most common methods for creating or updating resources are POST or PUT.
2. Confirm the endpoint URL: Double-check the endpoint URL you are using to access the Azure DevOps Wiki API. Make sure it is correct and matches the expected format. The URL should include the organization, project, and wiki information.
3. Validate authentication: Ensure that your script is properly authenticated and authorized to access the Azure DevOps Wiki. You may need to include authentication headers or tokens in your request to authenticate with the Azure DevOps API.
4. Verify permissions: Verify that the user or service account executing the PowerShell script has the necessary permissions to create or update wiki pages. The account should have appropriate access rights within the Azure DevOps organization and project.
5. Test the request with a REST client: To troubleshoot further, you can use a REST client (such as Postman or cURL) to manually send a request to the Azure DevOps Wiki API and observe the response. This can help you verify if the issue is specific to your PowerShell script or if it is a configuration issue on the server side.
6. Review API documentation: Refer to the official documentation or API reference for the Azure DevOps Wiki API to ensure that you are following the correct syntax and guidelines for creating or updating wiki pages.
7. Check for any restrictions or limitations: Some APIs may have restrictions or limitations on certain operations. Make sure you are not violating any specific constraints or limitations imposed by the Azure DevOps Wiki API.

If the issue persists, you may need to reach out to the Azure DevOps support team or consult their official documentation for specific troubleshooting steps related to the Wiki API.

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

If the reply was helpful, please don’t forget to upvote or accept as answer.

Best regards.