#Apply Baseline to Tenant

When a baseline is available, you can apply it to a tenant. You can apply multiple baselines to one or multiple tenants and set priority levels, enabling more flexible and tailored configurations across tenants.

Note the following:

• A baseline with only a draft version cannot be applied to tenants.

• If a baseline has multiple published versions, only the latest published version will be applied to tenant.

#From the Baseline Perspective

On the Baselines page, refer to the following steps to apply a baseline to one or multiple tenants:

1. Select a baseline and click Apply to tenant. Make sure the baseline status is Active, Unused, or Retrieved with exception.

2. In the Select tenants step, tenants displayed on the Tenants page are selectable. Select one or multiple tenants and click Apply.

3. Click Next.

4. In the Manage domain mappings step, map baseline domain names with tenant-specific alternatives across all domain-related properties. These mappings take effect during tenant configuration deployment and additionally serve as a reference for detecting drifts. For detailed instructions on domain mappings, refer to Manage Domain Mappings.

5. Click Next.

6. In the Drift detection settings step, settings that govern the drift detection results are displayed. Review and adjust them as needed.

   • Marching theory method – Select a matching theory method that will be used to match baseline and tenant instances during drift detection.

     • Name-based matching - Matches tenant instances against baseline standards solely based on their names. This is the default setting.

     • Similarity-based matching - Initially attempts to match tenant instances against baseline standards by name. If an instance cannot be matched by name, similarity scores will be calculated to identify potential matches. You can manually review and map these similarity-driven instances on the Map similarity-driven instances page for further comparison.

   • Drift-alignment scope policy – This policy is to define the monitor scope for drift detection and auto-alignment scope for reverting configuration changes. Select a policy from the drop-down list.

   • Drift-alignment alert policy – This policy is to define the workflows for drift notification and the frequency for drift detection. Select a policy from the drop-down list.

7. Click Next.

8. In the Deployment settings step, settings that govern the deployment process are displayed. Review and adjust them as needed.

   • Deployment settings – Choose if manual review is required before configuration deployment.

     • Manual review & deploy – Select this setting if you want a manual review process before configuration deployment. When a baseline is applied to tenant and Elements completes the configuration comparison process, a comparison page highlighting discrepancies between the tenant’s current configurations and the applied baseline will be generated, and the status of the tenant will display Review deployment. You need to review configurations, make updates as needed, and initiate the deployment process to deploy the finalized configurations to the tenant. For detailed instructions on manual review, refer to Review Deployment. This is the default setting.

     • Skip review & auto-deploy – Select this setting if you want to skip the manual review process and automatically deploy configurations to tenant after the baseline is applied to the tenant.

     If Skip review & auto-deploy is selected, you need to configure additional settings listed below:

   • Conflicts with baseline – Choose what to do when the tenant's configurations conflict with the baseline:

     • Match baseline – Select this setting if you want to update the tenant's value to match baseline. This is the default setting.

     • Keep tenant value – Select this setting if you want to keep the tenant's current value.

   • Unique to baseline – Choose how to process the configurations that only exist in the baseline:

     • Deploy – Select this setting if you want to deploy these configurations to the tenant. This is the default setting.

     • Skip – Select this setting if you want to skipping deploying these configurations.

   • Unique to tenant – Choose how to process the configurations that only exist in the tenant:

     • Keep as is – Select this setting if you want to keep these configurations in the tenant. This is the default setting.

     • Remove from tenant – Select this setting if you want to remove these configurations from the tenant.

       This setting will permanently and irreversibly delete all configurations and instances exclusive to this tenant, which may cause tenant service disruption or irreversible data loss. You need to enter Yes to confirm your understanding of these risks before proceeding.

9. Click Apply.

#From the Tenant Perspective

On the Tenants page, refer to the following steps to apply a baseline to one or multiple tenants:

1. Select one or multiple tenants and click Apply baseline.

2. In the Select baselines, baselines with the Unused, Active, and Retrieved with exception status are selectable. Select one or multiple baselines, and click Apply.

   If multiple baselines are selected, you need to rank these baselines, so that configurations will be applied following the order to resolve conflicts.

3. Click Next.

4. In the Manage domain mappings step, map baseline domain names with tenant-specific alternatives across all domain-related properties. These mappings take effect during tenant configuration deployment and additionally serve as a reference for detecting drifts. For detailed instructions on domain mappings, refer to Manage Domain Mappings.

5. Click Next.

