Surfacing Azure Boards Work Item Status in README.md by Installing the Azure Boards App for GitHub

Why the Answer Is Correct

The question asks what to do first, and the README.md status display depends entirely on the GitHub and Azure Boards integration existing. Installing the Azure Boards app for GitHub is that integration: once it is installed, Azure Boards can surface work item state into the GitHub repository, which is what makes the status information available to embed in README.md. Because the requirement is to minimize administrative effort, the enabling step is the right starting point, and the remaining configuration follows from it. The vote was 57 for C and 43 for D. Bakare118 and Dankho both answered C by reading the question's wording precisely, noting that it asks what to do first, and four separate comments including Gooldmember and MrAZ105 selected C on the grounds that the app installation is the required first step for the integration to work.

Why the Other Options Are Wrong

Selecting Allow anonymous users to access the status badge (D) configures who may view a badge that already works, so it is a later step and not the enabler. Dankho characterized this accurately, noting that the setting relates to badge visibility rather than getting the integration working, and that the primary step is establishing the integration. Creating a GitHub personal access token (A) is a credential step that may be needed for some API-based scenarios but is not the prerequisite for the board status integration, and it is not the first action the question is looking for. Enabling GitHub annotations for the board (B) turns comment annotations on for the board, which is a display preference for work item comments and has nothing to do with reflecting work item status into a repository file.

Community Comment Notes

The vote was close at 57 to 43, and the dissent is worth examining because it rests on a real documentation detail. schwagalla, the highest-liked commenter and the only D vote, argued that anonymous access is the easiest path and pointed to the status badge documentation, which does state that anonymous access must be allowed for the badge. Christian_garcia_martin answered C with the reasoning that the app is what links commits and pull requests to work items so that state changes reflect in the repository. The reconciliation is that the badge setting is genuinely required for visibility but is not the first step, which is why the majority reading of do first prevails.