Yes, it’s possible if the AD source is configured to bring in the whenChanged or similar timestamp attribute tied to the account being disabled. You can map this attribute in the account schema and pull it during aggregation. Then, store it as an account attribute or use it in a transform to expose it to the identity. You can compare this timestamp with the lifecycle state change date (if tracked via identity attribute or identity history). A rule or report can help automate this comparison for auditing or workflow triggers.