Skip to content
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
Cannot retrieve contributors at this time

Contributing to the AzureBI documentation

This document covers the process for contributing to the articles and code samples that are hosted on the AzureBI documentation site. Contributions may be as simple as typo corrections or as complex as new articles.

How to make a simple correction or suggestion

Articles are stored in the repository as Markdown files. Simple changes to the content of a Markdown file can be made in the browser by selecting the Edit link in the upper right corner of the browser window. (In narrow browser windows you'll need to expand the options bar to see the Edit link.) Follow the directions to create a pull request (PR). We will review the PR and accept it or suggest changes.

How to make a more complex submission

You'll need a basic understanding of Git and

  • Open an issue describing what you want to do, such as change an existing article or create a new one. Wait for approval from the team before you invest much time.
  • Fork the azurebi-docs repo and create a branch for your changes.
  • Submit a pull request (PR) to master with your changes.
  • Complete the requested checkmarks
  • Respond to PR feedback.

Markdown syntax

Articles are written in DocFx-flavored Markdown, which is a superset of GitHub-flavored Markdown (GFM).

Markdown file headers

Each markdown file part of the documentation should have an header.

uid: <uid>
title: <title>
tags: [
    { "name": "<tag1>" },
    { "name":  "<tagn>" }
system: {
    document_id: <guid>
Property Description
uid Unique reference to the document. Encoded with folderstructure, like pbi/ for the folder powerbi-visuals
title Friendly title of the document
tags Optional List of document tags. Each tag should have a new "name": "<tag>" line and seperated by a ,
system Required section of system settings
document_id A unique guid that represents the document. Is used to link to the GitHub issues by the feedback system
program_github Optional Relative reference to the product repository used by the feedback system

Folder structure conventions

For each Markdown file there may be a folder for images and a folder for sample code. For example, if the article is powerbi-visuals/, the images are in powerbi-visuals/images ( An image in the powerbi-visuals/ file is rendered by the following Markdown.

![description of image for alt attribute](powerbi-visuals/images/imagename.png)

All images should have alt text.

Markdown file names and image file names should be all lower case.

Internal links

Internal links should use the uid of the target article with an xref link:


See DocFX Cross Reference for more info.

Code snippets

Articles frequently contain code snippets to illustrate points. DFM lets you copy code into the Markdown file or refer to a separate code file. We prefer to use separate code files whenever possible, to minimize the chance of errors in the code. The code files should be stored in the repo using the folder structure described above for sample projects.

Here are some examples of DFM code snippet syntax that would be used in a configuration/ file.

To render an entire code file as a snippet:


To render a portion of a file as a snippet by using line numbers:


For C# snippets, you can reference a C# region. Whenever possible, use regions rather than line numbers, because line numbers in a code file tend to change and get out of sync with line number references in Markdown. C# regions can be nested, and if you reference the outer region, the inner #region and #endregion directives are not rendered in a snippet.

To render a C# region named "snippet_Example":


To highlight selected lines in a rendered snippet (usually renders as yellow background color):


Test your changes with DocFX

Test your changes with the DocFX command-line tool, which creates a locally hosted version of the site. DocFX doesn't render style and site extensions created for

DocFX requires the .NET Framework on Windows, or Mono for Linux or macOS.

Windows instructions

  • Download and unzip from DocFX releases.
  • Add DocFX to your PATH.
  • In a command-line window, navigate to the appropriate folder that contains the docfx.json file (azurebi-docs for AzureBI docs) and run the following command:
docfx --serve
  • In a browser, navigate to http://localhost:8080.

Mono instructions

  • Install Mono via Homebrew - brew install mono.
  • Download the latest version of DocFX.
  • Extract to \bin\docfx.
  • Create an alias for docfx:
function docfx {
mono $HOME/bin/docfx/docfx.exe

function docfx-serve {
mono $HOME/bin/docfx/docfx.exe serve _site
  • Run docfx in the azurebi-docs directory to build the site, and docfx-serve to view the site at http://localhost:8080.

Style, voice and tone

My goal is to write documentation that is easily understandable by the widest possible audience. I try to follow the Writing Style Guide Microsoft has written for their documantation and I ask my contributors to follow. It provides writing style and terminology guidance for all forms of technology communication. Regarding Voise and tone, see Microsoft .NET: Voice and tone guidelines for more information.