Deprecated rules

Overview

Cayosoft Administrator provides rule migration and deprecation toolsets aimed to address the rapid changes in the third-party vendor APIs used. If there is a newly deprecated rule in Cayosoft Administrator, the Deprecated Rules banner is prompted in the Action Required notification section.

Deprecated rules are the rules planned to be retired due to one of the following reasons:

• Changes introduced to a third-party API make an automated upgrade from a legacy rule to an updated version impossible.

• The rule functionality can no longer be provided due to the third-party API changes.

• A rule was completely redesigned. The automated upgrade is not feasible.

• A rule is no longer supported or used. All deprecated rules are disabled to stop working at a predefined EOL (end-of-life) date. New instances of these rules cannot be created from the new rule wizard. However, these deprecated rules are divided into two different categories:

  • An obsolete rule. These rules will no longer be supported after the specified EOL date and will be considered unsupported rules upon the EOL.

  • A rule with a migration path. These deprecated rules can be migrated into newer versions that include most or all the prior functions. After the migration, both the legacy and the new rule exist simultaneously; the deprecated rule must be removed manually. Refer to the following section to learn more about the migration functionality: Deprecated rules.

IMPORTANT: Deprecated rules do not get updated automatically in your environment; a manual migration or deletion is required.

Deprecated Rules node in Administrator Console

The Deprecated Rules node contains a list of rules supported until the end-of-life date (EOL) specified for each rule. After the EOL date, the rules become obsolete, unable to run on schedule, and not supported by Cayosoft. Depending on the affected functionality, you might be able to migrate the deprecated rule. Refer to the following examples:

• When a third-party vendor API is being deprecated, the related rule cannot be migrated.

• When the affected rule is being reworked into a different rule with extended functionality, the initial rule can be migrated.

Refer to the list of highlighted items:

1. A rule being deprecated. The line contains the rule name, current status, folder, rule schedule status, target version to deprecated the rule, and the EOL date.

2. The Export button exports the entire list of deprecated rules to a CSV file.

3. The Migrate button migrates the selected rule.

4. The Delete Rule(s) button deletes the selected rule with no further migration.

Exporting the list of deprecated rules

You can export the list of deprecated rules in CSV format by clicking the Export button. The exported CSV file follows the structure of the table in the Console with the addition of the RuleID value.

Available Migrate Rules settings

Depending on the selected mode, you get various settings to support the migration process. Review the following list of available settings:

• Add prefix to the source rule(s) name (Migration mode−specific)

  • Specify a unique prefix to differentiate the source rule from the migrated rule.

• Create Configuration DB backup before migration (Migration mode−specific)

  RECOMMENDED: Create a DB backup to be able to provide the before-after databases to the Support team and rollback to the previous version, if necessary.

• Save execution report (enabled by default)

  • Cayosoft Administrator produces a migration execution report containing the output messages. Review the report upon the completion.

• Open execution report on completion

  • Open the execution report in the browser of your choice on completion.

Migrating a deprecated rule

Depending on the scenario, you might be able to migrate the existing deprecated rule. Refer to the following steps to learn more about the migration process:

1. Highlight a rule and click Migrate.

2. In the Migrate Rules pop-up, select the rules you'd like to migrate and click Next.

   NOTE: If a rule is missing from the list, verify that the Show folder drop-down list specifies the correct folder.

3. Select the migration mode and proceed with the migration.

   • Select the What If analysis mode to run an execution report before the migration. The report includes details on the migration process and rule settings to be migrated. No rules are created, updated, or deleted.

   • Select the Migration mode to migrate the rules. Refer to the following section for additional information.

4. Click Finish to complete the migration process. Depending on the selected settings, you should get a corresponding output. Review the execution report for additional details.

Migration

The Migration mode migrates the deprecated rules. Review the steps Cayosoft Administrator performs during the migration:

IMPORTANT: Before you replace and delete the deprecated rules in your production environment, it is strongly recommended to review the new replacement rules on a limited scope of objects.

1. When you click Finish, Cayosoft Administrator creates a substitution rule and marks the source rule migrated.

2. Cayosoft Administrator migrates supported settings and reports unsupported or obsolete settings in the execution report.

3. The substitution rule is scheduled, if the source rule was previously scheduled. The schedule for the source rule is disabled.

4. The substitution rule replaces the source rule in runbooks, web actions, and other linked rules.

