Azure DevOps Licensing: Users Retaining Visual Studio Entitlements Despite License Removal — Investigation Needed

Problem description

I am experiencing an issue with Azure DevOps Services where, after removing Visual Studio Professional licenses for some users, a subset of them still appears to have a direct Visual Studio entitlement in Azure DevOps, despite no longer having the license or Visual Studio installed. I am seeking guidance on why this discrepancy persists and how to resolve it.

Environment

Azure DevOps Services, organization affected all projects, region not specified

What I've already tried

I confirmed removal of Visual Studio licenses in manage.visualstudio.com for affected users. Most users' access transitioned to group-based Basic after group rule reapplication or a delay of 1-2 days. For some users, the Visual Studio entitlement still appears as 'Direct' in Azure DevOps, leading me to manually assign Basic as a workaround. I have reviewed relevant Microsoft documentation and verified no active Visual Studio subscriptions or duplicate user entries. I have also removed those users from organization in devops but when they logged in to devops they got again Visual Studio Subscription licence...

Current status

I am seeking assistance to understand why some users still show Visual Studio 'Direct' entitlement and how to fully remove this entitlement to ensure licensing aligns solely with group-based rules.