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]

Hello @Sriram Pusuluri,

That empty Reconciliation Rules list on Network Adapter is exactly why the status flips. Reconciliation rules are what give a discovery source authority over a specific attribute (operational_status included). With zero rules defined for that CI class, there's no protection in place: any source, including a scheduled job, an import, or a stale record replay from cmdb_multisource_data, can freely write to operational_status regardless of which source actually ran most recently. The Most Recent Discovery timestamp only reflects that the Intune discovery source touched the CI, it does not mean Intune's payload is the one that "wins" that field.

Add a reconciliation rule for the Network Adapter class scoping the Intune discovery data source as authoritative for operational_status, and check the Data Refresh Rules section too since it's also empty, that governs when a lower-priority source is even allowed to touch a field once your Intune rule marks it stale.

Thank you,
Vikram Karety
Octigo Solutions INC