Home / Guides / A customer support portal for Azure Boards
A customer support portal for Azure Boards: your options compared
Your team plans and fixes everything in Azure Boards, and your customers want one place to report a problem and see what happened to it. Azure DevOps has no customer portal of its own, so teams build one from the parts they have. This guide compares the five common ways, from free to paid, says what each one costs you in work and licences, and gives you a script that shows the part most of them leave out: where each customer's request stands.
Short answer.
The free ways are Stakeholder access (customers sign in to Azure DevOps itself) and a form of your own that creates work items through the REST API. Power Automate can turn a shared mailbox or a Microsoft Forms response into a work item, but the Azure DevOps connector is Premium. A help desk such as Zendesk, Freshdesk or Jira Service Management gives customers a real portal, but tickets live in the help desk and reach Azure DevOps through an add-on. A portal built on Azure Boards, such as BoardwalkDesk, keeps every ticket a work item and gives the customer a portal to follow it.
The options at a glance
| Option | Customer needs an Azure DevOps account | Customer sees progress | Where tickets live | What it costs you |
|---|---|---|---|---|
| Stakeholder access | Yes | Yes, inside Azure DevOps | Azure Boards | Free licences; permission work on every area path |
| Your own form + REST API | No | No, unless you build it | Azure Boards | Your code, hosting and an identity to look after |
| Power Automate (email or Forms) | No | No, unless you build more flows | Azure Boards | A Power Automate licence with Premium connectors |
| Help desk with an Azure DevOps add-on | No | Yes, in the help desk portal | The help desk; escalations copied to Azure Boards | A paid seat per agent, plus the add-on |
| Portal built on Azure Boards | No | Yes | Azure Boards | A subscription per desk |
Option 1: free Stakeholder access
Stakeholder is a free access level with no user limit, and in a private project a Stakeholder can create and edit work items and follow them by email. It is the only built-in way to let customers see their own requests, but they become members of your organization: in an organization connected to Microsoft Entra ID each one is a guest in your tenant, and by default project members can see every work item in the project, other customers' included. Hiding work means a deny on View work items in this node for each area path. Let customers create Azure DevOps work items without a license covers the setup and the limits in detail.
Option 2: a form of your own
A web form on your site calls POST .../_apis/wit/workitems/${type} under an identity you own, so the customer never touches
Azure DevOps. The same guide has a PowerShell script for the call and advice on the identity (a service principal or managed identity, not
a personal access token). The catch is everything after the work item exists: the form does not know who the customer is, and the customer
hears nothing back.
Option 3: email or Microsoft Forms through Power Automate
Azure Boards does not turn incoming email into work items by itself. Many teams wire it up with a Power Automate cloud flow:
- Trigger: When a new email arrives in a shared mailbox (V2) from the Office 365 Outlook connector, on your support mailbox. For a web form, use When a new response is submitted and Get response details from the Microsoft Forms connector instead.
- Action: Create a work item from the Azure DevOps connector, with the subject as the title and the body and the sender's address in the description. Put the sender in a line such as Raised by name@example.com so you can find their requests later (the script below reads that line).
- Optional: a reply from the same mailbox telling the customer the work item number.
The Outlook and Forms connectors are Standard, but the Azure DevOps connector is Premium. A Microsoft 365 licence covers Standard connectors only, so the flow's owner needs a Power Automate licence that includes Premium connectors. Beyond the licence, think about:
- Anything that reaches the mailbox becomes a work item: spam, out-of-office replies and the customer's "thanks!" answer all create new items unless the flow filters them.
- Replies do not thread. Adding a customer's answer to the right work item means parsing the number out of the subject and calling another action.
- The customer still sees nothing. Status mail means more flows on When a work item is updated, and deciding which changes are worth sending.
Option 4: a help desk with an Azure DevOps add-on
Zendesk, Freshdesk and Jira Service Management all give customers a proper portal and email channel. The difference is where the ticket lives: in the help desk. Your developers still work in Azure Boards, so a ticket that needs a fix is escalated to a work item through a Marketplace app, and the two records are kept in step by that app.
- Most of these apps come from other publishers. When we checked in November 2026, none of the Zendesk Marketplace apps for Azure DevOps were made by Zendesk, Freshworks' own Azure DevOps connector was for Freshservice only, and Atlassian's official app shows commits, pull requests and builds in Jira but syncing work items needs a third-party app.
- Every agent needs a paid help desk seat, on top of their Azure DevOps access, and the customer portal can be tied to a higher plan.
- Two systems to keep straight. Comments, states and attachments have to be mapped between them, and someone owns that mapping.
A help desk is the right choice when support is its own team with its own channels (chat, phone, a knowledge base) and only some tickets ever reach development. The side-by-side pages on boardwalkdesk.com/compare list the plans, add-ons and sources for each of the three.
See what your customers would see: a status list for every request
Whichever free option you pick, the customer's first question is "what happened to my request?". This script answers it for you: it lists every work item with your customer tag that changed recently, grouped by the customer who raised it, with its state. It is read-only. It uses the Query By WIQL call to find the IDs (WIQL returns only IDs, at most 20,000) and then the Work Items Batch call to read the fields, 200 IDs at a time, which is the limit of that call.
# Get-CustomerRequestStatus.ps1: lists customer requests in Azure Boards and where each one stands.
# Read-only. Uses a Microsoft Entra token from the Azure CLI (az login, az login --identity or --service-principal).
param(
[Parameter(Mandatory)][string]$Organization,
[Parameter(Mandatory)][string]$Project,
[string]$Tag = 'Customer request',
[int]$Days = 30
)
$token = az account get-access-token --resource 499b84ac-1321-427f-aa17-267ca6975798 --query accessToken -o tsv
if (-not $token) { throw 'No Azure DevOps token. Sign in with az login first.' }
$headers = @{ Authorization = "Bearer $token" }
$base = 'https://dev.azure.com/{0}/{1}/_apis/wit' -f $Organization, [uri]::EscapeDataString($Project)
# Step 1: WIQL returns only the IDs of the matching work items (at most 20,000).
$wiql = "SELECT [System.Id] FROM WorkItems WHERE [System.TeamProject] = @project " +
"AND [System.Tags] CONTAINS '$($Tag -replace "'", "''")' " +
"AND [System.ChangedDate] >= @Today - $Days ORDER BY [System.ChangedDate] DESC"
$body = ConvertTo-Json @{ query = $wiql }
$found = Invoke-RestMethod -Method Post -Uri "$base/wiql?api-version=7.1" -Headers $headers `
-ContentType 'application/json' -Body $body
$ids = @($found.workItems | ForEach-Object { $_.id })
if ($ids.Count -eq 0) { "No work items tagged '$Tag' changed in the last $Days days."; return }
# Step 2: read the fields in batches of up to 200 IDs.
$fields = 'System.Id', 'System.Title', 'System.State', 'System.ChangedDate', 'System.Description'
$items = for ($i = 0; $i -lt $ids.Count; $i += 200) {
$batch = ConvertTo-Json @{ ids = @($ids[$i..([Math]::Min($i + 199, $ids.Count - 1))]); fields = $fields }
(Invoke-RestMethod -Method Post -Uri "$base/workitemsbatch?api-version=7.1" -Headers $headers `
-ContentType 'application/json' -Body $batch).value
}
# The customer's address is in the "Raised by ..." line the support form wrote into the description.
$items | ForEach-Object {
$f = $_.fields
$customer = if ("$($f.'System.Description')" -match 'Raised by ([^\s<]+@[^\s<]+)') { $Matches[1] } else { '(unknown)' }
[pscustomobject]@{
Customer = $customer
Id = $f.'System.Id'
State = $f.'System.State'
Changed = ([datetime]$f.'System.ChangedDate').ToString('yyyy-MM-dd HH:mm')
Title = $f.'System.Title'
}
} | Sort-Object Customer, @{ Expression = 'Changed'; Descending = $true } | Format-Table -AutoSize
Run it after az login with an account that can read work items in the project:
.\Get-CustomerRequestStatus.ps1 -Organization contoso -Project Support
.\Get-CustomerRequestStatus.ps1 -Organization contoso -Project Support -Tag 'Customer request' -Days 90
It finds the customer's address in the Raised by ... line that the form script in the
work items without a license guide writes into the description; a work item
without that line shows as (unknown). Change the pattern if your form or flow writes the address somewhere else. We tested it
against a mock of the two REST calls in Windows PowerShell 5.1 and PowerShell 7: 250 work items were read in two batches, a tag with an
apostrophe, a project name with a space and an empty result all worked.
That list is what a portal shows each customer, filtered to their own requests. Sending it to them is where the free options stop: each customer must only ever see their own lines, your team's comments must stay out of it, and it has to be up to date when they look.
Questions
Does Azure DevOps have a built-in customer portal?
No. Azure Boards is built for people in your organization. The closest built-in option is free Stakeholder access, which lets customers create and follow work items, but makes them members of your organization who can see the project unless you restrict each area path.
Can Azure DevOps create work items from email?
Not by itself. The usual way is a Power Automate flow: a shared-mailbox trigger from the Office 365 Outlook connector and the Create a work item action from the Azure DevOps connector. Some customer portals, BoardwalkDesk among them, can also turn forwarded support email into tickets.
Do I need Power Automate Premium for an email-to-work-item flow?
Yes. The Azure DevOps connector is a Premium connector in Power Automate, and the Power Automate use that comes with Microsoft 365 covers Standard connectors only. The flow's owner needs a licence that includes Premium connectors.
Can Zendesk or Freshdesk create Azure DevOps work items?
Yes, through Marketplace apps, most of them from other publishers. The ticket stays in the help desk and the app creates or links a work item for the issues you escalate, so agents work in the help desk and developers in Azure Boards.
How can customers see the status of their request in Azure DevOps?
Either they sign in as Stakeholders and follow their work items, or something outside Azure DevOps shows it to them: status emails from service hooks or Power Automate, or a customer portal that reads the work items and shows each customer only their own.
Related
- Let customers create Azure DevOps work items without a license
- BoardwalkDesk: a customer service desk for Azure DevOps
- All guides
Sources (Microsoft Learn): Stakeholder access quick reference, Azure DevOps connector, Office 365 Outlook connector, Microsoft Forms connector, Power Automate licensing FAQ, WIQL syntax reference, Wiql - Query By Wiql (REST API 7.1), Work Items - Get Work Items Batch (REST API 7.1), Work tracking, process and project limits.