6. In the Drift detection settings step, settings that govern the drift detection results are displayed. Review and adjust them as needed.

   • Marching theory method – Select a matching theory method that will be used to match baseline and tenant instances during drift detection.

     • Name-based matching - Matches tenant instances against baseline standards solely based on their names. This is the default setting.

     • Similarity-based matching - Initially attempts to match tenant instances against baseline standards by name. If an instance cannot be matched by name, similarity scores will be calculated to identify potential matches. You can manually review and map these similarity-driven instances on the Map similarity-driven instances page for further comparison.

   • Drift-alignment scope policy – This policy is to define the monitor scope for drift detection and auto-alignment scope for reverting configuration changes. Select a policy from the drop-down list.

   • Drift-alignment alert policy – This policy is to define the workflows for drift notification and the frequency for drift detection. Select a policy from the drop-down list.

7. Click Next.

8. In the Deployment settings step, settings that govern the deployment process are displayed. Review and adjust them as needed.

   • Deployment settings – Choose if manual review is required before configuration deployment.

     • Manual review & deploy – Select this setting if you want a manual review process before configuration deployment. When a baseline is applied to tenant and Elements completes the configuration comparison process, a comparison page highlighting discrepancies between the tenant’s current configurations and the applied baseline will be generated, and the status of the tenant will display Review deployment. You need to review configurations, make updates as needed, and initiate the deployment process to deploy the finalized configurations to the tenant. For detailed instructions on manual review, refer to Review Deployment. This is the default setting.

     • Skip review & auto-deploy – Select this setting if you want to skip the manual review process and automatically deploy configurations to tenant after the baseline is applied to the tenant.

     If Skip review & auto-deploy is selected, you need to configure additional settings listed below.

   • Conflicts with baseline – Choose what to do when the tenant's configurations conflict with the baseline:

     • Match baseline – Select this setting if you want to update the tenant's value to match baseline. This is the default setting.

     • Keep tenant value – Select this setting if you want to keep the tenant's current value.

   • Unique to baseline – Choose how to process the configurations that only exist in the baseline:

     • Deploy – Select this setting if you want to deploy these configurations to the tenant. This is the default setting.

     • Skip – Select this setting if you want to skipping deploying these configurations.

   • Unique to tenant – Choose how to process the configurations that only exist in the tenant:

     • Keep as is – Select this setting if you want to keep these configurations in the tenant. This is the default setting.

     • Remove from tenant – Select this setting if you want to remove these configurations from the tenant.

       This setting will permanently and irreversibly delete all configurations and instances exclusive to this tenant, which may cause tenant service disruption or irreversible data loss. You need to enter Yes to confirm your understanding of these risks before proceeding.

9. Click Apply.

#Track Progress

On the Tenants page, locate the target tenant and find its Status to track the progress.

#With Manual Review

If Manual review & deploy is selected, the tenant status updates as the tenant progresses through each stage of the process, including applying, reviewing, and deploying. The possible statuses are:

• Retrieving settings – During the process of applying a baseline to a tenant, this status appears.

• Settings retrieval failed (clickable) – If errors occur during the process of applying a baseline to a tenant, this status will appear.

  You can click the status link and then click Export report to export the report to find more details.

• Review deployment – When manual review is required, after a baseline is applied to a tenant and a comparison page is generated or after the baseline of the tenant has been changed and a comparison page is generated, this status will appear.

  You can click the status link to open the comparison page where you can review discrepancies between the tenant’s current configurations and the applied baseline, make updates, and deploy the reviewed configurations to the tenant. For detailed instructions, refer to Review Deployment.

• Deploying – During the process of the deployment, this status appears.

• Deployed with exception (clickable) – If the deployment finishes with exceptions, this status will appear. The total number of configurations and the number of deployed configurations are displayed.

  You can click the status link and then click Export report to export the report for details.

• Deployment failed (clickable) – If the deployment fails, this status will appear.

  You can click the status link and then click Export report to export the report for details.

• Monitoring – If the deployment is successful, this status will appear.

#Without Manual Review

If Skip review & auto-deploy is selected, the tenant status updates as baseline configurations are applied and deployed to the tenant. The possible statuses are:

• Deploying – During the process of the deployment, this status appears.

• Deployed with exception (clickable) – If the deployment finishes with exceptions, this status will appear. The total number of configurations and the number of deployed configurations are displayed.

  You can click the status link and then click Export report to export the report for details.

• Deployment failed (clickable) – If the deployment fails, this status will appear.

  You can click the status link and then click Export report to export the report for details.

• Monitoring – If the deployment is successful, this status will appear.