5. Cayosoft Administrator creates a report with migrated rules, listing affected runbooks, web actions and linked rules. The report lists unsupported or obsolete settings. If previously set up, the following actions are performed:

   • Cayosoft Administrator adds a prefix to the source rule name.

   • Cayosoft Administrator creates a configuration database backup before migration.

   • Cayosoft Administrator opens the execution report on completion.

Review the execution report to verify the migration status.

Lists of obsolete rules

Refer to the following sections to learn more about obsolete rules.

Obsolete rules EOL 2025-04-01

1. Office 365 Users | License Plan Change Cost Modeling (Plan & Options)

2. Office 365 Users Billing Count by AD Group Membership

3. AD Users | DirSync User Mapping

4. Office 365 Users | Create AD Users (On-Premises)

5. Office 365 Users | Delete Unlicensed Users

6. Office 365 Group Membership by User (Distribution, Security)

7. Office 365 Users in Recycle Bin

8. Office 365 Disabled Users | Send to Recycle Bin

9. Office 365 Recycle Bin | Remove Users (Permanent Deletion)

10. Office 365 Domains

11. AD Groups | Enforce App Role Assignments

12. Office 365 Users Alternative Contact Info Not Set

13. Office 365 Users | Update Organizational Attributes

14. AD Users Expired Office 365 Linked User Status

15. Text file | Dynamic Attributes™ Update Office 365 Users Properties

16. Hybrid Office 365 User with Mismatched UserPrincipalNames

17. AD Users Hybrid Inactive

18. Office 365 | Revoke Deleted User's assigned licenses

Obsolete rules EOL 2024-07-30:

• OneDrive for Business Users

Obsolete rules EOL 2022-11-01:

1. AD Users with Office 365 Licenses

2. Skype Properties

3. Office 365 Users | Enforce Skype Settings by AD Group Membership

4. Office 365 Users Billing Count by AD Group (Roll-up)

5. Skype Users (Online)

6. Skype for Business Users

7. Skype for Business Users | Set external access policy

8. Office 365 Users | Set Skype Online Policies

Obsolete rules EOL 2022-09-19:

• Office 365 Users | Skype post creation tasks

• New User | Office 365 Skype post creation tasks

Obsolete rules EOL 2022-08-26:

1. Office 365 Users Last Logon

2. Office 365 Users Last Logon with Custom Attribute

3. Office 365 | Enforce Clutter Settings

Obsolete rules EOL 2022-07-01:

• Office 365 Users | Enable Lync

• AD Computers (No filtering)

• AD Groups (No Filtering)

• Schema AD Computer Properties

• Schema AD Group Properties

• Schema AD Organizational Unit Properties

• Schema AD User Object Properties

• Schema Exchange Mailbox Database Object Properties

• Schema Exchange Mailbox Object Properties

• Schema Exchange Server Object Properties

• Schema Office 365 Domain Properties

• Schema Office 365 Group (Distribution) Properties

• Schema Office 365 Groups (Security) Properties

• Schema Office 365 Mailbox Properties

• Schema Office 365 User Properties

Rules with migration paths

The following sections provide additional information on rules with migration paths. The sections follow the deprecated rule > migrated rule structure, unless stated otherwise.

EOL 2025-04-01

• Office 365 Domains > Microsoft 365 Domains

EOL 2023-04-30

Reporting rules that should be migrated to Microsoft 365 Users rule:

1. Office 365 Users

2. Office 365 Users (No filtering)

3. Office 365 Users Custom Attributes

4. Office 365 Users Organizational & Contact Details

5. Office 365 Users Recently Created

6. Office 365 Users Usage Location Not Set

7. Office 365 Guests

Rules that should be replaced with the Microsoft 365 Groups rule:

1. Office 365 Groups

2. Office 365 Groups (Distribution, Security, and Mail-Enabled-Security)

3. Microsoft 365 Groups with Membership Empty or Below Threshold

4. Office 365 Groups (Distribution) Members Count

5. Office 365 Groups (Distribution) Members

6. Office 365 Groups (Distribution)

Rules that should be replaced with Microsoft 365 Groups and Members rule:

1. Office 365 Group Members (Distribution, Security)

2.  

3.  

List of obsolete web actions

EOL 2025-04-01

• Office 365 Global Admins Multi-Factor Authentication (Legacy MFA) Status

• Office 365 Global Admins | Enforce Multi-Factor Authentication (Legacy MFA)

• Office 365 Users Multi-Factor Authentication (Legacy MFA) Status

• Office 365 Users | Enforce Multi-Factor Authentication (Legacy MFA)

• MFA Settings (Active Directory)

• MFA Settings (Microsoft 365)