TABLE OF CONTENTS
- Readiness Tier
- How Readiness Is Calculated
- Using Readiness Tiers in Reports
- Readiness Panel
- What-If Analysis
- Readiness – Canonical Rules
- Readiness – Frequently Asked Questions
- Why does a User show as Not Ready?
- Why does my total count not match the number of linked items?
- Does a Completed Process always mean Ready?
- Why is an Application missing from the readiness calculation?
- How is the Ready Percent calculated?
- If a User is Ready, does that mean all linked items are Ready?
- Can readiness be overridden without changing Process status?
- Do What-If changes affect live data?
- What-If – Canonical Behaviour
- Common Support Scenarios
Readiness Tier
The Readiness Tier determines whether a module item (Apps, Users, Devices, Mailboxes, or Bespoke items) is considered Ready or Not Ready within a report.
Readiness can be evaluated in two ways:
- Direct Readiness – based on the item’s own Process status
- Indirect Readiness – based on the readiness of linked items
For example, a User’s readiness can be calculated directly from the User’s Process, or indirectly from the readiness of the Applications linked to that User.
How Readiness Is Calculated
Readiness is calculated from the status of the Process that a module item is currently in. Every Process must have a status.
- If the Process status is Ready, the item is treated as Ready in all readiness calculations.
- If the Process status is Out of Scope, the item is completely excluded from readiness calculations.
For example, an Application in the Completed Process typically has a status of Ready. Any User linked to that Application will count it as Ready.
If a User has 10 linked Applications and 3 of them are in an Out of Scope Process, the readiness calculation will only consider the remaining 7 Applications.
Using Readiness Tiers in Reports
You can add one or more Readiness Tiers to a Datamining Report. Multiple Readiness Tiers can be combined, and Readiness Tiers can be used alongside Reporting Tiers in the same report.
Direct Readiness
Direct Readiness measures whether the primary item in the report is Ready.
Add a Readiness Tier that matches the Primary Tier of the Datamining Report. For example, in a User Migration report, add a User Migration Readiness Tier.
The report will indicate whether each User is Ready based on whether the User is in a Process with a status of Ready.
Readiness by Module
Readiness by Module calculates readiness based on linked module items. This is the most commonly used readiness configuration.
For example, in a User Datamining Report, add an Application Readiness Tier to calculate User readiness based on linked Applications.
The report will display:
- Total number of linked items
- Number of Ready items
- Readiness percentage
- An overall Ready flag for each primary item
Readiness by Multiple Modules
You can calculate readiness across multiple module types in a single report.
For example, to evaluate a User’s readiness based on both Applications and Devices, add both the Application Readiness Tier and the Device Readiness Tier. Each tier is calculated independently.
Readiness by Individual Module Item
To see readiness at the individual linked-item level (for example, each Application per User), add both:
- The relevant Reporting Tier
- The corresponding Readiness Tier
This expands the report to show one linked item per row, including its individual readiness status.
Readiness Panel
Options
- Include Pending Apps
Includes Applications in the Pending queue in readiness calculations. - Exclude Core Apps
Excludes Applications flagged as Core Apps from readiness calculations. - Include Dependencies
Includes dependent linked items when determining readiness. - Include Archived or Deleted
Includes Applications that are archived or in the delete queue.
Fields
- Overall Readiness
True or False indicator showing whether the item meets readiness criteria. - Total
Total number of linked items included in the calculation. - Ready Count
Number of linked items with a Ready status. - Remaining Count
Number of linked items that are not Ready. - Ready Percent
Percentage of linked items that are Ready. - Out of Scope Count
Number of linked items excluded due to an Out of Scope status.
What-If Analysis
What-If Analysis allows you to simulate readiness changes without modifying actual Process statuses. This is useful for impact analysis and planning.
For example, if a specific Application is blocking many Users from becoming Ready, you can temporarily treat that Application as Ready and see how overall User readiness changes.
What-If – Id-Based Overrides
- What-If Ready Ids
Treats the specified item IDs as Ready for calculation purposes. - What-If Out of Scope Ids
Excludes the specified item IDs from readiness calculations.
What-If Link Tag Overrides
- Must Include Link Tags
Only linked items with these tags are included. - Must Exclude Link Tags
Linked items with these tags are excluded.
What-If Process Readiness
By default, readiness is derived from the status of an item’s Process. This panel allows you to override Process statuses for calculation purposes only.
Processes can be temporarily treated as Ready, Not Ready, or Out of Scope without changing the actual Process configuration.
Readiness – Canonical Rules
The following rules define how Readiness behaves in all reports. These rules are authoritative and apply regardless of report configuration unless explicitly overridden by What-If settings.
- Readiness is always derived from the Process status, not from the Process name.
- An item in a Process with status Ready is considered Ready.
- An item in a Process with status Out of Scope is excluded entirely from readiness calculations.
- Items excluded as Out of Scope do not count toward totals, percentages, or remaining counts.
- Readiness percentages are calculated only from items included in scope.
- When multiple Readiness Tiers are used, each tier is calculated independently.
Readiness – Frequently Asked Questions
Why does a User show as Not Ready?
A User is Not Ready when one or more linked items included in the readiness calculation are not in a Process with a status of Ready.
Why does my total count not match the number of linked items?
Items that are in an Out of Scope Process are excluded from the readiness calculation and are not included in the total count.
Does a Completed Process always mean Ready?
No. Readiness depends on the status of the Process, not its name. A Process named “Completed” is only considered Ready if its status is set to Ready.
Why is an Application missing from the readiness calculation?
An Application may be excluded if:
- It is in an Out of Scope Process
- It is archived or deleted and the relevant option is disabled
- It is flagged as a Core App and Core Apps are excluded
- It does not meet required Link Tag filters
How is the Ready Percent calculated?
The Ready Percent is calculated as:
Ready Count ÷ Total Included Count × 100
Out of Scope items are not included in either value.
If a User is Ready, does that mean all linked items are Ready?
Yes. A User is only considered Ready if all linked items included in the calculation are Ready.
Can readiness be overridden without changing Process status?
Yes. What-If Analysis allows readiness to be overridden for calculation purposes without modifying actual Process statuses.
Do What-If changes affect live data?
No. What-If settings only affect the current report calculation and do not persist or modify underlying data.
What-If – Canonical Behaviour
- What-If Ready Ids force specified items to be treated as Ready.
- What-If Out of Scope Ids exclude specified items from calculations.
- Link Tag filters apply before readiness is calculated.
- Process Readiness overrides affect calculation only and do not change Process configuration.
Common Support Scenarios
Scenario: A single Application is blocking many Users
Use What-If Ready Ids to temporarily treat the Application as Ready and review the impact on User readiness.
Scenario: System-generated Applications should not affect readiness
Use Must Exclude Link Tags to exclude Applications created by specific connectors (for example, Intune).
Scenario: Readiness percentages seem lower than expected
Check for:
- Applications not yet in a Ready Process
- Excluded Core Apps settings
- Pending or archived items being included
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article