1 Answer
- Newest
- Most votes
- Most comments
0
It was a user that was not populating correctly from AD, deleted user and added, all was then correct and the charge stopped happening
answered 4 years ago
Relevant content
- asked a day ago
- asked a year ago
- asked 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 4 months ago