MicrosoftMicrosoftNino_Bilic starting with "6bbc462b" it is third party add-in which we have already updated to the M365 centrally deployed tab, and vendor provided the updated xml.
However, I still see in both the areas 'Allowed and Blocked' I have tested my add-in just now and it is working as expected.
Could you please advise why it is showing at both the side and if I need to do anything from my end.
MicrosoftThe add-in will not be removed from "Allowed". Your "Allowed" shows that the last time this add-in requested and received a legacy token was 2/6 (February 6) so that is basically an "old entry" for your case. This add-in therefore is not actively using legacy tokens since February, even though it is still asking for legacy tokens (last time on 5/27). But if the add-in works, what likely is going on is that the add-in has a failback mechanism to request the legacy token, which then fails and then it uses NAA to auth so it keeps working even though it was "blocked" for legacy token issuance.
If your add-in works, you should not have to do anything.
Thanks Nino_Bilic I will keep monitoring however if it does not work then what I need to do , as vendor already provided the xml file and we already updated.
MicrosoftThe only way out is updating the add-ins. I want to make sure it is understood - per your screenshot, the add-in did not get legacy tokens since early February. I would think by now you'd know if the add-in was broken? Either way - if we are talking a 3rd party add-in, then they need to provide the update.
No, add-in is not broken I just checked today and will keep monitoring and contact vendor if we see any issue.
Thanks.
