Skip to content

Commit 8acec6c

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into fwcopilotga
2 parents bd0d466 + 9478967 commit 8acec6c

File tree

69 files changed

+4042
-2856
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

69 files changed

+4042
-2856
lines changed

articles/azure-netapp-files/configure-customer-managed-keys.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: b-ahibbard
66
ms.service: azure-netapp-files
77
ms.topic: how-to
88
ms.custom: references_regions, devx-track-azurecli, devx-track-azurepowershell
9-
ms.date: 03/21/2025
9+
ms.date: 03/25/2025
1010
ms.author: anfdocs
1111
---
1212

@@ -36,6 +36,7 @@ The following diagram demonstrates how customer-managed keys work with Azure Net
3636
* Azure NetApp Files supports the ability to [transition existing volumes from platform-managed keys (PMK) to customer-managed keys (CMK) without data migration](#transition-volumes). This provides flexibility with the encryption key lifecycle (renewals, rotations) and extra security for regulated industry requirements.
3737
* If Azure Key Vault becomes inaccessible, Azure NetApp Files loses its access to the encryption keys and the ability to read or write data to volumes enabled with customer-managed keys. In this situation, create a support ticket to have access manually restored for the affected volumes.
3838
* Azure NetApp Files supports customer-managed keys on source and data replication volumes with cross-region replication or cross-zone replication relationships.
39+
* Applying Azure network security groups (NSG) on the private link subnet to Azure Key Vault is supported for Azure NetApp Files customer-managed keys. NSGs don’t affect connectivity to private links unless a private endpoint network policy is enabled on the subnet.
3940

4041
## Supported regions
4142

articles/backup/backup-azure-exchange-mabs.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Back up Exchange server with Azure Backup Server
33
description: Learn how to back up an Exchange server to Azure Backup using Azure Backup Server
44
ms.topic: how-to
5-
ms.date: 03/28/2024
5+
ms.date: 03/25/2025
66
author: jyothisuri
77
ms.author: jsuri
88
ms.custom: engagement-fy24
@@ -11,7 +11,7 @@ ms.custom: engagement-fy24
1111

1212
This article describes how to configure Microsoft Azure Backup Server (MABS) to back up a Microsoft Exchange server to Azure.
1313

14-
## Prerequisites for backup of an Exchange server
14+
## Prerequisites
1515

1616
Before you continue, ensure that Azure Backup Server is [installed and prepared](backup-azure-microsoft-azure-backup.md).
1717

@@ -108,3 +108,4 @@ For online recovery points, there are five recovery types:
108108
## Next steps
109109

110110
* [Azure Backup FAQ](backup-azure-backup-faq.yml)
111+
* [Recover data from Azure Backup Server](backup-azure-alternate-dpm-server.md)

articles/backup/backup-azure-integrate-microsoft-defender-using-logic-apps.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,28 +1,28 @@
11
---
2-
title: Integrate Microsoft Defender's ransomware alerts to preserve Azure Backup recovery points
2+
title: Integrate Microsoft Defender's ransomware alerts to protect Azure Backup recovery points
33
description: Learn how to integrate Microsoft Defender for Cloud and Azure Backup using logic app.
44
ms.topic: how-to
55
ms.custom: references_regions
6-
ms.date: 03/13/2024
6+
ms.date: 03/25/2025
77
ms.service: azure-backup
88
author: jyothisuri
99
ms.author: jsuri
1010
---
1111

12-
# Solution sample to integrate Microsoft Defender's ransomware alerts to preserve Azure Backup recovery points
12+
# Integrate Microsoft Defender's ransomware alerts to protect Azure Backup recovery points
1313

14-
This article describes the sample solution that demonstrates how to integrate Microsoft Defender's ransomware alerts to preserve Azure Backup recovery points. Assume there has been a breach on the Virtual Machine that is protected by both Defender and Azure Backup. Defender detects the ransomware, raises an alert which includes details of the activity and suggested recommendations to remediate. As soon as a ransomware signal is detected from Defender, ensuring backups are preserved (i.e., paused from expiring) to minimize the data loss is top of our customers’ mind.
14+
This article describes how to integrate Microsoft Defender's ransomware alerts to preserve Azure Backup recovery points. Assume there has been a breach on the Virtual Machine that is protected by both Defender and Azure Backup. Defender detects the ransomware, raises an alert which includes details of the activity and suggested recommendations to remediate. As soon as a ransomware signal is detected from Defender, ensuring backups are preserved (i.e., paused from expiring) to minimize the data loss is top of our customers’ mind.
1515

1616
Azure Backup provides several security capabilities to help you protect your backup data. [Soft delete](backup-azure-security-feature-cloud.md), [Immutable vaults](backup-azure-immutable-vault-concept.md), [Multi-User Authorization (MUA)](multi-user-authorization-concept.md) are part of a comprehensive data protection strategy for backup data. Soft delete is enabled by default, with option to make it always-on (irreversible). Soft deleted backup data is retained at no additional cost for *14* days, with option to [extend the duration](backup-azure-enhanced-soft-delete-about.md). Enabling immutability on vaults can protect backup data by blocking any operations that could lead to loss of recovery points. You can configure Multi-user authorization (MUA) for Azure Backup as an additional layer of protection to critical operations on your Recovery Services vaults. By default, critical alert for destructive operation (such as stop protection with delete backup data) is raised and an email is sent to subscription owners, admins, and co-admins.
1717

1818
Microsoft Defender for Cloud (MDC) is a Cloud Security Posture Management (CSPM) and Cloud Workload Protection Platform (CWPP) for all of your Azure, on-premises, and multicloud (Amazon AWS and Google GCP) resources. Defender for Cloud generates security alerts when threats are identified in your cloud, hybrid, or on-premises environment. It's available when you enable enhanced security features. Each alert provides details of affected resources along with the information you need to quickly investigate the issue and steps to take to remediate an attack. If a malware or a ransomware attacks on an Azure Virtual Machine, Microsoft Defender for Cloud detects suspicious activity and indicators associated with ransomware on an Azure VM and generates a Security Alert. Examples of the Defender for Cloud Alerts that trigger on a Ransomware detection: *Ransomware indicators detected*, *Behavior similar to ransomware detected*, and so on.
1919

2020
>[!Note]
21-
> This sample solution is scoped to Azure Virtual Machines. You can deployed the logic app only at a subscription level, which means all Azure VMs under the subscription can use the logic app to pause expiry of recovery points in the event of a security alert.
21+
> This solution is scoped to Azure Virtual Machines. You can deployed the logic app only at a subscription level, which means all Azure VMs under the subscription can use the logic app to pause expiry of recovery points in the event of a security alert.
2222
23-
## Solution details
23+
## Solution workflow
2424

25-
This sample solution demonstrates integration of Azure Backup with Microsoft Defender for Cloud (MDC) for detection and response to alerts to accelerate response. Sample illustrates the following three use cases:
25+
This solution demonstrates integration of Azure Backup with Microsoft Defender for Cloud (MDC) for detection and response to alerts to accelerate response. The disgram illustrates the following three use cases:
2626

2727
- Ability to send email alerts to the Backup Admin.
2828
- Security Admin to triage and manually trigger logic app to secure backups.

articles/backup/backup-azure-sql-mabs.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Back up SQL Server by using Azure Backup Server
33
description: In this article, learn the configuration to back up SQL Server databases by using Microsoft Azure Backup Server (MABS).
44
ms.topic: how-to
5-
ms.date: 03/17/2024
5+
ms.date: 03/25/2025
66
author: jyothisuri
77
ms.author: jsuri
88
ms.service: azure-backup
@@ -38,7 +38,10 @@ To back up a SQL Server database and recover it from Azure:
3838

3939
## Prerequisites and limitations
4040

41+
Before you begin, review the following prerequisites and limitations:
42+
4143
* If you have a database with files on a remote file share, protection will fail with Error ID 104. MABS doesn't support protection for SQL Server data on a remote file share.
44+
* Ensure that you've [installed and prepared Azure Backup Server](backup-azure-microsoft-azure-backup.md).
4245
* MABS can't protect databases that are stored on remote SMB shares.
4346
* Ensure that the [availability group replicas are configured as read-only](/sql/database-engine/availability-groups/windows/configure-read-only-access-on-an-availability-replica-sql-server).
4447
* You must explicitly add the system account **NTAuthority\System** to the Sysadmin group on SQL Server.
@@ -64,10 +67,6 @@ To back up a SQL Server database and recover it from Azure:
6467
* SQL server 2014 added a new feature to create a [database for on-premises SQL Server in Windows Azure Blob storage](/sql/relational-databases/databases/sql-server-data-files-in-microsoft-azure). MABS can't be used to protect this configuration.
6568
* There are some known issues with "Prefer secondary" backup preference for the SQL Always On option. MABS always takes a backup from secondary. If no secondary can be found, then the backup fails.
6669

67-
## Before you start
68-
69-
Before you begin, ensure that you've [installed and prepared Azure Backup Server](backup-azure-microsoft-azure-backup.md).
70-
7170
## Create a backup policy
7271

7372
To protect SQL Server databases in Azure, first create a backup policy:

articles/backup/backup-azure-vms-agentless-multi-disk-crash-consistent.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Back up Azure VM with agentless multi-disk crash-consistent backup by using Azure Backup
33
description: Learn how to configure backup for Azure VMs with agentless multi-disk crash-consistent backup via Azure portal.
44
ms.topic: how-to
5-
ms.date: 03/14/2024
5+
ms.date: 12/03/2024
66
author: jyothisuri
77
ms.author: jsuri
88
---
@@ -118,4 +118,4 @@ Follow these steps:
118118
119119
## Next steps
120120

121-
[Run an on-demand backup of Azure VM](backup-azure-vms-first-look-arm.md#run-a-backup-immediately).
121+
[Run an on-demand backup of Azure VM](backup-azure-vms-first-look-arm.md#run-a-backup-immediately).

articles/backup/backup-dpm-automation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Use PowerShell to back up DPM workloads
33
description: Learn how to deploy and manage Azure Backup for Data Protection Manager (DPM) using PowerShell
44
ms.service: azure-backup
55
ms.topic: how-to
6-
ms.date: 03/29/2024
6+
ms.date: 11/26/2024
77
ms.custom: devx-track-azurepowershell, engagement-fy24
88
author: jyothisuri
99
ms.author: jsuri

articles/backup/backup-mabs-add-storage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Use Modern Backup Storage with Azure Backup Server
33
description: Learn about the new features in Azure Backup Server. This article describes how to upgrade your Backup Server installation.
44
ms.topic: how-to
5-
ms.date: 03/27/2024
5+
ms.date: 12/03/2024
66
ms.service: azure-backup
77
author: jyothisuri
88
ms.author: jsuri

articles/backup/backup-mabs-sharepoint-azure-stack.md

Lines changed: 15 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
2-
title: Back up a SharePoint farm on Azure Stack by using Azure Backup
3-
description: Use Azure Backup Server to back up and restore your SharePoint data on Azure Stack. This article provides the information to configure your SharePoint farm so that desired data can be stored in Azure. You can restore protected SharePoint data from disk or from Azure.
2+
title: Back up a SharePoint farm on Azure Stack using Microsoft Azure Backup Server
3+
description: Learn how to back up and restore SharePoint data using Microsoft Azure Backup Server (MABS).
44
ms.topic: how-to
5-
ms.date: 03/15/2024
5+
ms.date: 03/25/2025
66
ms.service: azure-backup
77
ms.custom: engagement-fy24
88
author: jyothisuri
@@ -48,6 +48,8 @@ Before you continue, ensure that you've met all the [prerequisites for using Mic
4848

4949
### Additional prerequisites
5050

51+
Before you back up a SharePoint farm, review the following additional prerequisites:
52+
5153
* By default when you protect SharePoint, all content databases (and the SharePoint_Config and SharePoint_AdminContent* databases) are protected.
5254

5355
To add customizations (such as search indexes, templates or application service databases, or the user profile service), you need to configure these for protection separately. Ensure that you enable protection for all folders that include these types of features or customization files.
@@ -124,14 +126,16 @@ Follow these steps:
124126

125127
## Monitor operations
126128

127-
After the protection group is created, the initial replication occurs and MABS starts backing up and synchronizing the SharePoint data. MABS monitors the initial synchronization and subsequent backups. You can monitor the SharePoint data in a couple of ways:
129+
After the protection group is created, the initial replication occurs and MABS starts backing up and synchronizing the SharePoint data. MABS monitors the initial synchronization and subsequent backups. You can monitor the SharePoint data using one of the following ways:
128130

129131
* Using default MABS monitoring, you can set up notifications for proactive monitoring by publishing alerts and configuring notifications. You can send notifications by e-mail for critical, warning, or informational alerts, and for the status of instantiated recoveries.
130132

131133
* If you use Operations Manager, you can centrally publish alerts.
132134

133135
### Set up monitoring notifications
134136

137+
To set up monitoring notifications, follow these steps:
138+
135139
1. In the MABS Administrator Console, select **Monitoring** > **Action** > **Options**.
136140

137141
2. Select **SMTP Server**, type the server name, port, and email address from which notifications will be sent. The address must be valid.
@@ -142,6 +146,8 @@ After the protection group is created, the initial replication occurs and MABS s
142146

143147
### Publish Operations Manager alerts
144148

149+
To publish Operations Manager alerts, follow these steps:
150+
145151
1. In the MABS Administrator Console, select **Monitoring** > **Action** > **Options** > **Alert Publishing** > **Publish Active Alerts**
146152

147153
2. After you enable **Alert Publishing**, all existing MABS alerts that might require a user action are published to the **MABS Alerts** event log. The Operations Manager agent that's installed on the MABS server then publishes these alerts to the Operations Manager and continues to update the console as new alerts are generated.
@@ -259,6 +265,8 @@ The following procedure uses the example of a server farm with two front-end Web
259265
260266
### Change the front-end Web server that MABS uses to protect the farm
261267

268+
To change the front-end Web server, follow these steps:
269+
262270
1. Stop the SharePoint VSS Writer service on `Server1` by running the following command at a command prompt:
263271

264272
```CMD
@@ -286,7 +294,7 @@ The following procedure uses the example of a server farm with two front-end Web
286294
287295
1. If you performed step 6, you can now remove the volume from the protection group.
288296
289-
## Next steps
297+
## Related content
290298
291-
* See the [Backup files and application](backup-mabs-files-applications-azure-stack.md) article.
292-
* See the [Backup SQL Server on Azure Stack](backup-mabs-sql-azure-stack.md) article.
299+
* [Backup files and application](backup-mabs-files-applications-azure-stack.md) article.
300+
* [Backup SQL Server on Azure Stack](backup-mabs-sql-azure-stack.md) article.

articles/backup/backup-mabs-system-state-and-bmr.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: System state and bare-metal recovery protection for Azure Backup
33
description: Use Azure Backup Server to back up your system state and provide bare-metal recovery (BMR) protection.
44
ms.topic: how-to
55
ms.service: azure-backup
6-
ms.date: 03/29/2024
6+
ms.date: 12/03/2024
77
author: jyothisuri
88
ms.author: jsuri
99
ms.custom: engagement-fy24

articles/backup/manage-azure-managed-disks.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Manage Azure Managed Disks
33
description: Learn about managing Azure Managed Disk from the Azure portal.
44
ms.topic: how-to
5-
ms.date: 03/21/2024
5+
ms.date: 01/16/2025
66
author: jyothisuri
77
ms.author: jsuri
88
ms.service: azure-backup
@@ -168,4 +168,4 @@ To delete a disk backup instance, follow these steps:
168168

169169
## Next steps
170170

171-
[Backup vaults overview](backup-vault-overview.md)
171+
[Backup vaults overview](backup-vault-overview.md)

0 commit comments

Comments
 (0)