Hi @Antima Pandey,
Thank you for posting your question on Microsoft Q&A Community. We're happy to help you with your concern.
This kind of issue can be tricky, especially after a long absence. To help scope it down and identify the root cause, could you please clarify the following:
1/ Are the problematic files stored in OneDrive, SharePoint, or within a Teams channel?
Are the files shared directly with the user or via a group/team membership?
2/ Could you share the exact error message the user receives?
Does it happen consistently across the same files or intermittently?
3/ Was the user’s account recreated or reactivated after the 2-year absence?
Is the user part of the same Azure AD group or Teams membership as before?
4/ Were the files shared via direct link, Teams post, or email?
Do the affected files show the user listed under Manage Access with the correct role (e.g., Viewer, Editor)?
5/ You mentioned the issue occurs with files shared by a few specific users, are those users still active, and do they have any conditional access policies or external sharing restrictions applied?
6/ Has the user tried accessing the files via Teams desktop app, web browser, or mobile app? Any difference in behavior?
Once we have more clarity on these points, we can better determine whether it’s a permissions sync issue, a legacy sharing link problem, or something related to identity or group membership
Looking forward to your response.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.