Operation Status 'Retired' even when Most Recent discovery is today in Intune Integration

[Sriram Pusuluri]

Hi Team,

In Intune Integration Operation Status 'Retired' even when Most Recent discovery is today. Operational Status is not changing in Intune Integration

But in AD integration Operation Status is Updating.

Can anyone help me how to check this or update this?

[Vikram Reddy]

Hi @Sriram Pusuluri,

This is almost always a Reconciliation Rule blocking the operational_status field for the Intune data source, not a timing or scheduling issue. Discovery touching the CI today just updates last_discovered, it does not automatically mean every field gets overwritten. Before changing anything, check:

• Under CI Class Manager, the Reconciliation Rules for operational_status on the Computer/Intune-mapped class, look for a filter condition such as operational_status is not Retired scoped to the Intune source
• The discovery_source value on the affected CI records, to confirm Intune is actually the winning source with the right precedence
• IRE debug logging (cmdb.ire.debug=true) while an Intune payload runs, to see exactly which rule is skipping the field

AD likely updates fine either because its reconciliation path has no such Retired-guard filter, or a higher precedence for that field.

Thank you,
Vikram Karety
Octigo Solutions INC

[Sriram Pusuluri]

Hi @Vikram Reddy 

I am not able to find the Reconciliation Rules in CI Class Manager, 

Is this right place to search

[Vikram Reddy]

Hey @Sriram Pusuluri,

Your screenshot is the CI Class Manager landing screen and you haven't drilled into an actual class yet, that's exactly why nothing shows: the tool defaults to that "Welcome to CI Class Manager" page until you open a class, and reconciliation rules only render once a class is in context. So yes, CI Class Manager is the right place, you're just one click short.

1. Click Open Hierarchy (or just click a class name in the left tree, e.g. Computer or whatever class your Intune CIs land in).
2. With a class selected, the right panel switches from the welcome screen to that class's detail view, which has tabs across the top: Identification Rule, Reconciliation Rules, CI Relationships, and CMDB Health.
3. Click the Reconciliation Rules tab to see the list of discovery sources, attributes, and priorities configured for that class.
4. If you'd rather skip the tree entirely, go to Configuration > Identification/Reconciliation > Reconciliation Definitions in the application navigator. That module lists reconciliation rules across all classes and lets you filter by table, no need to drill through the hierarchy at all.

One thing worth flagging before you spend time here: reconciliation rules only decide which discovery source "wins" when two sources try to write different values to the same attribute, based on priority. They do not govern the install_status (Operational Status) field on their own, and there's no out-of-box rule that flips a CI out of Retired just because a fresh discovery record came in. Operational Status on Intune-sourced CIs is normally set either by the connector's transform/normalization logic or by a retirement definition under CMDB Data Manager > Retirement Definitions (filtered to your Intune data source), and that's a completely separate config surface from CI Class Manager.

So checking Reconciliation Rules for the class is a fine sanity check, but if the actual complaint is CIs stuck at Retired despite recent discovery, I'd point you at the Retirement Definition tied to the Intune source first, since that's what's actually deciding the status value, not the reconciliation priority.

Is the class in question a custom Intune device class, or is it landing on the stock Computer/Mobile Device class? That changes whether you're looking at an out-of-box retirement definition or one your team added.

Thank you,
Vikram Karety
Octigo Solutions INC

[Sriram Pusuluri]

@Vikram Reddy 

Intune class is Network Adapter

when I click on Reconciliation Rules it is showing as empty