Skip to main content

Backup Profile for Org Apps - Migration

This article outlines Backup Profile, Auto-Configuration rules, and the migration of existing resources.

Updated over a week ago


Important

This feature will be available starting April 5, 2025. The rollout will occur in phases, and existing resources will migrate automatically—no action is required. For early access, contact support.


1. Introduction

We’re excited to introduce Backup Profile for Org Apps and Auto-Configuration Rules, a powerful new feature designed to enhance the protection of Microsoft 365 org applications, including Groups, SharePoint, and Teams. This update simplifies backup management by allowing you to create custom backup profiles and apply them automatically to a group of resources using auto configuration rules.

Key Benefits

With Backup Profile for Org Apps and Auto configuration rules, organizations can implement a scalable and granular approach to backup configuration, overcoming previous limitations. Here’s how this feature benefits you:

  • Streamlined Management – Organize similar Org Apps resources into groups for easier backup administration.

  • Automated Backup Assignments – Use attribute-based auto-configuration rules to automatically map predefined backup profiles to Microsoft 365 resources.

  • Granular Backup Control – Control which org app resources to back up based on attributes instead of backing up everything.

2. How This Feature Works

Step 1: Create Backup Profiles

A profile is a set of backup settings used to manage a group of org app resources. Profiles offer significant advantages by enabling standardized backup configurations that can be automatically applied to multiple users or applications.

For example: Let's create a new profile for the Groups app with backup frequency of Thrice a Week and data lock enabled.

After you define backup profiles, the next step is to map them to resources. This is where Auto Configuration Rules come in.

Step 2: Create Auto Configuration Rules

Auto Configuration Rules provide a powerful, automated approach to managing resource backup settings across your organization. These rules allow you to dynamically group and configure resources based on specific attributes, significantly reducing manual configuration efforts and ensuring consistent backup settings application.

For example, if you've created a backup profile called RPGroups that needs to be applied to groups containing the word test in their name. You can create a rule with the condition name contains text, which will automatically identify all impacted resources. The wizard will then prompt you to select a backup profile for these resources. You can choose an existing profile from the dropdown menu or create a new backup profile.

Step 3: Sync Rules

Click Sync Now on the Auto configuration rules window. Once the rule is synced, all discovered groups with test in their name will automatically have the settings from the RPGroups backup profile applied. The rule sync occurs every 24 hours, automatically updating backup profiles for resources based on the matching rule.

3. UI Changes

Listing Page

See the image below for the changes on the left navigation pane and the listing page.

Filters

The listing page now includes new filters for backup profiles and auto-configuration rules. These are shown in the graphics below.

4. Impact on Existing Configurations

All your existing resources will be migrated to Backup Profiles for Org App . Your current settings per resource will be preserved through custom rules. For further information regarding migration behavior, please refer to the section below.

How Will This Upgrade Affect Current Configuration?


📝NOTE:

Since rules require an assigned storage region, migrated org apps resources will not have one if auto-configuration was previously disabled.

Without a storage region, new auto-configuration rules cannot be created. To continue backups, create auto-configuration rules, fetch all or specific resources, assign a storage region, and manually sync the rule.


Scenario

Upgrade Impact

All resources for org app(s) were auto-configured with default backup settings.

No org apps resources were manually configured.

Three new backup profiles—one each for Groups, SharePoint, and Teams—will be created with default settings. A corresponding rule will also be created for each app, and these profiles will be mapped to it. All resources will be assigned and configured according to the default profile.

Custom Backup Settings

Few org app resources were manually configured with custom settings

In addition to default profiles, new custom profile(s) will be created and applied for each unique backup setting, ensuring no changes to existing backup and retention configurations for any resource.

For example, If you have 5 custom settings for SharePoint; in addition to default profiles, 5 new custom SharePoint profiles will be created and the resources will be mapped to them; Custom SharePoint Profile - 1, Custom SharePoint Profile - 2

Auto configuration was enabled, but the option Also apply this backup configuration setting to Groups already discovered but not yet configured for backup.was not checked on the UI.

Previously, if this option was not checked while auto configuration was enabled, only newly discovered resources were automatically configured, leaving the previously discovered resources unconfigured.

With this upgrade, all unconfigured groups will now be backed up using the default rule and backup profile.

How Will This Upgrade Affect Data locked Resources?

Scenario

New Configuration

Behavior

Scenario 1

  • Parent - Group configured with Profile P1 and Data Lock enabled.

  • Child - SharePoint/Teams unconfigured.

Parent's profile (P1) will be applied to child resources

The site/team follows all settings of the group's profile.

Scenario 2

  • Parent - Group configured with Profile P1 and Data Lock disabled.

  • Child - SharePoint/Teams configured with profile DL1 and Data Lock is enabled.

Child's own profile (DL1) will be applied.

The sync frequency of the backup is defined by parent profile P1 without impacting any profile setting defined by DL1.

Scenario 3

  • Parent - Group configured with Profile P1 and Data Lock enabled.

  • Child - SharePoint/Teams configured with profile DL1 and Data Lock enabled.

Child's own profile (DL1) will be applied.

The sync frequency of the backup is defined by parent profile P1 without impacting any profile setting defined by DL1.

Scenario 4

  • Parent - Group configured with Profile P1 and Data Lock disabled.

  • Child 1 (Higher priority) - Teams Profile P2 and Data Lock disabled.

  • Child 2 (low priority) - SharePoint Profile DL1 and Data Lock enabled.

Child 1 (Higher priority) follows profile P1

Child 2 (low priority) retains profile DL1.

The sync frequency of the backup is defined by parent profile P1 without impacting any profile setting defined by DL1.

Did this answer your question?