Hi @dikshabhart,
Whilst the temptation would be to 'fix' (update) the data directly in ServiceNow, my recommendation would be to re-push / trigger the update from the source system where the data is mastered - in your case AD.
The reason being there could be more data inconsistencies than you've noticed and it may (probably) will highlight the issue in the integration or where the break/outage is - this is vital to ensure this gap is plugged for future sync's.
If the data fix is urgent and is causing critical blockers, you do have the option to fix directly in ServiceNow, but I would implement this as a temporary fix and look to the bigger picture and ensure this is logged and tracked.
To help others (and for me to gain recognition for my efforts), please mark this response correct by clicking on Accept as Solution and/or Kudos.
Thanks, Robbie
