Mike, you're right, and the post didn't cover it. It said the count is only as current as the export, and that the approver may have left the tenant by the time the destroy runs. It said nothing about an account that is disabled but still in the export with its groups. The policy reads no account state, so the policy and the count still treat that user as a holder, and so would a recheck that re-evaluates the same policy. The recheck is a design in the post, not code in the series. The post now says this in two places: under "Approvals go stale" and under "What this check is not". The approval's expiry limits how long a leaver's approval stays usable, but only to whatever the issuer set; nothing caps that lifetime. The count has no time bound at all. Both of your options work, and they trade differently. Dropping disabled users at the export needs no policy change, but it holds only as long as the export keeps doing it, and nothing fails if it stops. An active attribute on User puts the rule in the policy, where it can be tested, at the cost of a schema change. On the diff: if the export drops disabled users, a reactivated account shows as one holder becoming two, which the diff flags today. If it keeps them, the diff sees nothing.