*.png binary

*.jpg binary

_site/

_themes*/

This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).

For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.

We welcome contributions from our community as well as from Microsoft employees from outside the documentation teams. How you contribute depends on who you are and the sort of changes you'd like to contribute:

* **Community - minor updates**: If you are contributing minor updates out of the goodness of your heart, you can find the article in this repository, or visit the article on [https://docs.microsoft.com/azure](https://docs.microsoft.com/azure) and click the **Edit** link in the article that goes to the GitHub source for the article. Then, just use the GitHub UI to make your updates. Or, you are welcome to fork the repository and submit updates from your fork. See our general [contributor guide](https://docs.microsoft.com/contribute/) for more information.

* **Employees**: If you are a technical writer, program manager, or developer from the product team for an Azure service and it's your job to contribute to or author technical articles, you should use the private repository (https://github.com/MicrosoftDocs/azure-docs-pr). Employees from other parts of the Microsoft world should use the public repo for minor updates.

Minor corrections or clarifications you submit for documentation and code examples in this repo are covered by the [docs.microsoft.com Terms of Use](https://docs.microsoft.com/legal/termsofuse).

If you submit a pull request with significant changes to documentation and code examples, you'll see a message in the pull request asking you to submit an online contribution license agreement (CLA). We need you to complete the online form before we can review your pull request.

Community contributors can use the GitHub UI or fork the repo to contribute - more information is available in our [contributor guide](https://docs.microsoft.com/contribute).

The content in the azure-docs repository follows the organization of documentation on https://docs.microsoft.com/azure. This repository contains two root folders:

The *\articles* folder contains the documentation articles formatted as markdown files with an *.md* extension. Articles are typically grouped by Azure service.

The *\articles* folder contains the *\media* folder for root directory article media files, inside which are subfolders with the images for each article. The service folders contain a separate media folder for the articles within each service folder. The article image folders are named identically to the article file, minus the *.md* file extension.

You can create reusable content sections to be included in one or more articles.

All the articles in this repository use GitHub flavored markdown. If you are not familiar with markdown, see:

* [Markdown basics](https://help.github.com/articles/markdown-basics/)

* [Printable markdown cheatsheet](https://guides.github.com/pdfs/markdown-cheatsheet-online.pdf)

In the public azure-docs repository, automated labels are assigned to pull requests to help us manage the pull request workflow and to help let you know what's going on with your pull request:

* **Change sent to author**: The author has been notified of the pending pull request.

* **ready-to-merge**: Ready for review by our pull request review team.

ms.date: 08/27/2018

title: Updating Azure Backup Central Reporting Content Pack

description: Information about updates to Azure Backup Content Pack in Power BI

[Azure Backup Content Pack](https://docs.microsoft.com/azure/backup/backup-azure-configure-reports#view-reports-in-power-bi) can be used to view reports about backup centrally. The content pack is updated regularly to add more features, and for bug fixes. This article leads you through the steps to update the Content Pack, to delay the update, and the updates that are made over time.

Your copy of the content pack will get updated automatically if you have not made any changes to it.

In case the content pack has been changed, you will get a notification in PowerBI, and an email notification about the same. You can choose to get the updated content pack as per your convenience.

The best practice is to import the content pack into a [custom workspace](https://youtu.be/26zyOtyHPJM?t=1m57s). You now have the ability to edit the reports.

As mentioned above, if the content pack is changed, you see a notification in PowerBI. You can choose to get the content pack later.

Azure Backup Content Pack is being updated to support more workloads, as SQL in IaaS VM backup, and SC DPM, in addition to the current support for MAB and Azure VM Backup. This means that you will soon be able to view and analyze data all your backup data at one central place. The [reports can also be customized](https://youtu.be/26zyOtyHPJM) to suit the needs of your organization.

To make the reports more meaningful across workloads, the set of reports pre-configured with Azure Backup Content Pack is being changed. A sneak peek into the upcoming set of reports is available here:

* [Share Reports across your organisation](https://youtu.be/26zyOtyHPJM)