How Rule Priority Works
Druva manages Microsoft 365 Group sites, SharePoint sites, and team sites through their parent applications. These sites follow a hierarchical backup system where parent applications take precedence over standalone SharePoint settings. The rule priority follows this order:
Microsoft Groups (Highest Priority)
Microsoft Teams
SharePoint (Lowest Priority)
When multiple rules are applied, the system determines priority based on the rule's assigned ranking. A rule with a higher priority (lower numerical value) takes precedence over lower-priority rules.
Understanding and Implementing Rule Priority
In this section, we will go through a step-by-step approach to demonstrate how rule priority affects site configurations with an example.
Creating the first rule – Setting up an initial rule and assigning a priority.
Creating a higher-priority rule – Overriding an existing rule by assigning a new one with a higher priority.
Changing rule priority – Modifying rule priority to change configurations dynamically.
Creating a group rule – Understanding how group rules take precedence over team and SharePoint rules.
Step 1: Create the First Rule
Rule Name: team-rule-1
Backup Profile: team-prof-1
Condition: Team name contains "OAP"
Priority: 1 (since it is the first rule)
After triggering the sync, Three sites that match this condition are now automatically configured with team-rule-1.
Step 2: Create a Higher-Priority Rule
Rule Name: team-rule-2
Backup Profile: Default team profile
Condition: Site URL equals
https://sharepoint.com/.../OAP__Team_t3...Priority: 1 (setting this rule as priority 1 changes team-rule-1 to priority 2)
After triggering the sync, the site that matches team-rule-2 is now configured with it, while the other two sites remain under team-rule-1.
Step 3: Change Rule Priority
Modify team-rule-2 priority to 2.
To change priority click the three-dot menu on the workload card, select Change Priority, and drag the rules to reorder them. Alternatively, you can edit the rule and choose a priority from the dropdown menu.
After triggering the sync, team-rule-1 takes precedence over team-rule-2, and all 3 teams are reconfigured under team-rule-1.
Step 4: Create a Group Rule
Group rules have the highest priority, meaning that the Group rule associated with a Parent Group takes precedence over the child team rules.
Rule Name: group-rule-1
Backup Profile: group-prof-1
Condition: Group name contains "OAP"
Priority: 1 (since it is the first rule for Groups)
After triggering a sync, the three teams previously configured using team-rule-1 are now configured under group-rule-1 because they are associated with groups that satisfy the group-rule-1 condition.
Data Lock Profile Behavior in Different Scenarios
Scenario 1: New Data Lock Profile Created for Group
When a new profile with the Data Lock enabled is created, the data lock settings apply to associated SharePoint sites and Teams. These settings propagate down the hierarchy, ensuring that all associated sites inherit the group's configuration.
Scenario 2: Manual Site Configuration Override
If a SharePoint site is manually configured without a Data Lock Profile, but its parent Group has a data lock-enabled profile, the site inherits the group's profile settings. As a result, data lock is automatically enabled for the site.
Scenario 3: Existing Site with "SharePoint Data Lock"
If a SharePoint site already has Data Lock enabled and its parent group is mapped to a new rule with Data Lock enabled, the site's existing data lock settings remain unchanged.
Since a resource with Data Lock enabled should not have its settings altered, the site's existing Data Lock backup profile is preserved and is not modified by the group association. The backup frequency is defined as per the parent Group’s profile.