Articles in this section

See more
Print

Deprecated Rules

  • Updated
Follow

Overview

Note: License assignment rules created in Cayosoft before 9.1.0 make use of the MSOnline PowerShell license assignment APIs. These APIs are being deprecated by Microsoft on August 26, 2022 (read details here and here), after which point these existing legacy rules will cease to function. As such, existing license enforcement rules are necessarily being deprecated as a result of Microsoft's decision. However, Cayosoft will provide new and improved license assignment rules in version 9.1.0, based on the new Graph API, and a migration path for all existing license assignment rules. 

Cayosoft Administrator 9.1.0 adds new rule migration and deprecation toolsets aimed to address the challenges of dealing with rapid change in the Microsoft cloud. When you open Administrator Console you will now see the Deprecated Rules link in the Urgent notification section on the Home page.

Deprecated rules are the rules that Cayosoft plans to retire in for one of the reasons below:

  1. Microsoft API breaking changes make an automated upgrade from a legacy rule to a newer version impossible
  2. Functionality is no longer provided or does not makes sense due to Microsoft changes.
  3. A rule was completely redesigned and an automated upgrade is not feasible.
  4. A rule is no longer used.

All deprecated rules will be disabled and 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: 

  1. Obsolete rules: these rules will no longer be supported after the given EOL time and will simply stop working as supported rules.
  2. Rules with migration path: these deprecated rules will be provided with migration functionality to newer versions of rules that include most or all of the deprecated rule functionality. After migration, both the legacy and the new rule exist simultaneously and the deprecated rule has to be removed manually.  Please see below for a full description of the migration functionality 

 Obsolete rules EOL 2022-08-26:

  1. Office 365 Users Last Logon
  2. Office 365 Users Last Logon with Custom Attribute
  3. Enforce Clutter Settings

Rules with migration paths:

Important: As mentioned at the begging of this article, existing license assignment rules created before the 9.1.0 release make use of APIs that Microsoft is retiring on August 26, 2022. These rules must be migrated to their corresponding new versions before this time or the functionality will stop working.  Deprecated rules can be deleted after migration.

Here is the list of rule pairs: old MSOL rule > Graph rule on which the old rule should be migrated:

EOL 2022-11-01

  1. AD Users | Enforce License > AD Users | Enforce License rule (New)
  2. AD Groups | Enforce License > AD Groups | Enforce License rule (New)
  3. Office 365 Groups | Enforce Licenses > Microsoft 365 Groups | Enforce Licenses rule (New)
  4. Office 365 Users | Enforce License > Microsoft 365 Users | Enforce License rule (New)
  6. Office 365 Users | Change selected license option by AD Group > Microsoft 365 Groups | Enforce Licenses rule (New)
  7. Office 365 Users | License Plan Change Cost Modeling & Enforcement > Microsoft 365 Users | Enforce License rule (New)
  8. Office 365 Users | Revoke Disabled Users Licenses > Microsoft 365 Users | Enforce License rule (New)
  9. Remote Linked Mailboxes | Enforce License > Remote Linked Mailboxes | Enforce License rule (New)

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 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

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

  1. Office 365 Group Members (Distribution, Security)
  2. Microsoft Teams Members
  3. Microsoft 365 Groups and Teams With No Owners or Members

 

The Deprecated Rules node has been introduced in the Administrator Console, where you can review and migrate such rules to a newer version. Before migration, you can perform What If analysis to get a report that will have the information about how the selected rule will be migrated.

 

Deprecated rules node in Administrator Console

The Deprecated Rules is a list of rules that are supported until the time that is specified next to each rule, after which they will become obsolete. Obsolete rules are not supported and cannot be run on schedule. 

If the rule can be migrated you will see the red banner on it with the information that the rule is deprecated and will become obsolete and unsupported after the specified date and with the Migrate Rule button.

If the rule cannot be migrated you will see just the red banner with the information that the rule is deprecated and will become obsolete and unsupported after the specified date. However, you can manually configure the new corresponding rule to achieve the same functionality.

How to migrate the rule:

  1. Select the rule in the Deprecated Rules list or select it in the Administrator Console tree and click Migrate Rule.
  2. Click Next.
  3. Select the mode: What if analysis or Migration.
  4. Click Finish.

What if analysis

No new rules will be created, no current rules will be updated or deleted. You will get the execution report with details on how the selected rules will be migrated, and what rules' settings can be and cannot be migrated.

 

Migration

These steps will be accomplished in migration mode:

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. Create substitution rules and mark the source rules as migrated.
  2. Migrate supported settings and report unsupported or obsolete settings.
  3. Enable the schedule on substitution rules if it was enabled on the source rules.
  4. Disable the schedule on the source rules.
  5. Replace links to the source rules in the runbooks, web actions, and other rules with the links to the replacement rules.
  6. Create a report with migrated rules, list runbooks web actions and rules where links were replaced, and list unsupported or obsolete settings.

Also, it is possible to do the following:

  1. Add prefixes to the source rule names.
  2. Create configuration database backup before migration.
  3. Open execution report on completion. 

 

 

 

 

Related articles

Comments

0 comments

Article is closed for comments.