Skip to content

Commit 557f3ab

Browse files
Merge pull request #273714 from AbhishekMallick-MS/Apr-29-2024-Freshness
Freshness - Email reports
2 parents 23222ae + e2a869d commit 557f3ab

File tree

1 file changed

+9
-6
lines changed

1 file changed

+9
-6
lines changed

articles/backup/backup-reports-email.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,17 @@
22
title: Email Azure Backup Reports
33
description: Create automated tasks to receive periodic reports via email
44
ms.topic: conceptual
5-
ms.date: 04/17/2023
5+
ms.date: 04/29/2024
66
ms.service: backup
77
author: AbhishekMallick-MS
88
ms.author: v-abhmallick
9+
ms.custom: engagement-fy24
910
---
1011

1112
# Email Azure Backup Reports
1213

14+
This article describes how to create automated tasks to receive periodic reports via email.
15+
1316
Using the **Email Report** feature available in Backup Reports, you can create automated tasks to receive periodic reports via email. This feature works by deploying a logic app in your Azure environment that queries data from your selected Log Analytics (LA) workspaces, based on the inputs that you provide. [Learn more about Logic apps and their pricing](https://azure.microsoft.com/pricing/details/logic-apps/).
1417

1518
## Getting Started
@@ -22,7 +25,7 @@ To configure email tasks via Backup Reports, perform the following steps:
2225
* **Data To Export** - The tab which you wish to export. You can either create a single task app per tab, or email all tabs using a single task, by selecting the **All Tabs** option.
2326
* **Email options**: The email frequency, recipient email ID(s), and the email subject.
2427

25-
![Email Tab](./media/backup-azure-configure-backup-reports/email-tab.png)
28+
:::image type="content" source="./media/backup-azure-configure-backup-reports/email-tab.png" alt-text="Screenshot shows the Email tab." lightbox="./media/backup-azure-configure-backup-reports/email-tab.png":::
2629

2730
3. After you click **Submit** and **Confirm**, the logic app will get created. The logic app and the associated API connections are created with the tag **UsedByBackupReports: true** for easy discoverability. You'll need to perform a one-time authorization step for the logic app to run successfully, as described in the section below.
2831

@@ -38,16 +41,16 @@ To perform the authorization, follow the steps below:
3841
1. Go to **Logic Apps** in the Azure portal.
3942
2. Search for the name of the logic app you've created and go to the resource.
4043

41-
![Logic Apps](./media/backup-azure-configure-backup-reports/logic-apps.png)
44+
:::image type="content" source="./media/backup-azure-configure-backup-reports/logic-apps.png" alt-text="Screenshot shows the Logic Apps." lightbox="./media/backup-azure-configure-backup-reports/logic-apps.png":::
4245

4346
3. Click on the **API connections** menu item.
4447

45-
![API Connections](./media/backup-azure-configure-backup-reports/api-connections.png)
48+
:::image type="content" source="./media/backup-azure-configure-backup-reports/api-connections.png" alt-text="Screenshot shows the API Connections." lightbox="./media/backup-azure-configure-backup-reports/api-connections.png":::
4649

4750
4. You'll see two connections with the format `<location>-azuremonitorlogs` and `<location>-office365` - that is, _eastus-azuremonitorlogs_ and _eastus-office365_.
4851
5. Go to each of these connections and select the **Edit API connection** menu item. In the screen that appears, select **Authorize**, and save the connection once authorization is complete.
4952

50-
![Authorize connection](./media/backup-azure-configure-backup-reports/authorize-connections.png)
53+
:::image type="content" source="./media/backup-azure-configure-backup-reports/authorize-connections.png" alt-text="Screenshot shows the Authorize connection." lightbox="./media/backup-azure-configure-backup-reports/authorize-connections.png":::
5154

5255
6. To test whether the logic app works after authorization, you can go back to the logic app, open **Overview** and select **Run Trigger** in the top pane, to test whether an email is being generated successfully.
5356

@@ -62,7 +65,7 @@ To perform the authorization, follow the steps below:
6265
* Tab-level filters such as **Backup Instance Name**, **Policy Name** and so on, aren't applied. The only exception to this is the **Retention Optimizations** grid in the **Optimize** tab, where the filters for **Daily**, **Weekly**, **Monthly** and **Yearly** RP retention are applied.
6366
* The time range and aggregation type (for charts) are based on the user’s time range selection in the reports. For example, if the time range selection is last 60 days (translating to weekly aggregation type), and email frequency is daily, the recipient will receive an email every day with charts spanning data taken over the last 60-day period, with data aggregated at a weekly level.
6467

65-
## Troubleshooting issues
68+
## Troubleshoot issues
6669

6770
If you aren't receiving emails as expected even after successful deployment of the logic app, you can follow the steps below to troubleshoot the configuration:
6871

0 commit comments

Comments
 (0)